Adding an Action

Actions are tasks that SOTI Connect performs on devices when specific conditions (triggers) are met. When configuring rules, you can add one or more actions to define what should happen when the rule criteria are satisfied.
Note:
  • The list of available actions depends on the device or device types the rule applies to. If multiple device types are selected, only the actions common to all selected types will be displayed.
  • Starting with SOTI Connect 2025.0.2, you can hover over the device group names to view the full path.
Actions are operations that can be automatically executed on devices. These include:
  • Check-in: Verifies device status or connectivity.
  • Set State: Changes the device's operational state (for example, from offline to online).
  • Rename: Updates the device name dynamically (for example, using DEVICEID).
  • Firmware Upgrade: Pushes new firmware to devices.
  • Configuration Update: Applies new settings or profiles.
  • Send Alerts: Notifies admins via email or SMS when issues arise.
  • Retry/Skip/Go to Action: Controls flow based on success or failure of previous actions.
Use actions in scenarios like:
  • Automated Maintenance: Schedule firmware updates or configuration changes during off-hours.
  • Error Handling: If a check-in fails, retry or skip to another action to ensure continuity.
  • Device Onboarding: Automatically configure and rename new devices upon enrollment.
  • Monitoring & Alerts: Trigger alerts when a device goes offline or reports an error.
  • Bulk Operations: Apply changes to multiple devices simultaneously to save time.
Actions can execute in:
  • Parallel
  • Sequential
    Note: For sequential actions, configure the reaction type for a failed action. Choose from:
    • Interrupt
    • Continue
    • Go to action
    • Retry

Actions Execute in Parallel

When actions execute in parallel, actions execute simultaneously. This means that you cannot predict which action completes first because both actions are running at the same time. This can be useful in situations where actions are independent and do not rely on each other to complete.

Warning: When using enrollment rules with parallel actions, a device action may execute before the enrollment action. In this case, the action will not be applied to the device. To avoid this issue, use "Execute Sequentially".
For example, the following enrollment rule has two actions: "Check In" and "Set State":
Rules with many actions run in parallel
Consider the evaluation of a compliance rule, along with the above enrollment rule that states "when Device State is Yellow, set Compliance Status to Non-compliant."
Unpredictable results occur when many rules evaluate in parallel
The compliance check evaluates unpredictably and either one of the following outcomes can occur:
  • Case 1: If A evaluates after B, the device is compliant.
  • Case 2: If B evaluates after A, the device is non-compliant.

Actions Execute Sequentially

When actions execute sequentially, actions execute one after the other. Each action must complete before the next one can begin. This ensures a predictable order of execution and outcomes, which is beneficial when actions are dependent on the completion of previous actions.

For example, consider this rule, where actions execute one after other:
Execute Sequentially

This rule causes the following actions to execute sequentially:

  1. Set device state to "Yellow."
  2. Begin device check-in. If device check-in fails, interrupt the rule.
  3. If device check-in succeeds, set device state to "Green."