Skip to main content
Version: 24.9

Flows

The Flows allow you to create automation flows to detect specific situations by evaluating the fulfillment of certain conditions, with the purpose of acting based on the result of this evaluation.

This approach simplifies proactive diagnostic actions, solves problems quickly when focused on their detection, and provides a very efficient way to enable self-remediation mechanisms for common issues.

It also allows technical teams to align devices with configurations defined by the organization, evaluating them periodically and adapting them if necessary.

flow1

Configuration​

Each flow comes with options that allow customizing its behavior:

A configuration change to an existing flow can take up to 15 minutes to apply to all linked devices.

Overview​

It stores general information about the flow.

  • Description: description of the flow
  • Created: creation date of the flow
  • Type: is the execution scope of the flow, determined by the type of microservice you want to run. It can be done at the user session level, with the corresponding permissions, or at the device level, with administrative access.
  • Cooldown period: marks the minimum time that will pass, once the evaluated condition is met, for that evaluation to be executed again.
  • Detection only: evaluates conditions in a "sampling" mode. Detects those devices where the conditions are met, but without executing the microservice defined in the flow.

Edit and delete a flow​

Using the Edit button, you can change the name, description, and flow reuse time. Delete allows you to remove a flow and gives the option to confirm its deletion.

flow-delete

Target​

This setting allows you to define the device groups where the flow will be executed. It supports the following configuration options:

  • All devices
  • A custom selection of devices
  • One or several groups of workspaces
  • One or several reporting groups

Flows​

From here, you can define the conditions to be evaluated, the required thresholds, and the action that will be executed if those conditions are met.

flow2

Flow conditions​

  • Existence of an ongoing process: allows evaluating periodically, in lapses from fifteen seconds to five minutes, the existence of an ongoing process. Supported operating system: Windows.
  • Detected Windows event log identifier: this condition searches, in intervals of five to twenty minutes, for events in the Windows event viewer with a specific name, provider, or ID. These must be specified in the format <logName>:<source>:<id>; for example Application:my_app:101. Where:
    • Logname = Application
    • Source = my_app
    • id = 101

evid

  • Operating system version: allows obtaining the operating system version at intervals between one and twelve hours, using operators where the value is equal, starts with, ends with, or contains a specific string of text. Supported operating system: Windows.
  • Operating system language: detects, at intervals between one and twelve hours, the operating system language. Uses operators where the value can be equal to, starts with, ends with, or contains a specific string of text. Supported operating system: Windows.
  • Percentage of free disk space of the operating system: allows evaluating and setting a target percentage value in intervals ranging from five to sixty minutes. Supported operating system: Windows.
  • Cron Match: checks if a cron string is met only when the current date and time exactly match the specified cron expression. The hours are defined in UTC.
  • Actions: once the conditions are evaluated and according to the obtained values, they allow an action to be executed. In this section, all enabled microservices in your subscription will appear to be selected and included in the flow.

Notification​

This parameter is optional and can be disabled. Allows sending notifications to users at the start and end of flow execution, using operating system notifications. Once activated, it allows setting:

  • Initial message: will be sent to users at the start of the execution.
  • Success message: will be sent to users upon successful execution.
  • Error message: will be sent to users upon execution errors.