Considerations for Configuring Components for Flows

Before you configure Lightning components for a flow, determine whether it should be available in flow screens or as flow actions and understand how to map data types between a flow and a Lightning component. Then review some considerations for defining attributes and how components behave in flows at runtime.

Lightning components in flows must comply with LockerService restrictions.
Flows that include Lightning components are supported only in Lightning runtime.

Note

Flow Screen Components vs. Flow Action Components
You can make your Lightning component available in flow screens or as a flow action. When choosing between the flow interfaces, consider what purpose the component serves in the flow.
Which Aura Attribute Types Are Supported in Flows?
Not all Aura data types are supported in flows. You can map only these types and their associated collection types between flows and Lightning components.
Design Attribute Considerations for Flow Screen and Action Components
To expose an attribute in the Cloud Flow Designer, define a corresponding design:attribute in the component bundle's design resource. Keep these guidelines in mind when defining design attributes for flows.
Runtime Considerations for Flows That Include Lightning Components
Depending on where you run your flow, Lightning components may look or behave differently than expected. The flow runtime app that's used for some distribution methods doesn't include all the necessary resources from the Lightning component framework. When a flow is run from the Cloud Flow Designer or a direct flow URL (https://yourDomain.my.salesforce.com/flow/MyFlowName), some base Lightning components look different because styling resources are missing, and force and lightning events aren’t handled.

Lightning Components Developer Guide

See Also