Naming conventions

A naming convention is used to differentiate the various versions of a project as it moves through the lifecycle of updating, deploying, co-deploying, undeploying, and archiving. Version names must be unique.

When you create a version, a version number, which you can change, is sequentially applied automatically.

An acronym is created when a project is created. Acronyms are generated by using the first 7 characters of the version name that fall into these types, if there is no conflict:
  • Capital letters (A-Z), numbers (0-9), a period (.)
  • lowercase characters that follow white space or an underscore (_), converted to uppercase

If there is a conflict, meaning a duplicated acronym, after following these rules, characters are removed from the end and replaced with a counter until the conflict is resolved. The remaining characters are followed by an underscore and a counter. For example, if you have MYVERSION1 through MYVERSION100, when MYVERSION101 is created the acronym might look like MYV_101.