Naming Conventions
Naming Conventions
Automation Anywhere and the Automation Anywhere logo are trademarks owned by Automation Anywhere
Software,
The information contained in this documentation is proprietary and confidential.Your use of this information and
Automation Anywhere Software products is subject to the terms and conditions of the applicable End-User
License Agreement and/or Nondisclosure Agreement and the proprietary and restricted rights notices included
therein.
You may print, copy, and use the information contained in this documentation for the internal needs of your
user base only. Unless otherwise agreed to by Automation Anywhere and you in writing, you may not otherwise
distribute this documentation or the information contained here outside of your organization without obtaining
Automation Anywhere’s prior written consent for each such distribution.
Contents
Naming Conventions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Naming Conventions
Capitialization and spacing styling in names.
• CamelCase—The practice of writing compound words or phrases where each word or abbreviation
begins with a capital letter. For example PrintUtility.
• bumpyCase—The same, but always begins with a lower letter. For example backgroundColor.
• Do not use underscores.—Underscores waste space and do not provide any value in these
contexts. Readability can be achieved by using Bumpy Casing and Camel Casing.
• Consistent values and flags.—Always use lower case Boolean values "true" and "false".
Never deviate, stick to this method of defining a boolean state. This also applies to flags. Always use
"true" or "false" for Boolean variables, never a 0 or 1 or anything else.
• Variable names—
Don’t include numbers in variable names.
Avoid single character variable names. Never use i or x for example. Use a variable name that
provides some clue about the variable purpose.
• Flag and Script names—
Name flags with Is, Has, Can, Allows or Supports, like isAvailable, isNotAvailable,
hasBeenUpdated.
Name scripts with a noun, noun phrase or adjective like Utility or Helper for example
FileSaveHelper.atmx.
• Pre-fixed fields—Don’t prefix fields. For example, don’t use g_ or s_ or just _.
Exception is the letter v as a prefix in order to make finding variables easier.
• Verb-object naming—Also use verb-object pairs when naming scripts like
GetMostRecentVersion.
Name variables with a descriptive name like employeeFirstName or socialSecurityNumber.