Skip to main content

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

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Why some standard rules are marked as Final

Updated on September 13, 2021


A developer asks: Why are some standard rules marked Final while others are not?

For example, the rules that define work object history displays have availability set to Final. I would like to customize this display. 


A small number of standard rules have availability set to Final to prevent customizations that hamper or make it impossible for Pegasystems to make product changes in later releases of Process Commander.

A final rule — a rule that cannot be overridden in a different RuleSet — can present obstacles to implementation of your intended approach. As a general response around the perceived obstacle of a final rule, explore those parameters that are available to you for customization. In some cases, you can copy the rule with a different name and cause your rule to run rather than the final rule.

Such cloning can address your specific question regarding work object history. Save the final history HTML rule to a custom name, then change the history icon (on the work object forms) to execute your HTML rule rather than the final, standard rule.

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