> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/forms/supporting-footer-tools/states.md).

# States

**Category:** Footer

**Version:** 1.0

**Last updated:** May 21, 2026

**Author**: Any2Info

***

### Description

The States List Footer is a mini designer available exclusively within the Forms Designer. It is used for defining and managing state lists, which are in turn exclusively used by the State Field and Workflow Field.

The footer allows users to create, edit, and delete state lists. A state list consists of a single-level collection of state items that define the possible states a form message can have.

Each state item consists of:

* A unique name
* A translated display value using a display text
* An internal state
* An optional color
* An optional icon

The configured states are applied to saved form messages through the use of a State Field or Workflow Field.

***

### State Item Configuration

| Setting        | Required | Description                                                        |
| -------------- | -------- | ------------------------------------------------------------------ |
| Name           | Yes      | The internal name of the state item.                               |
| Display Text   | Yes      | The translated display value shown to users.                       |
| Internal State | Yes      | Determines the behavior and editability of the saved form message. |
| Color          | No       | Optional color associated with the state item.                     |
| Icon           | No       | Optional icon associated with the state item.                      |

***

### Internal States

There are 3 available internal states:

| Internal State  | Description                                                                                                                    |
| --------------- | ------------------------------------------------------------------------------------------------------------------------------ |
| Open            | Any user authorized for the form message can edit and save changes to the message.                                             |
| Closed          | The form message becomes locked and can no longer be changed.                                                                  |
| Closed for User | Changes can no longer be saved manually by users. Updates are only possible through the API, typically performed by dataflows. |

***

### Usage

The **States List Footer** is used to define workflows and status progressions for forms.

Typical use cases include:

* Approval workflows
* Ticketing states
* Order processing stages
* Validation statuses
* Automated processing flows
* Locking completed forms

The created state lists become selectable within State Fields and Workflow Fields.

***

### Behavior

* State lists are single-level and do not support nested states.
* State items determine both the visual representation and editability behavior of a form message.
* Colors and icons are primarily used for visual indication within forms and overview screens.
* Internal states directly control whether users can modify saved messages.

***

### Tips & Best Practices

* Use clear and recognizable display texts for end users.
* Use colors consistently to improve readability and workflow recognition.
* Reserve the **Closed for User** state for automated workflows and integrations.
* Keep state lists concise and logically ordered.

***

### Errors & Troubleshooting

| Issue                       | Cause                                          | Solution                               |
| --------------------------- | ---------------------------------------------- | -------------------------------------- |
| State list not selectable   | No State Field or Workflow Field exists        | Add a compatible field to the form     |
| Users cannot edit a message | The current state uses a locked internal state | Verify the configured internal state   |
| API updates fail            | Incorrect API or workflow configuration        | Verify the dataflow or API integration |
| Missing colors or icons     | Visual properties were not configured          | Edit the state item configuration      |

***

### Related Features

* State Field
* Workflow Field
* Forms Designer
* Dataflows
* API Integrations

***

### Changelog

| Version | Date         | Change                               |
| ------- | ------------ | ------------------------------------ |
| 1.0     | May 21, 2026 | Initial documentation version added. |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://academy.any2info.com/any2info-academy/no-code-platform/app-studio/application-design/forms/supporting-footer-tools/states.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.