> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/interpolate-string.md).
# Interpolate String
## Description
This is a process node part that will safely interpolate text (ie resolve all variable constructions and create a text string complete with any HTML structures).
While this part has a wide variety of uses, two of the most common are:
* to safeguard any text input that could be used to execute malicious code
* to prepare dynamic text prior to printing to PDF
In Release 7.4 on, the part has the added feature of being able to run interpolation twice, on two different contexts (scope) which is useful when building a text string such as a query, and when the query base (fhir\_query) and target value (\_startvars.patient\_ref.fhir\_patient\_id) are in different contexts, as in the example below.
```
fhir_query = "Condition?patient=$(fhir_patient_id)",
_startvars = {
patient_ref = { fhir_patient_id = "123" }
}
```
## Editor Fields
| Field Name | Description/Use | Type/ Options | Mandatory/
Optional
|
| ---------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ----------------------------- |
| path | Enter the name of the data object where the result of the interpolation should be stored | data object | M |
| content | Enter the variable name (or text) that needs to be interpolated, using the $(...) construction | text | M |
| **Ist Interpolation** | | | |
| context | The scope or context in which to find the content variable.
By default, the current application context is used, but when a specific context is named, the interpolation will only look at the data-objects inside the named context.
| text | O |
| Escape $(...)-content
(v7.4+)
| Check this box if your content includes $(..) variables that should NOT be encoded.
Example:
mytext = "\Hello\
$(mytext) will appear as Hello (off) or \Hello\ (on)
If the content contains several interpolations only some of which need to be escaped, use the $(html(mytext)) construction to turn off escaping for specific variable.
| On\|Off | M |
| 2nd Interpolation
(v7.4+)
| This part can perform 2 step interpolation, which means that the result of the first interpolation is interpolated again.
This is a specific use case when the interpolation of data objects requires two different scopes.
In the example below, interpolating $(main\_context.caption) will return This is my name: Person X unless in the 2nd interpolation the Designer specifies the context as other\_context.person1
Download the example project into your Designer to see this working.
| | |
| context | As above | text | O |
| Escape $(...)-content
(v7.4+)
| As above | On\|Off | M |
## Example Project
An example project containing a simple demonstration of the 1st and 2nd interpolation is available [here](/release-9/example-gallery/example-projects-for-parts/interpolate-string-example-project.md).
---
# 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://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/interpolate-string.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.