Hi Prasad,

Yes there are ways to mitigate this, but you will find much more reliable success if you engage your IT department to consider using Enterprise mode instead. This will net you the ability to granularly set which specific sites/apps run in Quirks (your older apps), and which will be left alone (your Pega 7 app will run natively in Standards). This works even if they are on the same domain, which is what fails when using the older compatibility view option.

I have raised the SR-A89752 for the same, as per this the resolution provided by PEGA, to introduce harness rules which override the default behavior and force Pega to be displayed in Edge mode. This can be found in the advanced tab of the harness rules, under IE Document Mode.  But this change will work after we done with the PRPC authentication, which mean once we get into our application stack rules. When we make our application harness to set as advised. But please advise how to make the changes for unauthenticated users to proceed PRPC login.  I mean the initial PRPC login screen itself PEGA is not allowing if we enabled compatibility mode in IE. So what are the changes we need to make for initial login screen.

I have raised the SR-A89752 for the same, as per this the resolution provided by PEGA, to introduce harness rules which override the default behavior and force Pega to be displayed in Edge mode. This can be found in the advanced tab of the harness rules, under IE Document Mode.  But this change will work after we done with the PRPC authentication, which mean once we get into our application stack rules. When we make our application harness to set as advised. But please advise how to make the changes for unauthenticated users to proceed PRPC login.  I mean the initial PRPC login screen itself PEGA is not allowing if we enabled compatibility mode in IE. So what are the changes we need to make for initial login screen.