> 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/order-total-position/post-order-customisation.md).

# Post-Order Flows Customisation

**LFS version:** v12.49 or later

All Limio for Salesforce flows end with a summary component that shows an overview of the order details and order processing events, after submitting an order to Limio.

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

In order to allow for additional custom logic to be built into the flow **after** our summary screen, we introduce the following enhancements:

### New **output** properties

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

**isSuccess**\
A Boolean property: **true** if an order was successfully processed, and **false** if it failed.

**orderProcessingEvents**:\
A string representing a serialised object with all order processing steps in the following format:

```json
{
   "actionName":"New",
   "external_id":"345741VMN55",
   "id":"event-9a065d1bdd887a7ff93ca65b96b7c6a8",
   "order_reference":"4Q0PEHNNC8F0",
   "process":{
      "status":"processed",
      "steps":[
         {
            "name":"nexi",
            "success":true
         },
         {
            "name":"zuora",
            "success":true
         },
         {
            "name":"salesforceV3",
            "success":true
         }
      ]
   },
   "status":"submitted",
   "type":"order.new"
}
```

In case of a failure, it also includes error messages:

```json
{
   "actionName":"New",
   "external_id":"34574EDVVDO",
   "id":"event-62fd68214c51822e3186da2dca600b10",
   "order_reference":"32VLK22J2HGG",
   "process":{
      "status":"error",
      "steps":[
         {
            "name":"nexi",
            "success":true
         },
         {
            "error":{
               "message":"Request failed: https://rest.apisandbox.zuora.com/v1/orders [undefined] 'N/A' is not a valid currency code or name."
            },
            "name":"zuora",
            "success":false
         }
      ]
   },
   "status":"error",
   "type":"order.new"
}
```

**orderReference**\
A reference generated by Limio once an order is submitted and reached the system.

### New **input** properties

Controlling an order of actions is important and if you have other components in the flow dependent on the output of our Order Summary, you can hide the footer from the Order Summary screen, preventing users from advancing unless the Order submission is successful, or an order processing has finished, and trigger navigation to the next screen automatically.

1. **Navigate to next Screen on Success**

   This feature triggers the Flow to move to the next screen (similar to clicking the "Next" button in the Screen Flow) after a successful submission.
2. **Navigate to next Screen on Failure**\
   Similar to the above, allows our customers to enhance error handling.
3. **Number** (in seconds) of timeout before trigger navigate next

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


---

# 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/order-total-position/post-order-customisation.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.