> 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/app-logic/forms/events.md). # Events Forms and fields support a number of events, these events can be used to trigger actions Form events * On form open: This event triggers when a new form is created or when a form is opened from the overview or a subformfield Field events

Field	On value change	On click	Notes
Basics
Label	✓	𐄂
Separator	𐄂	𐄂
Numeric	✓	𐄂
Textbox	✓	𐄂
Masked textbox	✓	𐄂
Date & time	✓	𐄂
Text area	𐄂	𐄂
Group	𐄂	𐄂
Image	✓	𐄂
Checkbox	✓	𐄂
Media	✓	𐄂
Signature	✓	𐄂
Location	✓	𐄂
Download	✓	𐄂
PDF	✓	𐄂
Barcode	✓	𐄂
Hyperlink	✓	𐄂
Youtube	𐄂	𐄂
Selection and filtes
List	✓	𐄂
Tree	✓	𐄂
Filter	✓	𐄂
Barcode filter	✓	𐄂
Calculations
Calculation	✓	𐄂
Time calculation	✓	𐄂
Specials and support
Subform	✓	𐄂	Triggers when a subform is added or edited
Grid list	✓	𐄂	Triggers when update data is received
Form data	𐄂	𐄂
State	✓	𐄂
Flow	✓	𐄂
Button	𐄂	✓
Button bar	𐄂	𐄂
Color	✓	𐄂

The on value change events trigger when the value of the field is changed by the user, data is received for linked fields or if the value is changed by a set value action. --- # 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://academy.any2info.com/any2info-academy/no-code-platform/app-studio/app-logic/forms/events.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.