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:

Screenshot_2022-08-04_at_10.37.41.png

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

Screenshot_2022-08-04_at_10.40.00.png

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:

Screenshot_2022-08-04_at_10.54.16.png

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

mceclip0.png

Learn about dynamic variables mapping in other journeys in this article: .