Status of a Background Work Item 
The valid statuses for background work items (type B) are listed in the following table.
Work item status |
Description |
|
The work item has been scheduled for its requested start. A work item has this status after it has been created until the requested start specified in the workflow definition is reached. |
|
Temporary intermediate status of a background work item. The system calls the associated object method as soon as a background work item can be processed. The status of the background work item then changes to in process immediately. |
|
The work item is currently being processed. A work item also has this status
The point at which processing is completed cannot be detected by the workflow system in this status. |
|
The execution of the work item is completed. The result of the task represented by the work item is correct, i.e. the result modeled in the workflow definition. |
|
Execution of the work item with regard to the process logic is no longer meaningful or necessary for the process to continue. A work item changes to the logically deleted status in the following way:
When the required number of processing paths has been executed in a fork, the work items in the other paths that have not yet reached the completed status are automatically set to the logically deleted status.
The administrator can only set a work item to the logically deleted status if it has not yet reached the completed status and is not part of a higher-level workflow.
A work item with the logically deleted status may have caused database changes or other actions (generate event, send notification). These changes are not canceled automatically (compensated). |
|
Execution of the work item was terminated with an error. |

In addition to the statuses given above, a work item can be locked against execution. This is possible in any status and involves an administrative function which is selected for a work item via the Change option.