Clone the Omniscript, Flexcard, and Integration Procedures for Remote Vehicle Action
Before you create a service process for remote actions, make sure you clone and activate
the Omnistudio components that power the experience for service agents.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions.
User Permissions Needed
To modify Omnistudio components:
Omnistudio Admin
Enable the Omnistudio Metadata setting and disable the Managed Package Runtime setting in
Setup.
From the App Launcher, find and select OmniStudio.
In the Omnistudio app, from the navigation bar, select
OmniScripts.
Click ConctVehicleRemoteActions/LockUnlockDoors and select the first
version of the omniscript.
Click New Version.
Click Activate Version.
The service process for remote door lock and unlock uses the second version of this
Omniscript as a request intake form by default. If you create more versions, make sure you
update the service process to select the active Omniscript version that you want to use. See
Create a Service Process Definition for Remote Vehicle Action.
In the Omnistudio app, from the navigation bar, select
Flexcards.
Click RemoteActionsDisplayDoorLockUnlockStatus and select the first
version.
Click Clone.
Modify the name and other details as necessary, and click
Clone.
Click Activate.
In the Omnistudio app, from the navigation bar, select Integration
Procedures.
Click RemoteActions/DoorLockUnlockStatus and select the first
version of the procedure.
Click Create Version.
Save your changes.
Click Activate Version.
Only one version can be active at a time. You can't edit the active version.
Repeat steps 7–10 for the RemoteActions/CreateCase integration procedure.
Make sure the new version of the Omniscript refers to the active integration procedure
versions.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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.