We are planning to migrate to Microsoft Edge browser by next year. Already more than 75% automation that we have are all running on chrome browser. I would like to enquire on the remediation efforts it will take to move our automations from chrome/IE to Edge completely.
For IE, it will be huge impact since we need to change the adapter first Web adapter to Universal Web adapter and all controls will be freshly interrogated.
However for chrome adapters, how it will work out since Pega has provided edge browser option within universal web adapter itself alongside chrome and firefox (means do we still need to interrogate all the controls agains?)
@AdityaS02 To switch from Chrome to Edge, you should not need to re-interrogate. You can simply change the property in the UWA to indicate it should use Edge (assuming your application is not running in Compatibility mode).
Posted: 1 month ago
Updated: 1 month ago
Posted: 4 Oct 2021 10:48 EDT Updated: 4 Oct 2021 10:50 EDT
@AdityaS02 Assuming your application operates the same in Edge and Chrome, there are no changes to controls required to switch between them. Simply change the adapter property and it will launch in Edge instead of Chrome.
If your application is switching from IE to Edge or Chrome (and not using compatibility mode to run it in IE under Edge), then you will need to re-interrogate all of the controls as if it is a new application.
@ArunkumarBojan If you are interrogating an application from scratch in compatibility-mode, there are no specific settings. Just set the Universal Web Adapter to use Edge and interrogate normally. If you have an existing adapter in IE and want to move it to Edge in compatibility-mode, then you may contact our support team and they can assist you with that migration. You will need to tweak some of the automation steps likely, but not many.