Back Forward How to use the Rule Check-in approval process

This optional facility allows you to use a Process Commander flow rule to manage change to your application. Use this facility to coordinate the efforts of large development teams or to control changes to sensitive applications.

Set Up

To turn on controlled check-in for a RuleSet:

  1. Enable check-out features for the RuleSet, by selecting the Use Checkout? box on the Security tab of the RuleSet form.
  2. Enable check-out for each development team members, by selecting the Allowed to Check-out rules? box on the Security tab of the Operator ID form.
  3. On the RuleSet Name form, identify both key parts of a flow rule that is to control checking. Your system includes a standard work type Work-RuleCheckIn, standard properties and activities, and a standard flow ApproveRuleChanges for this feature. You can use the standard rules or copy and adapt them.
  4. Review (and override if desired) the standard decision tree rule named Work-RuleCheckIn.FindReviewers to identify the workbaskets used in this flow. Place the new decision tree rule in the RuleSet and version being developed.
  5. Include Work-RuleCheckIn among the Work Pools list, on the access group data instance associated with reviewers.
  6. Create a workbasket named ReviewChanges@org.com or others identified in the decision tree rule. Update the Operator ID data instances for each reviewer to allow them to access the workbaskets.
  7. Associate the standard access role PegaRULES:SysAdm4 (or another role with the privilege Rule-.UpdatePrivateRuleSets) with each Operator ID data instance who will approve check-ins.
  8. Update the standard RuleSet CheckInCandidates to identify an appropriate prerequisite RuleSet. Add this RuleSet (version 01-01-01) to the access group of those developers who are to approve check-ins.
  9. Finally, check the Approval Process box on the RuleSet Version form, for each version you want to enable.

Use

When this facility is in force for a RuleSet version, then as a developer begins rule check in, the flow starts.

zzz The flow creates a work object that is routed to a workbasket, waiting for an approver to review.

The approver may approve the check-in (which completes the check in), reject it (which deletes the changed rule), or send it back to the developer for further work.

Assignments corresponding to rules awaiting evaluation are held in the ReviewChanges@org.com workbasket.

Multiple rules can be associated with one work object. The flow rule notifies affected parties by e-mail about evaluation results.

Customization

You can enhance this process to meet local requirements in various ways. For example, certain empty (dummy) activities are called by this flow; your application can override these with desired processing. See Standard activities — Extension points.

Up Tools, accelerators, and wizards