Start a workflow manually
Start a published workflow on a ticket or without a ticket from Workflows, and understand when workflows start on their own.
On this page
Workflows with Starts: Manually are started by a person when needed, for example the onboarding process for a new employee on their ticket. The others start on their own with a catalog request or with a change.
Before you start
You need Operate in Workflows (the Agent role has it).
The workflow must be published and its Starts must be Manually. Only then does the Start button appear.
If you're going to start it on a ticket, have its number at hand (for example
REQ-000412) and make sure you can see that ticket.
Steps
In the side menu, go to Workflows. The Definitions tab opens.
On the workflow's row, press Start.
In Ticket (optional), enter the number of the ticket the workflow runs on, or leave it empty for a workflow without a ticket.
Press Start.
You'll see Workflow started. and the instance details open, where you can follow its progress.
A workflow without a ticket can't use anything from the ticket: actions that change it stop with an error, message waits are never met, and tasks assigned to the ticket's assignee or group end up with no recipient. Start without a ticket only the workflows designed for that.
There's no button to start workflows from the ticket record: start it from Workflows with the ticket number. Once started, the ticket record shows the Workflow panel.
Workflows that start on their own
You don't need to do anything for these workflows:
Starts | When it begins | From where |
|---|---|---|
Catalog request | When the request for a service catalog item that has this workflow in Workflow on request is created. The workflow receives the form answers. | The portal, or an agent ordering through the catalog. |
Change | When a change of one of the checked types (normal or emergency) moves to In assessment. | The Changes view of an MDA desk. |
In both cases, the same workflow doesn't start twice on the same ticket while the first instance is still running, waiting or stopped.
If there's no published version of the workflow, or the workflow is archived, nothing starts: the request or the change continue as usual, just without a workflow.
What happens next
The instance appears in Workflows → Instances as Running and, as soon as it reaches a task or a wait, as Waiting.
The people with tasks and approvals get their notice and see them in My tasks.
If the instance has a ticket, its record shows the Workflow panel with the workflow name, its state and the open tasks.
If something doesn't work
Message | What to do |
|---|---|
The ticket does not exist. | Check the number. If it exists, you may not see it because of your role's scope. |
There is no published version of that workflow. | Publish the workflow first. See Validate and publish a workflow. |
This workflow starts on its own (catalog or changes), not manually. | The workflow isn't manual. Change Starts in Settings if appropriate. |
The Start button doesn't appear. | The workflow isn't manual, isn't published, or you don't have Operate in Workflows. |