You are here:
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.
This information is for Omnistudio for Managed Packages. For Omnistudio on standard runtime, see Omnistudio Help.
| Product | Unique Name |
|---|---|
| Integration Procedures | 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. For example, Type=Auto and SubType=CreateUpdateQuote create a unique identifier Auto_CreateUpdateQuote. |
| Data Mappers | Interface Name: The Data Mapper Interface Name must be unique. The Interface Name can contain letters and numbers, dashes, and underscores, but no spaces. |
| Omniscripts | 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. For example, an Omniscript where Type=account, SubType=Create, and Language=English generates an LWC named accountCreateEnglish. |
| Flexcards | Name + Author: The combination of the card Name and Author 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. |
