Pega platfrom

Versioning: We can create a new version of a rule whenever case behavior needs to change. Pega maintains a history of changes to a rule, allowing system architects to review the change history and undo changes if needed. Since each rule describes a specific case behavior, the rest of the case is unaffected. For example, a system architect updates a UI form with instructions and removes a critical field. You can review the history of the form and revert back to the version before the changes were made, without changing other rules in the application.

Delegation: We can delegate rules to business users to allow business users to update case behavior as business conditions change. The business user updates the delegated rule, while other parts of the application remain unchanged. For example, expense reports that total USD25 or less are approved automatically. You create a rule to test whether an expense report totals USD25 or less and delegate the rule to the Accounting department. The Accounting department can then update the rule to increase the threshold for automatic approval increases to USD50, without submitting a change request for the application.

Reuse: We can reuse rules whenever an application needs to incorporate existing case behavior. Otherwise, you must reconfigure the behavior every time the behavior is needed. For example, you create a UI form to collect policyholder information for auto insurance claims. You can then reuse this UI form for property insurance claims and marine insurance claims.