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
Configure Components for Custom Tabs
Add Lightning Components as Custom Tabs in a Lightning Experience App
Add Lightning Components as Custom Tabs in the Salesforce App
Lightning Component Actions
Configure Components for Custom Actions
Configure Components for Record-Specific Actions
Override Standard Actions with Aura Components
Navigate Across Your Apps with Page References
Get Your Aura Components Ready to Use on Lightning Pages
Use Aura Components in Community Builder
Use Aura Components with Flows
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
Creating Apps
Styling Apps
Developing Secure Code
Using JavaScript
Working with Salesforce Data
Using Apex
Testing Components with Lightning Testing Service
Debugging
Performance
Reference
PDF

Newer Version Available

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

Lightning Component Actions

Lightning component actions are custom actions that invoke a Lightning component. They support Apex and JavaScript and provide a secure way to build client-side custom functionality. Lightning component actions are supported only in the Salesforce mobile app and Lightning Experience.
Available in: both the Salesforce mobile app and Lightning Experience
Available in: Essentials, Group, Professional, Enterprise, Performance, Unlimited, Contact Manager, and Developer Editions

My Domain must be deployed in your org for Lightning component actions to work properly.

Note

You can add Lightning component actions to an object’s page layout using the page layout editor. If you have Lightning component actions in your org, you can find them in the Mobile & Lightning Actions category in the page layout editor’s palette.

Lightning component actions can’t call just any Lightning component in your org. For a component to work as a Lightning component action, it must be configured for that purpose and implement either the force:LightningQuickAction or force:LightningQuickActionWithoutHeader interfaces. You must also set a default value for each component attribute marked as required.

If you plan on packaging a Lightning component action, the component the action invokes must be marked as access=global.