Action Types

To instruct the task service on how to route the task, rules can specify one of many task actions. This is done by updating the TaskAction fact asserted into the rule session. However, rules should not directly update the TaskAction fact. Instead, rules should call one of the action RL functions, passing the TaskAction fact as a parameter. These functions handle the actual updates to the fact. For example, to specify an action of go forward, you must add a call GO_FORWARD(TaskAction) to the action part of the rule.

Each time a state machine routing rule is evaluated, the rule takes one of the actions shown in Table 29-13:

Table 29-13 Business Rule Actions

Action	Description	Parameters
`GO_FORWARD`	Goes to the next participant in the routing slip (default behavior).	None
`PUSHBACK`	Goes back to the previous participant in the routing slip (the participant before the one that just set the task outcome). Note: Pushback is designed to work with single approvers and not with group votes. Pushback from a stage with group vote (or parallel) scenario to another stage is not allowed. Similarly, you cannot push back from a single assignee to a group vote (or parallel) scenario.	None
`GOTO`	Goes to a specific participant in the routing slip.	`participant`' A string that identifies the label of the participant (for example, `Approver1`) to which to route the task.
`COMPLETE`	Finishes routing and completes the task. The task is marked as completed, and no further routing is required.	None
`ESCALATE`	Escalates and reassigns the task according to the task escalation policy (usually to the manager of the current assignee).	None