Dynamic operators in Service Portal

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. You can create dynamic groups and admin tables etc 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. 

In the Service Portal, dynamic operators are utilized to configure conditions based on specific fields. 

These operators typically include options such as equals, not equals, greater than, less than, contains, does not contain, dynamic etc., allowing users to define precise conditions for triggering certain actions or displaying relevant information.

Configure Condition

The Condition tab in the Service Portal includes Field, Operator, and Value. The values under the tab load are based on user Role access. Figure: Condition
To configure Condition, perform the following general steps:

1.  Select Field from the dropdown list to apply the conditions.
2.  Select an appropriate operator from the drop-down list based on the field type. Specify when the condition should be triggered. This value can be selected from the respective field type for referenced fields such as single choice control.
   
   Note

   For adding conditions, icon can be used to include new conditions.

   For removing conditions,   icon can be used to delete unwanted conditions.
   See the Field Description table for more details.

Default Field

Field values 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.

No of Records

This is the field that is configured the by default first condition in the scheduler. The operators that can be used in this regard are =, >=, <=, >, <. 

Figure: No of Records condition

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. 

Figure: Condition stepper

Dot Walking

The Dot walking concept helps to create a dropdown based on the table selected 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 table
• Main table to Multiple 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. Furthermore, special considerations can be given to fields of Date type. Figure: Condition stepper Figure: Condition stepper - Dynamic

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.

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.

When Data Type is Boolean

Consider the example where the user has selected the Field as Is Active under Conditions, then the Operator will Is and Value as shown below.
Figure: When Data Type is Boolean

Value	Implication
	Yes
	No

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 three types:

1. 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.
   
   
2. 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.
   
   
3. 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.

Types of condition operators in Service Portal

This section details different scenarios of condition operators based on defined values.

• Tenant values load based on the role access of the logged-in user, with the option to select all tenants also available under 'All', and only those tenants selected at the General Step gets displayed.
  Figure: Tenant
  
  
• When fields are selected as user properties from the user master table, the operator list appears grouped into Dynamic and Static categories. For instance, if the field selected is Requestor (from the User master table), the Operator drop-down loads with options grouped under Static and Dynamic categories.
  Figure: Dynamic or static operator
  
  
• If the fields are selected from any other table except the user master table, then the operators will be static only. For instance, if the field selected is Incident ID from the Incident Master table, the operators will load as static only, not grouped, as shown below.
  Figure: Static operator
  
  
• For the user master field, if you select a dynamic operator, the value loads based on the Logged-in User and becomes greyed out. Refer to the screenshot for more details.Figure: Dynamic operator
  
  
• If a dynamic operator is selected, the value field populates with the Logged In User and becomes greyed out. Additionally, fields from the user master table are displayed in the value field, with the user master field about the condition being automatically selected and greyed out. For instance, in a scenario where the location dynamically populates based on the Logged-in User's Location, the corresponding field will be automatically selected in the value drop-down list and greyed out.
  Figure: Dynamic operator for user field