Automatic actions
Configure the steps Elion ITSM does on its own inside a workflow, like assigning the ticket, changing its state, sending a notice or creating a child ticket.
On this page
An Elion ITSM automatic action is a step that isn't done by a person: Elion ITSM does it as soon as the workflow reaches it. Actions come from a closed list and each one has its parameters, which are checked before publishing.
Before you start
You need Administer in Workflows.
Add an Elion ITSM automatic action from the palette, or use Add action in an element's menu.
Almost all actions work on the workflow's ticket. If the workflow starts without a ticket, only Send a notice and Call a registered webhook are useful.
Steps
Select the action in the diagram and enter its Name, for example "Assign to Field Support".
In Action, choose what it does (see the table below). Below the list, a help text appears with the parameters it uses.
Sample parameters load in Parameters (JSON). Change them to fit what you need.
If there's a problem, the panel says so below the parameters, for example to: target state in lowercase (in_progress, on_hold, resolved…).
When you change the action, the parameters are replaced with the new action's sample ones.
Available actions
Action | What it does |
|---|---|
Change the ticket state | Moves the ticket to another state, with the same rules as if a person did it. |
Assign the ticket | Assigns the ticket to a group and, if you want, to a person. |
Change a ticket field | Changes the priority, impact, urgency, category, service, tags or a custom field. |
Add a note | Adds an internal note or a public reply (which reaches the requester by email). |
Create a child ticket | Creates a new ticket linked to the workflow's ticket, in the group you specify. |
Send a notice | Notifies the requester, the assignee, the group, the approvers or a person, in the bell and by email. |
Suggest articles | Finds up to 3 published knowledge articles related to the ticket title and leaves them as suggestions on the record. |
Summarize with Elion | Asks Elion for a summary of the ticket, which is saved as an internal note. The workflow doesn't wait for the summary. |
Call a registered webhook | Sends a signed notice to an external system registered in Settings → Integrations. |
On the ticket, the changes an action makes appear as made by the workflow, with its name and version.
Parameters for each action
Parameters are written in JSON: inside braces, each parameter with its name in double quotes. These are examples you can copy.
Change the ticket state. to is the target state (in_progress, on_hold, resolved…). To put it on hold, add holdReason (requester, vendor, change or other); to resolve it, resolutionCode (solved, workaround, not_reproducible, duplicate, user_error, no_response or cancelled). note is optional.
{ "to": "resolved", "resolutionCode": "no_response", "note": "Cerrado por falta de respuesta." }Assign the ticket. groupId is the group id (if you don't give it, the ticket's current group is used). assignee can be round_robin (let the group's assignment decide), requester.manager (the requester's manager) or user:<id>.
{ "groupId": 4, "assignee": "round_robin" }Change a ticket field. field is priority (value P1 to P5), impact or urgency (1, 2 or 3), categoryId or serviceId (an id or null), tags (a list of up to 20 tags) or custom.<clave>.
{ "field": "priority", "value": "P2" }Add a note. kind is internal (only the team sees it) or public (it reaches the requester by email). body is the text.
{ "kind": "public", "body": "Tu pedido {{ticket.number}} fue aprobado y ya lo estamos preparando." }Create a child ticket. kind is incident, request, problem or change; title (up to 200 characters), description (can be empty) and groupId, the group that receives it. The child ticket number is available to the following steps in vars.<id>.number.
{ "kind": "request", "title": "Crear cuenta de correo para {{form.nombre}}", "description": "", "groupId": 7 }Send a notice. to is requester, assignee, group, approvers (those of the workflow's latest approval) or user:<id>. template is always workflow_notice. subject (up to 200 characters) and body (up to 5,000).
{ "to": "requester", "template": "workflow_notice", "subject": "Novedad de {{ticket.number}}", "body": "Necesitamos que confirmes la dirección de entrega." }Suggest articles and Summarize with Elion take no parameters: leave {}.
Call a registered webhook. integrationId is the integration id in Settings → Integrations, event the event name (lowercase letters, numbers, dot and _) and payload the data you send (up to 32 KB).
{ "integrationId": 2, "event": "alta.usuario", "payload": { "ticket": "{{ticket.number}}" } }Text with workflow data
In parameter texts you can insert workflow data:
{{ticket.number}}: the ticket number.{{form.campo}}: an answer from the request form.{{vars.x}}: data a previous step left behind.
The value is copied as is: no conditions or calculations are evaluated inside the braces.
If the action fails
If the problem is temporary (for example, an external system that doesn't respond), Elion ITSM retries on its own: up to 3 times for most actions and up to 5 for a webhook.
If it fails for good (a group that doesn't exist, a state the ticket can't move to, a workflow without a ticket), the instance becomes Stopped by error and administrators get the "Workflow stopped" notice. After fixing the cause, an administrator can press Retry on the instance. See Follow an instance.
The ids of groups, people and integrations don't appear on every screen. If you don't know them, ask whoever administers Elion ITSM in your company. To assign to the ticket group or to the requester's manager you don't need ids.