Oracle BPM Worklist enables business users to access and act on tasks assigned to them. For example, from a worklist, a loan agent can review loan applications or a manager can approve employee vacation requests.

Oracle BPM Worklist provides different functionality based on the user profile. Standard user profiles include task assignee, supervisor, process owner, reviewer, and administrator. For example, worklist users can update payloads or business data, attach documents or comments, and route tasks to other users, in addition to completing tasks by providing conclusions such as approvals or rejections. Supervisors or group administrators can use the worklist to analyze tasks assigned to a group and route them appropriately.

Users can filter their tasks by creating views or saved searches.

Using Oracle BPM Worklist, task assignees can do the following:

• Perform authorized actions on tasks in the worklist, acquire and check out shared tasks, define personal ToDo tasks, and define subtasks.

• Filter tasks in a worklist view based on various criteria.

• Work with standard work queues, such as high priority tasks, tasks due soon, and so on. Work queues allow users to create a custom view to group a subset of tasks in the worklist, for example, high priority tasks, tasks due in 24 hours, expense approval tasks, and more.

• Define custom work queues.

• Gain proxy access to part of another user's worklist.

• Define custom vacation rules and delegation rules.

• Enable group owners to define task dispatching rules for shared tasks.

• Collect a complete workflow history and audit trail.

• Use digital signatures for tasks.

Figure 32-1 shows an illustration of Oracle BPM Worklist.

The worklist is the list of tasks. A task form displays and updates the task details. You can create a task form using ADF task flows in Oracle JDeveloper. See Designing Task Forms for Human Tasks for more information.

You can build clients for workflow services using the APIs exposed by the workflow service. The APIs enable clients to communicate with the workflow service using local and remote EJBs, SOAP, and HTTP.