DocumentaciónHelp

Configure an approval

Define who approves a workflow step, how many approvals are needed and which path the workflow follows if it's approved or rejected.

On this page

An approval is a step where one or more people decide whether something moves forward: an equipment purchase, access to a system, a change in production. Each approver decides Approve or Reject, and the workflow continues once it has the decisions the mode requires.

Before you start

  • You need Administer in Workflows.

  • Add an Approval from the modeler palette (the task icon with a ✓). You can also select a task and choose Approval in Type.

Steps

  1. Select the approval in the diagram.

  2. Enter the Name: it's what approvers will see, for example "Approve laptop purchase" or "CAB approval".

  3. In Assignee, choose an option, for example Ticket group. The modeler requires it to validate the step, even though in an approval only the approvers decide.

  4. In Approvers, add one or more (see below).

  5. Choose the Mode.

  6. If you want, enter the Due time (for example P2D) and check In business hours.

Add approvers

  1. In the Approvers list, choose the type.

  2. If the type requires it, enter in the field next to it the number (id) of the group or person, or the form field.

  3. Press Add. The approver appears as a tag; press its × to remove it.

Approver type

Who decides

What you enter

Requester's manager

The manager of the person the ticket was requested for.

Nothing.

Leads of the service owner group

The leads of the group that owns the ticket's service.

Nothing. The ticket must have a service with an owner group.

Members of a group

Everyone in the resolver group.

The group id.

Leads of a group

Only the leads of that resolver group.

The group id.

A person

That person.

The person id.

Person chosen in the form

The person the requester chose in a person-type field of the catalog request.

The field identifier, for example jefe.

You can combine types. For example, Requester's manager and Leads of a group so that both the manager and the Security leads decide.

Requester's manager and Leads of the service owner group don't need ids and adapt to each ticket on their own. Use them when you can. If you need the id of a group or person, ask whoever administers Elion ITSM in your company.

If an approver is written incorrectly, you'll see Not understood: with what wasn't recognized.

Mode

The Mode says how many decisions are needed:

Mode

It's approved when

It's rejected when

Any (the first to decide)

The first person to decide approves.

The first person to decide rejects.

Majority

More than half of the approvers approve.

It can no longer reach more than half. With an even number, a tie rejects.

All

All approvers approve.

A single person rejects.

When the mode is met, the approval closes and the missing votes are no longer requested.

Which path the workflow follows

The approval doesn't choose the path on its own: it ends with a result, approved or rejected, and you decide what happens in each case with a Decision right after it.

Aprobación «Aprobar compra» ──► Decisión
                                 ├─ task.Aprobar_compra.outcome == 'approved' ──► Tarea «Comprar»
                                 └─ por defecto ─────────────────────────────────► Nota «Rechazado»

(Approval "Approve purchase" → Decision; approved → Task "Buy"; default → Note "Rejected".)

  1. Connect the approval to a Decision (exclusive gateway).

  2. Connect the decision to the "approved" path and to the "rejected" path.

  3. On the "approved" connection, enter the condition task.<id>.outcome == 'approved', where <id> is the approval identifier you see in the Properties header.

  4. Mark the other connection as the Default path.

See Decisions and conditions.

If you don't add a decision after the approval, the workflow follows the same path whether it's approved or rejected.

What happens next

When the workflow reaches the approval:

  • Elion ITSM calculates the approvers at that moment, only with active people, and they stay fixed;

  • each approver gets the notice "Pending approval: …" and, if the workflow has a ticket, an email with the Decide in Elion ITSM button;

  • agents decide in My tasks → Approvals and requesters in the portal's Approvals.

If no approver is active (for example, the requester has no manager on record), the instance stops with the error "The approval … has no active approvers." and administrators get a notice. See Follow an instance.

CAB approvals

The approval of a normal or emergency change is built the same way: a workflow that starts When a change of certain types is created, with an approval whose approvers are the CAB members (for example, Members of a group "CAB"). The change record shows in CAB who approved and who's missing.

A change that is Awaiting CAB can only be moved by the workflow, so the CAB workflow must do it:

Inicio ──► Esperar: el ticket pasa a «Pendiente de aprobación» ──► Aprobación del CAB ──► Decisión
                                                                  ├─ aprobado ─► Cambiar el estado: {"to": "scheduled"} ─► Fin
                                                                  └─ por defecto ► Cambiar el estado: {"to": "rejected"} ──► Fin

(Start → Wait: the ticket moves to "Pending approval" → CAB approval → Decision; approved → Change the state: {"to": "scheduled"} → End; default → Change the state: {"to": "rejected"} → End.)

  1. Start with a Wait for something on the ticket (message) that waits for The ticket moves to a state → Pending approval. The workflow begins when the change moves to In assessment, so the approval only opens once someone presses Request CAB approval.

  2. Then, the approval and a decision with task.<id>.outcome == 'approved'.

  3. On the approved path, a Change the ticket state action with {"to": "scheduled"}; on the other, with {"to": "rejected"}.

See Automatic actions and CAB approval.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

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