Naming conventions - Business Rules, Client Scripts ETC...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2011 06:01 PM
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2011 06:28 PM
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}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2011 07:21 PM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-21-2015 04:32 AM
We preface it with our company initials, so that we can easily see what is custom and what is OOB.