DocumentaciónHelp

Configure a task

Define who gets a workflow task, what form they fill in and when it's due.

On this page

A task is a workflow step a person does: prepare equipment, create an account, review a document. When the workflow reaches it, the task appears in My tasks for the right person, and the workflow waits until someone completes it.

Before you start

  • You need Administer in Workflows.

  • Open the workflow in the modeler and add a Task for a person or group from the palette. See Use the modeler.

Steps

  1. Select the task in the diagram. The Properties panel shows User task and, next to it, the element identifier.

  2. Enter the Name. It's the title the recipient will see, so it should say what to do: "Prepare laptop", "Create the email account".

  3. In Type, leave Task selected. If you choose Approval, the step becomes an approval (see Configure an approval).

  4. In Assignee, choose who gets it (see the table below). If you choose A person or A group, then choose the person or group in the second list.

  5. If you want, enter the Due time as a duration (see below).

  6. If the person completing the task needs to leave data, build the Form (see below).

Changes apply to the diagram when you leave each field. Remember to save the draft afterwards.

Who it's assigned to

Assignee option

Who gets it

Ticket assignee

The person assigned to the ticket at that moment. If the ticket has no assignee, the ticket group.

Ticket group

The ticket's resolver group. Any member claims it from My tasks → My groups.

Requester's manager

The manager of the person the ticket was requested for (or of the person who requested it). If they have no active manager on record, the ticket group.

A person

The person you choose in the list. If that person is no longer active when the workflow reaches the task, the ticket group.

A group

The resolver group you choose in the list.

The person or group is calculated when the workflow reaches the task and stays fixed. If something changes later, a workflow administrator or the group lead can reassign it. See My tasks.

If you haven't chosen who it's assigned to, the panel shows The assignee is missing. and the workflow can't be published.

"Requester's manager" uses the manager Elion ITSM has on record for each person. If your company hasn't loaded that data, the task will go to the ticket group. Ask whoever administers Elion ITSM in your company before basing a workflow on this option.

Due time

The Due time is the time the task has from when it's created. It's written as a duration in ISO 8601 format:

You enter

It means

PT30M

30 minutes

PT4H

4 hours

PT8H

8 hours

P2D

2 days

P1DT12H

1 day and 12 hours

P1W

1 week

Below the field you'll see the duration in words (for example "4 h"). The minimum is 1 minute (PT1M) and the maximum, 365 days (P365D).

Check In business hours so the time only counts during business hours, according to the ticket's SLA calendar or, if there isn't one, the company's.

The due time is shown in My tasks ("Due in…" or "Was due… ago" in red), but on its own it doesn't change anything in the workflow. If you want something to happen when it's due (notify, escalate, close), add a wait on the edge of the task. See Waits and due times.

Form

A form asks for data when the task is completed: whether it could be done, a serial number, a comment. The answers stay in the workflow and you can use them in the decisions that follow.

The form is written in the same format as service catalog forms (in JSON). The easiest way to start:

  1. With the Form field empty, press Use a sample form.

  2. A form loads with two fields: Resultado (result; a list with "Listo" (done) and "Quedó pendiente" (left pending), required) and Detalle (details; long text), which only appears if the result is "Quedó pendiente".

  3. Change the labels, options and fields to fit what you need.

You can use the same field types as in the catalog: text, long text, number, email, date, checkbox, list, single choice, multiple selection, person and attachment (up to 50 fields). With showIf you make a field appear only if a condition is met, for example form.resultado == 'pendiente'.

If the form has a problem, the panel says so below the field, for example The form is not valid JSON. or which field is wrong.

The task's answers are read later as task.<id>.data.<campo>, where <id> is the task identifier you see in Properties. For example: task.Task_1.data.resultado == 'ok'. See Decisions and conditions.

If the task has no form, completing it is a confirmation: "Mark the task as done?".

What happens next

When the workflow reaches the task:

  • the assigned person, or each group member, gets a "Workflow task: …" notice in the bell;

  • the task appears in My tasks, under Mine or My groups;

  • the workflow waits until someone completes it and then continues with the next step.

Related

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

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