Configure the Action Launcher for Service Processes
Enable service representatives to find and launch service processes by using the Action
Launcher component. Create a deployment that groups your service actions, and then add the Action
Launcher to the Account record page.
Required Editions
Available in: Lightning Experience
Available in: Enterprise, Unlimited, and Developer Editions with
Financial Services Cloud and Unified Catalog.
User Permissions Needed
To associate the Omniscripts for service processes with an Action Launcher
deployment:
Customize Application
Create an action launcher deployment.
From Setup, in the Quick Find box, enter Action Launcher, and then
select Action Launcher.
Edit a deployment, or click New Deployment.
Click Next.
Enter a label and an API name for the deployment.
In Guidance to Show, select Omniscripts.
Click Next.
Move Account from Available Objects to Selected Objects.
The selected objects determine the objects where you can show the action.
Click Next.
In Select actions to add, select the specific Omniscript for your service process.
Add the action launcher to the account record page.
In Setup, click Object Manager.
In the Quick Find box, enter Account, and then select
Account.
Click Lightning Record Pages.
Select your active account record page.
Click Edit.
From the Components tab, drag the Action Launcher component onto the page canvas.
With the Action Launcher component selected, look at the Properties pane.
In the Action Launcher Deployment field, search for and select the action launcher
deployment that you created.
Save and activate your changes.
The Action Launcher component now appears on the Account page. Service representatives can use
the search bar within the component to find the required service process and open the process
immediately. If you’re setting up card-related service processes, you can also add the action
launcher component to the card record page.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.