> 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.md).

# Forms

When you design workflows, you create forms to gather input from users or show them information. You use forms in user tasks and start forms to request a user to perform a manual action for a workflow to progress.

The Workflow Designer uses a JSON-based form definition structure as an output format. The form editor replaces the form properties previously used in the Flowable Eclipse Designer.

For an overview of all forms in a workspace, go to the **Models** page and filter the view to show only forms instead of all models.

## Page overview

The landing page shows a list of the existing forms.

![](https://2208542399-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAeKwSsP1BP6lDDArkTO2%2Fuploads%2Fgit-blob-99146f9d32b183f47a97eb157478d66a24a3b100%2Fdocs_workflows-designer-forms-overview.png?alt=media\&token=86096a12-9298-4a28-8dda-0bdefe21df1c)

From the forms view you can:

* See all the forms associated with a workspace.
* Go to a form editor by selecting one of the existing forms.
* Search by name and tag.
* Change the pagination and sorting.
* Change the display of forms to either a list or tiles.

For more details refer to the [Models](/workflows/designing-workflows/models.md) section.


---

# 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.md?ask=<question>&goal=<user_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.