Workflows and tasks
Automate processes with BPMN workflows that hand out tasks, request approvals and act on tickets, and handle what's assigned to you in My tasks.
On this page
A workflow is a process drawn as a diagram: what steps it has, who does each one, what's decided along the way and what Elion ITSM does on its own. You can use it, for example, so a laptop request goes through the manager's approval before reaching the desk, so a normal change waits for the CAB's go-ahead, or to close a ticket automatically if the requester doesn't reply within three days.
Workflows are drawn in Workflows, and the work they create for people arrives in My tasks.
What you get
A visual modeler that only offers what Elion ITSM knows how to run: tasks, approvals, decisions, automatic actions, waits and subprocesses.
Approvals with one or more approvers, in Any, Majority or All mode, which can also be decided from the portal.
Automatic actions on the ticket: assign it, change its state or a field, add a note, send a notice, create a child ticket, call a webhook, summarize it or suggest articles.
Versions: you publish a new version without affecting workflows that are already running.
Tracking of each running workflow with its diagram, the step it's on and its history.
Definitions and instances
In Workflows you'll see two tabs, because a workflow exists in two forms:
Tab | What it is | Example |
|---|---|---|
Definitions | The designed process: the diagram, its key, when it starts and its versions. | "Alta de usuario" (new user), version 3 published. |
Instances | Each time the process runs, usually on a ticket. | "Alta de usuario" running on REQ-000412. |
A definition can have many instances at once. Each instance continues with the version it started with, even if another one is published later.
How a workflow starts
Each definition says in Starts when it begins:
Manually: someone starts it from Workflows, with or without a ticket.
Catalog request: it starts on its own when a requester orders a service catalog item that has that workflow, with the form answers.
Change: it starts on its own when a normal or emergency change moves to assessment. It's how you build the CAB approval.
Where your tasks and approvals come from
When an instance reaches a step for a person, Elion ITSM creates:
a task, assigned to a person or a group, which gets completed (sometimes with a form); or
an approval, decided by one or more approvers.
You get a notice in the bell and the task appears in My tasks. If you're an approver, you also get an email with the Decide in Elion ITSM button. When you complete or decide it, the workflow continues on its own with the next step.
Pedido del catálogo ──► Aprobación de la jefatura ──► Decisión
├─ aprobado ──► Tarea de la mesa ──► Fin
└─ rechazado ─► Nota al solicitante ─► Fin(Catalog request → Manager approval → Decision; approved → Desk task → End; rejected → Note to the requester → End.)
What you can do depending on your access
Workflows and My tasks appear if your company's plan includes the Workflows module. Inside, it depends on your level in that module:
Level | What you can do |
|---|---|
View | See the definitions (the diagram, read-only), the instances and your tasks. |
Operate | Also start workflows manually, and claim and complete tasks. The built-in Agent role has it. |
Administer | Also create, model, publish and archive workflows, cancel and retry instances, and reassign tasks. The Administrator role has it. |
You don't need a special level to approve: you only need to be an approver for that approval. Requesters decide from the portal.
Pages in this section
Design a workflow
Operate workflows
Your work
If you only handle tasks and approvals, read My tasks and Approve or reject. If you're going to design workflows, start with Create a workflow.