A Flow is a graphical representation of the modeled conversation.
Flows are modeled and tested in the Flow Editor. It's a graphical user interface, applying the concept of flow based programming to conversations.
It is primarily defined by a set of Flow Nodes, which are aligned like a flow chart.
- Go to the Project Dashboard
- Create a Flow by clicking the Add button in the left-hand Resource list and then click Flow
- Enter a name and select the immutable language. A new Flow will be created and automatically opened in the interface.
Get started and build your Flow by creating new Flow Nodes
Limited Number of Nodes
In order to prevent degradation of performance of your Flow, try to keep the number of Nodes below 100. If you need more, you should consider breaking up your Flow with Execute Flow, Switch Flow Nodes and the Attached Flows feature.
Check out the getting started guide to learn more about Building a Flow .
Inside the Flow Editor the left hand navigation pane gives you easy access to configuration of all properties and information such as analytics for your Flow.
Navigate your Flow with Drag & Drop
You can simply drag and drop your view pane of your Flow Editor to get around
The search pane highlights Nodes matching your search term. It will find matches in both Node title and content.
The zoom pane in the bottom left of the Flow Editor view lets you zoom in and out of your Flow.
Any changes in your Flow are auto-saved in your Flow's current draft version.
A Flow version records the immutable state of your Flow. You can save a new version by clicking the three dots in the upper right corner of the Flow Editor. The Flow menu (see Figure 2) will open. For saving a current version select Lock Version.
This will prompt a dialog, asking you to write an optional commit message when saving your Flow. You can see the commit messages of all Flow versions in the overview tab of the Flow properties panel (see Figure 3), which makes it ideal to explain the changes you have made in the commit message. However, you can also leave this field empty and just save your Flow.
Lock your flows for better performance
The draft version of the flow is for editing and therefore is unable to be cached efficiently. Locked versions take less time to load and therefore perform better under heavy load.
Updated 2 years ago