The embedded content element makes it easy to embed documents, images, video, or other web content into your dashboard. Two configuration options are available. When you configure the element to be static, all you need is the URL of the content to be embedded. When you configure it by features, the element is data driven and you need to identify a data source. This means that each feature's attribute information can be used to dynamically construct a URL at run time. When configured by features, the embedded element can be the target of an action. Specifically, it can be the target of elements that support a selection change event.
- Some websites restrict embedding. This is a choice that some organizations make to protect their content from misuse by third-party users. If this is the case, you can link to the content using HTML.
The following tips are useful for using URLs in the embedded content element:
- URL references should use HTTPS. If an HTTPS connection is not possible, consider using a relative URL, which doesn't specify HTTPS or HTTP. For example, use //www.example.com/content.html.
- If the URL references a domain that differs from your organization, the server hosting the requested resources should support CORS requests from your organization.
If you're having trouble embedding content and are familiar with your browser's development tools, you can troubleshoot by monitoring the network traffic. You may see error messages for mixed content or embed restrictions. In the latter case, look for a property named X-Frame-Options in the response header.