---
schema_version: "1"
id: 438b59ee681f0f89959fa2530b41382bdacff33ee4ca552dad338b6f057ccacb
title: Create an Execution Procedure for a Vehicle Telematics Orchestration
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/auto_aeo_designcreate_an_execution_procedure.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.auto_aeo_designcreate_an_execution_procedure.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a43171efeb34a6618794ef612d0f806a7501cb68054e4559b137afb46731d12c
description: An execution procedure outlines the steps for an actionable event orchestration. Use expression sets or flows as execution procedures. Using the standard and custom elements in the expression set builder, users create a series of filters, calculation conditions, aggregation conditions, and eligibility parameters to define the type of action for a specific event. Using the elements in a Flow Builder and custom Apex actions, users can create complex business rules to trigger actions. The actions are automatically executed each time a decision table matches a specific event to the corresponding orchestration record.
products:
  - Automotive
release: "264"
---
# Create an Execution Procedure for a Vehicle Telematics Orchestration

An execution procedure outlines the steps for an actionable event orchestration. Use expression sets or flows as execution procedures. Using the standard and custom elements in the expression set builder, users create a series of filters, calculation conditions, aggregation conditions, and eligibility parameters to define the type of action for a specific event. Using the elements in a Flow Builder and custom Apex actions, users can create complex business rules to trigger actions. The actions are automatically executed each time a decision table matches a specific event to the corresponding orchestration record.

### 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: <strong>Enterprise</strong>, <strong>Unlimited</strong>, and <strong>Developer</strong> Editions.</td></tr></tbody></table>

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d15206e63">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d15206e63 ">To create an execution procedure:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d15206e63 ">Design Actionable Event Orchestration Processes</td>

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

1. Open an actionable event orchestration record and click **Open Procedure** from the quick actions menu.
    
    You can also click the record hyperlink on the Execution Procedure Name field.
    
    - For expression set-based orchestrations, the expression set builder opens with the most current active version.
    - For flow-based orchestrations, the Flow record page opens and you can click **Open Flow** to open the flow builder.
2. For resources within each element of a flow or expression set, use context variables or local variables to store input and output values.
3. Click **Save**.
4. To start using the execution procedure, click **Activate**.
    
    You can activate the related actionable event orchestration record only after you activate the execution procedure.

![Example](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-automotive-264-0-0-production-enus/55098325-b838-4fed-9e79-8cfa2d7b33a3/images/icon_example.png)

Example

Neo Motors wants to create an expression set-based execution procedure that automatically creates a record alert and a case for event type Critical Issues. The event type is related to multiple diagnostic codes. The record alert is displayed on the vehicle record page, and service agents can immediately take notice of the issue to further diagnose it. And the case can be used to collaborate with the customer and take the investigation further.

- P0110: Malfunction in the intake air temperature sensor circuit.
- P0500: Malfunction in the vehicle speed sensor.
- P0706: Fault in the transmission range sensor circuit range.
- P0442: System leak in a vehicle’s evaporative emission control system.

The user wants to add a filter to the procedure so that alerts and cases are only created for the codes P0101 and P0706. Here’s how they create the procedure.

- Drag the List Group element to the canvas.
- Drag the List Filter element to the canvas and place it inside the list container.
- In the List Filter element, add these values.
    
      
    | Field | Value | Details |
    | --- | --- | --- |
    | Filter Condition Requirements | Any Condition Is Met (OR) | A condition is created with two clauses. |
    | Resource | code | The diagnostic code is used as the filter condition. |
    | Operator | Equals | Exact code values are used to filter events. |
    | Value | P0101 | Malfunction in the intake air temperature sensor circuit qualifies as an event. |
    | Resource | code | The diagnostic code is used as the filter condition. |
    | Operator | Equals | Exact code values are used to filter events. |
    | Value | P0706 | Fault in the transmission range sensor circuit range qualifies as an event. |
- Drag the Record Action element to the canvas and place it inside the list container after the list filter.
- In the Record Action element, add the following values.
    
      
    | Field | Value | Details |
    | --- | --- | --- |
    | Operation | Create | Creates a record. |
    | Object | Record Alert | A record alert record is created. |
    | EffectiveDate | eventTriggeredDate | A context variable is created as part of the context definition mapping. The eventTriggeredDate is populated as the value. |
    | IsActive | isActive | A local variable created within the builder with the default value as True. |
    | ValidUntilDate | validUntilDate | A local variable created within the builder with the default value as a date two years in the future. |
    | WhatId | VehicleId | A context variable is created as part of the context definition mapping. The vehicleId is populated as the What ID. |
    | Subject | recordAlertSubject | A context variable is created as part of the context definition mapping. The recordAlertSubject is populated as the value. |
    | Description | recordAlertDescription | A context variable is created as part of the context definition mapping. The recordAlertDescription is populated as the value. |
- Drag another Record Action element to the canvas and place it inside the list container after the first record action.
- In the Record Action element, add the following values.
    
      
    | Field | Value | Details |
    | --- | --- | --- |
    | Operation | Create | Creates a record. |
    | Object | Case | A case record is created. |
    | Origin | caseOrigin | A local variable created within the builder with the default value as Vehicle Sensor. |
    | Status | caseStatus | A local variable created within the builder with the default value as New. |
    | Description | caseDescription | A context variable is created as part of the context definition mapping. The fault description is populated as the case description. |
    | AccountId | acccountId | A context variable is created as part of the context definition mapping. The owner name is populated as the Account ID. |
    | Subject | caseSubject | A context variable is created as part of the context definition mapping. The fault code is populated as the case subject. |