ServiceNow Best Practices · LessonBy Neelima, ServiceNow Architect · Published · ServiceNow · all levels
Service catalog best practices
Design catalog items people can complete without help, and fulfilment that does not depend on heroics.
Quick answer
Design catalog items people can complete without help, and fulfilment that does not depend on heroics.
Key takeaways
- Name items in user language, not system language
- Default everything you can from the user record
- Reference variables prevent free text cleanup later
- Retire unused items, catalog bloat hurts findability
Write for the requester
Name items the way users describe the need, not the way IT names systems. Ask only for what fulfilment genuinely requires, and default everything you can from the user record.
Variables and reuse
Use variable sets for repeated blocks, keep variable names stable because flows and reports depend on them, and use reference variables so free text does not create data cleanup work later.
Fulfilment design
The form is the easy part.
- Model the fulfilment steps as tasks so work is visible and measurable
- Set realistic delivery times and publish them on the item
- Review abandoned submissions, they usually indicate confusing questions
- Retire items with no requests in a year, a bloated catalog hides the useful items
Practice challenge
+0 XPStreak ×0
Question 1 of 2
What signals a confusing catalog item?
Frequently asked questions
How many variables is too many?
If a form does not fit on one screen, question whether every field is needed at request time. Some detail belongs in the fulfilment conversation.
Record producer or catalog item?
Record producer when you want to create a record such as an incident directly. Catalog item when the request needs fulfilment tracking and approval.