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.

Testing and promotion of business user-authored rules

Updated on September 13, 2021

Summary

A developer asks:

Do you have recommendations for rule promotion and testing practices when a site wants to allow business users to update certain rules directly? 

Our application has multiple clients who will each manage some of "their own" rules.  They need to be able to test their own rules — though not with a full Dev/QA cycle — and to control when a rule becomes live. 

We are looking for thoughts on ways to manage rule promotion for such business user-authored rules.



 

Suggested Approach

Consider creating an "authoring production" environment, where business rules are modified, tested (against a non-production database), and then moved from there to the production system. 

Provide each of the business user clients with its own RuleSet and its own area of the class hierarchy.  

Use RuleSet versioning to control promotion and demotion of new client-authored rules, to and from production.

Tags

Pega Platform 7.1.1 - 8.3.1 System Architect System/Cloud Ops Administrator System Administration

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