> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/using-limio-for-salesforce/legacy-features/compliance-scripts.md).

# Compliance Scripts (Legacy)

Limio For Salesforce Flows support fetching dynamic information from zuora; these dynamic fields can be used elsewhere in the flow for building script that the agent can read to the customer as a confirmation and summary of the order being placed.

The dynamic fields are retrieved by an apex action exposed to the flow, for example, in the Limio For Salesforce Category: Get Acquisition Order Preview:

<figure><img src="/files/yoVvybarzSgnSTZT23CZ" alt=""><figcaption></figcaption></figure>

The action inputs should be mapped as follows:

* Order Items as the orderItems property of the lwc Limio Order - New
* Purchase Country as the purchaseCountry property of the lwc Limio Offer Catalog

<figure><img src="/files/iLDACjA57KqPW7ox7jpy" alt=""><figcaption></figcaption></figure>

Important: make sure the apex action is added to the flow after the 2 lwc components mentioned above.

Once the apex action is added to the flow, its outputs can be used to build a dynamic text; for example, a standard component of type "Display text" can be added to a flow screen, and OrderPreview outputs used as merge fields in the text body:

<figure><img src="/files/J2pgMI8VEYrNzrnZhPuJ" alt=""><figcaption></figcaption></figure>

The same dynamic text component can be dynamically rendered on the screen using ootb flow visibility rules:

<figure><img src="/files/SKom9xLDPKb2PZka31Xw" alt=""><figcaption></figcaption></figure>

Learn about dynamic variables mapping in other journeys in this article: [OrderPreview Apex Class](/integrations/setting-up-limio-for-salesforce/apex-classes/dynamic-variables.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 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.limio.com/integrations/using-limio-for-salesforce/legacy-features/compliance-scripts.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.