> 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/case-conditionality-examples-and-formatting.md).

# Case Conditionality - Formatting Examples

See below some formatting directions to help when building conditions within your Case flows.

### Using a Date / Time in a Condition

Format to enter in value colum&#x6E;**: new DateTime(yyyy,MM,dd,hh,mm,s)**

&#x20;                                                      E&#x58;**: new DateTime(2020,05,30,12,00,00)**

![](/files/-MXq8A1xOD0CclVmY1Yw)

### **Using a Date in a Condition**

Format to enter in value colum&#x6E;**: new DateTime(yyyy,MM,dd)**

&#x20;                                                      E&#x58;**: new DateTime(2020,05,26)**

![](/files/-MXq8aruJXNn1fHHLW9M)

### **Using Short Text in a Condition**

Format to enter in value colum&#x6E;**: “String”**

&#x20;                                                      E&#x58;**: “To test Short text 1”**

![](/files/-MXq8t-8Z0jTYTDfmYAO)

### **Using Long Text in a Condition**

Format to enter in value colum&#x6E;**: “String”**

&#x20;                                                      E&#x58;**:** **"To test long text 1"**

![](/files/-MXq9We1cO_4u0NpUyY4)

### **Using a Decimal Number in a Condition**

Format to enter in value colum&#x6E;**:** x.y**M**

&#x20;                                                     E&#x58;**:** **1.2M**

![](/files/-MXq9lRaY-v6ZK7shxPo)

### **Using a Whole Number in a Condition**

Format to enter in value colum&#x6E;**: X**

&#x20;                                                      E&#x58;**: 10**

![](/files/-MXq9xbV-YIO4wH-cSNS)

### **Using a Boolean (Checkbox) in a Condition**

Format to enter in value colum&#x6E;**: true/false**

&#x20;                                                      E&#x58;**: true**

![](/files/-MXqADShDQnQd4uPi22r)

### **Using a Multi-level List in a Condition**

Format to enter in value colum&#x6E;**: “Level1.Level2.Level3”**

&#x20;                                                      E&#x58;**:** **"CONTACT NO.HOUSE.1234567"**

![](/files/-MXqASrmzoNS5h-kp2ts)

{% hint style="info" %}
Note: if you have only configured two levels that a dot should be placed after the second value (see below example).
{% endhint %}

![](/files/-MXqQETlqQEOQqEw0cqN)

### **Using a List in a Condition**

Format to enter in value colum&#x6E;**: “String”**

&#x20;                                                      E&#x58;**:** **"Blackberry"**

![](/files/-MXqAeqG_3FgBqMxaVb-)

### **Using an Email in a Condition**

Format to enter in value colum&#x6E;**: “Email Address”**

&#x20;                                                      E&#x58;**:** **"<jhon@gmail.com>"**

![](/files/-MXqApbwQOHd9K-t7KHN)


---

# 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/case-conditionality-examples-and-formatting.md?ask=<question>&goal=<endgoal>
```

`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.
