---
title: "Set Conditions"
slug: "set-conditions-scheduler-module"
tags: ["Dot Walking", "Dynamic Tables", "Default Fields", "No. of Records", "Tenant"]
updated: 2025-02-05T05:24:14Z
published: 2025-02-05T05:24:14Z
canonical: "help.symphonysummitai.com/set-conditions-scheduler-module"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Set Conditions

The third step in the Scheduler process is setting Conditions. To configure the Scheduler Conditions, define the Field, Operator, and Value. For more information, refer to the field description table below.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1712734971043.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

Figure: Condition configuration page

| Field | Description |
| --- | --- |
| Field | Select the record from the drop-down menu based on the table selected in the General Details tab.NoteAll the fields related to the main form and pop-over form are available for selection. |
| Operator | Choose the operator to meet the stipulated condition in value. The operator would vary depending on the type of values selected in the Field. For example, Text, Numeric etc. |
| Value | Specify the value to be attained. |

Note

- For adding conditions, ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1673347145573.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)  icon can be used to include new conditions.
- For removing conditions,  ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1673347727555.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D) icon can be used to delete unwanted conditions.

  

## Field

Fields will populate according to the transaction table chosen from the drop-down list in the General Details tab, from where you can select the necessary option.

### Default Fields

The following are the default fields set in the scheduler.

- No of Records
- Tenant

#### No of Records

This field is configured by default as first condition in the scheduler. The operators that can be used in this regard are =, >=, <=, >, <. The **number of records** condition cannot be removed from the scheduler.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1715062820941.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)Figure: No of Records condition

NoteThe value of count of records will by default be 1 and cannot be 0. It can be increased depending on the requirement for which the scheduler is created. 

#### Tenant

The by default second condition is Tenant selection on the condition screen. The Tenant will be populated based on the Domain and Sub Domain selected.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1715063263515.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

Figure: Condition stepper

### Dot Walking

The Dot walking concept helps us to traverse from one table to another table based on the data source of the field selected from the table in the general details screen. Usually, conditions can be set on properties connected to the parent table and related tables alike.

The concept is available for users who want to define conditions on the attributes of the parent table. The Dot Walking concept is applicable in all the below scenarios.

- Within the same table
- Main table to another associated table
- Main table to multiple associated tables

Dot walking is the process of using the dot notation to navigate from the parent table to the associated tables. It is easy to move from one table to another with dot walking. It decides which operators should be loaded and what values to take into account based on the types of fields. The operator would load based on the data type of the last node in dot walking.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1707114469108.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)Figure: Condition stepper

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1707115561680.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

Figure: Condition stepper - Dynamic

NoteThe dot walking concept allows to select conditions based on the resolution SLA percentage so that notifications can be sent to Workgroup members and Analyst. 

## Operator

The operators will be displayed based on the selected field value. Select the required operator from the drop-down list. The possible values for operators are as shown below.

**When the Data Type is String** Consider the example where the user has selected the **Description** field, then under the **Conditions**, the Operators loaded will be related to the **Textbox** values.

| Field | Operator | Value |
| --- | --- | --- |
| Description | Starts with | Outlook |
| Description | Ends with | Outlook |
| Description | Contains | Outlook |
| Description | Does not contain | Outlook |
| Description | Is | Outlook |
| Description | Is Not | Outlook |
| Description | Is Empty | NA |
| Description | Is Not Empty | NA |
| Description | Less than | 20 |
| Description | More than | 20 |
| Description | Changes | NA |
| Description | Doesn't change | NA |
| Description | Changes from | one to another |

### **When Data Type is Numeric**

Consider the example where the user has selected the **Numeric** field, then under the **Conditions**, the Operators loaded will be related to the **Numeric** values.

| Field | Operator | Value |
| --- | --- | --- |
| Cost | = | 15 |
| Cost | != | 15 |
| Cost | > | 15 |
| Cost | < | 15 |
| Cost | Is Empty | 15 |
| Cost | >= | 15 |
| Cost | <= | 15 |
| Cost | Between | 15 to 50 |
| Cost | Changes | 15 |
| Cost | Doesn't Change | 15 |
| Cost | Changes from | 15 to 50 |
| Cost | Is one of | 15 |
| Cost | Is not one of | 15 |

NoteThere is a provision to set multiple input in the values field by adding a comma separator when the operator is selected as **is one of** / **is not one of** . For example, when we want to search Incident ID, we can use the following operators **is one of** / **is not one of** to give values separated by commas. For more information, refer to the image below.  
  
![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1716526844788.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

### **When Data Type is Date**

Consider the example where the user has selected the **Date** field, then under the **Conditions**, the Operators loaded will be related to the **Date** values.

| Field | Operator | Value |
| --- | --- | --- |
| Date Type | On | 16-May-2023 |
|  | Not on | 16-May-2023 |
|  | Before | 16-May-2023 |
|  | On or Before | 16-May-2023 |
|  | After | 16-May-2023 |
|  | On or After | 16-May-2023 |
|  | Between | 1-1-2022 - 31-12-2022 |
| Closed Date | Is Empty | NA |
|  | Is Not Empty | NA |
|  | Is Anything | NA |
|  | Is Same | Logged Date |
|  | Is Different | NA |
|  | Is More Than | one day after current date |
|  | Is Less Than | two days before current date |
| Last Updated | Changes | NA |
|  | Doesn't Change | NA |
|  | Changes From | NA |

As illustrated below, the "Date control" operator function allows multiple conditions to be set on the conditions page. The operators that can be used in this scenario are:

- Is more than
- Is less than

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Dynamic%20Operator%20in%20Conditions.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

### **When Data Type is Boolean**

Consider the example where the user has selected the Field as **Is** **Active** under **Conditions**, then the Operator will be **Is** and Value as shown below. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1715766462441.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)Figure: When Data Type is Boolean

| Value | Implication |
| --- | --- |
| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1715848818645.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D) | Yes |
| ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1715848830315.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D) | No |

### Dynamic Operator

Tables in a user interface or an application's backend that can alter their content easily in response to events, user input, or data modifications are referred to as dynamic tables. We can create dynamic groups and admin tables to which the dynamic conditions can apply. Because of these tables' extreme flexibility and adaptability, developers may design interfaces that support a wide range of data types and user needs or interfaces that can adapt to different user needs and data formats.

The "Dynamic" operator function can be used to map the dynamic tables in the scheduler. When we select the Dynamic operator, we get two drop-down. The first drop-down is to select Dynamic groups/Admin Table and the second drop-down is to select the fields of the table selected. For more information refer the image below.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/Dynamic%20Tables.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

For more information on the Dynamic concept in Schduler, refer Dynamic Scheduler

- When Dynamic tables are selected in the condition stepper, all the Admin tables will appear grouped under Admin Table, whereas only those Dynamic groups will appear which belong to the Transaction table (Based on the table on which the Scheduler is being configured, the Admin Table/Dynamic Group should point to the same data source).  The selection of Field/Table points to the same data source (screenshot)**.**

NoteNumber of Dynamic conditions should be less than or equal to (n-1) columns of the Dynamic table, where n is the number of columns in the dynamic table. 

## Grouping of Conditions

When there are multiple conditions which need to be computed together, these conditions can be grouped together in a Scheduler. This can be achieved by using the **AND/OR** conditions and by using the grouping functionality provided in the tool.

![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-1713687054148.png?sv=2026-02-06&spr=https&st=2026-11-02T15%3A37%3A31Z&se=2026-11-02T16%3A37%3A31Z&sr=c&sp=r&sig=FCuLCLIXN%2FGsNN8XaSUlAaRhxbT5coiwpxkmcHHQXeA%3D)

Figure: Grouping of Conditions

Note

- A Static condition with **And** of Dynamic condition is allowed.
- A Static condition with **Or** of Dynamic condition is not allowed.

## **Value**

Based on the selected **Field** type and **Operator** the options are populated in the **Value** field.

The value field can be one of the following four types:

1. **Date**: Represents a calendar date. This can be used for inputting or displaying dates in various formats (e.g., MM/DD/YYYY or YYYY-MM-DD). In programming, date-related operations and formatting are commonly used for managing time-sensitive data.
2. **Dropdown**: A dropdown, also known as a drop-down menu or list, is a user interface element that allows users to select one option from a list of available options. This is often used when you have a predefined set of choices, and the user can choose one from the list.
3. **Numeric**: Refers to numerical data, including integers and floating-point numbers. Numeric input is used when you need users to enter numerical values, such as quantities, amounts, or any other numeric data. Validation is typically applied to ensure that only valid numeric input is accepted.
4. **String**: Represents a sequence of characters. String input is used for text-based data, such as names, addresses, or any other textual information. It's a versatile data type that can accommodate a wide range of alphanumeric characters.