Pend Rules
Pend rules can pend a policy for manual review. When a policy is pended, the user needs to manually decide to accept the pend reasons, that is, to resolve them after modifying or without modifying the policy. The pend rule describes the circumstances in which a policy pends. The pend reason describes why the policy has pended. Each pend rule must specify a pend reason that will be attached to the policy should that rule trigger.
Pend rule configuration consists of three different types of fields: to identify the rule, to describe the circumstances under which a policy pends and to drive what happens when the policy actually pends.
Field | Description |
---|---|
Code |
The identifying code of the pend rule |
Description |
The description of the pend rule |
Source |
The source of the policy: Integration Point, User Interface or Either |
Message |
If specified, one of the messages on the policy should match the message |
Message Group |
If specified, one of the messages on the policy should match one of the messages in the group |
Brand |
If specified, this brand should match the brand of the policy |
Condition |
The dynamic logic condition that is executed to determine if the policy must be pended |
Pend Reason |
The pend reason that is attached to the policy (see below) |
Process flow |
The process flow to which this pend rule is restricted |
Enabled? |
Is the pend rule enabled? |
The use of a policy pend rule can be restricted to a single policy process flow. If the rule’s process flow has no value, the pend rule can be used in any process flow.
Pend Reasons
As specified above, each pend rule must specify a pend reason that will be attached to the policy (describing why the policy has pended) should that rule trigger.
Field | Description |
---|---|
Code |
The identifying code of the pend reason |
Description |
The description of the pend reason |
Reattach? |
Should the pend reason be reattached? (if unchecked, this reason will not be reattached, that is, will not cause the policy to pend if the policy pend history shows that the same pend reason has been resolved in the past) |
Ind Publish Message |
If checked, the pend reason and the object it is attached to are included in the workflow task start message. |
Priority |
Numeric priority of the pend reason. The priority is sent in the workflow task start message. Thus, they can be used to differentiate between tasks of different priorities by putting them in different workflow queues. |
External Code |
External code which is sent in the workflow task start message. |
Policy Fields |
Dynamic function produces a list of name value pairs that are included in the workflow message. |
After all the rules have been evaluated, a start task message may have to be sent. If at least one pend reason with the publish message indicator checked, is attached, then such a message is sent out (for more details, see the chapter on Workflow Integration Point in the Developer Guide). This message will include information about the pend reasons and the priority that has been configured.