Following the Microsoft announcement of the IE11 end of support starting in 2021, you might want to migrate your automation processed from IE to Chrome, Edge or Firefox.
Below are a few important aspects to help you plan and implement the migration.
The UiPath automation for Chrome, Edge or Firefox uses browser extensions. These are offered as part of Studio and SetupExceptions tool, so please consider their installation on the test/production environments. The documentation provides instructions on how to install them based on your scenarios. Here are few helpful links:
If the source process has selectors starting with “<wnd …,” tag, you need to regenerate those via Studio->activity->indicate function. These selectors identify windows like pop-ups or alerts, which are rendered differently by IE vs Chrome/Edge/Firefox.
Selector identifying an IE alert window:
<wnd app='iexplore.exe' cls='#32770' title='Message from webpage' />
Thanks for this. Just want to comment - not all of the selectors will be converted by changing the app. If selectors are refined at lower levels the conversion is not as clean. My organization is already on a roadmap to convert all automations from IE to Chrome. Also, quick note, Edge is a little less consistent. We found Chrome to be more reliable.
To anyone having selectors issues when using EDGE with IE Mode, you have to manually tweak the selectors. UiPath detects the browser as IE so it doesn’t add “<html app=‘msedge.exe’” to the selector’s path so they are immediately invalid. Add it manually then they work.
Thank You very much, this was very helpful. Just 2 questions, Once the dependencies are updated, can it be back rev to older version if needed. And is UIAutomation.Activities the only depedencies to be updated, and not Excel, Mail, and System activities.