---
title: "Configure Flows"
slug: "configure-flows"
description: "Configure Flow behavior using the Properties tab in the Flow Designer, including available execution and design settings."
status: "update"
updated: 2026-10-23T19:26:35Z
published: 2026-10-23T19:26:35Z
canonical: "documentation.decisions.com/configure-flows"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Flows

## Overview

A Flow's behavior is determined by the properties configured in the Properties tab of the Flow Designer. This article describes each setting available in the Properties tab.

---

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1782484632989.png)

## Default

Existing [Flow Input Data](/version-10/docs/create-flows) is displayed in this section; Input Data may also be added here. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779133914113.png)

---

## Advanced

| Advanced Setting | Description |
| --- | --- |
| Colors | Customize the colors used in the Flow Designer for this specific Flow. |
|  | Designer Background | Changes the color of the workspace. |
|  | Links Color | Changes the color of the lines connecting steps. |
|  | Node Labels | Changes the font styling of steps. |
|  | Link Labels | Changes the font styling of labels of the lines connecting steps. |
| Shape Defaults | Changes the behavior of the lines connecting steps. |
|  | Link Line Type | Line Style - how the lines that connect Steps within the Flow look. |
|  |  | Default | Cornered style. |
|  |  | Direct | Makes lines sharper and more direct. |
|  |  | Cornered | Curved corner effect on lines. |
|  |  |  | Jump Lines | Applies a hill effect on lines that cross each other. |
|  |  |  | Avoid Nodes | Determines if paths in a Flow will route around Flow steps |
| [Statistics](https://documentation.decisions.com/version-10/docs/turn-flow-statistics-on) |  |
|  | Capture Statistics | Turns on Statistics |
|  |  | Category Name | Category Name for Statistics |
|  |  | Sub Category Name | Sub Category Name for Statistics |
| [Swimlanes](/version-10/docs/using-swim-lanes) |  |
|  | Swimlane Type | Applies Swimlanes to the workspace in a horizontal or vertical layout. |

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779133951095.png)

---

## Service Settings

Configure the [Integration](/version-10/docs/view-integration-details) Type to be API Service, User Interface, Webhook, or None. Once a Type is selected, additional configuration options become available, along with a VIEW button that provides settings, displays call information and expected outputs, and tests the integration.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779133993464.png)

---

## Data Provider Flow (For v10.4+)

In **v10.4** and above, Administrators can configure a Provider Flow to run before the main Flow. Outputs from the provider Flow are automatically added as inputs to the main Flow. If the Provider Flow fails, the main Flow also fails and will display a message identifying the Provider Flow. Users should note that copying a flow does not duplicate its associated data provider flow. The copied flow continues to reference the original Provider Flow.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1792783143813.png)

## Settings

1. In the Flow Designer, navigate to the **Properties** tab.
2. Expand the **Settings** panel.

| Setting Name | Description |
| --- | --- |
| Behavior Type | The **Behavior Type** drop-down list sets the desired **Flow Behavior.** |
| Recursion Policy |
|  | Use Top Flow Settings | Uses the Parent Flow's Recursion Policy settings. |
|  | Use This Flow's Settings | Uses the current Flow's Recursion Policy settings. |
|  | Off | Turns off the 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 Users intend to process more than 20000 records. |
| Allow Flow Start Recursion | Allows Flow Starts to bypass the recursion limit. |
| File Storage Association Policy | Determines how a file is stored in a Flow. |
|  | Always | Files will be associated with the Flow and move to the Flow Data directory. **Users should check this setting if the file must persist beyond the Flow's completion.** |
|  | Never | Files in the Flow will not move to the Flow Data directory and will only remain in the temp directory. **Users should check this setting if the file is only needed during the Flow.** |
| Storage Policy | **The Storage Policy defines how Flow Data is stored in the database when a****Flow** is abandoned. |
|  | Automatic | Flow Designer chooses between Journal and Snapshot. |
|  | Journal | Heavier processing but lighter on storage space in the database. |
|  | Snapshot | 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. |
|  | Use Default | Uses the default set in **System > Settings > Designer Studio Settings > Flow Designer.** |
|  | Yes | Clears Policy on Exception. |
|  | No | Prevents Policy from clearing on Exception. |
| Rollback Enabled | 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 determines whether Step data is stored in the database. |
|  | Sampling | Stores no more than ten records of Step data. |
|  | Always | Stores the Step data in the database. |
|  | Never | Step Statistics are not stored. |
| Enabled | These settings configure specific **Enablement** options for the **Flow**. |
|  | Enabled | By default, Flows are initially enabled. |
|  | Use Enabled Rules | Enables the Flow based on the evaluation of the Enabled Rule (must be configured). |
|  | Begin Date | Select a Start date for the Flow to be enabled. |
|  | End Date | Select an End date for the Flow to be disabled. |
| Flow Execution Messages | These settings configure specific **Start** and **End** behaviors for the Flow. |
|  | Flow Started UI Behavior |
|  |  | Default | Uses default Flow behavior. |
|  |  | Expect Form | Acts as if a Form is expected. |
|  |  | Show Message | Shows a Message in the Studio. |
|  |  | Show Notification | Shows a Notification in the Studio. |
|  |  | Run Silently | 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 | **Triggers** are used with the **Flow Step Trigger** behavior, 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. |

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779134215233.png)

---

## Feature Changes

| Description | Version | Release Date | Developer Task |
| --- | --- | --- | --- |
| Added a new Flow With Data Provider behavior that allows administrators to configure a provider Flow to run before the main Flow. Outputs from the provider Flow are automatically added as inputs to the main Flow. If the provider Flow fails, the main Flow also fails and displays a message identifying the provider Flow. When a Flow is copied, the associated data provider Flow is not duplicated and continues to reference the original provider Flow. | 10.4 | October 2026 | [DT-048970] |