Recommended Naming Conventions

This topic provides recommended naming conventions for various items in Automation Studio.

Consistency

The primary recommendation is to ensure consistency throughout each project and, ideally, across all projects in an organization.

Element Type Prefixes

When naming any element, for example a workflow or callout, it is useful to add a prefix to identify the element's type, for example wf (for workflow) or cll (for callout). Suggested prefixes are listed in the table below.

Recommended Conventions

The table below recommends naming conventions per item.

Item

Prefix

Case Style

ExamPle
Callout cll Upper CamelCase

  • cllAddAccount
Data Collection dc Upper CamelCase

  • dcAgentActivity
Event Handler eh Upper CamelCase

  • ehRespondToEmail
Screen Element se Upper CamelCase

  • seSearchButton
User-Defined Function Name fn UpperCamelCast

  • fnCalculateSalesTax
User-Defined Function Parameter fnp lower camelCase

  • fnpCostPrice
User-Defined Type Name ty Upper CamelCase

  • tyPhysicalAddress
User-Defined Type Parameter typ lower camelCase

  • typStreetName
Variable (to store constant value) vc UPPERCASE

  • vcSALES_TAX
Variable (to store variable data) (Option 1) - lower camelCase

  • streetAddress
(Option 2) i Upper CamelCase

  • iStreetAddress
Workflow Name wf Upper CamelCase

  • wfGetInformation
Workflow Input Parameter wi lower camelCase

  • wiEmailText
Workflow Step - Upper CamelCase

  • GetEmailAddress