Customization of the Rule check-in approval process

The rule check-in feature allows you to use a process to manage changes to the application. Use this feature to ensure that checked-in rules are meeting the quality standards by ensuring a senior member of the team reviews them.

Pega Platform™ comes with the Work-RuleCheckIn default work type for the approval process. The work type contains standard properties and activities and a flow called ApproveRuleChanges that is designed to control the rule check-in process.

For instructions on how to enable rule check-in approval, see the help topic Configuring the rule check-in approval process.

When the default check-in approval process is in force for a ruleset version, the flow starts when a developer begins rule check-in. The flow creates a work item that is routed to a workbasket. The standard decision tree is named Work-RuleCheckIn.FindReviewers returns the workbaskets. Rules awaiting approval are moved to the CheckInCandidates ruleset.

By default, the review work items are assigned to a workbasket with the same name as the candidate ruleset defined in the Work-RuleCheckIn.pyDefault data transform. Override the Work-RuleCheckIn.FindReviewers decision tree if you want to route to a different workbasket or route to different workbaskets based on certain criteria.

The approver can provide a comment and take three actions:

• Approve the check-in to complete the check-in process and resolve the rule check-in work item.
• Reject the check-in to delete the changed rule and resolve the rule check-in item.
• Send it back to the developer to route the work item to the developer and move the rule to the developer's private ruleset.

Affected parties are notified by email about the evaluation results.

You can enhance the default rule check-in approval process to meet your organization's requirements.