At Habanero we have come up with a naming convention for variables in Nintex. Why is this important?
- It makes it easy to know what the variable type is based on the naming convention.
- It is consistent and allows any team member working on a workflow to easily understand the logic of the workflow.
- It makes it easier to come up with new names for variables.
- There are less errors, which makes it easy to distinguish one variable from another if there are many variables.
Our variables always describe the content it stores. Similar to C#, our variables are one word and written with camel case capitalization style. With camel case, the first letter is lower case and the first letter of each subsequent concatenated word is capitalized. We also prefix the variable by a shortening the first three to four characters of the type of variable it is. For example, "txtProjectCode" tells us we are storing project code in a single line of text field.
These are the prefixes we use:
|
Variable Type |
Prefix |
Example |
|
Single line of text |
txt |
txtProjectCode |
|
Multiple lines of text |
mtxt |
mtxtProjectDescription |
|
Choice |
ch |
chProjectStatus |
|
Number |
num |
numProjectSize |
|
Date and Time |
date time |
dateProjectStart timeProjectLaunch |
|
Yes/No |
bool |
boolIsProjectCompleted |
|
Person or Group |
ppl |
pplProjectManager |
|
Integer |
int |
intProjectMembers |
|
List Item ID |
lid |
lidProjectTask |
|
Action ID |
aid |
aidProjectUserTask |
|
Collection |
col |
colProjectIDs |
