DocumentaciónHelp

Create a service catalog item

Define something requesters can order in the portal, which desk and group it goes to, with what priority, which workflow it starts and who sees it.

On this page

An item is a specific thing that can be requested in the portal, like "New laptop", "Access to a shared folder" or "Employment certificate". On the item you decide which desk the request goes to, how it's classified, who handles it, what priority it starts with, whether it starts a workflow and who can see it in the portal.

Before you start

  • You need the Administer level in Service catalog (for example, the Administrator role).

  • There must be at least one active catalog category. See Catalog categories.

  • There must be a service desk (MDA, ESM or CSM) you can see. See Create a desk.

  • If the request needs approvals or automatic steps, have the workflow ready in Workflows. See Workflows and tasks.

Steps

  1. Go to Catalog in the side menu.

  2. In the Items tab, press New item. The New item page opens, with three parts: Item (the details you'll see on this page), Form and Preview.

  3. In Item, fill in the details:

    Field

    What to enter

    Name

    What the requester will see and the title of the ticket that's created, up to 120 characters. Required. Use a name that says what they get: "New laptop", not "Request 1".

    Short description

    Optional, up to 300 characters. It appears under the name in the portal and in the list of items. Use it to clarify what's included or how long it takes.

    Catalog category

    Where the item is grouped in the portal. Required. Only active categories are offered.

    Receiving desk

    The desk where the ticket is created. Required. Only service desks you can see are offered.

    Ticket category

    Optional. Classifies the ticket inside the desk. The active categories of that desk (or shared ones) that are enabled for requests are offered. Choose the desk first: with no desk, the list is empty.

    Service

    Optional. The service the request is linked to. Only active services are offered.

    Handling group

    The resolver group that receives the ticket. With Assignment rules (the default), the desk's rules decide the group. Only the groups of the chosen desk are offered.

    Impact and Urgency

    High, Medium or Low. They're used to calculate the ticket priority according to the priority matrix. They default to Low.

  4. In Who sees it in the portal?, choose an option:

    • All requesters: anyone in the company who goes into the portal.

    • Only some departments, locations or accounts: a list opens where you check departments, locations (marked (location)) and customer accounts (marked (account)). Further down, in Who sees the item, it's explained how they combine.

  5. Leave Active (shown in the portal) checked if you want the item to be orderable as soon as you save it. Uncheck it if you're still building it.

  6. In Workflow on request, choose the workflow that should start when someone requests the item, or leave No workflow (ticket only). Further down, in The workflow on request, it's explained how it works.

  7. Build the questions in Form. See Design an item's form. An item can have no questions: in that case, the requester just confirms the request.

  8. Press Save.

You'll see the message Item created and the page now shows the item name, with Form version: 1 under the title.

While you build a new item, uncheck Active (shown in the portal). That way you can save it, test the form with Test on the server and activate it when it's ready, without anyone ordering it half-built.

If you change Receiving desk, Handling group and Ticket category are cleared, because groups and categories depend on the desk. Choose them again.

Who sees the item

With Only some departments, locations or accounts, Elion ITSM checks each type separately:

  • Within the same type, matching one is enough. If you check the "Finanzas" and "Personas" departments, anyone who belongs to either of them sees the item.

  • If you check more than one type, the person has to match all of them. If you check the "Finanzas" department and the "Santiago" location, only someone who is in Finanzas and works in Santiago sees the item.

  • Only active departments, locations and accounts appear in the list. They're managed in Settings. See Settings.

If you choose Only some departments, locations or accounts and don't check anything, no one will see the item in the portal. The same happens with a person who has no department or location assigned when the item is limited by that type.

The workflow on request

  • The list shows workflows that have the "catalog item" trigger and aren't archived. Those not yet published appear with (unpublished).

  • When someone requests the item, the ticket is created first and then the workflow starts, receiving the form answers. That way you can, for example, ask for the manager's approval before the desk starts working.

  • An (unpublished) workflow doesn't start: the ticket is still created, but without a workflow. Publish it in Workflows before activating the item.

  • If you don't have access to Workflows, or your plan doesn't include it, you don't see this list. If the item already had a workflow, you'll see Workflow: with its internal name and the note (edited in Workflows); when you save, the item keeps that workflow.

See Workflows and tasks.

Edit an item

  1. In the Items tab, press the item name or Edit on its row.

  2. Change what you need.

  3. Press Save. You'll see Item saved.

The changes apply to new requests. Requests already created don't change: they keep their desk, their priority and the answers as they were sent.

If you only have the View level, you can open the item and test its form, but the Save button doesn't appear.

What happens next

  • The item appears in the Items tab with its Category, its Desk, the number of Fields and the Status active or inactive.

  • If it's active, its category is active and the person is in the chosen audience, the item appears in the portal's Request something. Check it with a test user. See Request something from the catalog.

  • Each request creates a Request ticket (also a Request in an ESM desk) with the item name as the title, the answers in the description and the priority calculated from the item's Impact and Urgency. See Ticket types and priority.

If something doesn't work

  • Give the item a name.: the Name is missing.

  • Choose the catalog category and the receiving desk.: Catalog category or Receiving desk is missing.

  • Fix the form before saving.: there are yellow warnings under the form. See Design an item's form.

  • The ticket category does not exist in that desk. or The group does not exist in that desk.: the chosen value no longer matches the desk (for example, someone deleted it). Choose it again.

  • The workflow does not exist or is archived.: someone archived the workflow. Choose another one or No workflow (ticket only).

  • I don't see the desk I want in Receiving desk: only service desks are offered. Agile boards and project desks don't receive catalog requests. If it's a private desk, you have to be a member of it.

  • The item doesn't appear in the portal: check that it's active, that its catalog category is active and that the person is in Who sees it in the portal?.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

↑↓ to navigate · Enter to open · Esc to close