Skip to main content
Version: 24.5

Flows

Flows allow creating automation flows to detect specific situations by evaluating compliance with certain conditions, and act based on the result of that 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.

home_flow

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​

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: marks the minimum time that will pass once the evaluated condition is met before the evaluation is executed again.
  • Detection only: condition evaluation in "sampling" mode. Detects those devices that meet the conditions, but without executing the microservice defined in the flow.

Target​

This setting allows defining the device group(s) where the flow will run. It supports the following configuration options:

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

Flow​

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.

flow

Flow conditions​

  • Existence of an ongoing process: allows the periodic evaluation, in intervals from fifteen seconds to five minutes, of the existence of a running process. Supported operating system: Windows.
  • Detected Windows event log identifier: this condition searches for events in the Windows event viewer with a specific name, provider, or ID at intervals of five to twenty minutes. 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.
  • Actions: allow actions to be executed once the conditions are evaluated and according to the obtained values. In this section, all microservices enabled in your subscription will appear, so you can select and include them 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.