Question
Fifth third
US
Last activity: 11 Jan 2022 9:55 EST
Web controls mismatch in Universal Web adapter
I have used EdgeToIEModeConverter utility to convert from web adapter to Unviersal web adapter. Post conversion the web controls that are matched in Edge doesn't match in Chrome.
I don't believe it is due to the converter but unable to find out reason for the mismatch.
Any suggestions?
Pegasystems Inc.
US
@ArunkumarBojan Is your page running in Compatibility-mode for Edge? The utility that you mentioned is for converting an IE-based web adapter to a UWA in Edge running with the page in Compatibility-mode. If it is not in compatibility-mode, you will need to re-interrogate the controls. We do have a new wizard to help with replacing the new controls in builds starting with 19.1.95.
https://help.roboticautomation.pega.com/191/#t=automations%2Freplacing_controls_in_automations.htm
Fifth third
US
@ThomasSasnett Yes the application was running on IE Compatibility mode on Edge.
I will take a look at the link to learn about the wizard. Thanks for your suggestion.
Pegasystems Inc.
US
@ArunkumarBojan If it is running in compatibility-mode, then that link is not relevant. I would suggest interrogating one of the controls as a new control and comparing how it is matched versus your existing one. Perhaps the page has rendered itself differently (I don't believe this to be the case, but I have seen pages that render differently depending on the browser).
Fifth third
US
@ThomasSasnett If I create web controls by interrogating an application in Edge(not on IE Compatibility mode) the same cannot be used in Chrome. It had to be re-interrogated in Chrome. But the new controls can be replaced in the solution using the new replace wizard.
Is this a right understanding.
Pegasystems Inc.
US
@ArunkumarBojan If you are not using IE compatibility-mode, then Edge and Chrome are functionally the same. If you interrogate controls using Edge, you can then switch the "BrowserType" property of your adapter to "Chrome" and your controls should still match the same.
The new feature that I mentioned, is to help with switching from an application that previously ran in Internet Explorer and will now be running natively in Chrome (or Edge without compatibility-mode). As you are re-interrogating all of the required controls in Chrome (or Edge without compatibility-mode), then you can use the feature to help you replace the usage of the current controls with the new ones.