A common use case for iFrame widgets is to embed custom functionality from bespoke or internal systems, to provide functionality that is not available through Interact directly. This can range from something like a restaurant menu, to data dashboards, timesheets and scheduling. With the iFrame widget the possibilities are endless.
An iFrame widget is just like any widget in Interact. Your homepage administrator can add it to a homepage by editing the relevant zone and selecting the iFrame widget from the list of available widgets. The configuration options allow you to specify an optional title and the URL of the page to host in the iframe.
The diagram below gives one example of how a site can be built and used in an iFrame to allow things like Single Sign On through a shared SSO provider. Given that Interact is merely hosting another web site inside the homepage, the possibilities really are endless.
Look and Feel
One important aspect to consider when using iFrames is to try and make the contents of the iFrame look and feel like your intranet. This can be done by including your intranet CSS in the iFramed site and use the same classes that are used within Interact. This will ensure that colour themes, fonts and general styles can be used in the iFramed site.
In order to achieve this you simply need to determine the path to the relevant CSS. The easiest way to get the CSS file is by viewing the source of the page and looking for the file intact.css
This file (including your domain name) can then be referenced from the website you are building and the same classes used by Interact for your theme can be included in your website
This file path is tied to your theme, so if the theme changes then the path to the CSS file will need to be updated in your website
There are a number of requirements for the website that you want to host inside an iFrame inside Interact or any other website
The hosted site needs to use HTTPS - Interact is securely served via the HTTPS protocol following best practise. Modern browsers will therefore require any sites hosted in an iframe to also be served over HTTPS.
The hosted site (including any intermediate SSO sites) need to allow itself to be served in an iFrame. Some sites may block the ability to be served in an iFrame - this of course is not a problem if it's a website your organisation has built and managed
Updated about 2 months ago