Outcomes Tab Page
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.
The system determines the outcomes that are displayed on this tab page from the following specifications:
-
Possible values of the result of the method used in the task.
-
Terminating events of the task.
-
Exceptions for the method used in the task.
-
Step definition
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 Step executed 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 the status error.
The following table shows all possible outcomes:
|
The outcome is |
The 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 values of the results, the system activates the Step executed outcome. |
|
Object method exception |
The object method is defined with exceptions. |
|
|
Step executed |
|
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 (using Reject execution in the Business Workplace), the steps defined after this outcome are executed. |
|
Processing obsolete |
The work item can be set to obsolete using a step of the type process control. |
The steps defined after this outcome are executed. This outcome should only be activated if a step is contained in the modeled reaction to a missed deadline that sets the work item of this step as obsolete. |
|
Requested end Duration 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 this step to obsolete. You cannot deactivate these outcomes. |
|
Condition for the 'complete work item' is true. |
A condition for Complete work item is entered on the Conditions tab page. |
If this outcome is displayed, it is always active. |
At runtime, the workflow system creates an instance linkage only for the terminating events that you activate here and therefore include in the workflow definition.
No other events terminate the activity, even if they are entered as terminating events for the task.
If the indicator Not in the workflow log is set for an outcome, the entire branch that is connected to the outcome is not displayed in the graphical workflow log. Further steps are only displayed if this branch is joined with another branch again that is to be displayed.
You activate the outcomes that you want to actually transfer into the workflow definition. Select
in the corresponding 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 more information about an outcome, select it, and choose Detail in the context menu.