Loading
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
            Key Components of Actionable Event Orchestration for Connected Assets

            You are here:

            1. Salesforce Help
            2. Docs
            3. Connected Assets

            Key Components of Actionable Event Orchestration for Connected Assets

            Set up a touchless process that identifies key events based on information shared from an asset, applies qualification and eligibility conditions on the event data, and performs actions in Salesforce, such as creating records.

            Required Editions

            Available in: Lightning Experience
            Available in: Automotive Cloud, Communications Cloud, Energy and Utilities Cloud, Manufacturing Cloud, and Media Cloud. View edition availability.
            • Actionable Telematics Event Business API and Platform Events
              Different methods are available to bring asset events into Salesforce and execute actions on the event. Use the Actionable Orchestration Source Event platform event to publish events or use the Orchestration Inbound Events business API to trigger events. The platform event and the business API can be easily integrated with any external system, such as telematics provider systems.
            • 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.
            • 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.
             
            Loading
            Salesforce Help | Article