A Flow Application typically consists of one main flow and a number of fragments. The fragments used in the main flow are typically single swimlane, while the main flow can consist of multiple swimlanes.
Normal workflows where a single user executes the workflow.
Multiple swimlanes are used in offline workflows and in workflows with multiple users involved. Multiple swimlanes can also be used to perform background tasks in a machine swimlane in an online workflow.
When using a multi-user workflow, consider the rules of the ERP system. Make sure that the Flow process works with the ERP workflow rules and statuses.
Edit swimlane crossings and add task names that will be visible in the Flow Studio monitoring tab. Optionally, enable push notifications to the user/role receiving the task.
Configure a handover inbox to display new tasks. Remember to make the necessary variables public so that they are visible in the inbox.
To create an offline application, start by developing an online workflow. When the workflow has been tested and verified, then make an offline version:
Copy the online workflow.
Create an offline swimlane for the user-facing logic and a machine swimlane for application logic.
Configure the user swimlane as a seeded offline to use the offline inbox functionality.
Replace all datasets in the user swimlane with offline resources.
Try to group your offline resources in a logical way: basic data, document data, user data, fast moving, slow moving (depending on update interval).
Move application logic to the machine swimlane using splits.
Use checkpoints to notify the user before handing off to the machine swimlanes.
Edit swimlane crossings and add task names that will be visible in the offline transaction menu (My offline data).
Create a machine workflow for help requests that notifies a system admin/super user. Connect the workflow to the Help Request System Event.