How to implement business exception processing with policy overrides

Through OnChange rules and special flow rules, your application can create application-wide temporary pauses in flow processing — for example, to detect and review exceptions, suspect data or special cases — without altering the flow rules. This provides an alternative to use of tickets.

For a background on the benefits and purposes of this capability, see Understanding policy overrides and suspended work objects.

Configuration overview

This facility requires three components:

• A property or properties present in a work object that can signify a business exception.
• An OnChange rule that responds to a business exception by promptly suspending all assignments on all currently executing flows for the work object.
• An flow that supports independent review of the work object, allowing the reviewer to record a final verdict.
• A reviewer — an operator holding the Work-.ReviewPolicyOverrides privilege — who assesses the business exception and records, in the work object history, a verdict allowing normal flow processing to resume or end.

1. Define the business exception as a when condition rule

1. Identify the property or properties that are involved in the test.
2. Create a when condition rule that is true only when the property or properties assume an unlikely, suspect, or potentially erroneous values. Choose a condition that is rare; that for most work objects is false at all times from initial entry through resolution.

2. Create a policy override review flow

1. Create a flow rule to support review of work objects that become suspended when the business exception occurred. On the New dialog box, select PolicyOverride in the Template field. Design the flow to meet these criteria:

• Applies to the class of the suspended work object (or a parent class).
• Does not create a new work object.
• Calls as the last task the standard flow Work-.FinishPolicyOverride.

This flow may be simple  — containing only the Start, End Flow, and Call Subflow shapes — or it may require multiple tasks performed by multiple operators. Use the standard flow Work-.PolicyOverride as a starting point.

2. In the SubProcess Properties panel, complete four flow parameters for the Work-.FinishPolicyOverride flow, to control the e-mail correspondence it produces. You can send correspondence when the review results in a Deny verdict, and when it results in an Allow verdict.

3. Create an OnChange rule

The OnChange rule detects the business exception and starts the review flow.

1. Select the work type of the work objects as the Applies To class.
2. Complete the OnChange Properties tab. In the When field, reference the when condition rule created in step 1 above.
3. In the Choose Action field, select Suspend Work Object.
4. Identify the review flow in the Policy Override flow to run field.
5. Enter text such as "Too many payees" or the key to a message rule in the Error Message field, characterizing the reason for the suspension.

4. Adjust the routing

By default, the Work-.FinishPolicyOverride flow creates an assignment on the worklist of the operator administrator@org.com, where org.com is the organization owning the work object.

1. Override the routing activity Work-.ToPolicyOverrideOperator to route this assignment to a person (or one of a group) who is appropriate to act as a reviewer.

2. Ensure that the Operator ID of this person acquires the privilege Work-.ReviewPolicyOverrides. The standard role PegaRULES:SysAdm4 conveys this privilege, but you can create other roles appropriate to your application and organization.

5. Test application-wide exception processing

1. Open a flow rule in your application.
2. On the Diagram tab, click  Show Policy Override   .
3. Shapes mark each connector flow action that may update the properties listed in an OnChange rule marked Suspend Work Objects in the Choose Action field, directly or through forward chaining. For local flow actions — not visible on the flow diagram — the shape appears above the assignment.
4. Click a shape to identify the flow action and the OnChange rule or rules involved. These details appear in a pop-up window.
5. Through case-by-case testing, you can verify that the OnChange rules are executed when a user, through selection and operation of the flow action rule, updates the listed properties — through direct input, through computations, or through forward-chaining.

6. Ensure that reviewers complete their tasks

Each person who acts as a reviewer must review and act on assignments which have the status Pending-PolicyOverride. To verdict, they can choose Allow or Deny as the flow action.

If they choose Allow, processing resumes and any suspended assignments reappear in worklists or workbaskets. If they choose Deny, the work object status changes to Resolved-Revoked. Affected users may be notified by e-mail, if configured in the flow. In the unusual case that two or more reviews are underway for one suspended work object, the status changes occur only after all the reviews are complete.

7. Periodically monitor outstanding flow problems

Suspended work objects remain suspended until all open reviews are completed.

To see a report of suspended work objects, select View > System > Suspended Work > In Current Work Pool.

To see a list of assignments in suspense, select View > System >Suspended Work > Assignments.

Notes

• This capability illustrates how procedural rules — such as the flows — can operate with declarative rules — such as the OnChange rules — to directly support business processing. Pegasystems identifies this distinctive combination as the Pro-Dex capability.
• The  Show Policy Override   button appears at runtime only on flow rules created or updated in V4.2SP6 or later, and for users who have the @baseclass.FlowViewProDex privilege. This button does not appear on any flow actions for which the Auto- generated HTML box on the HTML tab is not selected.

	flow action, local flow action, policy override capability, ticket
	About OnChange rules Flow rules — Interacting with the Diagram tab

Process category