Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Asset Information Management

Embedding Sites within Sites

  • Last UpdatedMar 10, 2025
  • 2 minute read

Embed an External Site within the AIM Dashboard

It is possible to embed an external site within the Dashboard using the InfoLocator attribute of items. When the item is viewed, the external site is rendered in an HTML <iframe> element. However, this functionality is blocked by default.

In order to permit external sites to be embedded in the Dashboard the hostnames of the sites must be added to a configuration property called SafeDomains, which is a list of permitted hostnames.

For example, to embed the site https://example.com/path/page.html, the value example.com must be added to the SafeDomains list.

The embedded site must permit being embedded in an HTML <iframe> element. If a site restricts embedding through Content-Security-Policy or X-Frame-Options headers then it must in turn permit the Dashboard to embed it through the respective HTTP header.

To add or remove values from SafeDomains your CONNECT account administrator must create a ticket with AVEVA Support requesting one or more hostnames to be added to the SafeDomains list. When requesting changes specify:

  • the external site hostname

  • the full URL of the Dashboard instance to which it must be applied.

Changes to this configuration may be made during the regular maintenance window, or applied during an exceptional maintenance window to be agreed.

Embed the AIM Dashboard within an External Site

It is possible to embed the Dashboard within an external site, in an HTML <iframe> element. However, this functionality is blocked by default.

To allow the Dashboard to be embedded in an external site the origin of the external site must be added to a configuration property called AllowOrigins. An origin is the scheme, hostname, and port of the embedding site.

For example, to embed the Dashboard within the site https://example.com/path.page.html, the value https://example.com must be added to the AllowOrigins list .

To add or remove values from AllowOrigins your CONNECT account administrator must create a ticket with AVEVA Support requesting one or more origins to be added to the AllowOrigins list. When requesting changes specify:

  • the origins to be added

  • the full URL of the Dashboard instance to which it must be applied.

Changes to this configuration may be made during the regular maintenance window, or applied during an exceptional maintenance window to be agreed.

In This Topic
TitleResults for “How to create a CRG?”Also Available in