Skip to main content

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

Identifying the custom controls to configure

Updated on July 1, 2021

Pega Platform protects access to information in your application by using role-based settings and access control policies. Pega Platform provides additional request verification when you use autogenerated controls. When your application supports access checking and includes non-autogenerated controls, you need to identify and fix the controls.

Perform one or more of the following steps to identify the rules to be configured:

  1. Scan the security alert log for the message "Unregistered request encountered," and then configure the rule that is identified in the message.
  2. Review the attached list of Pega Platform rules that have been configured in the Pega rulesets. If your application overrides any of these rules, configure the custom rules.
  3. Use the attached branch ruleset to find sections and navigation rules that invoke the Run Script action. To use the branch ruleset, complete the following steps.
    1. In Dev Studio, import the attached archive file. The archive defines rules in the FindRunScript branch.
    2. Add the FindRunScript branch to your application definition, and save the application.
    3. Run the activity pzPopulateRulesWithActions, and check the box to exclude Pega internal rulesets. This activity outputs a spreadsheet named RuleList_RunScript.xlsx, which contains a list of rules that you need to examine and configure.

For information on how to configure the rules, see Verifying requests when using custom controls.

  • Previous topic Verifying requests when using custom controls
  • Next topic Configuring a custom control by using the rule 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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us