Maintenance of Tab Page Outcomes 
Maintenance of Tab Page Outcomes
Use
The specifications you make on this tab page determine the outcomes of the step for which you want to model a reaction. If reactions to missed deadlines are modeled, the outcomes defined for the relevant missed deadline are only displayed here.
Features
On this tab page you can only activate the outcomes Processing obsolete and Document could not be created. All other outcomes are determined by the system and activated automatically.
All possible outcomes are listed in the following table:
Outcome |
This outcome exists if ... |
Notes and comments |
Document could not be created |
Always |
Defined exception for the method of the standard document task. |
Task executed synchronously |
Always |
You cannot deactivate this outcome. |
Processing rejected |
The indicator Processing can be rejected is set. |
If processing of the relevant work item is rejected at runtime (via Reject execution in the Business Workplace), the subsequent steps defined after this exception are executed. |
Processing obsolete |
The work item can be set to obsolete via a step of the type process control. |
The subsequent steps defined after this exception are executed. This outcome should only be activated if the modeled reaction to a missed deadline contains a step that sets the work item for this step to obsolete. |
Requested end Latest end Latest start |
The relevant deadline monitoring is activated and a modeled reaction required. |
Within these branches, you can model a process control step that sets the work item of the step to obsolete. You cannot deactivate this outcome. |
Activities
You activate the outcomes that you want to actually transfer into the workflow definition. Select 
in the relevant line.
Active outcomes are marked with 
and have a modeling branch in the workflow definition.
If you deactivate an active outcome, the whole of the associated branch is deleted.
For further information about an outcome, select it and choose Detail in the context menu.