SA-23099

Summary

Users application has been upgraded from PRPC 5.5 SP1 to Pega 7.1.6. Developer Portal is not loading. It is saying Compatibility view not supported.

Error Messages

Compatibility view not supported.

Steps to Reproduce

1. Access the Developer URL.
2. Enter the user name and password.

Root Cause

The root cause of the reported behavior is user application which is rendering in compatibility mode.

Resolution

Here’s the explanation for the reported behavior: 

The user earlier was using PRPC 5.5 version so user has enabled compatibility view outside of PRPC to support their 5.5 app. This can be done through various means such as locally on the browser, pushed out through group policy, and so on.In other words, they have environmentally added this setting, independent of Pega.

Now that user is on Pega 7, is hosted on the same domain, hence Pega 7 app is breaking, as it is intended to run in HTML 5 standards.

User has already added this local-change “<meta http-equiv="X-UA-Compatible" content="IE=edge">” in pyMetaTags to support the compatibility for the application.

Note: Pega will not be supporting designer studio while running in compatibility view. Pega has and will continue to be very strict regarding developers and the browser requirements. But it is more flexible when discussing end user portals for business users.

Recommended approach is to set each and every harness to be rendered in HTML5 standards mode. You can make use of HTML5 Application Readiness<https://pdn.pega.com/sites/pdn.pega.com/files/help_v719/procomhelpmain.htm#basics/v6portal/landingpages/userinterface/html5applicationreadiness.htm>

The below two links will help you know more about the HTML5 document type option necessity in application after upgrading. Read through the below links:

1) https://pdn.pega.com/user-interface/upgrading-an-application-to-render-in-html5-document-type
2) https://pdn.pega.com/user-interface/what-you-need-to-know-about-upgrading-your-application-to-html5-document-type-standards-mode

Make sure that Pega 7 renders in standards mode which would resolve the reported behavior.

Read through the below article which might be of help:
https://pdn.pega.com/support-articles/fixed-modal-size-issue-w-compatibility-and-standards-mode.