This support article aims to provide you with insights into the utilization of operators across various field types.
Within PowerRouter, the available operators play a pivotal role in establishing dynamic conditions. This capability proves invaluable in tailoring the configuration of trigger components, segmentation, and other elements. By employing these operators, users can delineate criteria for their workflows, ensuring that specific actions are executed in accordance with the given conditions. The fundamental syntax for incorporating conditions is as follows:
Outlined below is a comprehensive breakdown of the operators at your disposal, along with their respective use cases:
- Equal (=) - This operator serves to validate whether the data field value of a lead corresponds precisely with the specified condition value. For example:
- Not Equal (!=) - Employing this operator involves examining whether the lead's data field value diverges from the value stipulated within the condition. For instance:
- Greater than (>) - This operator evaluates whether the numerical value of the lead's data field surpasses the value indicated in the condition. For example:
- Less than (<) - This operator investigates whether the numerical value of the lead's data field is lower than the value provided in the condition. For example:
- Greater than or equal to (>=) - This operator validates if the numerical value of the lead's data field is either greater than or equal to the value stated in the condition. For example:
- Less than or equal to (<=) - This operator ascertains whether the numerical value of the lead's data field is either less than or equal to the specified condition. For example:
- CONTAINS - This operator verifies if the lead's data field value contains the text mentioned in the condition. Multiple text values can be included, separated by commas. For example:
- NOT CONTAINS - This operator checks whether the lead's data field value does not incorporate the text indicated in the condition.
- IN - This operator guarantees that the lead's data field value aligns with at least one of the specified values within the condition. For example:
- NOT IN - This operator affirms that the lead's data field value does not correspond to any of the values given in the condition. For example:
- ISBLANK - This operator establishes whether a specific data field value is empty or not, resulting in a boolean response. For example:
- STARTS WITH - This operator examines if the lead's data field value commences with the provided text in the condition. For example:
- ENDSWITH - This operator authenticates whether the lead's data field value concludes with the designated text outlined in the condition. For example:
It's important to note that not all operators are suitable for every type of data field. To provide clarity, let's delve into the various data field types in PowerRouter and the applicable operators for each:
- TEXTAREA field: Common TEXTAREA fields in PowerRouter include Company, City, and Country, among others. Operators compatible with these fields are Equal, Not Equal, IN, NOT IN, STARTSWITH, ENDSWITH, and ISBLANK. For instance, a lead record will meet the condition only if the company name is "Kudos Pvt. Ltd.," while blank spaces won't satisfy the condition. For example:
- CHECKBOX field: Checkbox fields that accept boolean values (true/false) utilize operators like "=", "!=", and ISBLANK. For example:
- DATE/DATETIME/TIME field: These fields signify time and date values. Suitable operators for filtering based on time include "=", "!=", ">", "<", ">=", "<=", and "ISBLANK." As an illustration, consider a Date Field like "Last Activity." For example:
- NUMBER field: Numeric fields, such as "Annual Revenue," store numerical values. Applicable operators for filtering numerical values are "=", "!=", ">", "<", ">=", "<=", "IN," "NOT IN," and "ISBLANK." For instance:
Understanding the compatibility between operators and data field types empowers PowerRouter users to craft precise conditions that effectively guide trigger components and other functionalities. This sophisticated interplay between operators and data fields facilitates informed decision-making within the workflow process.
Was this article helpful?
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
We appreciate your effort and will try to fix the article