Lightning Flow for Service Developer Guide

Lightning Flow for Service
Implementation Checklist
Create Flows
Associate Flows with Records
Using a Deployment
Using Process Builder
Using SOAP
Using Apex
Customize Pages with the Component
Integrate with Live Agent
Integrate with Open CTI
Other Resources
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Associate Flows to Records with Process Builder

Process Builder is a point-and-click automation tool that you can use to design processes that kick off when a new or updated record meets specific criteria. After you create, test, and activate your flows, associate the flows with a record by building a process. Use Process Builder to create a process that, when triggered, creates a RecordAction. A RecordAction represents an association between a flow and a record that kicked off the process. When the process is triggered, a RecordAction is created.

Associated flows for a record appear in the record’s Guided Action List component.

When you associate flows to records using Process Builder, you override the default channel-specific flows that you configured in a Guided Action List deployment.

Note

  1. Define the process properties.
    The process properties uniquely identify your process.
  2. Configure the process trigger.
    Every process includes a trigger, which tells the process when to start. How you configure that trigger depends on what type of process you’re creating.
  3. Add process criteria.
    Define the criteria that must be true before the process can execute the associated actions.
  4. Add actions to your process and create a record from the process.
    After you define a criteria node, create a record from the process when criteria are met. Actions are executed in the order in which they appear in the Process Builder.

    Flows is a supported Action Type in Process Builder. This type is different from creating a RecordAction. The Flows Action Type supports only flows that don’t have screens, and is invoked immediately when the process is triggered. Creating a RecordAction doesn’t invoke the flow; rather, it associates a record with the flow so that your users can run it.

    Note

    To associate flows to records, you must create a RecordAction.

    Important

    Specify the following.
    • Action Type: Create a Record
    • Record Type: RecordAction
    Set field values for the Create a Record action.
    Field Type Value
    Flow Picklist Specify the flow you want associated to the record.
    Order Number Specify the order of the flow among all flows associated with this record. Flows are ordered in comparison to other flows in their pinned or unpinned region. If two flows have the same order, then the flows are sorted by their last modified date.
    Parent Record ID Field Reference Specify the record associated with the flow. For most use cases, select the ID for the object you’ve selected for your process trigger. For example, if you used the contact object, set the value to [Contact].Id.
    Pinned Picklist Specify whether the flow is pinned to the top or bottom of the Guided Action List component. To display the flow between pinned flows, use None.
    Is Mandatory Boolean If set to True, the flow is required. After a mandatory flow is launched, if the user tries to close the tab or window, a message appears reminding the user to complete the flow.
    Hide Remove Action in UI Boolean If set to True, users can’t see the Remove option for the flow in the component. However, flows can still be deleted using the API.
  5. Activate your process.
When your criteria are met and your process runs, the flows that you specified are associated to the parent record.

Example

Create a process that adds a required flow for users to verify a contact’s information, like an email address, when their phone number changes.
  1. Choose the contact object, and start the process when a record is created or edited. Screen shot of the Process Builder start screen.
  2. Create criteria for when the [Contact].MobilePhone field changes. Screen shot of the criteria window with specified changes.
  3. Add a Create a Record action, and specify RecordAction for the Record Type
  4. Set field values for the record, pointing to your Verify_Information flow and the parent record ID. To encourage the user to complete this flow, specify the Is Mandatory field as True.Screen shot of the create a record window with specified changes.
  5. Activate the process.

    When the contact’s MobilePhone field changes, the Verify Information flow opens as a subtab on the contact record. An asterisk next to the flow indicates that it is mandatory.