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
The system determines the outcomes that are displayed on this tab page from the following specifications:
You decide which outcomes you want to take into account in the workflow when modeling. The only outcomes that have to be taken into account whenever they are displayed on this tab page are the outcomes for missed deadlines Task executed synchronously and Processing rejected.
If you have not included an outcome that is required during execution into the definition, the associated workflow work item is forced into status error.
All possible outcomes are listed in the following table:
Outcome |
This outcome exists if ... |
Notes and comments |
Terminating event of task |
The task was defined with terminating events. |
If the underlying method is an asynchronous method, you must select at least one event as an outcome. |
Possible value of result of object method |
The synchronous object method is defined with a result, for which fixed values or a check table are maintained. |
If you deactivate all the values of the result, the system activates the outcome Task executed synchronously. |
Object method exception |
The object method is defined with exceptions. |
Exceptions in the Workflow Definition |
Task executed synchronously |
|
If this outcome is displayed, it is always active. |
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 steps defined after this outcome are executed. |
Processing obsolete |
The work item can be set to obsolete via a step of the type process control. |
The steps defined after this outcome 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 these outcomes. |
At runtime, the system enters an event receiver linkage only for those terminating events that you select in the definition of an activity and therefore include in the workflow definition.
No other events terminate the activity, even if they are entered as terminating events for the single-step task.
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, all steps already modeled in this branch are deleted.
For further information about an outcome, select it and choose Detail in the context menu.