> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/forms/form-outcomes.md). # Form outcomes You use form outcomes to complete a user task and allow the user to indicate the outcome, for example if a task is approved or rejected. Outcomes are displayed to the user as buttons in the task. {% hint style="warning" %} Outcome buttons are not available in [subforms](/workflows/designing-workflows/forms/form-components/subform.md). {% endhint %} You can define one or more outcome buttons by selecting **Outcomes** in the attribute bar. | Field | Description | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Label | The text of the button. | | Value |

A value that is assigned to the outcome variable.

Use simple text to define values. Do not use variables for this field.

| | Visible (Expression) | An expression that determines when the button becomes visible. | | Enabled (Expression) |

An expression that determines when the button becomes enabled.

By default, a primary button becomes enabled when all the mandatory form fields are completed.

| | Navigation URL |

The URL where you are redirected after clicking the button.

You can use absolute or relative links and include variables, for example /search?q={{searchTerm}}.

| | Ignore payload | Ignores the form data and any validation and just sends the outcome value. | | Ignore validation | Ignores the form validation and just sends the payload and outcome value. | | Primary |

The button replaces the default Submit button.

You don't need to assign any value to a primary button if you just want to change the text of the button.

| ## Outcome variables Use the **Outcome variable name** to bind the value of a button to a process variable, for example `myVariableName`. By default, this variable is named `form__outcome`, where \ is the model key of your form. You can then use the value to build conditions, for example `${vars:equals(form_myForm_outcome, "Approved")}` or `${form_myForm_outcome == "Approved"}`. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://developer.collibra.com/workflows/designing-workflows/forms/form-outcomes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.