Request for Alternative solution: Issues with Web Adapter Session Creation and URL Access in PEGA browser Extension
At click of StartMyDay, we need to load five applications, but runtime is falling to identify and create sessions for the Web adapter. Additionally, the auto-populated filed is not being populated in a particular application. This issue is occurring on a dedicated machine nothing but replica of production devices use by users to run this RDA application, which is significantly faster compared to our development and testing machines.
I would like to inform you that we are not going to click the “Allow Access to URL” checkbox in the PEGA browser extension. Due to this, sometimes messaging host taking long time to load.
Please guide us on whether it is necessary to check the “Allow Access to URL” checkbox in the PEGA browser extension or if there is any alternative solutions without selecting the checkbox.
Accepted Solution
Updated: 23 Sep 2024 7:27 EDT
Pegasystems Inc.
US
@RajivB503 Here are some relevant links to assist. Make sure you have followed the directions for allowing the extension via group policy. We don't mention anywhere needing to allow access to a URL for the extension that I could find anyway. I suspect the group policy isn't in-place. It may also be that your browser is blocking the extension. If the extension is enabled and allowed, then when you launch it the first time after a restart, you should see a new process launched called "Pega.Web.MessagingHost.exe" if you look on the "Details" tab of Task Manager. That is typically how I test to see that it is installed and configured before I test anything with the automations.
Installation - https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/installation/install-pbe.html
Edge Group Policy - https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/supported-technologies/edge-group-policies.html
@RajivB503 Here are some relevant links to assist. Make sure you have followed the directions for allowing the extension via group policy. We don't mention anywhere needing to allow access to a URL for the extension that I could find anyway. I suspect the group policy isn't in-place. It may also be that your browser is blocking the extension. If the extension is enabled and allowed, then when you launch it the first time after a restart, you should see a new process launched called "Pega.Web.MessagingHost.exe" if you look on the "Details" tab of Task Manager. That is typically how I test to see that it is installed and configured before I test anything with the automations.
Installation - https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/installation/install-pbe.html
Edge Group Policy - https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/supported-technologies/edge-group-policies.html
Chrome Group Policy - https://docs.pega.com/bundle/robotic-automation-221/page/robotic-automation/supported-technologies/chrome-group-policies.html