Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Connected Assets
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Context Definitions for Actionable Event Orchestrations for Connected Assets

            You are here:

            1. Salesforce Help
            2. Docs
            3. Connected Assets

            Context Definitions for Actionable Event Orchestrations for Connected Assets

            When an event is triggered in an asset, the event details are sent to Actionable Event Management via the Inbound Event API or the Actionable Orchestration Source Event platform event. The event's request payload contains the event's details. Create a context definition to represent the structure of an event's request payload. Then, use the context definition to supply the required event data to the execution procedure that perform the actions for the event. The nodes and attributes of the context definition must match the event attributes in the API payload. For example, if the request payload contains parameters for asset identifier, output power, health score, and activation status for a sensor error event, create a context definition with nodes that map to these parameters.

            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.

            Context definitions contain a set of information required to execute a process and help in the efficient retrieval and usage of data across applications in Salesforce. To learn how to create a context definition, see Create Context Definitions. You can create multiple context definitions depending on the type of request payload structure you expect for each event type and subtype. You can also create multiple context mappings for the same context definition.

            You can add a context tags as variables in an execution procedure.

            Example
            Example

            Durkheim Coolers is a food processing technologies company that wants to trigger orchestrations for critical issues in their air distribution systems, such as low airflow rate, high particulate matter level, and malfunctioning filters. The events originate in the telematics system, are sent to the integration layer, and then sent to Salesforce. The type of data that’s sent from the external telematics system for such events has fixed attributes that describe the event.

            Here’s a typical request payload.

            {
    "eventId" : "123",
    "assetUniqueIdentifier": "FOA1234",
    "eventType": "PerformanceAndDiagnostic",
    "eventSubtype": "MalfunctioningFilters",
    "eventCategory" : "Notification",
    "event data": [{
            "priority": "High",
            "eventProviderId": "P123",
            "airflowRate" : "1001",
            "particulateMatterLevel" : "1001",
            "filterStatus" : "string",
            "ambientTemperature" : "1001",
            "ventilationPerformance" : "1001",
            "eventTriggeredDate": "2023-05-16T15:13:41.236Z"
     }],
    "faults": [{
            "code": "string",
            "type": "string",
            "description": "string",
            "resolutionType": "string",
            "codeSensorValues": "string",
            "freezeFrameId": "string"
     }],
    },
    "signals": [{
            "value": "string",
            "timeStamp": "2023-05-16T15:13:41.236Z",
            "dataType": "string",
            "unit": "string",
            "name": "string"}

            The admin creates a context definition called Air Distribution System Diagnostics Events. Review the node structure of the context definition that corresponds to the event data attributes in the request payload.

            Node Name Node Level Attributes
            Event Parent Node
            • correlationId
            • assetUniqueIdentifier
            • assetType
            • eventId
            • id
            • priority
            • eventProviderId
            • eventTriggeredDate
            Faults Child of Event Node
            • ParentReference
            • faultCode
            • faultType
            • faultDescription
            • faultResolutionType
            • faultCodeSensorValues
            • freezeFrameId
            • code
            Event Data Child of Event Node
            • ParentReference
            • priority
            • airflowRate
            • particulateMatterLevel
            • filterStatus
            • ambientTemperature
            • ventilationPerformance
            • eventTriggeredDate
            Signal Child of Event Node
            • ParentReference
            • value
            • unit
            • name
            • timestamp
            • dataType
            Additional Event Attributes Child of Event Node
            • ParentReference
            • key
            Actions Child of Event Node
            • ParentReference
            • recordAlertSubject
            • recordAlertDescription
            • actionName

            The admin can specify which attributes are used as input and which attributes are used as output in the execution procedure. For example, the Event Provider ID is an input value used to identify the external telematics system as the source of the event. But the Asset Unique Identifier is both an input and an output because Durkheim Coolers wants to create a record alert for each malfunctioning filters event triggered for a specific asset.

            Each node and attribute of the context definition has a corresponding context tag. When designing the execution procedures, users can easily identify the attributes from the context tags

             
            Loading
            Salesforce Help | Article