Inclusion Rule
Inclusion rules define the roles that will be included in the approval path.
There are two types of inclusion rules:
-
Unconditional
-
Conditional
Unconditional inclusion rules always includes the role in the approval path, regardless of the context of the requisition or the offer (other than the specified requisition type for which the path is defined).
Example: Always include the job posting approver.
When creating an unconditional rule, the only thing that needs to be specified is the roles to be included. The operators for including roles are outlined below.
| Option | Description |
|---|---|
| From the manager role up to the number of specified
direct reports. The system administrator then defines the # of direct reports. |
When this type of rule is used, the system will ignore all roles in the system and pay attention only to the employee "reports to" structure. The system will look at who is the Manager of the requisition/offer and will go up the number of specified direct reports from that manager. |
| Only the selected role. | Allows the selection of a specific hierarchical or functional role in the approval path. Note: when a hierarchical role is used, the system will look at who is the Manager of the requisition/offer and will go through the "reports to" structure until it finds an employee with the specified hierarchical role. It will then include the first matching employee in that hierarchical role. For example, if there were two directors in the "reports to" structure and the director hierarchical role was selected, only the first director in the hierarchy would be added to the flow ordered by how they report to one another. |
| All roles included up to the specified number of
levels. The system administrator then specifies the role and the # of upper levels. |
Allows the selection of a series of employees using the hierarchical role structure in the approval path. The system will use the Hiring Manager of the requisition and will go through the reports to structure until it finds the first employee with the specified role. It will then include this person and every employee in the reporting structure up to and including the first employee it finds at # hierarchical roles above the specified role in the path. |
| All roles between the following roles. The system administrator defines the two roles. |
Allows the selection of a series of employees using the hierarchical role structure in the approval path. The system will use the Hiring Manager of the requisition and will go through the reports to structure until it finds the first employee with the lower level role. It will then include this person and every employee up to and including the first employee it finds at the upper level hierarchical role. |
Conditional inclusion rules include a role when certain conditions are met.
Example: Include the CFO on all requisitions where the base salary is > $100,000 and the Location is United States.
For conditional inclusion rules, the rule operator process is the same as it is with unconditional rules, but there is a another step involved where the user creates the conditions under which the specified roles will be included in the path. When creating a condition, the first step is to define the fields to be used in the condition. For each field there are available operators to define how the field condition will work. Conditions can be applied on requisition fields as well as on offer fields, depending on the approval type. For a requisition approval path, conditions can be applied only on requisition fields. For an offer approval path, conditions can be applied only on offer fields. All Offer and Requisition fields, either user-defined or system defined, can be used to create conditions. Conditional rules used within approval paths for offers may also contain a unique condition that compares the offer salary to the maximum salary on the requisition. Note that this comparison is entirely numeric, and does not take variables such as pay basis or currency into account when including an approver.
For example, for numeric fields, operator options include: is equal to, is less than, is greater than, is not equal to, is less than or equal to, is great than or equal to. Once the operator is set, the value is determined for the condition. An example of a condition might be: Salary is greater than or equal to 100,000K US.
Once a condition is created it can be added to the formula builder. The system administrator can add as many conditions as necessary to define the necessary rules. Once the conditions have been added, they can be strung together using boolean operator logic: And, Or, (,) and Not are supported functions. The conditions and formula functions can be moved around in the formula area by highlighting the item (represented in orange) using the < and > keys.