- 03 Aug 2023
- 3 Minutes to read
- Updated on 03 Aug 2023
- 3 Minutes to read
The way a Flow behaves is based upon the defined Properties found in the Flow Designer Properties tab.
Existing Flow Input Data is displayed in this section; Input Data may also be added here.
|Customize the colors used in the Flow Designer for this specific Flow.
|Changes the color of the workspace.
|Changes the color of the lines connecting steps.
|Changes the font styling of steps.
|Changes the font styling of labels of the lines connecting steps.
|Changes the behavior of the lines connecting steps.
|Link Line Type
|Makes lines sharper and more direct.
|Curved corner effect on lines.
|Applies a hill effect on lines that cross each other.
|Determines if paths in a Flow will route around Flow steps
|Turns on Statistics
|Category Name for Statistics
|Sub Category Name
|Sub Category Name for Statistics
|Applies Swimlanes to the workspace in a horizontal or vertical layout.
Configure the Integration Type to be API Service, User Interface, Webhook, or None. Once a Type is picked, further configuration options become available along with a VIEW button to supply additional settings, display information for calls and expected outputs, and test the integration.
- In the Flow Designer, navigate to the Properties tab.
- Expand the Settings panel.
|The Behavior Type drop-down list allows setting the desired Flow Behavior.
|Use Top Flow Settings
|Uses the Parent Flow's Recursion Policy settings.
|Use This Flows Settings
|Uses the current Flow's Recursion Policy settings.
|Turns off Recursion Policy settings.
|Stop Recursion At
|The default Stop Recursion At setting is 20000, preventing a Flow from an infinite loop and overflow memory. This number should be increased if intending to process more than 20000 records.
|Allow Flow Start Recursion
|Allows Starts of the Flow to ignore recursion limit
|File Storage Association Policy
|Determines how a file is stored in a Flow
|Files will associate with the Flow and move to the Flow Data directory.
|Files in the Flow will not move to the Flow Data directory and will only remain in the temp directory.
|Storage Policy sets the way Flow Data will be stored in the database if the Flow is abandoned.
|Flow Designer chooses between Journal and Snapshot
|Heavier processing but lighter on storage space in the database.
|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. Override this via the Clear Policy On Exception setting.
|Uses the default set in System > Administration > Settings > Designer Studio Settings > Flow Designer
|Clears Policy on Exception.
|Prevents Policy from clearing on Exception.
|Sets Rollback for 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.
|Stores no more than 10 records of Step data.
|Stores the Step data in the database.
|Does not store the Step data in the database.
|These settings are for configuring specific Enablement options for the Flow.
|By default, Flows are initially enabled.
|Use Enabled Rules
|Enables the Flow based on the evaluation of the Enabled Rule (must be configured).
|Select a Start date for the Flow to be enabled.
|Select an End date for the Flow to be disabled.
|Flow Execution Messages
|These settings are for configuring specific Start and End behaviors for the Flow.
|Flow Started UI Behavior
|Uses default Flow behavior.
|Acts as if a Form is expected.
|Shows a Message in the Studio.
|Shows a Notification in the Studio.
|Runs without a Notification.
|Flow Started UI Delay
|Used to configure the duration before the Flow Started behavior happens.
|Flow Started UI Message
|A customizable message appears after the Flow starts (after the specified Delay).
|Flow Ended UI Behavior
|The behavior that should be used when the Flow has ended.
|Flow Ended UI Message
|A customizable message appears when the Flow has ended.
|Triggers are used with the Flow Step Trigger behavior that is available in the Behavior Type drop-down list.
|Before Trigger Type
|Configures whether the before Trigger uses a Store or Run Flow function.
|After Trigger Type
|Configures whether the after Trigger uses a Store or Run Flow function.
|Error Trigger Type
|Configures whether the error Trigger uses a Store or Run Flow function.