Filter and Match Actionable Event Orchestrations Decision Table

The Filter and Match Actionable Event Orchestrations decision table matches an event that’s sent to Salesforce from an external system to the corresponding Actionable Event Orchestration record. When a vehicle telematics event is sent to Salesforce, the decision table finds the input values for Event Type, Event Subtype, and Event Category. Based on the type of event, the table gives the output values for the context definition, context mapping, and the execution procedure. For example, if an actionable event orchestration is defined for an engine malfunction event type, the decision table automatically matches each event of that type to the corresponding execution procedure.

Required Editions

Available in: Enterprise, Unlimited, and Developer Editions

Make sure that the decision table is active before you activate the execution procedures and actionable event orchestrations.

For orgs provisioned after Spring '25, refresh the decision table because we have updated the inputs parameters.

Note Event Type is a required input field for the decision table, while Event Subtype and Event Category are optional fields. If the incoming event has no subtype or category specified, the decision table can still match the event to the corresponding execution procedure based on the event type.

Let’s take an example of Neo Motors. The user has created two actionable event orchestrations.

Record 1
- Name: AEO1
- Context Definition Name: CD_1
- Context Mapping Name: CM_1
- Event Type: Transmission Failure
- Event Subtype: Low Transmission Fluid
- Event Category: Critical Events
The execution procedure for the AEO1 orchestration creates a record alert and a case for a vehicle for each event of the specified type.
Record 2
- Name: AEO2
- Context Definition Name: CD_1
- Context Mapping Name: CM_1
- Event Type: Transmission Failure
- Event Subtype: Clogged Filter
- Event Category: Critical Events
The execution procedure for the AEO2 orchestration creates a record alert for a vehicle for each event of the specified type.

A telematics event is triggered for a connected vehicle that has a request payload that looks like this.

{
    "eventId" : "123",
    "assetUniqueIdentifier": "VIN1234",
    "eventType": "Transmission Failure",
    "eventSubtype": "Low Transmission Fluid",
    "eventCategory" : "Critical Events",
    "event data": [{
            "correlationId" : "1001",
            "priority": "High",
            "eventProviderId": "P123",
            "vehicleId": "ABC1234",
            "eventTriggeredDate": "2023-05-16T15:13:41.236Z"
     }],
    "faults": [{
            "code": "string",
            "type": "string",
            "description": "string",
            "resolutionType": "string",
            "codeSensorValues": "string",
            "freezeFrameId": "string"
     }]

Based on the input data, the decision table provides an output.

Output Parameter Name	Output Parameter Value
Context Definition Name	CD_1
Context Mapping Name	CM_1
Execution Procedure Name	AEO1

If the execution procedure for the AEO1 orchestration is active, a record alert and a case are automatically created with the details of the transmission failure event.