Skip to content
Tutorials Center
My learning

Topics

Lesson 33 of 39 ยท ITSM and Administration

Service Catalog and Request Fulfillment in ServiceNow

Build catalog items in ServiceNow with variables, variable sets, catalog UI policies, and see how requests, requested items and catalog tasks are fulfilled.

Not every need is a break. When someone wants a new laptop, access to a shared folder or a software license, they make a request, and requests flow through the Service Catalog. The catalog is a storefront of things users can order, backed by fulfillment processes that you design. It is also one of the most visible parts of ServiceNow, so getting it right pays off.

The catalog is built on an instance. The steps are described, and the runnable blocks are labelled stand-ins that model variables and the request hierarchy.

Catalog structure

  • Catalog: a top-level storefront (for example "Service Catalog" for employees).
  • Category: grouping, such as Hardware, Software, Facilities.
  • Catalog item: one orderable thing, such as "Standard Laptop".
  • Record producer: a catalog item that creates a record in another table (for example an incident or a custom record), without a request.
  • Order guide: a bundle that orders several items at once, such as "New employee setup".

Create items in Service Catalog > Catalog Definitions > Maintain Items or the Catalog Builder. Important fields: Name, Short description, Category, Price and Recurring price, Picture, Catalogs, and Availability under Available for / Not available for user criteria.

Variables

A variable is a question the requester answers. Types include Single Line Text, Multi Line Text, Select Box, Reference, Checkbox, Yes/No, Date, Lookup Select Box, Container (layout) and Requested For. Each has a Question, Name, Mandatory, Order and optional Default value, Help text and Reference qualifier (to filter a reference list).

Reuse questions with Variable sets: a set such as "Delivery details" (building, floor, desk) is attached to many items. Variables on a record producer map to fields on the produced record.

Make behavior dynamic with Catalog UI Policies (hide, show, mandatory on a condition) and Catalog Client Scripts (onLoad, onChange), which mirror the form versions from the forms chapter but act on variables.

The request hierarchy

Ordering creates a chain of linked records:

flowchart TD
    R["REQ0010001: Request (the cart)"] --> I1["RITM0010001: Requested item: Laptop"]
    R --> I2["RITM0010002: Requested item: Docking station"]
    I1 --> T1["SCTASK0010001: Approve spec"]
    I1 --> T2["SCTASK0010002: Order from vendor"]
    I1 --> T3["SCTASK0010003: Deliver and configure"]
    I2 --> T4["SCTASK0010004: Pick from stock"]

One request can hold several requested items, and each item has one or more catalog tasks.

Record Table Meaning
Request (REQ) sc_request The order as a whole, one per checkout
Requested Item (RITM) sc_req_item One ordered item with its variables
Catalog Task (SCTASK) sc_task A unit of work for a fulfillment group

The variables answered by the requester are stored with the RITM and appear under Variables on its form.

Fulfillment with Flow Designer

To fulfill, attach a flow to the item (Process Engine tab, choose a flow or a Service Catalog trigger). The trigger offers the requested item and its variables as pills.

Typical fulfillment flow:

  1. Ask For Approval from the requester's manager.
  2. If approved: Create Catalog Task assigned to the fulfillment group, with the details from variables.
  3. Wait For Condition until the task is Closed Complete.
  4. Update Record on the RITM: State = Closed Complete.
  5. Send Email confirming delivery.
  6. If rejected: set RITM to Closed Incomplete and notify.

Use the Catalog item flow pattern rather than the older workflow editor for new items. Use Service Catalog > Catalog Administration > Item Designer features such as Catalog Item Quantity and Cart Layouts as needed.

Pricing, delivery and SLAs

You can set a price and show it in the cart, define delivery plans, and attach SLAs to the RITM table so requests have time targets as incidents do. For hardware, many teams integrate the fulfillment step with Asset Management, so a task on closure updates the asset record.

Good catalog design

  1. Ask only what fulfillment needs; every variable is friction.
  2. Prefer choice lists and references over free text.
  3. Use user criteria to show items only to who may order them.
  4. Write a short, clear description, not an internal name.
  5. Test with a user who has no special roles.
  6. Track abandoned carts and common rejection reasons, then improve.

Models of variables and requests

The first stand-in validates variables the way mandatory flags and catalog UI policies would.

JS Stand-in: validate catalog variables with conditions

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The second stand-in creates the REQ, RITM and SCTASK hierarchy from an order guide to show how many records one checkout makes.

JS Stand-in: build the request hierarchy

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which record represents ONE ordered item within a request?

    The requested item (sc_req_item) is one ordered item; the request holds the cart as a whole.
  2. 2. What does a record producer do?

    A record producer turns a catalog form into a record such as an incident.
  3. 3. Which tool reuses a group of questions across several catalog items?

    A variable set is a reusable group of variables attached to many items.
  4. 4. Where do the requester's answers to catalog questions appear on fulfillment records?

    Variables are stored with the RITM and shown on its form, and flows can use them as pills.

Summary

  • The catalog holds items, categories, order guides and record producers; variables collect the requester's answers.
  • Ordering creates a REQ, RITMs and SCTASKs; flows attached to the item run approval and fulfillment.
  • Use variable sets, catalog UI policies and user criteria for maintainable items.
  • Ask only what is needed and test as a normal user.

Next: Users, Groups, Roles and ACLs