Skip to main content
Version: 24.10

Flows

This functionality allows you to create automation flows to detect specific situations on devices by evaluating the compliance of certain conditions, and act based on the result of that evaluation.

flow1

This approach simplifies proactive diagnostic actions, quickly solves problems when there is a focus on their detection, and provides a highly efficient way to enable self-remediation mechanisms for common issues. It also allows technical teams to couple devices to configurations defined by the organization, evaluating them periodically and adapting them if necessary.

Each flow has options to customize its behavior:

info

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

Overview​

Agent

Stores general information of the flow.

  • Description: description of the flow
  • Type: it is the execution scope of the flow, determined by the type of microservice to be executed. It can be done at the user session level, with the corresponding permissions, or at the device level, with administrative access.
  • Version: indicates the version of the flow, each edition increments the counter by 1.
  • Reuse time: 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.
  • Status: allows you to see if the flow is enabled or disabled.
  • Created on: shows the creation date.
  • Update date: shows the update date.
info

On the top right, there is a button that, depending on the state of the flow, allows it to be enabled or disabled.

Edit and delete a flow​

flow-delete

Using the Edit button, you can change the name, description, and reuse time of the flow.

  • The Detection Only checkbox allows you to activate or deactivate the Detection Only execution mode, in which the compliance with the conditions defined in the flow is evaluated, but the microservice is not executed.
  • The Delete button allows you to delete a flow.

Target​

analog

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

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

Flow​

From here you can define the conditions to evaluate, the required thresholds and the action to execute if these conditions are met.

flow2

Flow conditions​

  • Existence of an ongoing process: allows you to periodically evaluate, in intervals of fifteen seconds to five minutes, the existence of a process in progress. Supported operating system: Windows.
  • Windows event log identifier detected: 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 you to obtain, in intervals between one and twelve hours, the operating system version using operators where the value is equal, starts, ends, or contains a certain string of text. Supported operating system: Windows.
  • Operating system language: detects the operating system language at intervals of one to twelve hours. It uses operators where the value can be equal, start, end, or contain a certain string of text. Supported operating system: Windows.
  • Percentage of free disk space in the operating system: allows you to evaluate and set a target percentage value at intervals of five to sixty minutes. Supported operating system: Windows.
  • Cron Match: checks if a cron formatted string matches only when the current date and time exactly align with the specified cron expression. The hours are defined in Coordinated Universal Time (UTC).
  • Actions: once the conditions are evaluated and according to the obtained values, allow an action to be executed. In this section, all the microservices enabled in your subscription will appear to be selected and included in the flow.

Notification​

Agent

This parameter is optional and can be disabled. Allows notifications to be sent to users at the start and end of the flow execution, using the operating system notifications. Once enabled, you can set:

  • Initial message: will be sent to users when the execution begins.
  • Success message: will be sent to users on successful execution.
  • Error message: will be sent to users on execution with errors.
info

To learn how to create a flow, please refer to the Scheduled Execution of Microservices guide.