Question
The Bank of Nova Scotia
CA
Last activity: 19 Apr 2022 7:30 EDT
Best practice to identify UWA has been closed manually/accidentally
In continuation to The Universal Web Adapter is remains in started status even if we close the browser if we have multiple Universal Web Adapter. | Collaboration Center (pega.com)
- Above thread concluded with the assumption that if any of the pages we've interrogated are not matching then adapter must have been stopped manually.
However pages not matching can be because of other reasons too.
1. Like @ThomasSasnett pointed out, its only for pages that have been interrogated. If we run into a new page we will try to restart the adapter
2. Matches may not be matching because something has changed on the application.
Restarting wont help in either of the 2 scenarios above. Is there any best practice to handle this currently on UWAs?
Pegasystems Inc.
US
@SreejaP3444To recap;
- IsRunning will tell you if the adapter itself has been started.
- The UWA is essentially MonitorAll once started, so it will match in any Chrome (or Edge) window open on the machine.
- If I want to determine if a user has closed the application, I check the IsCreated property for all of my interrogated pages.
- One trick you can do to match any page within an application is to interrogate a "Generic" page that has a really simple URL match rule that would match any page within the application. This page must be interrogated last however. If you ever need to interrogate another page, you must delete this one and then re-interrogate it last. This allows all of the other pages to get matched first (since they have more specific match rules) and when all of those fail to find a target, the generic one will attach to anything.
- If you have configured the AcceptedDomains and BroserStopMethod properties of the adapter, and the user has simply navigated away from the application or you're on an entirely unknown page, then restarting the adapter shouldn't cause any issues.
- You might also use the Process.Start method (this is a Static method you can add to your Toolbox from the "System" assembly) to launch a new instance of Chrome (or Edge) and as long as your adapter IsRunning is true, then your pages would match in this new window or tab.
Does this make sense?
The Bank of Nova Scotia
CA
@ThomasSasnett thanks for your reply. Yes it makes sense.
Yes restarting shouldnt be any issue if we were on a entirely new page, but we didnt want to restart unless it was absolutely necessary (like if browser is closed) as it might mean we would have to repeat all previous steps for that transaction.
We will have to use the IsCreated property of all pages or the generic page. Will try that out. Thank you