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.