General

Resource Naming

• Indicate your organization in the naming of your resource.  They should be named ${Organization} - Short Description.

For example:

CS - Special Business Rule

Yale - Special Client script

• Be as descriptive as possible in the short description, while being concise.
• Specify the reason this resource was created in the description field.

Field Naming

• Don't abbreviate if possible.  It should be clear if possible what the field is used for without knowing the context.
• Field names should be all lowercase and underscore delimited.
• Don't override the automatic prepending of the "u_" to field name under any circumstances.

Scripting

• Pretty much just follow the coding, client script and business rule best practices from ServiceNow.
• Comment your code!  Follow the guidelines for this at ServiceNow as well.

Catalog

Variable Naming

In addition to the standards already mentioned, variable names used in catalog items should be prepended with the name of the item.  For example:

fw_type

In this case abbreviation is acceptable for the prefix.