---
schema_version: "1"
id: 5a3a2b9bc04e8ec425f159455ac2cd8460c4b8d3af0c1b7fd1a1535f53e835d5
title: Context Definitions for Actionable Event Orchestrations for Connected Assets
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/ca_aeo_context_definition.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.ca_aeo_context_definition.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5a974a7782cf1dd61a2da70ef40ea7247f7a9a8f8f2d0c8becf3f2a4aaa0ab28
description: 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.
products:
  - Industry Solutions
  - Cross Cloud
release: "264"
---
# 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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Lightning Experience</td></tr><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in: Automotive Cloud, Communications Cloud, Consumer Goods, Energy and Utilities Cloud, Manufacturing Cloud, and Media Cloud. <a href="https://help.salesforce.com/s/articleView?id=xcloud.ca_editions.htm&amp;release=264.0.0&amp;type=5" title="Review the supported products and editions for Connected Assets features.">View edition availability</a>.</td></tr></tbody></table>

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](https://help.salesforce.com/s/articleView?id=ind.context_service_create_context_definitions.htm&type=5&language=en_US). 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](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-connected_assets-264-0-0-production-enus/eb4c6dd7-4aef-4e97-9c56-46929d5b166e/images/icon_example.png)

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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col style="width:33.33333333333333%">
              <col style="width:33.33333333333333%">
              <col style="width:33.33333333333333%">
            </colgroup>
            <thead class="slds-text-title_caps ">
              <tr class="">
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d3436e91">Node Name</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d3436e94">Node Level</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d3436e97">Attributes</th>
              </tr>
            </thead>
            <tbody>
              <tr class="">
                <td data-label="Node Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e91 ">Event</td>

                <td data-label="Node Level" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e94 ">Parent Node</td>

                <td data-label="Attributes" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e97 "><a name="ca_aeo_context_definition__ul_elv_2ry_zbc"><!-- --></a>
                  <ul id="ca_aeo_context_definition__ul_elv_2ry_zbc">
                    <li>correlationId</li>

                    <li>assetUniqueIdentifier</li>

                    <li>assetType</li>

                    <li>eventId</li>

                    <li>id</li>

                    <li>priority</li>

                    <li>eventProviderId</li>

                    <li>eventTriggeredDate</li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Node Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e91 ">Faults</td>

                <td data-label="Node Level" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e94 ">Child of Event Node</td>

                <td data-label="Attributes" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e97 "><a name="ca_aeo_context_definition__ul_flv_2ry_zbc"><!-- --></a>
                  <ul id="ca_aeo_context_definition__ul_flv_2ry_zbc">
                    <li>ParentReference</li>

                    <li>faultCode</li>

                    <li>faultType</li>

                    <li>faultDescription</li>

                    <li>faultResolutionType</li>

                    <li>faultCodeSensorValues</li>

                    <li>freezeFrameId</li>

                    <li>code</li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Node Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e91 ">Event Data</td>

                <td data-label="Node Level" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e94 ">Child of Event Node</td>

                <td data-label="Attributes" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e97 "><a name="ca_aeo_context_definition__ul_sq4_bwr_bcc"><!-- --></a>
                  <ul id="ca_aeo_context_definition__ul_sq4_bwr_bcc">
                    <li>ParentReference</li>

                    <li>priority</li>

                    <li>airflowRate</li>

                    <li>particulateMatterLevel</li>

                    <li>filterStatus</li>

                    <li>ambientTemperature</li>

                    <li>ventilationPerformance</li>

                    <li>eventTriggeredDate</li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Node Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e91 ">Signal</td>

                <td data-label="Node Level" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e94 ">Child of Event Node</td>

                <td data-label="Attributes" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e97 "><a name="ca_aeo_context_definition__ul_glv_2ry_zbc"><!-- --></a>
                  <ul id="ca_aeo_context_definition__ul_glv_2ry_zbc">
                    <li>ParentReference</li>

                    <li>value</li>

                    <li>unit</li>

                    <li>name</li>

                    <li>timestamp</li>

                    <li>dataType</li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Node Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e91 ">Additional Event Attributes</td>

                <td data-label="Node Level" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e94 ">Child of Event Node</td>

                <td data-label="Attributes" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e97 "><a name="ca_aeo_context_definition__ul_ilv_2ry_zbc"><!-- --></a>
                  <ul id="ca_aeo_context_definition__ul_ilv_2ry_zbc">
                    <li>ParentReference</li>

                    <li>key</li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Node Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e91 ">Actions</td>

                <td data-label="Node Level" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e94 ">Child of Event Node</td>

                <td data-label="Attributes" class="slds-cell-wrap" style="vertical-align:top;" headers="d3436e97 "><a name="ca_aeo_context_definition__ul_jlv_2ry_zbc"><!-- --></a>
                  <ul id="ca_aeo_context_definition__ul_jlv_2ry_zbc">
                    <li>ParentReference</li>

                    <li>recordAlertSubject</li>

                    <li>recordAlertDescription</li>

                    <li>actionName</li>

                  </ul>
                </td>

              </tr>
            </tbody>
          </table>

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