Question
Marsh & McLennan Agency LLC
IN
Last activity: 20 Sep 2018 11:33 EDT
Edge Browser Suppport
Guys,
Does PRPC 7.1.9 version supports Edge Browser ?
I have recently tried to hit our application url in edge and it redirects to IE 11 browser.
Thanks,
Prasanna
***Edited by Moderator: Pallavi to update platform capability tags***
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
FR
Hello,
No redirection to IE 11 for me. Working correctly with Pega 7.1.7 as well
Marsh & McLennan Agency LLC
IN
Hello,
Do we need to make any changes to Edge browser before we start using our application ?
-
Gabe Isko neeraj soni Ravi Kumar Pisupati Marc Cheong Armin Schmid and 1 More
Pegasystems Inc.
IN
Hi Prasanna,
Yes 7.1.9 works in Edge browser.
Thanks,
Tashika
Marsh & McLennan Agency LLC
IN
Tashika,
As per support guide 7.1.x versions only support IE 11 and not Edge browser but you have mentioned Edge browser is supported.
Pegasystems Inc.
IN
Hi,
Sorry for the misunderstanding.
7.1.9 works fine in Edge but not supported. In Pega 7.2.1 and later, both IE11 and the Edge browser are supported.
Thanks
Vodafone
IN
Hello,
The product has not been tested in Edge browser, as when Pega 7.1.9 release - Edge browser was not available. Pega platform support guide hasn't mentioned about Edge browser support.
Pega 7.1.9 will work on Edge browser but not officially mentioned in any documentation.
On release of Pega 7.2.1 Edge browser is available and officially noted in Pega platform guide.
Regards,
Naveen
Adaps
IN
Below link might help you
https://collaborate.pega.com/question/does-pega-v721-support-microsoft-edge-browser
Marsh & McLennan Agency LLC
IN
Thanks guys.
My issue is narrowed down, I have two node url's and a load balancer url. The redirection to IE 11 happens only when I use load balancer url and with node url's im able to login without any issues in Edge as well.
Anyone experienced this particular scenario.
Pegasystems Inc.
IN
Hi,
Then there must be some setting in load balancer that is causing the redirection. You can check with your respective team.
Thanks