Question
Merative
US
Last activity: 9 Jul 2024 2:36 EDT
Unable to access Rules/tracer in PEGARules application
I have created an operator to access PEGA OOTB application with PRPC:Administrators access group.
Once I log in, I am unable to access any of the rules/tracer. It says "refused to connect" error. Can you help me with it?
Tracer Error:
Pegasystems Inc.
IN
@SathishKumarJ17003558 - Can you share the error message seen in browser developer tools console tab?
Thank you.
Merative
US
Merative
US
@Priyanka BogaI am able to see all the rules except Section, Harness, Skin Preview and Tracer. Only these four are giving the error, "Refused to connect".
Lantiqx Systems India Private Limited
IN
Hi @SathishKumarJ17003558 Are you using PRPC personal edition ? if in that case once restart the server and check it.
Regards,
Prasad.
Merative
US
@Prasad Reddy Muddam No, this is our client DEV environment. Not personal edition.
Updated: 1 Jul 2024 5:51 EDT
Eclatprime Digital Private Limited
IN
- First, verify that the “PRPC : Administrators” access group exists and is correctly configured.
- Ensure that your operator ID is associated with this access group.
- As a workaround, try logging in using the
[email protected]operator ID. - Create a new access group with the same name (or a different name like “Revenue:AdministratorNew”).
- In the access group settings, select your application and version, and set the default portal to “Developer.”
- Review the operator record for your user ID.
- Confirm that the access group assigned to your operator is valid.
- Make sure the specified access group exists
Merative
US
@MahavishnuN04 All that is working fine. I am able to access all other rules except for Section, Harness, Skin rule preview and tracer. When I try to access these four rules, I am getting this error.
Merative
US
@SathishKumarJ17003558This issue is resolved now. We had setup the DSS http response headers with X-Frame-Options: Deny. also, we had a CSP in our application that would restrict the frame ancestors. Our application should have the same CSP with this DSS setup. If we remove this option from DSS, then the CSP has to be removed. That's the only way, application would load all the UI rules.