Lightning Aura Components Developer Guide

What Is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Aura Component Bundle Design Resources
Use Aura Components in Lightning Experience and the Salesforce Mobile App
Navigate Across Your Apps with Page References
Get Your Aura Components Ready to Use on Lightning Pages
Use Aura Components in Experience Builder
Use Aura Components with Flows
Considerations for Configuring Components for Flows
Flow Screen Components vs. Flow Action Components
Which Custom Lightning Component Attribute Types Are Supported in Flows?
Design Attribute Considerations for Flow Screen Components and Local Actions
Runtime Considerations for Flows That Include Aura Components
Customize Flow Screens Using Aura Components
Create Flow Local Actions Using Aura Components
Embed a Flow in a Custom Aura Component
Display Flow Stages with an Aura Component
Add Components to Apps
Integrate Your Custom Apps into the Chatter Publisher
Using Background Utility Items
Use Lightning Components in Visualforce Pages
Add Aura Components to Any App with Lightning Out (Beta)
Lightning Container
Communicating with Events
Communicating Across the DOM with Lightning Message Service
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Working with Salesforce Data
Testing Components with Lightning Testing Service
Debugging
Performance
Reference
PDF

Newer Version Available

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

Design Attribute Considerations for Flow Screen Components and Local Actions

To expose an attribute in Flow Builder, define a corresponding design:attribute in the component bundle's design resource. Keep these guidelines in mind when defining design attributes for flows.
Supported Attributes on design:attribute Nodes
In a design:attribute node, Flow Builder supports only the name, label, description, and default attributes. The other attributes, like min and max, are ignored.

For example, for this design attribute definition, Flow Builder ignores required and placeholder. 

1<design:attribute name="greeting" label="Greeting" placeholder="Hello" required="true"/>
Calculating Minimum and Maximum Values for an Attribute
To validate min and max lengths for a component attribute, use a flow formula or the component's client-side controller.
Modifying or Deleting design:attribute Nodes
If a component’s attribute is referenced in a flow, you can’t change the attribute’s type or remove it from the design resource. This limitation applies to all flow versions, not just active ones. Remove references to the attribute in all flow versions, and then edit or delete the attribute in the design resource.