Lightning Aura Components Developer Guide

Introducing Aura Components
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
Customize Flow Screens Using Aura Components
Configure Components for Flow Screens
Control Flow Navigation from an Aura Component
Flow Navigation Actions
Customize the Flow Footer with an Aura Component
Build a Custom Navigation Model for Your Flow Screens
Customize the Flow Header with an Aura Component
Dynamically Update a Flow Screen with an Aura Component
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
Use Aura and Lightning Web Components Outside of Salesforce 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
Debugging
Performance
Reference
PDF

Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.

Flow Navigation Actions

The availableActions attribute lists the valid navigation actions for that screen.

A screen’s available actions are determined by:

  • Where in the flow the screen is. For example, Previous isn't supported on the first screen in a flow, Finish is supported for only the last screen in a flow, and you can never have both Next and Finish.
  • Whether the flow creator opted to hide any of the actions in the screen's Control Navigation settings. For example, if Pause is de-selected, the Pause action isn't included in availableActions.

Here are the possible actions, their default button label, and what's required for that action to be valid.

Action Button Label Description
NEXT Next Navigates to the next screen
BACK Previous Navigates to the previous screen
PAUSE Pause Saves the interview in its current state to the database, so that the user can resume it later
RESUME Resume Resumes a paused interview
FINISH Finish Finishes the interview. This action is available only before the final screen in the flow.