# Launch from Salesforce (LFS)

**Launch from Salesforce (LFS)** denotes a functionality enabling users to directly initiate or access specific apps from **Salesforce**. This feature offers a streamlined process for seamlessly transferring data from the **Salesforce CRM** platform to our Valorx Fusion apps, eliminating the need for additional logins. 

Designers can launch an app directly from **Salesforce** and export **CRM** data to **Excel**, by selecting the "**Launch from CRM**" option in **Workflow and UX**. To initiate the launch, users should access **Salesforce**, navigate to the desired location, and click on the Custom Button / Quick Action created within **Salesforce**. 

* Start an App and open the **Workflow and UX** from Valorx Fusion Ribbon and locate **Workflow Settings** on the right-hand side.
* Click on the name of the Workflow to access its settings.
* Select the "**Launch from CRM**" option by checking the corresponding box. 

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

Click on **Launch from CRM instructions** and a popup window “Launch from CRM instructions” page will open which guides the users on how to configure a workflow to launch it from CRM. This page will have clear instructions with examples on how to create **Detail Page Buttons** and also shows how to add the buttons to the page layout.

![](/files/sNuOLxE2hKD0hsstV5hV)

Select the object from the "**Select Objects to open its Page Layouts**" dropdown.

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

Upon clicking "**Open layouts**", the Designer will be redirected to **Salesforce**, where they can access the page layout for the selected object.

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

To create a **Detail Page Button** before adding it to the **Page Layout**, please follow the instructions below:

1. Log into **Salesforce** using your login credentials.
2. Navigate to **Object Manager** and select the relevant object from **Label**.

<figure><img src="/files/0lI91HiYt8ohAZg5fDqF" alt=""><figcaption></figcaption></figure>

3. On the left-hand side, click on "**Button, Links, and Actions**".
4. Choose "**New Button or Link**" on the right-hand side.

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

5. Provide a descriptive Label that explains the button and the Name will display when we do a tab.
6. Fill in the details for Display Type, Behavior, Display Type, and Content Source in the respective fields as mentioned in the **Launch from CRM instructions** page.
7. Select the object from the "**Select Field Type**" dropdown.
8. Copy the URL from the **Launch from CRM instructions** page and paste it into **Context Source**.

<figure><img src="/files/VKcUTRxL2xKxmmCKiCi0" alt=""><figcaption><p>Launch from CRM instructions</p></figcaption></figure>

Here are two example images illustrating the **URL with** and **without inbound** integrations.

<figure><img src="/files/y69YHTNofBTTcEjAcaEX" alt=""><figcaption><p>Without  inbound integration</p></figcaption></figure>

<figure><img src="/files/ZgGS2TwqmdIo8k1dufqT" alt=""><figcaption><p>With inbound integration</p></figcaption></figure>

{% hint style="info" %}
Copy the URL with and without Inbound integrations as per the requirement.
{% endhint %}

9. Click **Check Syntax** to verify any syntax errors.
10. Click on **Save**.

<div align="left"><figure><img src="/files/5O13CJs5WfyH1Qr5nwkw" alt="" width="543"><figcaption></figcaption></figure></div>

11. A message will appear, prompting us to add the new button to page layouts. Now, click **Ok**.

<div align="left"><figure><img src="/files/nxhahGh7nBMwpgGdTHF3" alt=""><figcaption></figcaption></figure></div>

12. To return to the **Page Layout**, you can either select "Open layouts" from the **Launch from CRM instructions** page or choose "**Page Layout**" in **Salesforce**.

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

13. Below mentioned are the two sections where Designer should add the newly created **Detail Page Buttons**.
    1. For Salesforce Lightning UI, add the button to "**Salesforce Mobile and Lightning Experience Actions**" by selecting "**Mobile & Lightning Actions**" from Fields.
    2. For Salesforce Classic UI, add the button to "**Custom Button**" by selecting " **Buttons**" from Fields.
14. Click **Save** to finalize.

<figure><img src="/files/858I4NZkm91keFRFOTD7" alt=""><figcaption></figcaption></figure>

#### Runtime Experience on Windows Platform

Once, the Designer has completed the creation of the **Detail Page Button** and its addition to the **Page Layout**. Now, it is time to run the app by clicking on the created button for Windows.

1. Navigate to the **Sales** section and either select the Object from the header or search for it. Then, click on the record to open it.

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

2. On the right-hand side, choose the **Detail Page Button** from the dropdown menu.

<div align="left"><figure><img src="/files/tLpYO9OuvRrZKiDgCwyZ" alt="" width="300"><figcaption></figcaption></figure></div>

3. Confirm the popup to open up in a new window and click **Open Valorx Home**.&#x20;

<div align="left"><figure><img src="/files/dv6Hw6wMr1pLqppuqmex" alt=""><figcaption></figcaption></figure></div>

4. Before opening the app it will perform the steps of launch and set up in Valorx Fusion, then the Runtime app will open.

{% hint style="info" %}
The Valorx App will initiate or start from the designated Workflow where the LFC (Launch from CRM) has been set up.
{% endhint %}

#### Runtime Experience on Mac Platform

Once, the Designer has finished creating the **Detail Page Button** and adding it to the **Page Layout**, it is now time to run the app on **Mac**. Follow the steps below to run the app on the **Mac** platform.

1. Navigate to the **Sales** section and either select the Object from the header or search for it. Then, click on the record to open it.

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

2. On the right-hand side, choose the **Detail Page Button** from the dropdown menu.

<div align="left"><figure><img src="/files/tLpYO9OuvRrZKiDgCwyZ" alt="" width="300"><figcaption></figcaption></figure></div>

3. When the message "**Open this page?**" pops up, click on the **Open** button. This message displays when users have chosen the behavior to "**Display in a new window**".

<div align="left"><figure><img src="/files/paPB9zYOqXSsf2Im70RA" alt="" width="481"><figcaption></figcaption></figure></div>

4. When the message below appears, click on **Allow** to grant permission for downloading the file.

<div align="left"><figure><img src="/files/kQl7DQ7sn6qWGahbP1aR" alt=""><figcaption></figcaption></figure></div>

5. To launch the Runtime Valorx App on **Mac**, navigate to your downloads folder and open the downloaded file.

{% hint style="info" %}
Launch behavior from the **CRM** platform exhibits variations between **v1.9** and prior versions of the managed package compared to the **upcoming v2.0** release. This variation is applicable for **Windows** and **Mac** platforms. For more detailed information, please refer to the release notes of the managed package for [**version 2.0**](https://docs.valorx.com/Versions-and-release-notes/Versions-and-release-notes/managed-packages/version-2.0).
{% endhint %}

###


---

# Agent Instructions: 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:

```
GET https://docs.valorx.com/valorx-fusion/runtime/runtime-ux/launch-from-salesforce-lfs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.