> 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/fields-toolbox/specials-and-support/state.md).
# State
**Category**: Field
**Version**: 1.0
**Last Updated**: March 18, 2026
**Author**: Any2Info
***
### Description
The **State** field allows a form to take on a certain state. Defined by the **States** section in the a **FormDefinition.**
A **State** dictates what can happen with the form. Whether it is allowed to be saved or not.
***
### General Properties
The **State** field inherits general Field Properties such as ‘Font size’, ‘Font color’ and ‘Icon color’.
***
### Special Properties
The **File** field has a few special properties unique to it. These include:
| Name | Value | Explanation |
| -------------- | ---------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| State | State | The value is a state list created in the FormDefinition |
| Selected color | Color | A color value that indicates which of the State property values is selected currently |
| Display type | Set list of: **List**, **Checkbox list**, **Radio list**, **Dropdown** | How the state will look like when seen in the viewer |
***
### Tips & Best Practices
* Give the states in the list a proper DisplayText, otherwise it may not be clear what each value is.
* If the form states are determined through a different means than direct editing, try hiding the **State** field and set the Value of the field through an **ActionFlow**.
***
### Examples
Below is the most basic example of a **State** field
If the form is saved with “Open” selected, it will remain editable.
However if we decide to try and save the form with the “Closed” option selected, the following prompt will show:
The same goes for the “Closed for user” option.
If the **State** field is selected as a **FormOverview** field it will display the colors that are set in the State list, below is a simple example of “Closed for user”, “Open” and “Closed”.
States may also be edited outside the confines of the Viewers. Such as when using the **Export to Form** node.
***
### Changelog
| **Version** | **Date** | **Change** |
| ----------- | -------------- | -------------------------------- |
| 1.0 | March 18, 2026 | Initial document & documentation |
---
# 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/fields-toolbox/specials-and-support/state.md?ask=&goal=
```
`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.