Deployment workflowsNEW
Define what a new VM goes through, as stages, tasks and steps, and pick a workflow per template.
The Deployments page
Deployments (in the sidebar) holds the organization's workflows in three tabs. Saving workflows needs org.settings; everyone can read them.
| Tab | Purpose |
|---|---|
| Provisioning | What a new VM goes through. Picked per template. |
| Configuration | Workflows you run on existing VMs. See Configuration runs. |
| Runs | Every configuration run, per VM and step. |
How a workflow is built
- Stages run in order, for example Infrastructure, Guest setup and Availability. A stage can have a caption and a pause before it starts.
- Tasks group the work inside a stage. A task is shown either as one progress bar or as a checklist of steps.
- Steps do the work. Each step has a name, an optional command text shown in the live view, an expected duration and an action.
- A workflow can end with a summary: a title, a short text and a copyable connect line such as mstsc /v:{{vm.ip}}.
A step without an action is display-only. Actions are described on the Workflow actions page.
Editing
| View | Use it for |
|---|---|
| Builder | Edit stages, tasks and steps as a structured list with action forms |
| Canvas | Edit the workflow as a drag-and-drop node graph (can be turned off with the Deployments canvas feature flag) |
| JSON | Edit or paste the raw workflow definition |
| Preview | Play the workflow as a simulated run to see timing and messages |
- Problems such as missing required fields or unknown variables are listed before saving; the preview needs a valid workflow.
- Standard starts from the built-in deployment with every step and its real action. Duplicate copies a workflow as a new one.
The built-in deployment
- 1Clone the template, start the VM and assign the node's backup job (continues on error).
- 2Wait for the Verlocx agent to come online.
- 3Set the hostname, join the domain, add local admins, verify hostname and domain.
- 4Add the VM to high availability (continues on error).
Save it as your own workflow, add steps such as scripts, waits or reboots, and assign it to templates.
Use a workflow for a template
- 1Open the template from the Templates page and go to its Defaults tab.
- 2Choose the workflow under Deployment workflow and save. The template's rule must be enabled.
- 3New VMs from that template now run the workflow. A provisioning workflow must contain the clone action; otherwise new VMs use the built-in steps.
If the chosen workflow is deleted later, the template shows it as missing and new VMs fall back to the built-in steps.
Watching a deployment
The VM page shows the running deployment live: each stage and task with its status, progress bars for long operations, and the latest message from the guest agent. Each job keeps a frozen copy of the workflow it started with, so editing a workflow never changes a deployment that is already running.
Features on this page
- Deployment workflowsNEW
- Builder, Canvas, JSON and PreviewNEW
- Standard workflow as a starting pointNEW
- Live deployment viewNEW
More in AutomationAll topics
Workflow actionsThe action catalog, variables, conditions, timeouts and error handling for workflow steps.Configuration runsApply configuration workflows to existing VMs with idempotent building blocks, a dry run and a results grid.Workflow actionsThe action catalog, variables, conditions, timeouts and error handling for workflow steps.