Build Signal Policy Conditions

Define conditions for when SOTI MobiControl triggers a Signal policy by using categories, attributes, and values. Use logical operators to group multiple conditions and monitor device or system events.

Before you begin

Confirm you meet all prerequisites by reviewing Create a New Signal Policy.

About this task

As part of configuring a Signal policy, you must define the specific conditions that trigger it. This task guides you through the process of creating those conditions. You can select categories, specify attributes, and define values. Use logical operators to combine multiple conditions and set the actions the policy executes when those conditions are met.
Build conditions of your Signal policy to:

  • Automate device responses based on specific properties or events.

  • Monitor critical system thresholds, such as memory usage or license availability.

  • Target specific device groups with tailored policy conditions.

Procedure

  1. In the Conditions tab of the Create Signal Policy dialog box, select Add Condition to add a condition to your first condition group.
    1. Choose a Category for your condition.
      Category dropdown expanded in the Signal policy condition screen, showing available options.
    • Managed Device: Properties and events related to devices enrolled in SOTI MobiControl.
      Important: Supported managed devices can evaluate specific Managed Device properties at a defined frequency. This enables Signal policies to be much more responsive, as earlier SOTI MobiControl versions required device check-ins with the server to evaluate Signal policies and trigger actions. See Configure Signal Policy Settings for more details.
    • Management Server: Properties and events related to the SOTI MobiControl Management Server.
    • Deployment Server: Properties and events related to the SOTI MobiControl Deployment Server.
    • Profile: Properties and events related to profiles managed in the SOTI MobiControl web console.
    • System: Properties and events related to system devices, such as the percentage of remaining licenses.
    • System Certificate: Properties and events related to SOTI MobiControl system certificates in the web console.
    • Policy: Properties and events related to policies, such as policy name and type.
    • User, Group, and Role: Properties and events related to users and groups, such as group or user name.
    • Cloud Link Agent: Properties and events related to Cloud Link Agent.
      Tip: In SOTI MobiControl 2024.0 and later, you can build a condition using Custom Data for the Managed Device category. See Using Custom Data for more information.
  2. Choose the appropriate condition attribute type.
    • Property: Details of devices, servers, or location zones such as available memory, server name, or device count (within a zone).
    • Event: Details of common events in the daily operation of devices, servers, or location zones, such as SIM card inserted or deployment server stopped.
    1. When selecting a property and an attribute, select an operator (such as Starts With or Is) and enter a value to build the condition.
      For example, you can create a condition that monitors a managed device with available memory less than 2 GB.
      Selecting an operator for a condition in a Signal policy.

      Remember: For Custom Attributes and Custom Data to be selectable from the Attributes dropdown, you must first create them. See Creating Custom Attributes and Creating Custom Data Items.
    2. Select Add to add your condition to the list of conditions.
      Note: When creating a Managed Device category condition, select Select Device Groups to watch at least one device group.
  3. Repeat step one to add more conditions as required.
    Tip: Hover over the existing condition rows to edit or delete them.
  4. Optional: If you add more than one condition, you can change the dropdown menu, X of these conditions must be satisfied, such that X is one of the following options:
    • ALL: The Signal policy triggers only when all listed conditions evaluate to True. This configuration creates an AND style condition set. For example:
      • Device Battery < 10% AND Device Memory < 1 GB
    • ANY: The Signal policy triggers if any listed condition evaluates to be True. This creates an OR style condition set. For example:
      • Device Battery < 10% OR Device Memory < 1 GB
    Criteria dropdown expanded, showing options for evaluating multiple conditions in a Signal policy.
  5. Select New Group to add a new group of conditions to combine with those added earlier. Later groups can feature different categories.
  6. When adding more than one group of conditions, set the Grouped Conditions to Trigger Actions Must Include dropdown menu to ANY or ALL described in step three.
    For example, for condition groups A, B, C, D, and E:
    • Select ANY to set up an OR style condition set between the condition groups: [(A AND B AND C) OR (D AND E)]
    • Select ALL to set up an AND style condition set between the condition groups: [(A OR B OR C) AND (D OR E)]

What to do next

After specifying your conditions, select Next to continue to the next step in the Signal policy creation process: defining the actions your policy performs when triggered. For details, see Add Signal Policy Actions.