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.
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.
Posted: 3 years ago
Updated: 3 years ago
Posted: 29 Nov 2017 12:05 EST Updated: 29 Nov 2017 12:04 EST
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,
Posted: 3 years ago
Posted: 18 Dec 2017 13:39 EST
Rett Hean (Rett_Hean_GCS)
Principal Software Solutions Engineer
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.