HR Criteria VS User Criteria

G24
Kilo Sage

What is "HR Criteria" and what exactly is the difference between "HR Criteria" and "User Criteria"?

1 ACCEPTED SOLUTION

G24
Kilo Sage

HR Criteria

The "HR Criteria" concept is a just versatile way of specifying a collection of Users which satisfy one or more Conditions.  HR Criteria records define the "audience" for HR Content or Services.

 

Once an HR Criteria record is defined, it may then be used in various places in ServiceNow such that only those Users satisfying the Criteria will be given access to a particular function, or will show up for selection in a particular form field.

 

You define an HR Criteria record by specifying one or more HR Condition records.  The HR Condition records are where the rubber meets the road.

 

To understand "HR Criteria", start with a couple example Conditions...

Example 1: "All Office-Based Employees" - That is, users who appear in the "User" field of the "HR Profile" table provided the "Location Type" of the HR Profile is "Office Based".

Example 2: "Users currently handling one or more active incidents" - That is, users who appear in the "Assigned To" field of the "Incident" table provided the "Active" flag of the Incident is "True".

 

Note, after you setup each HR Condition record, the form will show you exactly how many Users are included by the condition and will even give you a link to the table in question with the condition applied, so you can see the results.

 

Recap

In an HR Condition record, you specify which table points to the set of users you care about, and which field in that table is the actual Reference Field to the User (sys_user) table.  You can specify any table which has a reference field to the User table, such as "HR Criteria" or "Incident".

   - You specify the table in the "Table" field.

   - You specify the Reference Field in the "User column" field.

 

Important Notes

1)  You will almost NEVER choose the sys_user table in the Table field, unless you care about Managers of Users, since the User table only has one Reference Field back to itself, and that field is "Manager".  If you wanted to pull users from the sys_user table directly, you would use the "User Criteria" concept, not the "HR Criteria" concept.  User Criteria is a little easier to understand, but is also less versatile.

2)  If there are multiple Conditions specified by a single HR Criteria record, the user must satisfy ALL conditions in order to be included!  However, if a record such as an HR Service record specifies multiple "HR Criteria" records, any user who satisfies At Least One of the HR Criteria records will be included.

 

HR Criteria Tables

HR Criteria (sn_hr_core_criteria)

     HR Conditions for Criteria (sn_hr_core_m2m_condition_criteria)

          HR Condition (sn_hr_core_condition)

 

Use Cases for HR Criteria

- To filter HR Services based on the Subject Person specified during case creation or transfer.

- To determine which Widgets a user can see on the Employee Service Center.

- To filter "Lifecycle Events Activities" in the "Human Resources Scoped App: Lifecycle Events" plugin.  This helps to personalize the workflow.

- To specify a document template to use when an HR Case is created form a particular HR Service.

- To specify a set of users when creating Bulk HR Cases.

 

Final Note: HR Criteria is scoped to the HRSD Application and intended for HR Use Cases.

 

Now let's see some examples of HR Criteria Screenshots!

 

HR Criteria Record with 2 Conditions in the Related List:

1_HR_Criteria_Record.jpg

 

Condition 1:

2_HR_Condition_Record_A.jpg

 

Condition 2:

3_HR_Condition_Record_B.jpg

 

HR Service which makes use of the HR Criteria record:

4_HR_ServiceX.jpg

 

Creation of HR case from the HR Service.  The HR Service will only appear in the list IF the Subject Person meets the HR Criteria demanded by the HR Service.

5_Use.jpg

 

Finally, for CONTRAST, let's see what a User Criteria record looks like.  Note that there is no Related List of condition records.  All tables and fields are specified on a single form, which is "easier" but less versatile:

6_UserCriteria.jpg

 

Please mark as "helpful" if this discussion helped you.  Thanks.

View solution in original post

1 REPLY 1

G24
Kilo Sage

HR Criteria

The "HR Criteria" concept is a just versatile way of specifying a collection of Users which satisfy one or more Conditions.  HR Criteria records define the "audience" for HR Content or Services.

 

Once an HR Criteria record is defined, it may then be used in various places in ServiceNow such that only those Users satisfying the Criteria will be given access to a particular function, or will show up for selection in a particular form field.

 

You define an HR Criteria record by specifying one or more HR Condition records.  The HR Condition records are where the rubber meets the road.

 

To understand "HR Criteria", start with a couple example Conditions...

Example 1: "All Office-Based Employees" - That is, users who appear in the "User" field of the "HR Profile" table provided the "Location Type" of the HR Profile is "Office Based".

Example 2: "Users currently handling one or more active incidents" - That is, users who appear in the "Assigned To" field of the "Incident" table provided the "Active" flag of the Incident is "True".

 

Note, after you setup each HR Condition record, the form will show you exactly how many Users are included by the condition and will even give you a link to the table in question with the condition applied, so you can see the results.

 

Recap

In an HR Condition record, you specify which table points to the set of users you care about, and which field in that table is the actual Reference Field to the User (sys_user) table.  You can specify any table which has a reference field to the User table, such as "HR Criteria" or "Incident".

   - You specify the table in the "Table" field.

   - You specify the Reference Field in the "User column" field.

 

Important Notes

1)  You will almost NEVER choose the sys_user table in the Table field, unless you care about Managers of Users, since the User table only has one Reference Field back to itself, and that field is "Manager".  If you wanted to pull users from the sys_user table directly, you would use the "User Criteria" concept, not the "HR Criteria" concept.  User Criteria is a little easier to understand, but is also less versatile.

2)  If there are multiple Conditions specified by a single HR Criteria record, the user must satisfy ALL conditions in order to be included!  However, if a record such as an HR Service record specifies multiple "HR Criteria" records, any user who satisfies At Least One of the HR Criteria records will be included.

 

HR Criteria Tables

HR Criteria (sn_hr_core_criteria)

     HR Conditions for Criteria (sn_hr_core_m2m_condition_criteria)

          HR Condition (sn_hr_core_condition)

 

Use Cases for HR Criteria

- To filter HR Services based on the Subject Person specified during case creation or transfer.

- To determine which Widgets a user can see on the Employee Service Center.

- To filter "Lifecycle Events Activities" in the "Human Resources Scoped App: Lifecycle Events" plugin.  This helps to personalize the workflow.

- To specify a document template to use when an HR Case is created form a particular HR Service.

- To specify a set of users when creating Bulk HR Cases.

 

Final Note: HR Criteria is scoped to the HRSD Application and intended for HR Use Cases.

 

Now let's see some examples of HR Criteria Screenshots!

 

HR Criteria Record with 2 Conditions in the Related List:

1_HR_Criteria_Record.jpg

 

Condition 1:

2_HR_Condition_Record_A.jpg

 

Condition 2:

3_HR_Condition_Record_B.jpg

 

HR Service which makes use of the HR Criteria record:

4_HR_ServiceX.jpg

 

Creation of HR case from the HR Service.  The HR Service will only appear in the list IF the Subject Person meets the HR Criteria demanded by the HR Service.

5_Use.jpg

 

Finally, for CONTRAST, let's see what a User Criteria record looks like.  Note that there is no Related List of condition records.  All tables and fields are specified on a single form, which is "easier" but less versatile:

6_UserCriteria.jpg

 

Please mark as "helpful" if this discussion helped you.  Thanks.