Skip to main content
Version: 1

Launch Flow Future

  • Category

    • Scheduled

    • Future Call

    • Flow

  • Flow Icon

Overview

The Launch Flow Future component in Plinqx is adept at executing Salesforce flows in a future context, akin to Apex future calls. This functionality is especially beneficial for executing transactions or processes that need to be run asynchronously or outside the immediate context of your primary integration flow.

Inputs

  1. flowName:

    Specify the API name of the flow you intend to launch.

  2. namespace:

    If the flow is part of a managed package, provide the namespace of the package. Leave this undefined for non-managed package flows.

  3. param1-10 Name:

    Up to ten parameters are allowed. Provide the name of each input variable in the flow being called.

  4. param1-10 Value:

    Corresponding to each parameter name, provide the value that you want to pass to the flow.

  5. useFutureLaunch:

    A Boolean value (required) indicating whether to launch the flow in a future context.

Outputs

  1. errorMessage:

    Any error message encountered during the execution of the flow.

  2. isSuccess:

    A Boolean indicating whether the flow execution was successful (True) or not (False).

Example Scenario - Post-Transaction Customer Feedback

Scenario Overview:

A Salesforce org wants to send a customer feedback survey one day after a service case is closed. The survey is managed through a separate Salesforce flow, which needs to be triggered asynchronously after the case closure.

Implementation with Launch Flow Future Component:

  1. Flow Setup for Case Closure:

    • Create a Salesforce flow triggered upon the closure of a service case.
  2. Adding Launch Flow Future Component:

    • Integrate the Launch Flow Future component into the flow, setting it to trigger the customer feedback survey flow.
  3. Configuring Inputs:

    • 'flowName' is set to the API name of the feedback survey flow.

    • 'namespace' is defined if the feedback flow is part of a managed package.

    • 'param1 Name' and 'param1 Value' are used to pass the case ID and customer contact details to the feedback survey flow.

    • 'useFutureLaunch' is set to true, scheduling the feedback survey flow to run the next day.

  4. Executing Future Flow:

    • Upon case closure, the primary flow executes the Launch Flow Future component, scheduling the feedback survey flow for execution the following day.
  5. Monitoring and Handling Outputs:

    • Any errors encountered during the scheduling are captured in 'errorMessage'.

    • 'isSuccess' indicates the successful scheduling of the feedback survey flow.

Results:

By implementing the Launch Flow Future component, the Salesforce org efficiently automates the process of sending post-transaction feedback surveys. This approach ensures timely engagement with customers while maintaining the efficiency of the service team’s workflow.