# Invoke Flows from Manage Subscriptions Console (Legacy)

**LFS version:** requires Limio for Salesforce v12.02 or later

Limio for Salesforce exists in two major forms: a single-page app called Manage Subscriptions (legacy), and a set of Flows representing all Limio-supported actions and journeys.

Some of the recently released features of the Limio for Salesforce package are only available at the flow level and not on the Manage Subscriptions page, so we introduce a middle layer that allows invoking flows on subscription actions within the Manage Subscriptions page.

This should be considered an intermediate step towards a full migration to Limio Flows.

All Limio Flows are managed OOTB, so start with *creating a copy of the flow you want to trigger* from the Manage Subscriptions app context. In order to map a Manage Subscriptions action to a Limio Flow Copy, navigate to the Custom Metadata Types => ic Assist Config => Subscription Actions.

Proceed with mapping an action to a copied flow by editing a JSON object in the *Config* field: add or edit an **actionToFlowMap** property in the following format **{ "action\_API\_name": "limio\_flow\_copy\_API\_name" }**.

Supported action API names are:

"remove",\
"switch",\
"renew",\
"refund",\
"change\_address",\
"change\_payment",\
"redeem\_gift",\
"pause\_print".

Flow API name can be found a flow details page.

Example:

<pre><code><strong>"actionToFlowMap": {
</strong><strong>   "remove": "Limio_Order_Cancel_Copy__c"
</strong><strong>}
</strong></code></pre>

<figure><img src="https://3950144701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxTpA9AeeNYx1ml6UpHj%2Fuploads%2FcpGDQikxGXXmTsxHZasd%2Fimage.png?alt=media&#x26;token=8e9f9e0e-6287-408c-bdbc-e9eb974245cc" alt=""><figcaption></figcaption></figure>

If the config doesn't include an **actionToFlowMap** property at all, then all actions are executed as usual - in the Manage Subscriptions app context.

Actions mapped to an existing *active* Limio Flow Copy in the **actionToFlowMap** property trigger a modal window to open with a referenced flow inside. For the actions that are *not* mentioned in the **actionToFlowMap**, the behaviour remains unchanged.

<figure><img src="https://3950144701-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FKxTpA9AeeNYx1ml6UpHj%2Fuploads%2F6KNQRXTeULrBHWbN5RBT%2Fimage.png?alt=media&#x26;token=c2787e1a-e227-4d3d-bdb8-c12a6956a9da" alt=""><figcaption></figcaption></figure>
