Approval task

An Approval task is very similar to a User Action task. The difference is how the action item completes. The actions to complete the action item are always approve and reject. The Approval task understands acceptance and rejection, which it translates into success and failure.

For action items created by an Approval task to work properly, the target of the Approval task must include the approval state transitions. If it does not, records associated with the action items will not have accept or reject actions. It will be impossible to complete the action item.

The Approval shape is in the task palette only if the workflow is asynchronous. This aspect of a workflow is specified by its Concurrence property which is described in "Start task".

The form for an Approval task is very similar to the form for a User Action task (described in "User action task"). It differs from the User Action task form in only these ways:

The heading says Approval Task Properties instead of User Task Properties.
There is no Lock Record for Other Users check box. It is not needed because Approval tasks always lock the record to be approved.
There is no Action field. It is not needed because the actions that complete an Approval task are always Approve and Reject.

In all other ways, the properties form for an Approval task is the same as for a User Action task and the same descriptions apply.

You may notice that in the IBM® TRIRIGA® applications an approval engine has been implemented that expands the options to the user to include other actions than Approve and Reject. For more information on approvals, see the IBM TRIRIGA: Application Administration User Guide.