> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/case-conditionality/conditionality-based-on-an-actions-checklist.md).
# Conditionality Based on an Action's Checklist
When using conditionality in your Case flows, you can use a number of types of system data as part of your condition, for example standard system work item fields and custom data fields.
We have now added the ability to use the results of individual checklist items, both global and local, in your conditions, letting you choose alternate routes depending on how a check has gone.
Watch this video to see how that can be done, or read below for more specifics and details:
{% embed url="" %}
Clicking on the dropdown will reveal the Actions that have checklists to choose from. They will be displayed in the order in which the Actions appear in the flow. Clicking on an Action will show the checks that you can choose to base your condition on, displayed in order in which they appear on the checklist.
You can only use the 'Equals' and 'Not Equals' conditions for conditions based on the results of a check in an Action's checklist, just as you would short text data fields.
The values you can create conditions for against a checklist item are "Yes", "No", and "NA" for Not Applicable. Be aware that these values are case sensitive and should be entered in the value field exactly as above within double quotes.
As standard, make sure to create an 'else' branch, to handle the flow when you're conditions are not met. At runtime, if the condition is not met, the system will execute the 'else' branch.
If you're using the advanced option to build a more complex expression, checklist items can also be incorporated here - once you've picked them from the dropdown list they'll be added into your expression with a unique identifying GUID.
{% hint style="info" %}
Note that you can only use checks from Actions in a previous step in your conditional expressions and you cannot use check from ad-hoc Actions.
{% endhint %}
Once you're happy with your condition settings, click 'validate' to ensure they'll work at runtime, then 'OK' to apply the condition to the Case flow.
---
# 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://docs.enate.net/enate-help/builder/builder-2021.1/case-configuration/case-conditionality/conditionality-based-on-an-actions-checklist.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.