ServiceNow Service Catalog & Request Management Guide (RITM, Tasks)

Introduction: The Self-Service Storefront

The Service Catalog is the storefront of ServiceNow ITSM — a self-service place where employees order hardware, software, access, and services, like an online shop. Request Management is the machinery behind the counter that fulfils those orders.

Together they are one of the three heaviest-weighted areas of the CIS-ITSM exam, so it pays to know the data model cold.

Catalog Structure

The main definition tables:

Table	What it holds
sc_catalog	A catalog (best practice: at least two — one customer-facing, one IT-facing)
sc_category	Categories grouping items (keep top-level to 8-10, nest only 1-2 deep)
sc_cat_item	The catalog items themselves
sc_cat_item_guide	Order guides

The Request → Item → Task Model

This is the single most important thing to memorize. When a user checks out, three record types are created:

Record	Table	Prefix	Purpose
Request	sc_request	REQ	The overall order
Requested Item (RITM)	sc_req_item	RITM	One per item ordered
Catalog Task	sc_task	SCTASK	The fulfilment work for an item

Fulfilment work happens at the RITM / catalog task level, not the request level — a classic exam trap.

Building Order Forms

• Variables are the questions on a catalog item form; variable sets are reusable groups of variables shared across items.
• Catalog UI policies make variables mandatory, visible, or read-only based on conditions — the catalog equivalent of form UI policies.
• Catalog client scripts run client-side to validate input or populate fields dynamically.
• The Variable Editor displays a request's variables (respecting catalog UI policies) on RITM and catalog task forms.

Record Producers

A record producer is a catalog-style front end that creates a record on any table — an incident, a problem, an HR case — while gathering exactly the information needed. It is a friendlier, more controlled alternative to adding fields directly to a form.

Order Guides and User Criteria

• Order guides bundle items commonly ordered together (classic example: employee onboarding). With cascade variables, common answers are collected once and copied to each included item.
• User criteria decide who can and cannot see or request catalogs and items. A CANNOT rule overrides a CAN rule, even if a user matches both — remember this precedence.

Fulfilment

Fulfilment is driven by Flow Designer (or legacy workflows / execution plans). Stages track progress through a requested item; when the flow completes, business rules flip the item to a closed state and set it inactive.

Key Roles

Role	Responsibility
catalog_admin	Full catalog administration
catalog_manager	Manages catalogs, categories, assigns editors
catalog_editor	Creates/edits/publishes items in assigned catalogs
sn_request_read / sn_request_write	Scoped access to request records

Frequently Asked Questions

What is the difference between a Request, a RITM, and a Catalog Task? The Request (REQ) is the overall order; each item ordered becomes a Requested Item (RITM); and the fulfilment work for a RITM is done through one or more Catalog Tasks (SCTASK).

What is a record producer used for? To create a record on any table (like an incident) through a friendly catalog-style form, instead of exposing the underlying table form or adding extra fields to it.

What is the difference between a variable and a variable set? A variable is a single question on a catalog item; a variable set is a reusable group of variables you can attach to many items.

How do user criteria decide access? They define who can and cannot access catalogs and items. If a user matches both a CAN and a CANNOT rule, the CANNOT wins.

What drives catalog fulfilment today? Flow Designer is the modern default; older instances may still use workflows or execution plans.

Key Takeaways

• Memorize the model: Request (sc_request) → Requested Item (sc_req_item / RITM) → Catalog Task (sc_task).
• Fulfilment happens at the RITM/task level.
• Variables, variable sets, catalog UI policies, and catalog client scripts build and control order forms.
• Record producers create records on any table via a catalog front end.
• With user criteria, a CANNOT rule overrides a CAN rule.

Where to go next

• Where self-service content also lives: Knowledge Management
• The automation behind fulfilment: Flow Designer basics
• Practise: free practice test