---
schema_version: "1"
id: f39b8c8da3bd93d43e1b19857b9d88c8770f1fe5f0532e07d30e898631d464ee
title: Service Process Generation for Telemetry Action Definitions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/auto_telemetry_defn_actn_mgmt_svc_proc_generation.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.auto_telemetry_defn_actn_mgmt_svc_proc_generation.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 5bee3660aa2b9d0c9156d16f2915d7744ac764db22cc572da13dd768f02aeaf2
description: Generate a service process from a telemetry action definition record. Review the changes to be made for the Omniscript-based intake form, update the predefined integration definition and activate the generated service process. Create a catalog and category on Unified Catalog for the service process to launch it from the Action Launcher.
products:
  - Automotive
release: "264"
---
# Service Process Generation for Telemetry Action Definitions

Generate a service process from a telemetry action definition record. Review the changes to be made for the Omniscript-based intake form, update the predefined integration definition and activate the generated service process. Create a catalog and category on Unified Catalog for the service process to launch it from the Action Launcher.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition"><colgroup><col style="width:100%"></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: <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>
          <col>
        </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="d120275e72">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e72 ">To create and update Telemetry Action Definitions:</td>

            <td class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d120275e72 ">Telemetry Definition and Action Management Designer and Unified Catalog
              Admin</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e72 ">To generate service process:</td>

          </tr>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" rowspan="2" style="vertical-align:top;" headers="d120275e72 ">To access Unified Catalog:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e72 ">Unified Catalog Admin</td>

          </tr>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e72 ">Context Service Admin</td>

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

Once a service process is generated, users can customize the intake form and fulfillment flow if required from Unified Catalog, or use the predefined intake form and fulfillment flow with a few changes. A case is generated when a service process is initiated to track the asynchronous details.

1. Generate a service process for a telemetry action definition.
    1. From Setup, in the Quick Find box, enter and select **Telemetry Definition and Action Management**.
    2. Go to the **Action Definition** tab.
    3. Open your telemetry action definition record.
    4. Click **Generate Process**.
2. Add a Retrieve Integration Procedure to the Omniscript-based intake form.
    1. From the App Launcher, search and select **Unified Catalog**.
    2. Open the Products tab from the navigation menu.
    3. Open the generated service process for your telemetry action definition record with the same name.
        
        You can also access this record by directly clicking the link in the Related Process field on your telemetry action definition record in Setup.
    4. Go to the Intake Form tab by clicking **Next** twice.
    5. Click **Open Editor**.
    6. Under Remote Properties, for the NAMED\_CREDENTIAL key, enter the named credential of your Mulesoft asset.
    7. Activate the Omniscript.
3. Add a Data Mapper Transform Action to the Omniscript-based intake form.
    1. Repeat steps a. to e. in step 2.
    2. Drag and drop a Data Mapper Transform Action component from the Data Mapper Actions section in the Elements panel.
    3. On the properties panel, for Data Mapper name, select **DataMapperTransformDemoActionOmniscriptSubmitIPAction**.
    4. Open the data mapper.
    5. Create mappings for the JSON input fields and map them to the Custom Attributes node.
    6. Save your changes.
4. Add a Set Values component to the Omniscript-based intake form.
    1. Repeat steps a. to e. in step 2.
    2. Drag and drop a Set Values component from the Standard Actions section in the Elements panel.
    3. On the properties panel, for name, enter Set RecordId.
    4. Click **Add Element Value**.
    5. For Element Name, enter RecordId.
    6. For Value, enter %recordId%.
    7. Save your changes.
    8. Activate the Omniscript.
5. Save the Intake Form.
6. Update the integration definitions for retrieve or submit integration procedures as created for the Omniscript-based intake form in step 2.
    1. From Setup, in the Quick Find box, enter and select **Integration Definitions**.
    2. Open the Connected Services Remote Operations integration definition.
    3. Enter these details for a submit integration procedure.
        
        <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
                <colgroup>
                  <col style="width:50%">
                  <col style="width:50%">
                </colgroup>
                <thead class="slds-text-title_caps ">
                  <tr class="">
                    <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d120275e391">Fields</th>
                    <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d120275e394">Submit</th>
                  </tr>
                </thead>
                <tbody>
                  <tr class="">
                    <td data-label="Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e391 ">Apex Class</td>

                    <td data-label="Submit" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e394 ">industriesconnectedservice.TelemetryRemoteOperationProcessIntegrationProvider</td>

                  </tr>
                  <tr class="">
                    <td data-label="Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e391 ">Attribute Name and Attribute Value</td>

                    <td data-label="Submit" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e394 "><a name="auto_telemetry_defn_actn_mgmt_svc_proc_generation__ul_prc_whs_pgc"><!-- --></a>
                      <ul id="auto_telemetry_defn_actn_mgmt_svc_proc_generation__ul_prc_whs_pgc">
                        <li dir="ltr">Connected Service Named Credential</li>

                        <li dir="ltr">The named credential of your Mulesoft asset. </li>

                      </ul>
                    </td>

                  </tr>
                  <tr class="">
                    <td data-label="Fields" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e391 ">Attribute Name and Attribute Value</td>

                    <td data-label="Submit" class="slds-cell-wrap" style="vertical-align:top;" headers="d120275e394 "><a name="auto_telemetry_defn_actn_mgmt_svc_proc_generation__ul_hnd_yhs_pgc"><!-- --></a>
                      <ul id="auto_telemetry_defn_actn_mgmt_svc_proc_generation__ul_hnd_yhs_pgc">
                        <li dir="ltr">Remote Action URL Path</li>

                        <li>The URL that Mulesoft uses. For
                          example,<kbd>/digitalTwin/v1/telemetry/{sourceSystemIdentifier}/command</kbd>.</li>

                      </ul>
                    </td>

                  </tr>
                </tbody>
              </table>
    4. Save your changes.
7. Activate the service process.
8. Create a Catalog and Category for the generated service process.
    1. From the App Launcher, search and select **Unified Catalog**.
    2. Open the Catalogs tab from the navigation menu.
    3. Click **New**.
    4. Enter a name and description for the catalog.
    5. Select a Catalog Type.
    6. Save your changes.
    7. Open the created catalog record.
    8. Under Categories, click **New**.
    9. Enter a name and description for the category.
    10. Save your changes.
    11. Open the created category record.
    12. From the dropdown Add menu, click **Existing Products and Services**.
    13. Select your service process and save your changes.
9. Add the Action Launcher component on a vehicle record page.
    1. From the App Launcher, search and select **Vehicles**.
    2. Open a vehicle record page and from the Setup icon dropdown, click **Edit Page**.
    3. On the Lightning App Builder, drag and drop the Action Launcher component from the Standard section of the Components panel.
    4. For Action Launcher Configuration, select **Unified Catalog**.
    5. For Service Catalog, select the catalog created in the step above.
    6. Save your changes.

When a customer support rep launches a service process from the Action Launcher on a vehicle record page, and fills and submits the Omniscript-based intake form, the predefined fulfillment flow that's attached to the generated service process updates the case record created after the action's execution.