Skip to main content


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

Configuring a custom control by using the rule form

Updated on July 1, 2021

When you see the message "Unregistered request encountered" in the security alert log, you need to fix the behavior of the non-autogenerated control that invokes the specified rule.

There are various ways to prevent this alert from being logged:

Use the rule form when a control such as a button calls the Run Script action, which in turn calls a custom function. This rule form configures registration of the custom rules that are invoked from the custom function.

For example, a button calls the Run Script action, which calls the setStockPrice function. This function runs the data transform setStockPriceDT. In the rule form, you register setStockPriceDT.

  1. Registering the action and preventing the security alert

    When you see the message "Unregistered request encountered" in the security alert log, you need to fix the behavior of the non-autogenerated control that invokes the specified rule. One way to prevent this alert from being logged is to register the action.

  2. Submitting the action request content in encrypted form

    An alternate to registering the data transform is to encrypt the submitted action request content. The developer can write code in a non-auto section or html fragment and include it in the harness

  • Previous topic Identifying the custom controls to configure
  • Next topic Registering the action and preventing the security alert

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