Actions are the tasks that SOTI Connect performs on devices when certain
conditions (triggers) are met. Add one or more actions when configuring Rules.
Select the action you want a rule to perform when meeting rule criteria.
Note: The list of actions that are available depends on the
device or devices to which a rule applies. If you select different device types,
only the actions common to all selected device types displays.
Note: For SOTI Connect 2025.0.2, you can now
hover over the device group names to see 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.
For example, the following enrollment rule has two actions:
"Check In" and "Set State":
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."
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:
This rule causes the following actions to execute sequentially:
Set device state to "Yellow."
Begin device check-in. If device check-in fails, interrupt the rule.
If device check-in succeeds, set device state to "Green."
