Skip to main content

Latest Post

Custom Metadata Types vs Custom Settings vs Custom Labels

  Custom Metadata Types vs Custom Settings vs Custom Labels 💬 In plain words:  Three lookalikes: Custom Metadata = configuration that DEPLOYS with your code (best for app settings). Custom Settings = org/user-specific values, changeable at runtime (hierarchy type is great for bypass switches). Custom Labels = translatable text for the UI. 📌 Example:  API endpoint URLs per environment → Custom Metadata (deploys with code, sandbox vs prod values). A 'Bypass_Automation__c' checkbox an admin flips during data load → hierarchy Custom Setting. The word 'Submit' translated to Hindi → Custom Label. 🎬 Real-Life Example: The Fee Table Trapped Inside Code  Skyline charges a different delivery fee per city. Apex needs those rates on every booking. The Old/Bad Way:  if (city == 'Delhi') fee = 50. Else if (city == 'Mumbai') fee = 65. … Every rate change is a code change, a test run, and a deployment. Why this is bad:  Business data is trappe...

Adding Lightning Flow in LWC: A Full Dynamic Working Code Example

Introduction:

Lightning Web Components (LWC) are a powerful way to build user interfaces in the Salesforce Lightning Platform. They offer a modern JavaScript programming model with a component-based architecture. One common requirement in many applications is integrating Lightning Flow into LWC components. In this blog post, we will explore how to add Lightning Flow into an LWC component and provide a full dynamic working code example.

Prerequisites:


Before proceeding with this tutorial, make sure you have the following prerequisites:

  1. Salesforce Developer Account or Org.
  2. Knowledge of Lightning Web Components (LWC).
  3. Understanding of Lightning Flow and its capabilities.

Step 1: Create a New LWC Component


First, create a new Lightning Web Component by following these steps:

  1. Open your Salesforce Developer Account or Org.
  2. Navigate to the Developer Console.
  3. Create a new Lightning Web Component by clicking on "File" > "New" > "Lightning Web Component".
  4. Enter a name for your component (e.g., "AddLightningFlow").
  5. Click on the "Submit" button to create the component.

Step 2: Add the Lightning Flow Component


Next, we need to add the Lightning Flow component to our LWC. Open the newly created component and update the HTML and JavaScript files with the following code:


addLightningFlow:


<template>

  <lightning-card title="Add Lightning Flow" icon-name="utility:add">

    <div class="slds-m-around_medium">

      <lightning-button label="Start Flow" onclick={handleStartFlow} variant="brand"></lightning-button>

      <template if:true={flowStarted}>

        <lightning-flow runtime-id={flowRuntimeId}></lightning-flow>

      </template>

    </div>

  </lightning-card>

</template>


addLightningFlow.js:


import { LightningElement, track } from 'lwc';


export default class AddLightningFlow extends LightningElement {

  @track flowStarted = false;

  @track flowRuntimeId;


  handleStartFlow() {

    this.flowStarted = true;

  }


  connectedCallback() {

    // Dynamically generate the Flow name and version based on your requirements

    const flowApiName = 'Your_Flow_Name';

    const flowApiVersion = 'Your_Flow_Version';


    // Create the Flow URL

    const flowUrl = `/flow/${flowApiName}?flow.api.platform=lightning&flow.api.startRecordId=Your_Record_Id&flow.api.flowDevName=${flowApiName}&flow.api.flowVersionId=${flowApiVersion}`;


    // Fetch the Flow runtime ID

    fetch(flowUrl)

      .then((response) => response.json())

      .then((data) => {

        this.flowRuntimeId = data.flowRuntimeId;

      })

      .catch((error) => {

        console.error('Error fetching Flow runtime ID:', error);

      });

  }

}


Step 3: Customize the Code


Now, let's customize the code to fit your specific requirements:

  1. In the addLightningFlow file, modify the Lightning Card title and any other HTML elements according to your preference.
  2. In the addLightningFlow.js file, update the flowApiName with the actual API name of your Lightning Flow.
  3. Update the flowApiVersion with the version of your Flow.
  4. If needed, modify the flowUrl construction logic to include any additional parameters required by your Flow.

Step 4: Add the LWC Component to a Lightning Page


To see your LWC component with the Lightning Flow in action, add it to a Lightning Page. Follow these steps:

  1. Navigate to the Lightning App Builder.
  2. Create a new Lightning Page or edit an existing one.
  3. Drag and drop the "Add Lightning Flow" component onto the desired section of the page.
  4. Save the Lightning Page.

Conclusion:


In this blog post, we explored how to add Lightning Flow into an LWC component. We provided a full dynamic working code example that you can customize to fit your specific requirements. By following the steps outlined above, you can seamlessly integrate Lightning Flow capabilities into your LWC applications. Experiment with different flows and parameters to enhance your user experience and streamline your business processes. Happy coding!

Popular Posts

Salesforce LWC Code for Multi-Select Lookup

Introduction: In Salesforce Lightning Web Components (LWC), implementing a multi-select lookup field can enhance the user experience and provide greater flexibility for selecting multiple related records. In this blog post, we will walk through the process of creating a multi-select lookup field using LWC. We will cover the required code snippets and provide step-by-step instructions to help you implement this functionality in your Salesforce org.