Workflows
Workflows in SVIEW let you define and trigger a sequence of platform
operations — for example, updating a set of Components in a particular order
rather than one at a time. Each Workflow belongs to a Service.
This article is deliberately brief. A worked end-to-end example is being
prepared and will be added here. Until then, if you want to use Workflows for
a specific case, raise a request in your Slack channel and CTO2B will walk
through it with you.
Where to find them
Open a Service and go to its Workflows tab. The list shows the
Workflows defined for that Service, each with its name, the outcome of its last
run, and when that run happened.
Creating and running a workflow
From the Workflows tab you can create a new Workflow, define the steps it
should carry out, and optionally give it a schedule so it runs automatically.
An existing Workflow can also be started manually from its own page.
While a Workflow runs, each step reports its own status. If a step fails, the
run stops there, and that step's output is where to look first before running
it again.
When workflows help
Workflows suit repeatable, multi-step platform operations — sequencing updates
across several Components, or running the same set of steps after an
Environment resumes from suspension.
For a one-off change to a single Component, editing the Component directly is
simpler.
Related articles
- Key Concepts — Service and Component
- Environments — including suspend and resume
- Getting Help — how to raise a request
Updated about 6 hours ago