Mentioning accepted domain, web page is not getting identified @ chrome.
Also robotics is not able to identify separately the chrome session opened through robotics and the one opened separately. if same webpage is opened, its matching both the web pages.
2 Interrogate few fields in the webpage
3. Close the interrogation
4. Add accepted domain add the accepted domain and start interrogation.
5. Check if the controls are matching
Pegasystems Inc.
US
"We initially noticed stopping one chrome adapter is closing all the open chrome adapters."
This is correct. The Universal Chrome Adapter (UWA) will close all Chrome windows/tabs that it is actively monitoring.
"When we added the domain, the controls are no longer matching which matches fine when accepted domain is left blank"
I have reviewed this product area and I had issues with the 'Simple' and 'EndsWith' Modes. Do you see this same behavior when using 'Contains' or 'StartsWith'? When using AcceptedDomains, the UWA will only close the tabs that are in the accepted domains list. (the developer later responded that Contains works!)
"Also robotics is not able to identify separately the chrome session opened through robotics and the one opened separately. if same webpage is opened, its matching both the web pages."
"We initially noticed stopping one chrome adapter is closing all the open chrome adapters."
This is correct. The Universal Chrome Adapter (UWA) will close all Chrome windows/tabs that it is actively monitoring.
"When we added the domain, the controls are no longer matching which matches fine when accepted domain is left blank"
I have reviewed this product area and I had issues with the 'Simple' and 'EndsWith' Modes. Do you see this same behavior when using 'Contains' or 'StartsWith'? When using AcceptedDomains, the UWA will only close the tabs that are in the accepted domains list. (the developer later responded that Contains works!)
"Also robotics is not able to identify separately the chrome session opened through robotics and the one opened separately. if same webpage is opened, its matching both the web pages."
This is expected behavior. You'll notice it is the same with all adapters; if you have two of the same applications hooked, both controls from the applications will try to match. If you predict this scenario happening, you will need to account for this scenario in your automation logic.