Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Group Naming Best Practices

MiY
Tera Contributor

What are some best practices for naming groups?

In my current project, we are implementing a ServiceNow change request process.

We have a group responsible for implementing and approving changes for each product provided by the client (AWS, CrowdStrike, etc.). Separate from these groups, there is also a product operations group.

We are planning to define groups for each product using the following names. Are there any other good naming or best practices?

・Change Working Group: {Product Name} Change
・Change Approval: {Product Name} Change Approver
・Operations Group: {Product Name}

5 REPLIES 5

Rafael Batistot
Kilo Patron

Hi @MiY 

 

May you consider adding prefixes for easier sorting and identification:
• CHG-WG-{Product Name} (Change Working Group)
• CHG-APP-{Product Name} (Change Approver)
• OPS-{Product Name} (Operations)

If you found this response helpful, please mark it as Helpful. If it fully answered your question, consider marking it as Correct. Doing so helps other users find accurate and useful information more easily.