SOTI Pulse Logo

SOTI Signal rule does not trigger when using "All groups must match"

QY
Qing Ye
meferi2023

SOTI Signal rule does not trigger when using "All groups must match"

Hi everyone,

I recently encountered an issue while configuring a SOTI Signal rule and wanted to check whether this is expected behavior or a configuration problem.

I currently have two condition groups configured:

Condition Group 1

  • Configuration Name = a-3

Condition Group 2

  • Device Name contains xxx

At the top-level rule logic, I selected:

All groups must match

Based on my understanding, the rule should trigger only when:

  • the device name contains xxx
    AND

  • the configuration name is a-3

However, during testing:

  • When using "All groups must match", the rule never triggers

  • When changing it to "Any group matches", both conditions can trigger successfully

So both conditions themselves appear to be working correctly.

My current suspicion is that:

  • the configuration condition

  • and the managed device condition

may belong to different event contexts/entities, causing the AND logic across groups to fail.

I would like to ask:

  1. Is this expected behavior in SOTI Signal?

  2. Can configuration conditions and device conditions be combined with AND logic across separate groups?

  3. Should both conditions be placed inside the same condition group instead?

  4. Has anyone encountered a similar issue before?

Thanks in advance.

11 days ago
SOTI MobiControl
ANSWERS
K
KJMOD@soti.net
3 days ago

Hi Qing Ye,

Thanks for posting on SOTI Pulse.

1) Yes, the behavior you are observing where the rule does not trigger with "All groups must match" is expected. This is often due to how conditions are processed based on their context. Conditions that reference different entities (like device attributes vs. configuration settings) may not communicate effectively when evaluated together with AND logic across separate groups.

2) Generally, when conditions belong to different contexts, combining them with AND logic can lead to issues. In your case:

  • Condition Group 1 (Configuration Name) deals with the configuration applied on the device.
  • Condition Group 2 (Device Name) pertains directly to attributes of the device itself.

Given that these two conditions refer to inherently different contexts (one focusing on the configuration settings and the other on the device properties), the system may not evaluate them in the same logical scope when enforcing the "All groups must match" rule.

3) Yes, to achieve the desired outcome where both conditions must be satisfied before the rule triggers, you should place both conditions within the same condition group. This way, the logic can evaluate the conditions directly relative to each other within a unified context.

4) This type of issue is not uncommon in rule-based configurations where conditions span different contexts.

Kindly let me know if you have any further concerns.

Thank you for choosing SOTI.

Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net

Similar Discussions