Top-Down Modeling
Top-down modeling allows you to create workflow definitions taking into account block orientation without knowledge of the individual tasks used. At an early modeling stage, it is therefore possible to create incomplete but consistent workflow definitions. It may well be appropriate to define the flow logic initially for complex workflows for example.
You have selected Use Top-Down Modeling in the Workflow Builder options (see also: Workflow Builder Options).
Top-Down Modeling
You can use all the step types available when modeling. Model the workflow by using drag&drop to assign the steps you want to use accordingly. The exact specification takes place at a later stage. For this reason, the system does not switch to the detail view of the new step when a new step is added. You should overwrite the proposed step name with a name that describes the significance or function of this step in your scenario.
Task TS30100074 is used for the activity step type:
|
Task |
TS30100074 |
|
Abbreviation |
WF_MODTASK |
|
Name |
Name Modeling task for TOP/DOWN approach |
The top-down task references an object method with a result. The system only offers one outcome as standard. Add the required number of outcomes for your scenario by using drag&drop in the step type Add Outcome and name them. You can use the top-down task more than once in a workflow definition.
Productive Use
To use the "top-down" modeled workflow productively, enter a task ID in each definition of the individual steps. The definition of the task entered is read and the binding definition between the workflow container and task container generated if applicable. The outcomes of the activity can be described in the normal way. For more information, see Maintenance of Tab Page Outcomes. When you return from the definition of the activity to the display of the workflow definition, superfluous outcomes of the top-down task are deleted. New branches are created in the workflow definition for additional or unassigned outcomes of the task entered.