Which statement about OmniScript naming is true?

Which statement about OmniScript naming is true?

• A. PascalCase is the naming convention.
• B. camelCase is the naming convention.
• C. snake_case is the naming convention.
• D. UPPERCASE is the naming convention.

Answer: (A)

OmniScript uses PascalCase (UpperCamelCase) for naming, where each word in the name starts with a capital letter and there are no spaces or separators. This approach makes names easy to read and consistent with other Salesforce artifacts like Lightning components and Apex classes, which helps when you’re organizing elements, steps, and actions in the designer and when referencing them elsewhere. Examples would look like AccountBalance, CustomerOnboardingFlow, or OrderTotal—clear, readable, and scalable as scripts grow. Using camelCase would start with a lowercase letter and can blur distinctions between elements and variables in some contexts. snake_case adds underscores, which isn’t aligned with how Salesforce metadata is typically named, and UPPERCASE is hard to read and reserved for constants. Therefore, PascalCase is the standard and best fit for OmniScript naming.

OmniScript uses PascalCase (UpperCamelCase) for naming, where each word in the name starts with a capital letter and there are no spaces or separators. This approach makes names easy to read and consistent with other Salesforce artifacts like Lightning components and Apex classes, which helps when you’re organizing elements, steps, and actions in the designer and when referencing them elsewhere.

Examples would look like AccountBalance, CustomerOnboardingFlow, or OrderTotal—clear, readable, and scalable as scripts grow.

Using camelCase would start with a lowercase letter and can blur distinctions between elements and variables in some contexts. snake_case adds underscores, which isn’t aligned with how Salesforce metadata is typically named, and UPPERCASE is hard to read and reserved for constants. Therefore, PascalCase is the standard and best fit for OmniScript naming.