PRPC 7.2 in Compatibity mode IE11
Though PRPC 7.2 portal does not need compatibility view setting: Display Intranet sites to be checked in.
But how shall we configure: section,harness and all the UI parts so that they open even when Display Intranet sites is marked checked in compatibility view setting of IE
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accepted Solution
Pegasystems Inc.
US
Yes. I still would strongly encourage every IT department to reconsider their approach because it is outdated and effectively deprecated. At any rate, if you are in this situation, this is the only solution Pega can offer at this time. Since you are past 7.1.9, that is why you are getting hit with this check at the very login screen itself. It is warning you that you are going down a bad path. But if you must, this is your solution.
Pegasystems Inc.
IN
Hello Ipsita,
Thanks for posting your query in PSC :)
On a new browser session, on setting 'Display intranet sites', on hitting the Pega 7 application, it gives below message:
Pega 7 uses the latest web technology and your internet browser must run in standards mode. Please disable compatibility mode under the menu Tools -> Compatibility View Settings.
I see similar requirement as per this post wherein the suggestion is to modify the document mode for the harness. Alternatively, try using different browser.
Regards,
Rincy
Pegasystems Inc.
US
Hi Ipsita,
You can try including the meta tag - "<meta http-equiv="x-ua-compatible" content="IE=edge" >" as the first element in rule "pyMetaTags", this would override the other settings and cause portal to be rendered in standards mode.
Sai.
Citi
IN
Hi Sai,
<meta http-equiv="x-ua-compatible" content="IE=edge" >
<pega:when test='pyIsMobile'>
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="apple-touch-fullscreen" content="yes">
<meta name="format-detection" content="telephone=no">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="mobile-web-app-capable" content="yes">
<meta name="apple-mobile-web-app-status-bar-style" content="black">
</pega:when>This is how my py<etaTags looks now,but its still not working in Compatibility mode
Pegasystems Inc.
US
Please please please consider and advocate to your business/IT to consider Enterprise mode in IE11. It was introduced to specifically address catch 22 scenarios where your IT needs to support legacy applications along with modern applications in parallel.
This way you set Enterprise mode for your legacy app, and then leave IE11 alone, unmodified and untampered with for your modern [HTML5] apps such as Pega 7.
If this is off the table, only then, I would consider local changes from Pega's side. Using this hierarchy of approaches will net you less headache and an overall better user experience.
Updated: 29 Nov 2017 12:04 EST
NJ Courts
US
Hello Rett,
We are in same boat and would like to clarify few things. Below is our issue:
Our application was in 7.1.7 and worked fine after we made changes to pymetatag to include <meta http-equiv="X-UA-Compatible" content="IE=11,IE=10,IE=9,IE=8,IE=edge,chrome=1"> . Our end users access pega applications in IE11 and even though compatability view is enforced at domain level, Pega portal launched absolutely fine.
Recently we upgraded our lower environments to 7.2.2 and we are being forced to disable compatible mode with error message," To access the Pega 7 Platform, disable compatibility mode by accessing the Compatibility View settings." Since compatibility is being forced at domain policy level, we are not able to control the same at browser. So is there way to get around the same ?
Thanks in advance,
Chaits
Accepted Solution
Pegasystems Inc.
US
Yes. I still would strongly encourage every IT department to reconsider their approach because it is outdated and effectively deprecated. At any rate, if you are in this situation, this is the only solution Pega can offer at this time. Since you are past 7.1.9, that is why you are getting hit with this check at the very login screen itself. It is warning you that you are going down a bad path. But if you must, this is your solution.