---
schema_version: "1"
id: 12e5cc72569de7b587c5dc152864afad1726f8528d7df4962073e79e09f9a242
title: Naming Conventions in Omnistudio for Managed Packages (Managed Package)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/os_omnistudio_for_vlocity_naming_conventions.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_for_vlocity_naming_conventions.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 8e17039f6d44c90131a00453a1c15e065b1042faa886f96deb207d13da107566
description: For the managed package runtime, follow the recommended naming conventions when you create an Omnistudio for Managed Packages component, such as an Omnistudio Data Mapper, a Flexcard, an Integration Procedure, or an Omniscript.
products:
  - Omnistudio
release: "264"
---
# Naming Conventions in Omnistudio for Managed Packages (Managed Package)

For the managed package runtime, follow the recommended naming conventions when you create an Omnistudio for Managed Packages component, such as an Omnistudio Data Mapper, a Flexcard, an Integration Procedure, or an Omniscript.

![Managed Package app icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-omnistudio_for_managed_packages-264-0-0-production-enus/aa2554ec-624a-4ee6-8da4-6435670e6e62/resources-global/_corporate/images/managedpackageicon.png) This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see [Omnistudio Help](https://help.salesforce.com/s/articleView?id=xcloud.os_omnistudio_standard.htm&language=en_US).

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col>
        <col>
      </colgroup>
      <thead class="slds-text-title_caps ">
        <tr class="">
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d146969e46">Product</th>
          <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d146969e49">Unique Name</th>
        </tr>
      </thead>
      <tbody>
        <tr class="">
          <td data-label="Product" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e46 ">Integration Procedures</td>

          <td data-label="Unique Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e49 ">
            <p>Type_SubType: The Type and SubType are joined by an underscore to create a
              unique identifier used to call the Integration Procedure. The Name Type and
              SubType can contain letters, numbers, and special characters, but no
              spaces.</p>
            <p style="margin-bottom:0;">For example, <kbd>Type=Auto</kbd> and
              <kbd>SubType=CreateUpdateQuote</kbd> create a unique
              identifier <kbd>Auto_CreateUpdateQuote</kbd>.
            </p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Product" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e46 ">Data Mappers</td>

          <td data-label="Unique Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e49 ">Interface Name: The Data Mapper Interface Name must be unique. The Interface
            Name can contain letters and numbers, dashes, and underscores, but no
            spaces.</td>

        </tr>
        <tr class="">
          <td data-label="Product" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e46 ">Omniscripts</td>

          <td data-label="Unique Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e49 ">
            <p>TypeSubtypeLanguage: Type, SubType, and Language combine to create a unique
              identifier that becomes the name of a compiled Omniscript's Lightning web
              component. The Type and SubType can contain letters and numbers, but no spaces
              or underscores and can’t exceed 104 characters.</p>
            <p style="margin-bottom:0;">For example, an Omniscript
              where&nbsp;<kbd>Type=account</kbd>,&nbsp;<kbd>SubType=Create</kbd>,
              and&nbsp;<kbd>Language=English</kbd>&nbsp;generates an LWC
              named&nbsp;<kbd>accountCreateEnglish</kbd>.</p>
          </td>

        </tr>
        <tr class="">
          <td data-label="Product" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e46 ">Flexcards</td>

          <td data-label="Unique Name" class="slds-cell-wrap" style="vertical-align:top;" headers="d146969e49 ">Name + Author: The combination of the card&nbsp;Name&nbsp;and&nbsp;Author&nbsp;must be unique
            in your Org. Name and Author can only contain letters, numbers, and
            underscores, begin with a letter, not include spaces, not end with an
            underscore, and not contain two consecutive underscores. </td>

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