---
title: "Setting Required Value For Outcome Path"
slug: "setting-required-value-for-outcome-path"
description: "This document shows how to setup a Form in Decisions that contains a text-box that evaluates an input for either an Optional or Required Value outcome.  Using a Required Outcome, ensures that users input the proper sort of information in a text-box, and prevents human error in filling out a Form. "
tags: ["Dynamic Behaviors", "Forms", "Outcomes"]
updated: 2025-06-23T17:26:20Z
published: 2025-06-23T17:26:20Z
canonical: "documentation.decisions.com/setting-required-value-for-outcome-path"
---

> ## 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.

# Setting Required Value For Outcome Path

## Overview

This tutorial demonstrates how to set required fields on the Form dynamically. With this feature, the Flow automatically decides which data is/is not optional based on data evaluation before loading the Form without need of Designer input for each field.

Each data input within a Form can have its Outcome Scenarios settings changed for each outcome path in the following methods:

| Data Requirement | Description |
| --- | --- |
| Required | Data must be entered into this control to submit the Form down this outcome path. If missing, a validation error prevents submission. |
| Optional | Data may be entered into this control for other Flow logic, but is not required for submission. If this data is empty upon submission, the Form will still submit successfully. |
| Not Used | Data entered here is not used for this outcome path. Regardless if a value is entered here or otherwise, it will not be present for selection in Flow logic after this Form. |

---

## Example

In this example, build a simple Flow with a Form. The Form will have a text-box control that may be set to be either required or optional. This will be set as a Form input.

1. In the Flow Designer, add a [Show Form](https://documentation.decisions.com/v9/docs/create-a-form) step and create a new Form.
2. In the Form Designer, design the Form with the following controls: two **Buttons** and a **Text Box.** Give the Text Box a Label during creation.
3. Navigate to the Text Box **Properties > Outcome Scenarios**. Select Submit's outcome scenario to **Required** and Cancel's to **Not Used**.
4. Save the Form and close Form Designer.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-23_13h23_40.png)
5. In the Flow Designer, select the **Show Form** step. In the **Properties** panel's 'Example Data' Input**,** set it's mapping type to **Ignore**.
6. Connect the Submit outcome path to the end step. Add a second End step, name it 'Cancelled', and connect the Cancel outcome path from the Form to it.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2025-06-23_13h25_24.png)

---

## Debug

1. Select **Debug** on the top panel in the Flow Designer
2. Attempt to **Submit** the Form without providing input in the Text-Box. Notice a validation issue preventing Form submission.
3. Add text to the Text Box, and the Form will be submitted successfully.