The CreatorCon Call for Content is officially open! Get started here.

Naming conventions - Business Rules, Client Scripts ETC...

gaidem
ServiceNow Employee
ServiceNow Employee

sherman.1206 inspired me to post this topic.

What are others doing for naming conventions throughout the system? Client Scripts, Business Rules, WorkFlows, Events, etc...

Look forward to your responses!

3 REPLIES 3

sherman_1206
Tera Contributor

We have started the following convention for workflows:



<table name> { <description> }

So for example for change management running on the change_request table we have entries such as:



Change Request {emergency}
Change Request {standard}


gaidem
ServiceNow Employee
ServiceNow Employee

I haven't come up with a naming convention, but since the table name is usually available for these types of records, as well as who created it and when it was created, I tend to put just a description in the name.


We preface it with our company initials, so that we can easily see what is custom and what is OOB.