Click the Other Callbacks tab.

Using Approval Management 26-49 The Header also contains custom and system actions. Custom actions are those that depend on task metadata outcomes. For example, if the metadata contains Approve and Reject outcomes, then Approve andReject appear in the Header as custom actions. If the metadata contains more than two outcomes, then the custom actions appear in the Header as a dropdown list instead of separate buttons. In Figure 26–51 , Approve and Reject appear as separate buttons. This indicates that the task metadata includes Approve and Reject outcomes. System actions, such as Escalate, Suspend, and Resume, always appear in a dropdown list. The actions that appear depend on what the user is doing. For example, after a task has been initiated it can be withdrawn. Subsequently, if a user logs into the Worklist Application to view the details of an initiated task Withdraw appears in the list containing the available actions. Table 26–9 lists all the actions the administrator can perform from the Header and their descriptions. Priority The priority level assigned to the task. Creator The user who originated the task. Created The task’s creation date. Updated The date the task was last updated. Expires The date the task expires. Assignees The names of the administrators to whom the task has been assigned. Acquired By The name of the user who claims the task before any action is taken on it. Due Date The date by which the task is due. Table 26–9 Header Actions Action Description Reject Enables the administrator to reject the task. Approve Enables the user to approve the task. Delegate Enables the administrator to assign a task to another person to act on his or her behalf. Reassign Enables the administrator to transfer a task to another administrator. Suspend Enables the administrator to suspend the task to work on it at a later time. Resume Enables the administrator to resume a suspended task. Withdraw Enables the administrator to withdraw an initiated task. Escalate Enables the administrator to escalate a task to a supervisor. Delete Enables the administrator to delete a task. Appears for all To Do tasks. Purge Enables the administrator to purge a task. Appears for all To Do tasks. Table 26–8 Cont. Header Fields Field Description 26-50 Modeling and Implementation Guide for Oracle Business Process Management

26.5.1.2 Task Payload View

The Task Payload view, shown in Figure 26–52 , displays the details of the task parameters and provides the ability to update them. Any parameter that has been designed based on SDOs also can be viewed here. While the values of the general parameters are based on what was passed to the task or update by any user, the values of the SDO-based parameters reflect the current value of the business object as it was updated in the underlying application. Figure 26–52 Task Payload For more information, see Designing Task Display Forms for Human Tasks in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

26.5.1.3 Task History View

The Task History view, shown in Figure 26–53 , provides a graphical and tabular view of events in the task life cycle. In addition, if the Edit Approver Configuration option was selected in the designer, special controls in the tabular view that allow futire approvers to be edited are available. Any approver added manually can be deleted and new approvers can be added. Approver changes made in the tabular view are immediately reflected in the graphical view. When the task is saved or a custom action, such as approve or reject, is performed on the task, all approver-related changes also are saved. Go Enables the administrator to go to the action selected from the dropdown list. Save Enables the administrator to save the task. Table 26–9 Cont. Header Actions Action Description