# Template and its uses Know some validations and treatments that can be done with the Freemarker language when you use [**Template Transformer**](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/tools/template-transformer). For the examples you'll see next, consider this input JSON: ``` { "request": { "code": 213, "value": 4513423.1322, "description": " test request ", "items": [ { "name": "item 1", "quantity": 2 }, { "name": "item 2", "quantity": 1 } ] } } ``` ### LIST Enables you to make iterations in an array (list) in JSON. Imagine this function in the creation of a dynamic elements list in the output, that transforms JSON into XML. **Syntax** ``` <#list YourList of elements> block of information to be iterated. ``` **Example** Using the input informed in the beginning of this article, you can create a dynamic elements list using the template. What you must inform in the template is: ```xml <#list items as item> ${item.name} ${item.quantity} ``` **XML output** ```xml item 1 2 item 2 1 ``` {% hint style="info" %} Remember that the **Template** output is an XML in a string. {% endhint %} ### IF/ELSE You can use this function to validate some information. Even when its fields are null or empty, there's no great impact on your data transformation. **Syntax** ```xml <#if condition> Block of information in case the condition in if is true. <#elseif Syntax> Block of information in case the condition in elseif is true. <#else> Block of information in case none of the conditions are taken. ``` There's no limitation for the quantity of *elseif,* and it's also possible to use just an *if* without the *else* - it all depends on your need. **Example** Using the input informed at the beginning of this article, you can create a validation in which the "code" field needs to be greater than 0 (zero). What you must inform in the template is: ```xml <#if code > 0 >${code} ``` **XML output**\ If the condition is true: ```xml 213 ``` If the conditions is false: ```xml ``` Did you know the use of the function isn't limited to simple conditions? You can also use expressions to validate if the field exists (??) or if it has content (has\_content). **Syntax** ```xml <#if yourField?? && yourField?has_content> Block of information if the field exists and has content. <#else> Block of information if none of the conditions is taken. ``` {% hint style="info" %} It's possible to use logical operators for a more advanced condition. {% endhint %} ***&&*** - for AND. ***||*** - for OR. **Example** Now see how to improve the validation so that the *if* applied in the first case is used only if the "code" field exists and has content. What you must inform in the template is: ```xml <#if code?? && code?has_content> <#if code gt 0 >${code} ``` **XML output**\ If the condition is true: ```xml 213 ``` If the condition is false... ... and the "code" field has a value that is null, empty, or doesn't come in the input: ```xml ``` ### TRIM This function is used to remove the blank spaces at the beginning and in the end of a string. **Syntax** ```json ${YourField?trim} ``` **Example** Using the input informed at the beginning of this article, you can remove the blank spaces at the beginning and in the end of the "description" field". What you must inform in the template is: ```xml ${description?trim} ``` **XML output** ```xml test request ``` ### REPLACE This function is used to replace a pre-established value in the field. **Syntax** ``` ${YourField?replace} ``` **Example** Using the input informed at the beginning of this article, you can replace the "test" value in the description with "prod". What you must inform in the template is: ```xml ${description?replace("test","prod")} ``` **XML output** ```xml prod request ``` ### SLICE (SUBSTRING) This function is used when the field must have a determined size. **Syntax** ``` ${YourField[0..9]} 0 = initial value9 = final value ``` **Example** Using the input informed at the beginning of this article, you can determine for the field to have 10 characters only, even if it has a greater size. {% hint style="info" %} A good practice applicable to this function is to use IF/ELSE to validate the desired size for the field. That way, you avoid errors if the field is smaller than the established value. {% endhint %} What you must inform in the template is: ```xml <#if description?length < 10> ${description} <#else> ${description[0..9]} ``` **XML output** ```xml request ``` ### LOCALE This function is used in the template to set the location in a numeric value. **Syntax** ```xml <#setting locale="en_US"> ${YourField} <#setting locale="pt_BR"> ${YourField} ``` To use it, you must provide the tag before the dynamic field. Check how to do it in the examples below. **Example** Using the input informed at the beginning of this article, you can format the value to be in the legacy system standard. What you must inform in the template is: ```xml <#setting locale="en_US"> ${value} <#setting locale="pt_BR"> ${value} ``` **XML output** ```xml 4,513,423.13 4.513.423,13 ``` ### Custom If the desired format isn't accepted by your system, you can define the necessary number for formatting through the *"*number\_format" tag. It allows you to customize the number formatting. **Syntax** ```xml <#setting number_format="0.##"> ${yourField} ``` {% hint style="info" %} The hashtags (#) define the quantity of decimal places to be used. {% endhint %} **Example** Using the input informed at the beginning of this article, you can format the value to be in the legacy system standard. What you must inform in the template is: ```xml <#setting number_format="0.#"> ${value} <#setting locale="pt_BR"> ``` **XML output** ```xml 4513423.1 ```