Unwired Orchestrator uses a process flow model in which activities are linked by connectors that represent the sequence in which the activities are performed. The flow of data is not necessarily implied between activities although certain activities require the specification of input and output data.
The process flow model enables you to work at a high level without requiring the data related or runtime implementation details. The general layout of the activities for a business solution can be created with or without detailed binding details. If the design is completed without binding the high-level design to data and runtime implementation details, that information can be added later by a more technical user.
A process flow originates with an activity connected to the IN node on the business process canvas and continues down the normal path through the designed sequence of activities and services until the path ends at an End activity or the OUT node on the business process canvas. All activities in the flow are connected to indicate the order they are performed. Branches in the flow can be added to handle the different scenarios that might occur during a business function.
The following types of tasks can be involved in building a flow:
Branching Normal Activity Flow
Exceptions to Normal Activity Flow