Skip to main content

Registering rules in the regulatory stack

Suggest edit Updated on November 5, 2021

The regulatory stack is the registry of all the rulesets in your application that contain KYC types and all the rules that constitute the KYC types, or example, applicability conditions of the KYC type or the on-change data transforms.

The rulesets listed in this registry are monitored by the SPU engine for the addition or deletion of ruleset versions. When a change is detected, a policy update is triggered. Similarly, the addition or deletion of rulesets in the registry is treated as a policy change and thus is considered for a policy update.

  1. In the header of Dev Studio, search text field and enter PegaKYC-Data-RegulatoryStack.KYCRegulatoryRulesetsRegistry and select the dynamic system setting.
  2. Create an application-specific version of the data transform if you have not already created one.
  3. Register the new ruleset in the data transform.
  4. In the RegulatoryRulesets page list, add the pyRuleSetName property for each regulatory ruleset.
Result: A ruleset that is added to the regulatory stack should not be removed from the list or the application. Doing so adversely affects the policy-freezing capability of the SPU engine.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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