Documentation

How Conditional Parameters Work?

Before exploring individual conditions, let’s consider an example to understand how conditional parameters are applied.

Example Scenario: Evaluating a Student’s Score

Suppose an automation needs to evaluate a UserScore against predefined criteria, such as PassingScore and ReviewScore. The automation should determine whether the student has:

Passed (UserScore >= PassingScore)

Needs Review (UserScore = ReviewScore)

Failed (UserScore < PassingScore)

For this example, we define the following variables:

• UserScore: Represents the student’s actual score.
• PassingScore: The minimum required score to pass.
• ReviewScore: A threshold score that triggers further review.

These values can be dynamically assigned or hardcoded within the workflow.

Equality and Comparison Conditions:

1. STD_EQUALS – Checks if two values, strings are exactly the same.
   • Configuration: In the Element Key field, enter the variable to be compared (e.g., ${UserScore}).
   • In Parameter, enter the condition keyword followed by the reference value (e.g., STD_EQUALS,${PassingScore}).
   • Syntax: STD_EQUALS,${PassingScore}
   • Example: If UserScore is equal to PassingScore, the system determines that the student has passed.

2. STD_EQUALSIGNORECASE– Checks if two values are the same, ignoring case sensitivity.
   • Configuration: The first value must be given in the Element Key field, and the second value should be entered in the Parameter section after STD_ EQUALSIGNORECASE, separated by a comma (,).
   • Syntax: STD_EQUALSIGNORECASE, “excellent”
   • Example: “Excellent” and “excellent” are treated as the same.

3. STD_NOTEQUALS – Checks if two values are different.
   • Configuration: The first value must be given in the Element Key field, and the second value should be entered in the Parameter section after STD_ NOTEQUALS, separated by a comma (,).
   • Syntax: STD_NOTEQUALS, ${PassingScore}
   • Example: If UserScore is not equal to PassingScore, the system marks the student for review.

4. STD_ALLEQUAL – Ensures all compared values are equal.
   • Configuration: List the standard value in Element Key and define the condition in the Parameter section.
   • Syntax: STD_ALLEQUAL,${UserScore1}, ${UserScore2}, ${UserScore3
   • Example: If all students scored the same, they are grouped together.

5. STD_ALLNOTEQUAL – Ensures all compared values are different.
   • Configuration: List standard value in Element Key and define the condition in the Parameter section.
   • Syntax: STD_ALLNOTEQUAL, ${UserScore1}, ${UserScore2}, ${UserScore3}
   • Example: If all students have different scores, they are categorized individually.

6. STD_LESSTHAN – Verifies if a value is less than another.
   • Configuration: The first value should be in Element Key, and the second value should be provided in the Parameter section.
   • Syntax: STD_LESSTHAN, ${PassingScore}
   • Example: If UserScore is less than PassingScore, the student has failed.

7. STD_GREATERTHAN – Verifies if a value is greater than another.
   • Configuration: The first value should be in Element Key, and the second value should be provided in the Parameter section.
   • Syntax: STD_GREATERTHAN,${PassingScore}
   • Example: If UserScore is greater than PassingScore, the student has passed.

String and List Conditions:

1. STD_CONTAINS – Checks if a string contains a specific substring.
   • Configuration: Enter the main text in the Element Key field and the substring in the Parameter section.
   • Syntax: STD_CONTAINS,Report
   • Example: If “Final Report” contains “Report”, it is classified as a report file.

2. STD_CONTAINSIGNORECASE – Checks for substring presence, ignoring case.
   • Configuration: Enter the main text in the Element Key field and the substring in the Parameter section.
   • Syntax: STD_CONTAINSIGNORECASE,report
   • Example: “Review Report” matches “report” even with different casing.

3. STD_NOTCONTAINS – Ensures a string does not contain a specific substring.
   • Configuration: Enter the main text in the Element Key field and the substring in the Parameter section.
   • Syntax: STD_NOTCONTAINS,Rejected
   • Example: If “Approved” does not contain “Rejected”, the process continues.

4. STD_ALLCONTAINS – Ensures all elements in a list contain a substring.
   • Configuration: Enter the list in the Element Key field and the substring in the Parameter section.
   • Syntax: STD_ALLCONTAINS,Report
   • Example: [‘Pass Report’, ‘Fail Report’] all contain “Report”.

5. STD_ALLNOTCONTAINS – Ensures all elements in a list do not contain a substring.
   • Configuration: Enter the list in the Element Key field and the substring in the Parameter section.
   • Syntax: STD_ALLNOTCONTAINS, “Pending”
   • Example: If [‘Approved’, ‘Rejected’] do not contain “Pending”, they are considered final decisions.

Element and UI Status Conditions:

1. STD_PRESENT – Checks if an element is present on the UI.
   • Configuration: Enter the element name in the Element Key field and use STD_PRESENT in the Parameter section.
   • Syntax: STD_PRESENT
   • Example: If the ‘Submit’ button is present, the user can proceed.

2. STD_NOTPRESENT – Ensures an element is absent from the UI.
   • Configuration: Enter the element name in the Element Key field, and use STD_NOTPRESENT in the Parameter section.
   • Syntax: STD_NOTPRESENT
   • Example: If the ‘Cancel’ button is not present, cancellation is not an option.

3. STD_ENABLED – Confirms an element is enabled.
   • Configuration: Enter the element name in the Element Key field and use STD_ENABLED in the Parameter section.
   • Syntax: STD_ENABLED
   • Example: If the ‘Submit’ button is enabled, the form can be submitted.

4. STD_DISABLED – Confirms an element is disabled.
   • Configuration: Enter the element name in the Element Key field and use STD_DISABLED in the Parameter section.
   • Syntax: STD_DISABLED
   • Example: If the ‘Submit’ button is disabled, the user cannot proceed.

5. STD_SELECTED – Checks if a dropdown option or radio button is selected.
   • Configuration: Enter the dropdown or radio button name in the Element Key field and the option in the Parameter section.
   • Syntax: STD_SELECTED,Grade A
   • Example: If ‘Grade: A’ is selected, the student has achieved an excellent grade.

6. STD_NOTSELECTED – Ensures an option is not selected.
   • Configuration: Enter the dropdown or radio button name in the Element Key field and the option in the Parameter section.
   • Syntax: STD_NOTSELECTED,Grade F
   • Example: If ‘Grade: F’ is not selected, the student did not fail.

7. STD_CHECKED – Verifies if a checkbox is checked.
   • Configuration: Enter the checkbox name in the Element Key field and use STD_CHECKED in the Parameter section.
   • Syntax: STD_CHECKED
   • Example: If the ‘Agree to Terms’ checkbox is checked, the user can proceed.

8. STD_UNCHECKED – Ensures a checkbox is unchecked.
   • Configuration: Enter the checkbox name in the Element Key field and use STD_UNCHECKED in the Parameter section.
   • Syntax: STD_UNCHECKED
   • Example: If the ‘Subscribe to Newsletter’ checkbox is unchecked, no emails are sent.

9. STD_ON – Confirms a toggle or switch is turned on.
   • Configuration: Enter the toggle name in the Element Key field and use STD_ON in the Parameter section.
   • Syntax: STD_ON
   • Example: If ‘Dark Mode’ is enabled, the interface switches to dark mode.

10. STD_OFF – Confirms a toggle or switch is turned off.
    • Configuration: Enter the toggle name in the Element Key field and use STD_OFF in the Parameter section.
    • Syntax: STD_OFF
    • Example: If ‘Notifications’ are off, no alerts are sent.

These predefined conditions simplify the configuration of IF ELSE logic, allowing users to create reliable automation workflows without advanced programming knowledge.