> 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/forms-events/form-life-cycle.md).

# Form life cycle

This page explains when form events are executed, this page does not include the datahub triggers

Since version 4.3 form definitions support events. In version 4.3 we only supported the "On form open" event but since 4.5 we support a number of new events.

Currently supported form definition events:

* On form open
* On form created
* On form saved
* On new form saved
* On form updated
* Before form saved
* Before form deleted

### When are events triggered

Below are three scenarios shown and when the events are triggered. All the steps are color coded.

**Blue**: actions which take place on the client (Web or app)

**Light blue**: conditions

**Yellow**: Are the events, when an event is executed all related action (Linked fields, calculations, action flows) are executed before the flow continues

**Green**: server side actions

#### Open form

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2F38w24frMCwqWBJhjPDmi%2FForm%20life%20cycle%20Open%20Form%20Event%20Image.png?alt=media&amp;token=a4edefb9-e167-4ca6-a95e-6201c2593fd9" alt=""><figcaption></figcaption></figure>

#### Save form

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FeAhY1BeUZnAO331D1kZw%2FForm%20lifecycle%20Save%20Form%20Event%20Image.png?alt=media&amp;token=35b9d8b4-734c-4f25-8ff0-79612a7d24bf" alt=""><figcaption></figcaption></figure>

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2FUSwYUymFub2f49SsjfYR%2FForm%20life%20cycle%20Perform%20Save%20Event%20Image.png?alt=media&amp;token=1d583e4f-c4f1-468e-aa0e-8e68cb762988" alt=""><figcaption></figcaption></figure>

#### Delete form

<figure><img src="https://870194474-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_kE41Rl4pOtwKfvvQq%2Fuploads%2Fd5sJuVPaGcrXQC3jS2f4%2FForm%20lifecycle%20Delete%20Form%20Event%20Image.png?alt=media&amp;token=0c4c1480-9a08-4761-83e3-12ff7aa619ee" alt=""><figcaption></figcaption></figure>


---

# 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/forms-events/form-life-cycle.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.