Conditions

Conditions

Conditions

A rule is composed of conditions and actions. Conditions evaluate data in the system to produce a true or false result. Actions perform automated tasks in the system when those conditions are true.

When more than one condition exists in a rule, the conditions are bound together by using AND logic. For example, condition 1 has field X equal to Yes. Condition 2 has field Y equal to Yes. In order for the overall rule conditions to be true, and an action to occur, field X, and field Y both need to be Yes. OR statements are added by creating another rule with a different set of conditions, or by using the Link to existing rule condition where branching of rules can occur.

Multiple existing conditions that are using different fields on the same form are grouped, and thus evaluated together for multiple form instances.

Category

To create a new condition, select a Category.

• The category selection further refines the selections to specify the condition.
• The list of categories that are available might change depending on the Trigger Mechanism and Trigger Context that is selected for the trigger.
• In cases where there is no candidate in context, all candidate conditions are hidden. In cases where there is no req in context, all req conditions are hidden.
• For more information on the available categories and typical uses, see the Category Reference.

Name

If applicable, the Name selection is presented when the category is selected. For more information on names available for categories, see the Category Reference.

Field

If applicable, the Field selection is presented when the Name is selected. For more information on the fields available for categories, see the Category Reference.

Operation

The Operation selection is presented when the Field is selected. Operations determine how to evaluate the field or category that is selected. The available operations depend on the field type selected. The following lists the operations based on field type.

• Single select, Multi select, Query select, Radio button, Checkbox fields
  • Equals
  • Not Equals
  • Is Blank
  • Is Not Blank
• Date
  • Equals
  • Not Equals
  • Greater Than
  • Less Than
  • Is Blank
  • Is Not Blank
  • Greater Than (# days)
    • Using this operation takes the Define Value for this condition and adds it to today’s date, producing Date X. The date field selected (say Date Y) here is then compared to Date X. If Date Y is greater than Date X, then this condition is true.
    • Negative values can be input into the Define Value box.
    • Within scenario – use Greater Than (# days) with negative value.
  • Less Than (# days)
    • Using this operation takes the Define Value for this condition and adds it to today’s date, producing Date X. The date field selected (say Date Y) here is then compared to Date X. If Date Y is less than Date X, then this condition is true.
    • Negative values can be input into the Define Value box.
    • Not Within scenario – use Less Than (# days) with negative value.
    • If date on the form is considered as an actual expiration date – use Less Than (# days) with 0.
• Numeric
  • Equals
  • Not Equals
  • Greater Than
  • Less Than
  • Is Blank
  • Is Not Blank
• Text
  • Contains
  • Not Contains
  • Is Blank
  • Is Not Blank
  • Equals
  • Not Equals

Select Values.

When the field or category that is selected has a finite list of options to choose from, for example a single select list, then the Select value(s) option is available. This allows selection of the specific value to evaluate. It is evaluated based on the operation selected.

Compare Value

When the field or category that is selected is available to be compared, then the Compare value option is shown. This selection compares this field to another field. A second field must be selected to be used in the comparison. The comparison logic uses the Operation that is defined.

• Date and Numeric field types can only be compared to fields of the same type. All other field types can be interchanged for comparisons.
• If comparing a text field with an options list (that is Single-select), then the comparison uses the Code of the options list to compare. It does not compare the Description.
• Multi-selects are always treated as an OR scenario when performing the comparison logic. For example, if a text field is selected, and the comparison is to a multi-select field with two options (Option A and Option B) selected, then the condition evaluates whether the text matches either Option A OR Option B.
• Example: an internal candidate selects a question about their current division. A comparison can be used to determine whether the answer matches the req division field.

Define Value

When the field does not have a finite list of options to choose from (a text field) the Define value option is available. Text that is entered into this text box is evaluated based on the Operation defined.

For example, the assessment form banding field is of type text. It is selected with an operation of “Contains”. The Define value text entered here is “Pass”. When this condition runs, it looks up the band field to see whether the value has the text “Pass” in it.

Use a semi-colon to separate multiple contains statements within the same condition.

Multiple Form Instances

When you select a multiple per candidate, multiple per candidate per req, or multiple per req form (req sub form), you must specify which form version to use, since more than one might be on file for the candidate or req. In addition, you can add logic for the form to apply the condition scenario across reqs for candidate forms. The following options are available for each form type.

• Single per candidate
  • Not applicable
• Multiple per candidate.
  • Match most recent version.
  • Match any form version.
  • Match all form versions.
• Single per candidate per req.
  • Match form version for this req.
  • Match most recent version across reqs.
  • Match any form version across reqs.
  • Match all form versions across reqs.
• Multiple per candidate per req.
  • Match most recent version for this req.
  • Match any form version for this req.
  • Match all form versions for this req.
  • Match most recent version across reqs.
  • Match any form version across reqs.
  • Match all form versions across reqs.
• Multiple per req (Req subsidiary form)
  • Match most recent version.
  • Match any form version.
  • Match all form versions.

Email WatsonTalentTraining@us.ibm.com if you have a suggestion for improvement, or encounter an issue on this documentation. Include the product and page title in your email.