> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/designer/documents-and-assessments/forms-conditional-logic.md).

# Forms Conditional Logic

Welkin's Form Designer supports conditional logic to show and hide fields on forms. To use this functionality, the sections, questions and answer fields must be added to the form first. Once all of the questions and answer fields have been added, go to the "Conditions" tab within the form configuration to add your show/hide logic.

In the following scenario, I want to show a question "Enter LMP" or "Enter EDD" based on which date type will be used to calculate the gestational age.

Condition logic needed:

If date type = LMP then show "Enter LMP" question

If date type = EDD then show "Enter EDD" question

**Steps to configure the conditions for the scenario above:**

1. Go to the "Conditions" tab in the form configuration.
2. Click "Add Element".
3. Choose the section of the form where the fields you want to show/hide are located
4. Choose the field you want


---

# 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://docs.welkinhealth.com/designer/documents-and-assessments/forms-conditional-logic.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.