> For the complete documentation index, see [llms.txt](https://help.tahua.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tahua.io/knowledge-base/administrator-help-guides/applications/application-templates/field-events.md).
# Field Events
Field Events let you show or hide follow-up questions based on how an applicant answers a previous question. For example, if an applicant selects "Yes", they can be shown (and required to complete) a "Yes" follow-up field — while the "No" follow-up remains hidden, and vice versa.
**Setting up your fields**
Before configuring any Field Events, add **all** the fields you need to your form template — including any follow-up fields you only want to show conditionally. They will all be visible in the editor, but Field Events will control when applicants see them.
**Creating Field Events**
1. Click the **main question field** (the one whose answer will trigger the conditional logic).
2. In the left-hand panel, open **Field Events** and click **Create new Event**.
3. Set the **Condition** — for example, *If equals Yes*.
4. Set the **Action** — either:
* **Show element** — the follow-up field appears but applicants are not required to fill it in, or
* **Require element** — the follow-up field appears and must be answered.
5. Set the **Target** — select the follow-up field you want to show or require.
6. Repeat for each answer option. For example, a Yes/No question would typically have up to four events if the follow-up question is to be mandatory:
* *If Yes → Show* the Yes follow-up
* *If Yes → Require* the Yes follow-up
* *If No → Show* the No follow-up
* *If No → Require* the No follow-up
> **Tip:** If you want a follow-up to be mandatory, you'll need two events for that answer — one to **Show** the field and one to **Require** it. If you only need the follow-up to be optional, a single **Show** event is all that's required.
**What applicants see**
Applicants only ever see the follow-up question relevant to their answer. The screenshots below show this in action:
* **No answer selected** — only the main question is shown, with no follow-ups visible.
* **"Yes" selected** — the Yes follow-up field appears and is marked as required.
* **"No" selected** — the No follow-up field appears instead, also marked as required.
---
# 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://help.tahua.io/knowledge-base/administrator-help-guides/applications/application-templates/field-events.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.