Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Extending Request access

Updated on January 18, 2021

The Request access case type can be extended to any other cases by completing the following steps.

  1. For read access restrictions:

    1. Configure the Access Role to Object for the case that needs to be restricted based on the work party roles.

      Refer to PegaGP:ICMAgent and PegaPS-Work-ICM-Investigation-Initiate.

    2. Create the access when rules for the read instance.

      Refer to HasReadAccess that was created for investigation case, which is used to check if the user is the owner of the case or is an interested party for the case.

  2. For write edit access restrictions:

    1. Configure the Access control policy and Access control policy condition for the case to which edit access needs to be restricted based on the work party roles.

      Refer to the UpdateInvestigation Access control policy and the IsOperatorAllowedToEdit Access Control Policy Condition.

    2. If required, update the Access When rule HasUpdateAccess, which is used to check if any of the following conditions are satisfied to allow the operator to modify the case:

      • Is the operator an owner of the case?
      • Does the operator have edit access to the case?
      • Is the operator a supervisor?
      • Is this a new case?
  3. For extending custom access, such as for a new Reports investigation component, for example, Reports:

    1. Save as the following rule in the implementation layer:

      • For desktop configurations: CaseAdditionalDetails (PegaPS-Work-ICM-Investigation-Initiate)
      • For mobile configurations: CaseFile (PegaPS-Work-ICM-Investigation)
    2. Add the Reports component to the following sections:

      • For desktop configurations: in the CaseAdditionalDetails section after creating a different layout, such as Notes
      • For mobile configurations: in the CaseFile section directly in column layout
    3. Save as the CustomAccess (Data-Party) section in the implementation layer. Add the respective check box for the new component that you added by using the CustomAccess page group property with the index set to the component name, which in this example is Reports.

    4. Create a when rule that is similar to ShowNotes, for example, ShowReports, with the same logic that you used for the when condition, replacing Notes with the index name that you used for the check box in step 3c.

    5. Add the visibility when condition ShowReports to the added Reports component in CaseAdditionalDetails and CaseFile in the Notes component to show Reports only when access is provided.

    6. Add another section, NoAccessMessageForSections (PegaPS-Work), along with Reports in CaseAdditionalDetails in the implementation layer, passing the name of the component as a parameter. Use the same when condition that you used with ShowReports with the negation !ShowReports.

    7. For mobile view, after adding a new component in CaseFile (implementation layer), add another section, NoAccessMessageForMobile (PegaPS-Work), passing the name of the section and the header of the section as parameters.

    8. Add the same when conditions that you used in CaseAdditionalDetails to the sections that you added in the case file.

  • Previous topic Request access case workflow
  • Next topic Setting up an email listener for request access in an implementation layer

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us