`) attributes are configurable through the UI and XML.

Attribute Name	Attribute XML	Description
Parse template (default)	`doc:name`	Editable name for the component to display in the canvas.
N/A	`doc:id`	Automatically generated identifier for the component.
Content	`content`	String representing the template where embedded expressions are evaluated and replaced by their results.
Location	`location`	Location of the template file. Mule inserts values extracted from the message properties or variables into this file.
Output encoding	`outputEncoding`	Encoding of the payload that this component outputs.
Output mime type	`outputMimeType`	MIME type of the payload that this component outputs. For more information, see Using Reader and Writer Properties.
Parameters	N/A	Appends a key-value pair for a reader property to the value of the `outputMimeType` attribute. Multiple key-value pairs are allowed. Reader properties are specific to the MIME type. For example, see the JSON reader properties for `application/json`. To find other reader properties, navigate to a supported format from the DataWeave format documentation, and see Using Reader and Writer Properties.
Target Variable	`target`	Name of the variable in which you want to store message data. Names can only include numbers, characters, and underscores. For example, hyphens are not allowed in the name. See Enrich Data with Target Variables in the Mule documentation.
Target Value	`targetValue`	Value of the data to store in the target variable. By default, the value is the message payload (payload). The field accepts any value that a variable accepts: any supported data type, DataWeave expressions, the keywords `payload`, `attributes`, and `message`, but not the keyword `vars`. See Enrich Data with Target Variables in the Mule documentation.

## Examples The following examples use Parse Template to load data dynamically into HTML. ### Example: Processing Results of a Database Query Dynamically The following example uses Parse Template in a Mule application that loads employee data from a database into an HTML template. The flow returns the template-built output to the caller. ```xml

SELECT * FROM Employees WHERE id=#[attributes.queryParams['id']]

``` #### Template Content The template selects fields containing name, department, job title, start date, and employee type values from the input payload. ```html

First Name	Last Name	Department	Job Title	Start Date	Employee Type
#[payload['first_name']]	#[payload['last_name']]	#[payload['department']]	#[payload['job_title']]	#[payload['start_date']]	#[payload['employee_type']]

``` #### Input to Parse Template Assume that you start the flow with a URI that contains a query parameter that identifies the ID of an employee, such as `http://localhost:8081/getEmployee?id=1234`, and that the Select operation returns the following input to Parse Template: ```html { "first_name": "Melba", "last_name": "Roy Mouton", "department": "Computers", "job_title": "Assistant Chief of Research Programs", "start_date": "01/01/2021", "employee_type": "mathematician" } ``` #### Output of the Template The [example](#template) returns template-built output. The output is HTML with the selected employee data. ```xml

First Name	Last Name	Department	Job Title	Start Date	Employee Type
"Melba"	"Roy Mouton"	"Computers"	"Assistant Chief of Research Programs"	"01/01/2021"	"mathematician"

``` ### Dynamically Generating Data in HTML Rows The following example uses Parse Template on employee records that are represented as an array of objects. ```xml

``` #### Template Content The following template uses a DataWeave script to iterate over the input array and construct an HTML row for each object in the array: ```html #[%dw 2.0 output application/java --- payload.*Employee[0] map ((item) -> " ") joinBy ""]

First Name	Last Name	Department	Job Title	Start Date	Employee Type
" ++ (item.first_name default "") ++ "	" ++ (item.last_name default "") ++ "	" ++ (item.department default "") ++ "	" ++ (item.job_title default "") ++ "	" ++ (item.start_date default "") ++ "	" ++ (item.employee_type default "") ++ "

``` #### Input to Parse Template Assume that Parse Template component receives the following payload from Set Payload: ```html { Employee: [ { "first_name" : "Melba", "last_name" : "Roy Mouton", "department" : "Computers", "job_title" : "Assistant Chief of Research Programs", "start_date" : "01/01/2021", "employee_type" : "mathematician" }, { "first_name" : "Annie", "last_name" : "Easley", "department" : "Software Development", "job_title" : "Technical Lead", "start_date" : "06/02/2020", "employee_type" : "Rocket Scientist" } ] } ``` #### Output of the Template The [example](#template2) returns template-built output. The output is HTML with the dynamically produced rows and data from the objects in the array. ```xml

First Name	Last Name	Department	Job Title	Start Date	Employee Type
Melba	Roy Mouton	Computers	Assistant Chief of Research Programs	01/01/2021	mathematician
Annie	Easley	Software Development	Technical Lead	06/02/2020	Rocket Scientist

``` ## Special Characters Parse Template supports the use of expressions within a template and the use of literals within these expressions. The template recognizes certain special characters, such as the sequence `\#[` and quotations marks. You can escape such characters to treat them as regular characters. - `#[an-expression]`: Within a template, use the characters `#[]` to designate an expression. For example, a template can contain expressions within HTML elements, such as `#[upper("mulesoft")]`, which resolves to `MULESOFT`. Empty expressions (`#[]`) return an error, but empty strings, such as `#['']` or `#[""]` are valid expressions. - Sub-expressions: To resolve a sub-expression that is surrounded by quotation marks, surround the sub-expression with another `#[]`. For example, the four elements in the template snippet below contain the same sub-expression (`upper("world")`), either inside or outside of quotation marks. The first two return the same results. The last two do not process `upper("world")` because the sub-expression is inside the quotation marks but not surrounded by another `#[]`. Parse Template Snippet: ```XML #['hello #[upper("world")]'] #['hello ' ++ upper("world")] #['hello upper("world")'] #['hello ++ upper("world")'] ``` Output Values: ```XML hello WORLD hello WORLD hello upper("world") hello ++ upper("world") ``` - Escape character (`\`): Parse Template uses the character sequence `#[` to identify where an expression begins. To avoid this behavior and treat that sequence as literal characters, escape it with `\`, for example, `#[` returns `#[`. In addition, expressions can contain strings with special characters that you want to treat as regular characters. To escape any special characters within a string that is embedded inside an expression, append `\` to the character. Examples of special characters include the sequence `#[`, quotations marks (`'` or `"`), apostrophes (`'`), and `$`. It is not necessary to escape `\#` or `[` unless they are adjacent to one another in the string, with the `\#` preceding the `[`. Parse Template Snippet: ```XML \#[ #['abcd\#[-1234' ++ now() as String ++ '.log'] 'abc'def' #['abc\'def'] "xyz"xyz" #["xyz\"xyz"] #["abc\$DEF\#ghi\[JKL]"] ``` Output Values: ```XML #[ abcd#[-12342020-07-06T17:20:10.683-07:00.log 'abc'def' abc'def "xyz"xyz" xyz"xyz abc$DEF#ghi[JKL] ``` For more information, see [Escape Special Characters](https://docs.mulesoft.com/dataweave/2.4/dataweave-language-introduction#escape-special-characters).