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
Configure Components for Custom Tabs
Add Aura Components as Custom Tabs in a Lightning Experience App
Configure Components for Custom Actions
Configure Components for Record-Specific Actions
Create an Email as a Quick Action
Override Standard Actions with Aura Components
Standard Actions and Overrides Basics
Override a Standard Action with an Aura Component
Creating an Aura Component for Use as an Action Override
Packaging Action Overrides
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
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.

Packaging Action Overrides

Action overrides for custom objects are automatically packaged with the custom object. Action overrides for standard objects can’t be packaged.

When you package a custom object, overrides on that object’s standard actions are packaged with it. This includes any Lightning components used by the overrides. Your experience should be “it just works.”

However, standard objects can’t be packaged. As a consequence, there’s no way to package overrides on the object’s standard actions.

To override standard actions on standard objects in a package, do the following:

  • Manually package any Lightning components that are used by the overrides.
  • Provide instructions for subscribing orgs to manually override the relevant standard actions on the affected standard objects.