Know your map elements

The Map element in Flow represents any node or element in your flow diagram. Every map element has a unique identifier and version identifier. The unique identifier remains the same throughout the lifecycle of the flow; the version identifier changes every time the element is modified.

When a flow snapshot is created, the build process takes the latest version of all elements associated with the flow, and locks the flow to those versions of the elements. A flow references all of the elements that are needed for it to run.

These are some of the things you can do in a flow with map elements:

  • Show the user a screen
  • Update data
  • Collect information
  • Insert/edit/delete database records
  • Execute business rules
  • Send messages to third-party applications

Map elements are typically connected with other map elements by outcomes. Outcomes help route the execution path of your flow. Incidentally, you can also have a flow where you use navigation instead of outcomes to guide the user journey.

Map elements are found on the left-hand side of the Flow canvas.

There are eight map elements in Flow. 1|. Step, 2|. Page, 3|. Operator, 4|. Decision, 5|. Message, 6|. Database Load, 7|. Database Save, and 8|. Database Delete.

You can drag and drop each of these map elements into your Flow canvas.

Dragging and dropping a map element to the canvas opens a configuration panel on the right.

You can customize the functionality of the map element from this panel.

Configuration options

The configuration options that are common to all map elements include: Data Actions, Message Actions, Listeners, Operations, Navigation Overrides, Voting, and of course, Outcomes. As mentioned earlier, you can see these options in the configuration panel, which opens on the right-hand-side when you drag and drop the map element to the canvas.

Data actions: A data action is used to perform create, read, update, or delete (CRUD) operations on data. Map elements that support data actions are Database Save, Database Load, and Database Delete.

Listeners: A listener is used to listen to events on objects stored or managed by a service. Map elements that support listeners are Database Save, Database Load, Message, and Page.

Message actions: A message action is used to map values in a flow to the inputs and outputs specified by a service. Map elements that support message actions are Message and Page.

Operations: An operation is used to make a change to a value or execute a macro in your flow. Map elements that support operations are Operator.

Outcomes: An outcome lets the user running the app move from one map element in the flow to another, or from one map element into another flow.  As you can guess from this definition, outcomes also help show the execution path of a flow. All map elements support outcomes. Map elements that support outcomes with comparison/rules are Decision, Message, and Page.

Vote: The vote object is used to configure voting or multi-user approval options on an outcome. Map elements that support voting are Step and Page.

Apart from the generic configurations, you will also see configuration options specific to the map element you are working with. For example, steps have the Feedback configuration; where you can show an optional message to users who are not authorized to perform an action.

You also have the option to enter comments about a particular element in the Comment field in the configuration panel.

Looking for reference documentation on map elements? We have you covered. Click here!