Best practices on naming conventions for sevice catalog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi Team, I'm looking for set the process for SRM(Service Request Management). May I know the "best practices on naming conventions for service catalog"
1) Naming conventions for forms (nomenclature) to avoid duplicates and unclear titles.
2) Avoiding redundant forms by improving workflow documentation and checks before creating new forms.
3) Documenting the process from request intake to delivery, including rationale for task assignment and a RACI matrix for accountability.
4) Limiting the number of fields and conditional logic in forms to prevent performance issues, and exploring Catalog Builder features in the new ServiceNow version.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
check these links
Application Guide: Service Catalog Best Practices
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hope you are doing good.
Did my reply answer your question?
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Refer below articles for guidance and best practices
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
Hi @Umesh G
- Naming conventions – Use clear, consistent, descriptive titles (e.g., [Category] – [Action] – [Item]), to avoid duplicates/unclear forms.
- Avoid redundancy – Maintain workflow/process documentation and check for existing items before creating new ones.
- Governance & accountability – Document full lifecycle (intake → delivery), define rationale for task assignments, and use a RACI matrix.
- Form design – Keep forms lean (minimal fields, use conditional logic carefully to avoid performance issues). Leverage Catalog Builder features for standardization and governance.