Create an actionable event orchestration to declaratively define the types of actions
you want to take for a specific event type. Automotive companies can create an orchestration that
maps an execution procedure to a specific type of critical telematics event, and to a context
definition that specifies the structure of the event payload. When an event of the specified type
is shared by an external system, a decision table matches the event type to the corresponding
actionable event orchestration record, and the execution procedure is automatically triggered. The
context variables in the procedure are used to retrieve the event data based on which the
procedure automatically creates and updates records.
Required Editions
| Available in: Enterprise, Unlimited, and Developer
Editions |
| User Permissions
Needed |
| To create an actionable event orchestration: |
Design Actionable Event Orchestration Processes |
| To create actionable event orchestration template records: |
Create Actionable Event Templates |
Make sure that the admin has created a context definition that outlines the
structure of the event request payload.
-
From the App Launcher, find and select Actionable Event
Orchestration.
-
Click New.
-
Enter a name.
The API name is populated automatically.
-
Select an event type.
-
If needed, select an event category.
-
For Usage Type, select Automotive.
-
If needed, select an event subtype related to the event type.
-
For Execution Procedure Type, select Expression-Set Based or
Flow-Based.
-
Select an expression set or a flow definition as the execution procedure name.
- If you are using an expression set as the execution procedure, you can also leave
this field blank so that the application automatically creates a procedure. The API name
of the actionable event orchestration record is used to name the execution procedure but
you can modify it later. Or, select an active expression set of usage type Actionable
Event Orchestration.
- If you are using a flow as the execution procedure, make sure the process type of
the flow is Actionable Event Orchestration, the flow is active, and uses contextId as an
input variable.
-
Select a context definition name, and if needed, select a context mapping name related
to the context definition.
-
Select Active.
The related execution procedure must be activated before you activate the actionable
event orchestration record.
-
To allow users to create similar orchestrations by cloning the record, select
Template.
You can't activate an orchestration record that you select as a template. After users
clone an actionable event orchestration template, they can activate the cloned
record.
-
Save your changes.