System generated Access templates do not work correctly
The system generated Access templates are updated to remove the Create permission for the primary and child territories and only the Read permission is provided. However, when an operator is loaded and assigned the default access, the operator has the access to Create Contacts.
On debugging and tracing, the canCreateContact property is always set to True in the system Template instance and hence, is set on the operator as well. A When rule is present to display or hide the Create Contact button which views the canCreateContact property value on the Declare_crmOperatorAccess page.
Steps to Reproduce
- Create an application on Pega Sales Automation for Financial Services (SAFS) 8.3.
- Update the system Access template to have only the Read access for contacts for the primary and child territories.
- Set up an operator and assign the default access.
- Log in with the operator to determine if the operator can create a contact.
A defect in Pegasystems’ code or rules.
When an operator is loaded through the Data Loader to the system, the Permission settings are inaccurate. If the operator does not have the Permission to Create Contacts in the Access template, the operator can still create contacts after the import. The Permission settings within the SA UI works correctly.
However, the issue occurred because the Data Loader works differently when the UI is implemented. While the UI uses only the respective record in the appropriate line of the Access template, the Data Loader uses the top level property.
Published April 1, 2020 - Updated December 2, 2021
Was this useful?
0% found this useful
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.