Design actionable event orchestrations for critical vehicle events by setting up event
types, subtypes, and execution procedures. Use predefined context definitions and their
variables in an execution procedure, or extend the definitions to create additional nodes based
on the event data attributes shared by your telematics provider.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions.
Create Event Types and Subtypes for Vehicle Telematics Orchestration Define the types and subtypes of external or internal events so that the orchestration process can automatically trigger the relevant actions for a specific event. For example, Technical Faults can be an event type with multiple subtypes such as Engine Issue, Transmission Failure, or Oil Leak.
Create a Vehicle Telematics Orchestration 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.
Create an Execution Procedure for a Vehicle Telematics Orchestration An execution procedure outlines the steps for an actionable event orchestration. Use expression sets or flows as execution procedures. Using the standard and custom elements in the expression set builder, users create a series of filters, calculation conditions, aggregation conditions, and eligibility parameters to define the type of action for a specific event. Using the elements in a Flow Builder and custom Apex actions, users can create complex business rules to trigger actions. The actions are automatically executed each time a decision table matches a specific event to the corresponding orchestration record.
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.