Categories
With a parent category, order and active or inactive state.
Argunis/Elion ITSM/Service catalog
Everything that can be requested has its form, its desk, its group and, when needed, its approval workflow. The request arrives complete the first time.
Categories organize the catalog, with subcategories and their order. Each item says which desk and group it goes to, with which ticket category and service, and who it is open to: the whole company or a department, a location or a customer account.
"Who handles a new laptop request?"
Build the questions field by field and test them in the preview exactly as the requester will see them. A field can show only when it applies, based on the answer to another.
On submit, a request is created in the item’s desk, with the answers laid out on the record. If the item has a workflow, it starts with those answers, for example to get the manager’s approval before the desk begins.
With a parent category, order and active or inactive state.
Everything that can be requested, with its desk, group and state.
Text, number, date, email, lists, checkbox, person and attachments.
A field that appears only depending on the answer to another.
The form exactly as the requester will see it, before publishing.
The whole company or a department, a location or an account.
Desk, group, ticket category and service of the request.
Approvals and tasks that start with the form answers.
The team sees the item and each answer on the ticket.
Only the requesters it is open to: the whole company or a department, a location or an account. An item from a private desk doesn’t show for people who aren’t members.
Yes. Attach a workflow with the manager’s or another person’s approval to the item. It starts when the request is submitted and receives the form answers.
Yes. An item can go to an enterprise service desk, for example HR, where it is created as a request.
We show you Argunis on your own operations and answer your questions in one call.