Create an Action Launcher Deployment

Create a deployment that includes the component settings for the Action Launcher component. The settings determine the actions, such as flows, flow orchestrations, Omniscripts, and quick actions, which users can initiate from the Action Launcher search results. The Action Launcher component includes RecordAction junction objects, which associate an action with the parent record.

Required Editions

Available in: Lightning Experience

Available in: Starter, Professional, Enterprise, and Unlimited Editions with the required add-ons

User Permissions Needed
To create an Action Launcher deployment:	Industry Service Excellence permission set
To give users access to Omniscripts:	Omnistudio Admin permission set

Before you configure a deployment, set up the flows, flow orchestrations, Omniscripts, and quick actions that you want to show in the component.

Note You can't launch headless quick actions from Action Launcher because they don't open a modal window.

From Setup, in the Quick Find box, enter Action Launcher, and then select Deployments.
Click New Deployment.
Name your deployment.

Note Deployment names can’t contain special characters except underscores and can’t exceed 40 characters. Special characters other than underscores are automatically removed from the API Name field.
Select one or more action types.

Note The OmniScripts checkbox is visible only if Omnistudio is installed in the Salesforce org.
Select up to 10 objects for which you want to show specific quick actions.

A list of custom objects and allowlisted standard objects appears.

You can associate quick actions with specific objects to give the quick actions an object-specific, rather than global, context. When a user opens a page for a selected object, the component lists the global- and object-specific quick actions. On other pages, the component shows only the global quick actions.

For example, you define an object-specific quick action for Contacts. To show this quick action in the component on Contact pages, add Contact as a context object.

Note Flows, flow orchestrations, and Omniscripts always have a global context.
Select the actions to launch at run time.
You can add up to 1,000 actions in a deployment. Custom Aura components implementing these interfaces in the .cmp file are available for selection: lightning:isUrlAddressable, flexipage:availableForAllPageTypes, forceCommunity:availableForAllPageTypes.
- The Action Label column (1) shows the name of actions.
  - To modify the Omniscript names, go to OmniStudio | OmniScript | Setup and change the value of the Console Tab Title field.
  - To localize the name of an Omniscript, create a custom label with the translated text and include the custom label in the Console Tab Title field. Depending on the locale of users, Action Launcher shows the name of the Omniscript in the appropriate language.
  - The setup flow shows the Aura components that implement lightning:isUrlAddressable and flexipage:availableForAllPageTypes tags.
- A hyphen in the Context column (2) indicates a global flow, flow orchestration, or Omniscript action.
- The Context column shows Global (3) for a global quick action and the object name for an object-specific quick action.
If you want, you can select up to 10 frequently used actions to show on Action Launcher by clicking next to an action.
- To remove a selected action from Action Launcher, click .
- To reorder the actions, drag the actions to a different position on Action Launcher.
  The icon indicates a valid place to drop the action.
- To search for specific actions, use the search field.
Save your changes.
Go to Lightning App Builder.