Skip to tutorial content
Rate module Not yet rated

Catalog Item or Record Producer?

4 min read
On this page

In this lesson, you will learn:

  • The difference between the two
  • When to use each
  • How a record producer fills fields
  • How to build SNWR Report a VPN problem

🔁 Quick look back: Last time: Catalog Item Design Standards. You learned SNWR’s item standard, with a clear name, few questions and a shared Requested for variable set.

1 “My VPN is broken. Is that a request?”

Sam’s VPN stops working. He looks in the catalog.

  • He finds only order forms.
  • He orders “VPN access”, which he already has.
  • Desktop Support gets a request that should be an incident.

🎯 The problem: Broken things raised as requests go to the wrong team, with the wrong targets.

👉 The fix: give Sam a catalog form that creates an incident, not a request.

2 Two kinds of form

Key term: Record producer

A catalog form that creates a record on another table, like an incident, instead of a request.

Key term: Catalog item

A catalog form that creates a request: REQ, RITM and tasks.

Catalog item versus record producer. Catalog item: Sam wants something new, like a monitor. It creates REQ, RITM and SCTASK, with request SLAs. Record producer: something is broken, like the VPN. It creates an incident, with category Network and subcategory VPN already set, and incident SLAs.
Figure 1. Want something? Catalog item. Something broken? Record producer.

3 Filling fields for the agent

On the form, Sam gives On the incident, it becomes
What’s wrong? Short description
When did it start? Description
(nothing) Category Network, subcategory VPN
(nothing) Channel: Self-service

💡 Good to know: Set category and subcategory for the caller. Sam shouldn’t need to know SNWR’s categories.

💡 Good to know: Need a refresher? See Fundamentals › Record Producers › Mapping Variables to Fields.

4 Let’s try it: build the record producer

  1. Open Service Catalog › Record Producers and create SNWR Report a VPN problem. Table: Incident. Put it in the Access category, next to VPN access.
  2. Add variables What’s wrong? and When did it start?. Map the first to Short description.
  3. In the Script field, set category to network and subcategory to vpn, and contact type to self-service.
  4. Impersonate Sam and submit the form from Employee Center.
  5. Open the new incident. Check the fields are set, and it went to SNWR Network Support.

5 Quick recap

  • A catalog item creates a request
  • A record producer creates another record, like an incident
  • Something broken? Use a record producer
  • Set fields like category for the caller
  • SNWR Report a VPN problem creates a Network › VPN incident

6 Check yourself

Think of your answer first. Then tap to check.

1 Sam wants a new monitor. Which form? Show answer

A catalog item.

2 Sam’s VPN is broken. Which form? Show answer

A record producer that creates an incident.

3 Why set category for Sam? Show answer

He shouldn’t need to know SNWR’s categories, and it routes the incident correctly.

4 Which SLAs apply to SNWR Report a VPN problem? Show answer

Incident SLAs, because it creates an incident.

Nice work! Sam can now report a broken VPN from the catalog. 🎉
Next up: Catalog Builder for Catalog Managers

Was this lesson helpful?

Have a question or doubt?

Ask here and get help from instructors and fellow learners.

0 / 300

Only logged-in learners can post.