Worklist controls enable the automated manipulation, creation, and management of Tasks. A Task instance represents a unit of work that requires completion within a certain time period. After the work is completed, you can use a Task instance to represent a detailed record of that unit of work.
A Task instance is a particular object in the run-time Worklist system that represents a work assignment in the real world. Task instances are part of the WebLogic Integration server and exist independently of any controls or business processes. Multiple business processes can interact with a Task throughout its lifecycle concurrently. Tasks remain in the run time indefinitely, either until they are explicitly deleted or purged by the WebLogic Integration purging process.You can create, delete, and manage Tasks through the following mechanisms:
Task instances, or simply Tasks, offer a variety of properties that describe the work to be done and the state of the work. Task instance properties can describe the following:
The list of users and groups that have permission to claim the task and work on it. |
|
The records that describe the work to be done and the results. |
Tasks have the following characteristics, qualities and behaviors that can be defined, configured or used:
The following Worklist controls are provided for building a Worklist system with WebLogic Integration:
Worklist controls are extensible. Common extensions include implementing callback functions and performing system queries. Extensibility is provided by Java annotations.
Creating a New Task Worker Control
![]() |
![]() |