Lightning Flow for Service Developer Guide

Lightning Flow for Service
Supported Apps, Channels, and Objects
Considerations
Sample Use Case
Implementation Checklist
Create Flows
Associate Flows with Records
Create Custom Console Pages
Access the Guided Action History
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

Lightning Flow for Service Considerations

Learn about how packaging and the sharing model can impact your Lightning Flow for Service implementation.
Packaging

Packaging is only minimally supported in this release. In certain cases, channel or guided action settings are not included, and you must manually add referenced flows. We plan to support packaging fully in a future release.

Note

When you package up your implementation, processes and flows that reference a flow through RecordAction are included in the package. For example, if Flow A creates a RecordAction that references Flow B, adding Flow A to a package also adds Flow B to the package.

When you add your app to the package, here’s what’s included:
  • All the objects in the app
  • For each object, the associated page layouts, Lightning pages (including the page with the Guided Action List component), active processes, and quick actions. Channel or guided action settings are not included.
  • If a process includes flow actions, those flows are included.

If you package a process or flow that creates RecordAction records, the associated flow is included in the package only if you used the Picklist type to select the flow. If you manually entered the flow name or used a formula, you must manually add the flow to the package.

Note

Sharing Model
Access to the RecordAction object is determined by a user’s access to the associated parent record. This sharing model applies to access in the user interface, API, and Bulk API.
  • If the user has Read access on the record that the flow is associated with, the user can perform all operations (Create, Read, Update, and Delete) on the corresponding RecordAction.
  • If the user doesn’t have Read access on the record that the flow is associated with, then the user doesn’t have access to the associated RecordAction.

When using RecordAction and Salesforce Object Query Language (SOQL), make sure that your queries filter by the parent record. To filter by the parent record, use a where clause for users without Modify All Data permission. Otherwise, the query doesn’t work. If the user has Modify All Data permission, a where clause isn't necessary to filter correctly.

Here’s an example of a where clause for RecordAction.

SELECT fields FROM RecordAction WHERE RecordId=ENTITY_ID

Note