Overview

The basic automation construct in Sirveo is called a flow. The management UI provides a flow editor to create and test flows, which are in turn executed by the flow engine. The flow engine supports three kinds of flows, each suited to a different automation scenario.

Graph flows

Graph flows support data-driven automation scenarios. A graph flow is modelled as a directed graph, which is useful for expressing many kinds of processes in an automation context.

This is an example graph flow in Sirveo’s flow editor. This flow measures the latency of an API, and sends notifications when the API is down, or when a response time threshold is exceeded.

Task flows

Task flows are used for automation scenarios which are task-driven. A task flow is modeled as groups of one or more tasks, which executes in phases.

This example of a task flow does the following:

• Fetch some price data
• If the request succeeded;
  • perform some calculations
  • send a notification when a price spike occurred
  • Forward the data to two other API’s, in parallel

Web flows

Web flows are used for interacting with People, via browsers. Web flows support a wide range of automation scenarios where user input is required, as well as seamless integration with task and graph flows.

For example, one of our internal tools quickly generates Sirveo server configuration, based on a series of user selections and inputs. Web flows automatically handles UI generation for browsers, which may looks like this.

A visual layout builder is used to customize the UI of web flows.