Thank you for attending our recent webinar for robotics professionals on Wednesday, January 26 at 11 am ET.
Description: With Microsoft's official end-of-life date for Internet Explorer (IE) approaching in June 2022, it's essential robotics system architects (RSAs) migrate their existing IE web adapters into new Edge versions. This webinar provides an overview of best practices as well as a demo of new product features available from Pega to assist with this migration process.
So, what’s next?
Let’s keep the conversation going! If you have any additional questions for Becky and Stephen reply here to let them know.
We hope you understand we couldn’t get to every question during our Q&A session, but we’d like to provide answers to as many as we can.
Check them out below:
For adapters with multiple 50+ pages, is there a way to convert the IE adapter to the Edge adapter?
Unfortunately, no. This is a manual process that must be performed for your IE adapter; however, the Replace Usages functionality should help significantly.
If you enter an incorrect ID – for example, an object name or UniqueID that doesn’t exist – will you get a warning? Is it possible to have the prompt specify UniqueID as the required ID?
Yes. If you enter an invalid UniqueID or the type for the associated property, method, or event you entered doesn’t match the target for replacement, you will receive a detailed failure message.
Will this process work for Chrome as well?
Yes. The process works for any type of adapter or type of control.
Yes. You can still use the ExecuteScript method on pages in the Universal Web adapter.
The migration tool is useful when replacing individual controls across automations, but not for creating new Edge Web adaptors – is this correct?
That is correct. You must manually create new Edge Universal Web adapters.
What is the Pega Runtime/Studio version needed to use the conversion wizard?
What can be done for an HTML table designer since there is no option for it with the Universal Web adapter?
In the Universal Web adapter, you would interrogate the separate pieces of the table: Use the SelectElement interrogation mode and start by interrogating a single cell in your table as this will show your table hierarchy, then create containers out of the table and row elements within the table. Next, set the interrogated row to be a cloned control (Use Keys = TRUE).
Please look at the automation called FinanceFindCustomer in the attached sample solution (FinanceAfter) to see how the table was searched to find the correct customer link to click.
Is there any dependability about compatibility mode?
There are no dependencies on Pega’s part, but Compatibility Mode in Edge only works with IE 11.
Is there the possibility of running the existing standard web adapter in compatibility mode in Edge by toggling a switch?
There isn’t a switch that can be toggled and converts between IE and Edge, nor between Edge-compatibility mode or Edge-non-compatibility mode. Re-interrogation and migrating automations are required.
Thank you again for attending, and we hope to see you at our upcoming events.