Lightning Components Developer Guide

What is the Lightning Component Framework?
Quick Start
Creating Components
Using Components
Lightning Component Bundle Design Resources
Use Lightning Components in Lightning Experience and the Salesforce Mobile App
Navigation in Lightning Experience and the Salesforce Mobile App Using Page References
Get Your Lightning Components Ready to Use on Lightning Pages
Use Lightning Components in Community Builder
Use Lightning Components with Flows
Considerations for Configuring Components for Flows
Customize Flow Screens Using Lightning Components
Configure Components for Flow Screens
Control Flow Navigation from a Lightning Component
Flow Navigation Actions
Customize the Flow Footer with a Lightning Component
Build a Custom Navigation Model for Your Flow Screens
Customize the Flow Header with a Lightning Component
Dynamically Update a Flow Screen with a Lightning Component
Create Flow Local Actions Using Lightning Components
Embed a Flow in a Custom Lightning Component
Display Flow Stages with a Lightning Component
Add Components to Apps
Integrate Your Custom Apps into the Chatter Publisher
Use Lightning Components in Visualforce Pages
Add Lightning Components to Any App with Lightning Out (Beta)
Lightning Container
Communicating with Events
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Using Apex
Lightning Data Service
Testing Components with Lightning Testing Service
Debugging
Fixing Performance Warnings
Reference
PDF

Newer Version Available

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

Control Flow Navigation from a Lightning Component

By default, users navigate a flow by clicking standard buttons at the bottom of each screen. The lightning:availableForFlowScreens interface provides two attributes to help you fully customize your screen's navigation. To figure out which navigation actions are available for the screen, loop through the availableActions attribute. To programmatically trigger one of those actions, call the navigateFlow action from your JavaScript controller.

When you override the screen's navigation with a Lightning component, remember to hide the footer so that the screen has only one navigation model.