--- title: "Create Flows" slug: "create-flows" description: "Learn how to create and configure Flows in the Designer Element, utilizing Steps to manipulate data and enhance functionality effectively." status: "update" updated: 2026-07-02T20:13:19Z published: 2026-07-02T20:13:19Z canonical: "documentation.decisions.com/create-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. # Create Flows ## Overview A Flow is the Designer Element visually represents the logic used to execute a process. Flows can move and manipulate data, perform various actions, and provide functionality to other Designer Elements. These processes are created by adding and configuring functions referred to as Steps. Steps are a graphic way to represent each point within a Flow. Steps are added to Flows via the Flow Designer from the step catalog known as the Toolbox. The following article will walk through the basics of creating a Flow. --- ## Example 1. In a **Designer Project**, select CREATE FLOW. 2. The **Create Flow** gallery will appear, displaying various [Flow Behavior](/version-10/docs/about-flow-behaviors) options. Select **Flow** found under the Favorites or Default sections**.** 3. Enter a Flow name in the text box provided. Select CREATE.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1783023186948.png) | Option | Description | | --- | --- | | [View History](/version-10/docs/how-to-versioning) | Views the history of the Flow. | | Name | The provided Name for the Flow. This field can be updated with the changes reflected in the portal after the Flow is saved. | | Description | A written description of the Flow. | | [Owner](https://documentation.decisions.com/version-10/docs/actions-glossary) | The current owner of the Flow. Based on specific [designer settings](/version-10/docs/designer-studio-settings), the owner can be notified if changes are made to the Flow. The Current owner can be updated using the Pick action. | | [Tags](/version-10/docs/tagging-overview) | Tags can be added to the Flow for easier searchability in the portal. | | [Behavior Name](/version-10/docs/about-flow-behaviors) | The current Flow behavior used by the Flow. | | Element Attribute | Provides information on the current Designer Element to which this item belongs. | | Created in Version | The version the Flow was initially built in. | | Modified in Version | The version the Flow was last updated in. | | Id | The Flow ID is used for identifying the Flow in the database. ID's of Designer Elements can also be found in the URL while in the editor or within the Data Explorer. | | Created On Date | The date the Flow was built. | | Modified Date | The latest date the Flow was saved and changed. | | Created By | The account associated with making the Flow. | | Modified By | The account that had most recently modified the Flow. | Once the Flow has been created, selecting the Info in the side panel can provide the user with various details of the Flow, such as the name, Owner, and Flow ID. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778865076767.png) 4. At the top of the Flow Designer, select **SETUP INPUT DATA**. Input Data is data passed into the Flow to manipulate with Steps. 5. In the **Flow Input Data** dialog, select **DEFINE** under **Define Input Data** to open the **[Flow Name]: Input Data** window. The Input Data window is where data that needs to pass through the Flow can be defined. This window presents three fields that can be configured for each piece of data; **N****ame,****T****ype****,** and **Is List**. Alternative to the Input Data window, data can also be defined in the **Properties** panel of the **Start** step.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778865111077.png) 6. In the **[Flow Name]: Input Data** window, type "First Number" in the **Name** field on the first line. Expand the drop-down list for **Type** and select **Int32** **[Number]**. Leave the 'Is List' option unchecked. 7. On the second line, type "Second Number" for the **Name,** select **Int32[Number]** for the **Type,** and leave **Is List** unchecked. 8. Select **Save** and then close the **Input Data** window.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1782418491492.png) 9. In the **Toolbox** panel, expand **DATA > NUMBERS**. Drag and drop the **Add** step onto the workspace. Connect the **Start** step to the **Add** step. The Toolbox houses thousands of [Steps](https://documentation.decisions.com/step-library/docs) that manipulate and move data throughout a Flow.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778865307474.png) 10. With the **Add** step selected, navigate to the **Properties** panel. The step Properties panel includes step settings, additional [outcome paths](https://documentation.decisions.com/version-10/docs/using-the-mapping-editor), [testing and simulation](/version-10/docs/using-the-testing-simulation-in-the-debugger) settings, and inputs and outputs. Input is the expected data that the step needs to function. Next to each input is a drop-down list set to Unknown by default. This drop-down represents the [**Mapping Type**](/version-10/docs/input-output-types-overview) for an input value. Output is the information the step passes out once it has finished its process. In the Help Center section of the Flow, a red exclamation mark will appear when new steps are added that have not been configured yet. This indicates an Exception within the Flow that would need to be resolved before the Flow can function as intended. 11. Under **Inputs > Value1** select **Pick**. In the Pick Data For Input: value1 dialog, choose First Number. 12. Under **Inputs > Value2** select **Pick**. In the Pick Data For Input: value2 dialog, choose Second Number. Alternatively, begin typing "Second Number" within the textbox to display a drop-down of all matching data available to the Flow.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778865580382.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1782418708350.png) 13. Connect the outcome path from the **Add** step to the End step. Move the **End** step next to the other logic; it is best practice to keep lines within the Flow straight to have an organized view. 14. Select **Debug** in the top action bar. The **Debugger** is a tool that tests the Flow to confirm that the logic is working as expected. It will show the number of times a step was reached, its path, and input and output data to see how it changes from step to step. 15. Type numbers into the First and Second Number boxes and select Start Debugging. 16. In the Debugger, click the **Add** step, then view the **Input/Output Data**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778865790695.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1782418568183.png)![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1782418812415.png) --- ### Reviewing Mappings in the Data Explorer After the Flow is configured, the **Data Explorer** can be used to review mapped data within the Flow Designer. Selecting an input from the Explorer tree displays arrows to indicate its mapping. Steps associated with the selected input are emphasized, while the remaining steps are minimized. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1778866149133.png) --- ## Feature Changes | Description | Version | Release | Developer Task | | --- | --- | --- | --- | | The Data Explorer has been enhanced to display arrows for mapped inputs and emphasize the corresponding steps while minimizing the remaining steps. | [9.21](https://documentation.decisions.com/v99/docs/version-921x-release-notes) | March 2026 | [DT-046504] | | The Type Picker has been redesigned. This can be found when selecting Edit Input Data and then picking the data type. | [9.5](https://documentation.decisions.com/v99/docs/version-95x-release-notes) | November 2024 | [DT-042365] |