Service catalog
Build the list of things requesters can order in the portal, with their form, the desk that receives them and the workflow they start.
On this page
The service catalog is the portal's shop window: the list of things a person can request without having to explain everything in writing, like a laptop, access to a folder, a license or an HR certificate. Each thing that can be requested is an item, and each item has its own form with the questions the desk needs to handle it right the first time.
In this section you build that catalog: the categories that organize the items, each item with its form, which desk and group the request goes to, and which workflow starts when someone requests it.
How the requester sees it
In the portal, the requester presses Request something, chooses a category or searches by name, opens the item and fills in the form. When they press Send request:
A ticket is created in the desk you chose for the item. In an MDA or CSM desk it's a Request; in an ESM desk, a Request as well.
The ticket title is the item name and the description contains the form answers, in order. On the ticket record, the team also sees the Catalog request block with the item name and each answer.
The ticket goes to the group you set on the item or, if you didn't set one, to the one the assignment rules decide.
If the item has a workflow, the workflow starts with the form answers; for example, to ask for the manager's approval before the desk starts working.
The requester only sees active items in active categories that are open to them (for the whole company or for their department, location or account). See Request something from the catalog for the step by step from their side.
Where it is
Go to Catalog in the side menu. The screen has two tabs, each with the number of elements it has:
Tab | What you see | Button |
|---|---|---|
Items | Each item with its Category, the Desk that receives it, how many Fields its form has and its Status (active or inactive) | New item |
Categories | Each category with its Parent category, its Order, how many Items it has and its Status (active or inactive) | New category |
Inactive items appear at the end of the list, dimmed. The list updates on its own when someone else makes a change.
Who can use it
With the View level in Service catalog you see the lists and can open an item to review its form and test it in the Preview, but you don't see the buttons to create, edit, save or delete.
With the Administer level (for example, the Administrator role) you can also create, edit, deactivate and delete categories and items.
The service catalog comes with plans that include service desks (MDA, ESM or CSM).
You only see items from desks you can see: an item from a private desk doesn't appear for people who aren't members of it.
See Roles and what each one sees.
Before you start
For an item to be set up properly, it helps to have ready:
A service desk to receive the requests (MDA, ESM or CSM). Agile boards and project desks don't receive catalog requests. See Create a desk.
At least one catalog category to organize the items. See Catalog categories.
Optional: ticket categories offered for Requests, in Settings → Categories, to classify the ticket that's created.
Optional: active services, in Settings → Services, to link the request to a service.
Optional: the desk's resolver groups, in Settings → Resolver groups, if you want a fixed group to handle the item.
Optional: departments and locations, in Settings → Organization, if the item will be only for part of the company.
Optional: a workflow with the "catalog item" trigger, published in Workflows, if the request needs approvals or automatic steps. See Workflows and tasks.
Pages in this section
Catalog categories: create, order, edit, deactivate or delete categories.
Create a service catalog item: which desk it goes to, with what priority, which workflow it starts and who sees it.
Design an item's form: field types, fields that appear based on another answer, and how to test it.
Deactivate or delete an item: how to retire an item without affecting what was already requested.