Service catalog
The self-service storefront where users request what they need.
The Service Catalog is the "shop" where users request things, a laptop, access, a new-hire setup, through a friendly, structured front end instead of a free-text ticket. Structured requests mean predictable fulfilment, approvals and automation.
- The building blocks
- Request → item → task
- Catalog item vs record producer
- Where users see it
- Common mistakes
The Service Catalog is the "shop" where users request things, a laptop, access, a new-hire setup, through a friendly, structured front end instead of a free-text ticket. Structured requests mean predictable fulfilment, approvals and automation.
The building blocks
Request → item → task
Submitting builds a three-level hierarchy that fulfilment teams work against:
Fulfilment is orchestrated by Flow Designer, approvals first, then tasks routed to the right groups, with the request closing when all items complete.
Catalog item vs record producer
Where users see it
The catalog is surfaced through the Service Portal / Employee Center, the consumer-grade experience most requesters use, with search, categories and a shopping-cart flow.
Common mistakes
- Using a record producer where a catalog item is needed (or vice versa).
- Duplicating variables instead of a shared variable set.
- Hard-coding approvals in the item instead of a reusable flow.
- One giant item with 40 variables instead of an order guide.
Practice challenge
FAQ
How to change approval from Requested in ServiceNow?
An approval sits in the Requested state until acted on. An approver changes it from the record's Approvers related list or the My Approvals module by clicking Approve or Reject. Admins can also update the sysapproval_approver record's state field directly, or automate the transition with a flow.