Skip to main content


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

Updating from Pega Platform version 7.3, 7.3.1, or 7.4: granting access to the Requester Management landing page

Updated on February 9, 2022

To access the Requester Management landing page in your application, add privileges to the @baseclass and Pega-Landing access classes in your access roles.

Note: This section applies only to updates from the following releases.
  • Pega 7.3
  • Pega 7.3.1
  • Pega 7.4

If you are updating from another version, skip this section.

If you added these privileges prior to the update, skip this section.

  1. Click the Operator menu in the Dev Studio header and select Operator.

  2. In the Application Access section, expand an access group and click the role that you need to modify.

  3. Click the @baseclass class in the Access Class column.

  4. In the Privileges section, click the Plus icon and, in the Name column, add the following privileges for the type of access required.

    • pzSystemOperationsObserver – Required to access the Requester Management landing page and to view performance and trace entry details.
    • pzSystemOperationsAdministrator – Required to access the Requester Management landing page and perform most actions on requestors. To trace requestors and view the clipboard you also need to have the pzDebugRemoteRequestor privilege.
  5. Enter 5 for the production level in the Level column.

    Production level 5 provides the highest security.
  6. Click Submit.

  7. In the Access Class column, click the Pega-Landing class and repeat steps 4 through 6.

    Note: If the Pega-Landing class is not in the table, add it by clicking the Plus icon at the end of the table and entering Pega-Landing in the Class field.
  8. Save the access role form.

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.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us