The issue here is I want to automate the windows application .exe but while giving start interrogation, it is redirected into a web application to enter the user credentials. So, I am using Universal web application to interrogate the username and password and few more details by creating separate web adapter. I have attached the screenshot on how the automation is built now the match rule is not matching with the web adapter for web application. The URL and title name for web application is also correctly given where I am using contains in the elements to match correctly.
@Sanjanaa20 You will probably need to have your Universal Web Application setup with a “StartMethod” of “MonitorAll” and have it start on project start. You would then start the Windows application. You may need to adjust the StartMethod here too, depending on if the application actually starts or only launches from the web application. I cannot tell what match rules you are using from your screenshot, but I don’t suspect you have those incorrect. It is more likely an issue with the adapter not being connected to the application. I would use a tool like Process Explorer (you can also use Task Manager, but the processes aren’t grouped in the views it provides, so it is much harder) to understand how your Windows application actually launches the Chrome or Edge part.
One thing to try to is to make sure that interrogation works before Runtime. This means that you setup your adapters the same way they will be at Runtime. Clicking the “Start Interrogation” button is the same as the StartMethod on the adapter. For the Universal Web Adapter (since it is MonitorAll) you would click it before the Windows application. Once it is started, you’d then click “Start Interrogation” on the Windows adapter and watch how it is connected.
@ThomasSasnett Thank you for the clarification. “Monitor all” works and the match rule is fixed.