Adding an Evaluation

This section covers following topics:

• Adding Filters
• Adding Evaluation Scoring

To add an Evaluation:

1. Navigate to the Evaluation details page.
2. Click Add on the Evaluations tool bar. The Add Evaluation page is displayed.

   Figure 10-2 Adding an Evaluation

   
   

   

   
   
3. Enter the following details:
   • Name: Enter the name of the evaluation.
   • Processing Segment: Select the processing segment from the drop-down list.
   • Activity: Select the activity from the drop-down list.
   • Join Type: Select the type of Join from the drop-down list:
     • Inner : This option performs the intersection of records between two tables and gives a FAIL for no intersection.

       Note:

       This is the default option.
     • Left: This option lists the records between two tables which are based on a particular condition and gives a NULL for no transaction.
4. Click Save. A confirmation message is displayed.

Joins

Joins are of two types:

• Inner Join: This type of Join performs the join of two tables by finding the intersection columns and displays only those records. So, this type of Join only gives a FAIL for no intersection. It does not provide more information on whether the information is missing in a table, or if the condition is not met. Supporting inner joins restricted applications not to distinguish between records that fail to meet business logic (filter conditions) or lack of data.
• Left Join: This type of Join performs the exclusive join between two tables by listing the records based on a certain condition. So, in this case, we will have a certain number of records displayed even if the intersection is zero. This will give a result of NULL indicating zero intersection and shows whether data was missing or the condition was not met.

Use Case for Joins

Select  
 case parameter. pscore is null then 20 else parameter.pscore end score // calculating score
From cust 
  join Parameter
On cust.acct_type = parameter.acct_type
Where cust.balance > 5000

This evaluation scores a customer whose balance is greater than 5000. Score is derived from Parameter table depending on the account type.

• Inner join: Inner join approach scores all transaction into default bucket. Irrespective of whether data is missing or filter conditions failed.

  Inner join cannot distinguish if customer balance is less than 5k or if customer's account type is invalid and balance is greater than 5000.

  Both transactions will be scored using default bucket(ZERO).

• Left Join: Using left joins, IPE distinguishes between transactions with missing data and failing to meet the business logic.

  Select  
   case parameter. pscore is null then 20 else parameter.pscore end score // calculating score
  From cust 
   LEFT join Parameter
  On cust.acct_type = parameter.acct_type
  Where cust.balance > 5000

  If customer balance is less than 5000 and valid acct_type then score is ZERO default bucket.

  If customer balance is greater than 5000 and invalid acct_type then score will 20.