At Boomi Flow, the word we use for an ‘app’ is ‘flow’. We build a flow by logging in to the Boomi Flow drawing tool, connecting an identity service for authentication (or not, to create a public flow), dragging and dropping elements to a canvas, configuring the elements, and connecting them with outcomes. Outcomes connect elements in the canvas and show how a flow progresses. The outcomes get converted into clickable buttons in the app.
We can think of elements as building blocks, which we combine to build an app.
Elements come in various flavors:
- Map elements
- Navigation elements
- Group elements
Flows can execute sequentially where flow control is passed from one element to the next, only when the previous element has been executed. Each sequential element has the ability to affect the outcome, and therefore the next element to be executed in sequence. Smart processes? You bet!
You can also build non-sequentially, where flow control is managed by navigation or unmanaged completely allowing execution to be jumped based on any external event.
Any time a flow execution is started, a state is created. The state contains all data about the instance of the flow. A state can be used by individual users, or shared with many users, to support collaboration between individuals and teams.