Automate sequences (workflows)

What it is for

A workflow is a sequence of steps that run one after the other on devices: for example "check disk space → if above 90 % clean up → otherwise send an email". You build it in an editor in the console, publish it and start it by hand, on a schedule or when something happens — for example when a device comes online or an alert is raised. In the console an access is called tenant.

What you need

• Role: tenant administrator or higher to create, edit and release; technician or higher to start.
• Cloud: for steps with scripts the service "Scripts", for steps with packages "Software distribution" (paid Cloud).
• Script steps need the same conditions on the device as a script (G6).

How to do it

Step 1: Create a workflow

1. Sidebar Workflows → New workflow.
2. Enter Name and Tenant, Create.
3. In the editor drag steps from the palette onto the canvas or click them, and connect them with edges. The second edge of a step becomes a condition.
4. Save. The editor shows what would still prevent a start.
5. Publish. Only a published version can be started; schedules and triggers only run afterwards.

The library ships ready-made workflows, for example for releasing USB storage for 60 minutes or reporting suspected malware (G13). You bring in a file from another installation with Import (JSON).

Step 2: Release

A workflow only runs where it is released — for your access, for single devices or for all accesses.

• Drag the workflow in the list onto your access in the tree on the left, or menu ⋮ → Assign tenants….
• For a single device: in the device list right-click → Run & deploy → Assign workflows….

Step 3: Test

Workflow menu ⋮ → Test run…. The test run takes the saved draft and runs on exactly one device.

Step 4: Start

• By hand: menu ⋮ → Start…. In the dialog Start workflow choose Individual devices or All devices in a group under Target, fill in Variables for this run: if needed, then Start.
• From the device list: right-click → Start workflow… — also for several ticked devices.
• On a schedule or event: menu ⋮ → Schedules and triggers…. - Schedules: Cron expression (UTC) (for example "30 2 * * *" = daily 02:30 UTC) or Interval (Every … minutes); Target All devices of the tenant, One group or Specific devices. - Triggers: an Event such as Device online, Device offline, Ticket created, Tag added, Entity inbox or Alert raised (G12); target for example Device of the event. - Apply, then Save.

How you know it worked

• Sidebar Runs → Workflow runs: every run with its state; a click shows every device and its path through the workflow. Below that Upcoming runs of the next seven days from your schedules.
• The list of workflows shows the state (published version, changed draft) and the number of schedules and triggers.

What the other side sees

A workflow can show the person at the device a message or ask a question. If the workflow contains a step that requires a confirmation in the console, it appears at the top of the Workflows view in the list of open questions; a counter on the menu item shows how many you may answer. Confirm or Reject — in the run also via Respond….

Good to know

• A global workflow (for all accesses) belongs to the system administrator; administrators of an access see and start it but do not change it.
• Times in schedules are UTC, not local time.
• Devices that are offline wait in the run ("waiting for the device") instead of aborting the run.
• Values from devices never become code: conditions insert script results as values. A device cannot force another branch this way.
• Not clicked through on a real relay: the editor is measured in the console mock, not clicked through on browserdesk.de.
• Questions on the device when starting via a start button: G13.

If it does not work