Setting Up and Using Rules for the Evaluation Management System

Entity Profiles

Because the Rules Engine always accesses data via the Entity Registry, the Entity Registry Entity Profile construct is used to restrict access to one or more entities, as well as the properties within a specific entity. An Entity Profile is an important attribute of a Rule Category, which is the Rules Engine feature that governs security.

Defining Rule Categories

Access the Rule Category - Definition page (select Set Up SACR, then select System Administration, then select Rules Engine Setup, then select Define Categories, then select Definition).

Field or Control	Definition
Entity Profile Name	System Profile EMS: This entity profile enables rules with this rule category to use the included system (delivered) entities as its ‘base’ entity. As noted earlier in this topic, this Entity Profile is intended as an example and likely will not meet the wide array of your evaluation business use cases. The image of the Entity Profile page (Set Up SACR, System Administration, Entity, Entity Profile) later in this section is just one illustration of the way that entities may be grouped into an Entity Profile to support the rules used under one Rule Category.
Allow Rules, Allow Functions, Allow Triggers	Theses check boxes indicate the Rules Engine privileges available to roles (or an individual user) authorized for this rule category. As delivered, this Evaluation Management System Category definition enables users to create Rules and Functions. As noted above, it is likely that you will create your own rule categories and set these check boxes according to your business needs.
Valid Rule Categories	Valid rule categories allow a user with explicit security access to a rule category (as defined on the Rule Category security page – see later in this documentation), in this case Evaluation Management System, to call rules from these categories without having specific access to those categories. For example user CSUSER-01 has access to Evaluation Management System. When creating a rule of this category, CSUSER-01 can call rules with any of the specified categories here, but cannot create a rule with one of those categories.

Defining Rule Category Rule Groups

Access the Rule Category - Rule Groups page (select Set Up SACR, then select System Administration, then select Rules Engine Setup, then select Define Categories, then select Rule Groups).

Field or Control	Definition
Rule Group Required	If this check box is selected, users with this rule category must always create a rule from a rule group listed in the Valid Rule Groups grid.

Defining Rule Category Security

Access the Rule Category - Security page (select Set Up SACR, then select System Administration, then select Rules Engine Setup, then select Define Categories, then select Security).

Security can be granted via role or by specific User ID.

Viewing Rule Category Information

Access the Rule Category - Cross Reference page (select Set Up SACR, then select System Administration, then select Rules Engine Setup, then select Define Categories, then select Cross Reference).

Use the Cross Reference page to view rules, rule groups, system variables and triggers that use this rule category.

EMS Rating Component Calculation Rule Group

This Rule Group definition has been designed specifically for use in the creation of rules that will calculate a rating value for a Rating Component. When a rule using this Rule Group is invoked, the system populates the input variables with data from the evaluation that is being processed. The rule is responsible for setting values for the output variables Result Rating Value and Result Calculated. The Result Rating Value represents the Rating Value that has been calculated for the Rating Component. The Result Calculated variable indicates if the Rating Component should be updated with the Result Rating Value calculated by the rule. Result Calculated must be set to True in order for the Rating Component to be updated with the Rating Value calculated by the rule. The following variables are included in the Rule Group definition:

A Rule Group also determines the data that can be accessed by a rule, according to the rule categories that are associated with it. A Rule Group must be associated with at least one Rule Category. The EMS Rating Component Calculation Rule Group has been associated with the delivered Rule Category Evaluation Management System and is therefore subject to the Entity Profile System Profile EMS.

It is intended that this delivered Rule Group is used by users to create rules that calculate rating value results for rating components that are part of an EMS calculated rating scheme.

EMS Rating Scheme Calculation Rule Group

This Rule Group definition has been designed specifically for use in the creation of rules that will calculate the overall rating value for a Rating Scheme based on the rating component rating values. When a rule using this rule group is invoked, the system populates the input variables with data from the evaluation that is being processed. The rule is responsible for setting values for the output variables Result Overall Rating and Result Calculated. The Result Overall Rating represents the Overall Rating that has been calculated for the Rating Scheme. The Result Calculated variable indicates if the rating scheme should be updated with the Result Overall Rating calculated by the rule. Result Calculated must be set to True in order for the Rating Scheme to be updated with the Overall Rating calculated by the rule. The following variables are included in the Rule Group definition:

It is intended that this delivered Rule Group is used by users to create rules that calculate the overall rating value for an EMS calculated rating scheme.

EMS Early Result Rule Group

This Rule Group definition has been designed specifically for use in evaluating the result at a specific order in the evaluation to determine whether the workflow should stop or continue. When a rule using this rule group is invoked, the system will populate the input variables with data from the evaluation that is being processed. The rule is responsible for setting values for the output variables Early Result, Route to Administrator, Recommendation, and Recommend Prize. The following variables are included in the Rule Group definition:

SCC_RULE_ID_20140303114951 Test Score Rule Example - Rating Component Calculation Rule Group

This rule returns a rating value for the rating component based on the highest score value in a comparison of ACT scores and SAT 1 scores. Calls a number of rules to get the scores from the test score records, evaluate those results against a rating scale to obtain the rating value to populate the rating component. Rules called from the Test Score Rule Example are:

└ SCC_RULE_ID_20140226160705 Get Highest Test Component Score
			└ SCC_RULE_ID_20140226155857 Get Test Component Scores

└ SCC_RULE_ID_20140304120320 Get ACT Rating Value

└ SCC_RULE_ID_20140304121526 Get SAT 1 Rating Value

SCC_RULE_ID_20140226160705 - Get Highest Test Component Score Example

SCC_RULE_ID_20140226155857 - Get Test Component Scores Example

SCC_RULE_ID_20140304120320 - Get ACT Rating Value Example

SCC_RULE_ID_20140304121526 - Get SAT 1 Rating Value Example

SCC RULE ID 20140519124427 Early Result Evaluation Workflow Rule Example - Rating Component Calculation Rule Group

This rule can return an Early Result variable value of True based on the outcomes of the segment of the evaluation using Overall Rating and Recommendation values as the determinant.

Rules Belonging to the Evaluation Management System Category

Evaluation Management Rules Engine Rule Hierarchy for rules in the Rating Component Calculation Rule Group

SCC_RULE_ID_20140306173039 Academic Qualification Example

└ SCC_RULE_ID_20140304170413 Get High School Rating Driver
			└ SCC_RULE_ID_20140304162158 Get High School Rating
						└ SCC_RULE_ID_20140304123947 Get GPA Rating
						└ SCC_RULE_ID_20140304155504 Get Percentile Rating

SCC_RULE_ID_20140306172622 Courses Completed Requirement Example

└ SCC_RULE_ID_20140306143945 Get Course Requirement Rating
			└ SCC_RULE_ID_20140306161125 Get Courses Completed Count
			└ SCC_RULE_ID_20140306141320 Get Course Count Rating

SCC_RULE_ID_20140303114951 Test Score Rule Example

└ SCC_RULE_ID_20140226160705 Get Highest Test Component Score
			└ SCC_RULE_ID_20140226155857 Get Test Component Scores
└ SCC_RULE_ID_20140304120320 Get ACT Rating Value
└ SCC_RULE_ID_20140304121526 Get SAT 1 Rating Value

Functional Scenario

A Rating Scheme is defined for use with Auto-Calculations. It includes three Rating Components, each of which is associated to a Rule. In this setup configuration, there is no rule identified for the Rating Scheme itself, so for the evaluations using this scheme, the Overall Rating value on the transaction pages will be calculated by the record PeopleCode.

That Rating Scheme is associated with an Evaluation Code. This code is set up to only use a Calculated Scheme; there are no other schemes included in this setup.

An Evaluation is manually created for EMPLID CCEM0019. At the time of the Evaluation creation, only the Test Score data exists in the system for this ID. At the save of the Manage Evaluation component, the rule linked to the TESTS component is invoked and a value is returned to that rating component:

In this example, ID CCEM0019 has the following Test Score data: ACT COMP score of 15, SAT 1 VERB of 600, MATH of 600. The Test Score example rule evaluates the scores, derives a rating of value of 15 for the ACT COMP score and a rating value of 25 for the total of the SAT 1 VERB and MATH scores. Since the SAT 1 total results in a higher rating value, that value is returned to the rating component.

Sometime later the data needed to calculate the other rating components is entered in the system. In this example that is Education data which includes GPA, Percentile Rank and External Subject details.

The SCC_GE_CALC process runs (you can schedule this to run as frequently as needed according to your business needs). The rules for the ACADEMIC and SCNDRYREQ components are invoked and rating values are returned by the batch process for those components. Because all required rating component values are present, the Overall Rating is also calculated:

The Academic rating value results from a calculation of the Education Data converted GPA and/or Percentile Rank. In our scenario, ID CCEM0019 has the following data:

• Converted GPA = 2.0

• Percentile Rank = 30%

The Academic Qualification rule determines that the Percentile Rank has a higher rating value and returns that value to the rating component.

The SCNDRYREQ rating value results from a count of External Subject completed courses. In our scenario, ID CCEM0019 has a total of 18 external subject completed courses. The SCNDRYREQ rule counts the number of courses completed and applies the rating scale to that number and returns a rating value to the rating component.

In this example above, because no rule was associated for the rating scheme, the Overall Rating is derived by PeopleCode and produces an average of the rating values.

Because this evaluation has not been determined to be final, if there are changes to the underlying data, the rules can be executed again to pick up those changes and do a recalculation. Let us say in this scenario higher ACT scores are received. The COMP score value is 36. The SCC_GE_CALC process is run and the newer score picked up and the TESTS rating component value is recalculated based on that score. The Overall Rating value is also recalculated:

After the Evaluation Status is set to Final, no additional re-calculations will occur.

Functional Scenario Variation

The Rating Scheme setup is modified to use a rule to calculate the Overall rating. Additionally, we have included a Math rating component that is not associated with a rule and is determined then to be populated manually.

When an evaluation is assigned to an ID, there is now a component which needs to be manually entered.

Functional Scenario

An evaluation is setup with an Early Result Rule defined in the Define Evaluation Code component:

Workflow is used in this evaluation, no calculated scheme is associated with the evaluation code. There are 3 schemes defined as part of the evaluation, as shown above.

Based on the Evaluator results at Order 1, an Early Result rule can determine whether those results require whether the evaluation needs to progress or whether the evaluation can be completed based on the results at Order 1. If those results indicate the workflow should be stopped and the evaluation completed, then the rule’s logic is used to grey down all other levels in the evaluation and populate the Evaluation Status and Recommendation fields on the Evaluation Overview tab for the evaluation. Workflow ceases and no worklist items or notifications (if enabled) will be created for any of the next levels. If the evaluation is to proceed, workflow continues and worklist items and notifications are created for the next level evaluator(s) at Order 2. Again, logic in the rule determines what should happen at this level of the evaluation just as it did for Order 1.

Here are the Evaluations and Calculations in the Rule:

Here is how the rule works with this scenario:

Our evaluator in the Individual Evaluator Scheme LAFIRSTREV is the first to go in the workflow processing order. In our sample rule, we’ve set the logic so we only want the evaluation to progress if that evaluator’s results are within certain parameters:

| - IF Evaluator.Evaluator Type = 5 And Evaluator.Scheme = LAFIRSTREV And Evaluator.Overall Rating >= 30
| | | - ASSIGN Early Result = True, Route To Administrator = False, Recommendation = ADMIT, Recommended Prize = MCL
| | - IF Evaluator.Evaluator Type = 5 And Evaluator.Scheme = LAFIRSTREV And Evaluator.Overall Rating <= 10
| | | - ASSIGN Early Result = True, Route To Administrator = False, Recommendation = DENY
| | | - EXIT FOR EACH

In this example the evaluator type of 5 equates to an individual evaluator ; see more at the end of this section about evaluator types. If the evaluator’s overall rating value is equal to or greater than 30 or equal to or less than 10, the evaluation flow will stop and the evaluation completed using the values specified in the rule for Recommendation to populate the Recommendation value on the Evaluation Overview page. For both conditions, Route to Administrator is false so no intervention by the Evaluation Administrator is expected. The Evaluation Status for the evaluation is set to final, all levels of the evaluation are grayed, no further workflow processing takes place. To continue with our scenario, let’s say the evaluator’s overall rating results were 25, so the workflow processing has continued and the evaluation advances to the Order 2 which is a committee scheme.

Let’s look at the next part of the rule:

| - IF Evaluator.Evaluator Type = 4 And Evaluator.Scheme = UGLAFACREV And Evaluator.Recommendation = ADMIT
| | | - ASSIGN Early Result = True, Route To Administrator = False, Recommendation = ADMIT
| | - IF Evaluator.Evaluator Type = 4 And Evaluator.Scheme = UGLAFACREV And Evaluator.Recommendation = DENY
| | | - ASSIGN Early Result = True, Route To Administrator = True, Recommendation = DENY
| | | - EXIT FOR EACH

In this section of the rule we are referencing the scheme at Order 2. Evaluator type equates to the Committee Administrator. The committee members have all submitted results and the committee administrator will finalize the results for the committee. As with the first example, we have set conditions that are going to direct the workflow, but this time using the Recommendation value that is given for the committee rather than the Overall Rating as in the first example. The logic is much the same, but note that if the Evaluator Recommendation = Deny and we return the Early Result of True, here we are setting the Route to Administrator to True. In that event that all levels of the evaluation are grayed, no further workflow processing takes place except for the Evaluation Administrator: a worklist item would be created and notifications sent. On the Evaluation Overview page, the Recommendation field would be populated with Deny but the field would not be grayed. The Evaluation Status field would not be updated with a final value. Again for purposes of our scenario, let’s say that the committee recommendation is HOLDNXREV (Hold for next review) so the workflow processing has continued and the evaluation advances to the Order 3 which is an individual evaluator scheme.

Here is the final part of the rule:

| | - IF Evaluator.Evaluator Type = 3 And Evaluator.Scheme = LADEANREV And Evaluator.Overall Rating >= 35 And Evaluator.Recommendation = ADMIT
| | | - ASSIGN Early Result = True, Route To Administrator = True, Recommendation = ADMIT, Recommended Prize = DEANLS
| | - IF Evaluator.Evaluator Type = 3 And Evaluator.Scheme = LADEANREV And Evaluator.Overall Rating <= 15 And ( Evaluator.Recommendation = DENY Or Evaluator.Recommendation = WAITLIST )
| | | - ASSIGN Early Result = True, Route To Administrator = True, Recommendation = DENY
| | | - EXIT FOR EACH

In this section of the rule we are referencing the scheme at Order 3, LADEANREV. Evaluator type equates to the Individual Evaluator Scheme Administrator. In this scheme there are multiple evaluators and it is the scheme result (think of this as a consensus of the various evaluators) as set by the administrator which will be considered by the rule. As with the previous examples, we have set conditions that are going to direct the workflow, but this time using the both the Overall Rating and Recommendation values that are given for the scheme. The logic is much the same, but with more complexity. In both conditions, we set the Route to Administrator to True.

Functional Scenario Variation

In the previous scenario, the evaluation code was set up for use with only Individual Evaluator and Committee Schemes. You can incorporate a calculated scheme into the evaluation code setup and have an Early Result Rule recognize the results of the calculated scheme to direct the workflow. Here is the evaluation code setup:

Workflow is used in the evaluation. Note that the Calculated Scheme Option is set to ‘Hold Workflow’. There are also Individual Evaluator and Committee Schemes in the evaluation code setup, as shown above.

Here are the Evaluations and Calculations in the Rule:

This is the same rule seen previously but cloned to account for the use of the calculated scheme in the scenario. The calculated scheme evaluates data in the system and returns an overall rating value. For more information, see Evaluation Management System/Rules Engine Integration: Rating Component Calculation and Rating Scheme Calculation Rule Groups.

In this scenario, we want the calculated scheme overall rating to determine what happens next in the evaluation flow, so we have set the Calculated Scheme Option to Hold Workflow. This means that the workflow will not trigger until all required rating components have rating values and an Overall Rating is calculated. When used with this Early Result Rule, the logic in the rule will direct whether the workflow should start or not. Here is the relevant part of the rule that evaluates for the calculated scheme:

IF evaluatorCount = 0 And Overall Rating >= 25
| - ASSIGN Early Result = True, Recommendation = ADMIT
IF evaluatorCount = 0 And Overall Rating <= 15
| - ASSIGN Early Result = True, Recommendation = DENY

In terms of activity in the evaluation, since we are holding workflow, the calculated scheme essentially is the first portion of the evaluation to take action. Once the Overall Rating is calculated this signifies a submit action. The early result rule is invoked. Since no evaluators are returned in the count, we know this is a calculated scheme and the logic as shown above is applied. In this scenario, the evaluation could be completed based on the calculated scheme results (if Overall Rating is > = 25 or <= 15). If the Overall Rating falls between those values, the evaluation will proceed and workflow will then start and advance the evaluation to the scheme at Order 1. From there the same scenario ensues as discussed in the previous section.

A Note on Evaluator Types

Evaluator Types is a construct used behind the scenes in Evaluation Management in the management of Self Service pages display to the user and in workflow processing . We have leveraged the EMS Evaluator Decision Info Data set as well. When building rules there is a prompt available to aid in selecting the correct value. For reference here is the list of Evaluator Types:

1. Evaluation Administrator.

2. Committee Scheme Administrator.

3. Individual Scheme Administrator.

4. Committee Administrator.

5. Individual Evaluator.

6. Committee Evaluator.