About Flow Settings
- Updated on 17 Feb 2020
- 2 minutes to read
This document is a general overview of the Flow Settings in the Flow Designer. In Decisions, a Flow is a visual representation of the entire process being built. A Flow is built using the Create Flow tab in the Action Panel located at the bottom of the Designer Studio.
Begin in the Flow Designer and expand Settings on the Properties panel.
The following options should display:
In the Behavior Type drop-down list we can set the desirable Flow Behavior:
- Agent Flow lets you integrate intuitively with other servers or machines. Use this behavior when you want a client machine to work with the Decisions Server as part of its local environment.
- A Batch Processing Flow creates an async flow that expects to receive large amounts of data. It handles the data in multiple threads to limit memory use and errors.
- A Converter Flow requires flow input data (to be converted) and output data (the converted data). For example, if you have number data stored as string type data, you can create a converter flow that converts it to Int32 data.
- A Custom Email Parsing Flow expects an email response job from an assignment. It lets you pull in this data to perform rules or other manipulations. Use this behavior when you want to manipulate email response data from an assignment.
- A Default Flow Behavior acts like an interface definition for a Flow. It can enforce expected inputs and outputs as well as create the expected inputs when the behavior is assigned.
- A Default Flow Behavior (Sync) is a "sync" behavior, meaning that if this flow is called by another flow that flow will wait for it to fully complete (hit the end step) before moving on. A good example of this behavior would be an approval subflow that needs to complete before the parent flow moves on.
- Use Top Flow Settings - uses parent Flow’s recursion policy
- Use This Flows Settings
Stop Recursion at
The default is 20000. This setting prevents a Flow from an infinite loop and overflow memory.
This sets the way Flow Data is going to be stored in the database if the Flow is abandoned:
- Journal- is heavier on processing but lighter on storage space in the database.
- Snapshot - is lighter on processing but heavier on storage space in the database.
Clear Policy On Exception
When a Flow ends on an exception, by default it does not clear the Flow data that may have been saved in the database. We can override this with the Clear Policy On Exception setting.
- Use Default: is set in System > Administration > Settings > Designer Studio Settings > Flow Designer
This sets to rollback Flow data based on the ‘Clear Policy On Exception’ setting.
Keep Active Time Span
This setting determines how long a Flow remains in the ‘running state’ if it is stalled on a sync step. Once it is no longer active the Flow becomes abandoned.
Abandoned Storage Policy
Defines if Flow data should be Saved or Discarded if a Flow is ‘abandoned’
Store Step Statistics
This setting defines if Step data should be stored in the database:
- Sampling - stores only more than 10
- Always - stores
- Never- does not store