> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/wemreference/data-types/yes-no-boolean.md). # Yes / No (Boolean) ### Description The Yes/No datatype is used as Boolean (True/False) and has 2 specific values (Yes/True or No/False) besides the Unknown situation (which is not really a specific value), and is mostly used for conditional statements. When a YesNo field-value is displayed on a page, it will - based on the current language - display Yes or No or nothing when the situation is Unknown. In Expressions the True and False equivalents are implicated; Unknown should be regarded specifically if that situation may occur (check the [If-Unknown operator](/platform/wemreference/operators/if-unknown.md)) * `True` * `False` * `Unknown` ### Unknown An unknown value can be written as `UnknownBoolean`. --- # 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.wem.io/platform/wemreference/data-types/yes-no-boolean.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.