Filter and Match Actionable Event Orchestrations Decision Table for Connected Assets

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. Each event sent to Salesforce has a type and can also have a subtype and a category. Based on the type, subtype, and category of an event, the decision table provides a context definition, a context mapping, and an execution procedure for the event. For example, if an actionable event orchestration is defined for an Environmental Condition type and High Ambient Temperature subtype, the decision table automatically matches each event of that type and subtype to the corresponding execution procedure.

Required Editions

Available in: Lightning Experience

Available in: Automotive Cloud, Communications Cloud, Consumer Goods, Energy and Utilities Cloud, Manufacturing Cloud, and Media Cloud. View edition availability.

The input values of the decision table are Event Type, Event Subtype, and Event Category. The output values of the table are Context Definition, Context Mapping, Execution Procedure, and Execution Procedure Type.

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

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

Example

Grant Johnson, an energy technologies company, manages a lot of heating, ventilation, and air conditioning (HVAC) systems. Their HVAC systems send telematics events to Salesforce via an external system.

The admin at Grant Johnson creates three actionable event orchestrations.

Actionable Event Orchestration	Name	Context Definition	Context mapping	Event Type	Event subtype	event category	execution procedure
1	AEO1	CD_1	CM_1	Energy Management	High Power Surge	Critical Events	The execution procedure creates an asset milestone for each event of the specified type.
2	AEO2	CD_2	CM_1	Performance Monitoring	High Humidity Level	Monitoring Event	The execution procedure creates a record alert and a case for each event of the specified type.
3	AEO3	CD_1	CM_2	Performance Monitoring	Low Pressure Level	Critical Events	The execution procedure creates a work order for each event of the specified type.

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

{
    "eventId" : "123",
    "assetUniqueIdentifier": "HVAC1234",
    "eventType": "Performance Monitoring",
    "eventSubtype": "High Humidity Level",
    "eventCategory" : "Monitoring Event",
    "event data": [{
            "correlationId" : "1001",
            "priority": "High",
            "eventProviderId": "P123",
            "assetId": "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	CD_2
Context Mapping	CM_1
Execution Procedure Name	AEO2
Execution Procedure Type	ExpressionSet-Based