Defining Orchestrations in the UserRole
An orchestration describes the flow and interaction among one or more tasklets. You typically divide your mobile application into multiple orchestrations, where each orchestration represents a business activity or transaction, such as viewing customer details or sending a sales order. The orchestrations are then pieced together with actions to form the complete application. The procedures for defining an orchestration involve:
-
Creating the orchestration. See How to: Create an Orchestration.
-
Specifying tasklets of the orchestration. See Defining Tasklets.
-
Defining actions to navigate the tasklets of the orchestration. See Working with Actions for Soft Keys and Menu Items.
Important |
|---|
|
You must define at least one orchestration for the application. This orchestration opens when the application starts and must contain at least one tasklet definition. |
Orchestration Flow Types
There are two flow types that you can define between tasklets in an orchestration:
-
One type combines tasklets in a tree structure.
-
The other type combines tasklets in a wizard.
It is important to know the type of orchestration flow when you start defining an orchestration, because it determines the actions that you use on the tasklets.
Note |
|---|
|
You can use both flow types within an orchestration. |
Tree-Structure Orchestration Flow
In a tree structure orchestration flow, the flow moves in one direction. From a single tasklet, you can navigate to other tasklets of the orchestration in the order that you choose.
When you close a tasklet, you return to the previous tasklet. If you go back to the tasklet again, any data provided in your first visit is gone. This type of orchestration flow is done using open actions.
Wizard Orchestration Flow
In a wizard orchestration flow, you are led through a specific sequence of tasklets. You can navigate between the tasklets without losing any provided information.
A wizard orchestration flow involves defining the wizard steps together with the next and previous actions. For details on wizards, see the section Defining a Wizard.
Important