Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Content Freeze

As of July 25th, 2023, there is a content freeze on this page.

Internet Explorer Compatibility View

Recent versions of Microsoft Internet Explorer include a feature called Compatibility View which allows Internet Explorer's rendering to emulate older versions, in order to maintain compatibility with older websites. With default settings, IE will use Compatibility View for any pages that it deems to be in the Intranet Zone, although this can be adjusted by the user. Compatibility View will emulate Internet Explorer 7, unless the web page instructs it otherwise by sending an HTTP header (X-UA-Compatible). 

To avoid reduced functionality caused by this, Atrium requests the latest available IE mode (known as Edge mode) using an X-UA-Compatible header. 

Adjusting Atrium's X-UA-Compatible Header

It is recommended to use the default Edge mode, but there are some cases where you might need to adjust this for compatibility with 3rd party applications running inside Atrium. Atrium uses HTML <iframe> containers to present web applications in tabs. Internet Explorer will take the parent page's X-UA-Compatible header and apply the setting to all pages running in <iframes> on the page. This means that Atrium's mode will be used, regardless of the mode setting within individual applications. 

A data area PUIIEMODE in the Profound UI installation library controls Atrium's X-UA-Compatible header. The data area can be set in two ways: 

  • A specific Internet Explorer version number, such as '9', '10', '11', etc.
  • 'edge', to request the latest available Internet Explorer rendering mode. 

For example: 

Specific Version
CHGDTAARA DTAARA(PROFOUNDUI/PUIIEMODE *ALL) VALUE('9')
Latest Available
CHGDTAARA DTAARA(PROFOUNDUI/PUIIEMODE *ALL) VALUE('edge')
  • No labels