Final rules overridden
+
This content applies to On-premises, Client-managed cloud and Pega Cloud environments
After a rule is marked as final, no one can create a second rule with the same visible key in any ruleset other than the ruleset that the first rule belongs to. If the ruleset version of a final rule is locked, you cannot create a second rule with the same visible key in any version of any ruleset, except a higher version of the ruleset containing the final rule. By locking critical rules, the rule is easier to update in the future. Unlocked rule extension points are provided for features that clients typically modify.
An extension point is an activity or other rule that is designed and intended to be overridden to meet application needs. Many such rules are empty stubs that contain no steps. Typically, the overriding rule is in a derived class.
For more information, see:
How to identify
The rows in the output report from the Pega Cloud Readiness Tool are:
Area: Final Conflicts
Rule Type: Rule-
How to modernize
To modernize an application with overwritten final rules, revert all custom changes back to OOTB final Pega rules, or withdraw customized final rules. Leverage available extensions points to implement custom changes.
Pega finalized some rules in Customer Service and Sales Automation version 8.5, and documented how to address rules that override these final rules. This can also serve as a general example of modernization for overwritten final rules.
For more information, see: Rules finalized in version 8.5 to prevent overrides
Previous topic Dynamic System Settings (DSS) Next topic Authentication Profiles