Starting Points

Starting points specify which screen the user sees when they perform a certain action.

Starting points include:

• Client-initiated – this starting point is activated when the user opens the mobile workflow on the device.
• Activate – this is the starting point that is activated when the user first opens the mobile workflow. It does not activate on the second and subsequent times the application is started. Multiple workflow applications can share the same Activate starting point. Different workflows can specify an activation key, and workflows with the same activation key share their activation status. For example, if Workflow A and Workflow B both specify an activation key of AB (via the key attribute on the RequiresActivation tag), when Workflow A gets activated, it also activates Workflow B such that when Workflow B is invoked for the very first time, its activation screen will not be displayed.
  Note: A mobile workflow application with an Activate starting point is considered to be successfully activated only if it is closed with a Submit Workflow menu item.
• Credential request – this starting point is activated when the mobile workflow application requires a user name and password and the program does not have one in its cache, or the values in the cache are no longer valid.
• Server-initiated – this starting point is activated when a notification message is sent to the device that matches the matching rules specified in the mobile workflow application. The developer can add conditions, based on the notification message, to determine which application screen opens first.

Each starting point has a list of keys with which it is associated. View the keys associated with the starting point in the Properties view for the starting point.

• Adding a Starting Point Manually
  Every screen must be part of a flow that connects to a starting point.
• Creating a Server-initiated Starting Point
  Create a server-initiated starting point.
• Creating Keys
  Create new keys to bind to controls.