2016-15: Add Missing Step to Area B Residency Logic for Classification of B0 Non-Residents

Problem / Issue

Colleges are reporting multiple problems wth the Area B logic regarding students who report out-of-state activities but are still being classifed as "Residents" in the Area B logic and the overall Residency Status calculation. Colleges are requesting that the logic be revised in Step 1 to classify these applicants as B2 (and set a flag) to ensure they are reaching Step 4 with the correct classification, which is the poiint in the logic that separates the residents from the "possible residents" and the "non-residents". . 

Proposed Solution

The solution is to change Step 1 from: "Set Class B0 - Non-resident > Go to Step 4"  to  "Set Class B2 > Set flag (30 > Go to Step 2" which is the point where California residency for 2years is identified. If the answer is "No" at step 2, the "B0" classification is then set, and the logic advances to step 3 and 4. At step 4, unless the student with the "B0" classification is determined to be a current or former Foster Youth, they keep the "B0" classification and skip to the end for final B0 classification. If the user is a Foster Youth, the class is set back to "B2", a flag is set, and they advance through the rest of the logic with that classification.  

Extensive testing has been documented in a table of use cases and edge cases to ensure that the changes do not "break" any other steps in the logic.  

Requirements Summary

Proposed Technical Specifications

NOTE: All of the proposed changes to the Area B logic pertain to the "If NO" column only. There are no changes to the "If Yes" columns, other than the addition of the new Step 12 (which is a completely new step with all new columns).

1. REVISE Step 1 of the Area B of the residency algorithm to change the action if the user indicates Yes to any of the four "out-of-state" indicator questions (as indicated in the Data Elements & Logic Statement in Step 1). 
   
   

   1. Change the logic in the "IF NO" column of Step 1 of the Area B logic from::
      
      Step 1:

      1. Change the logic in the "IF NO" column of Step 1 of the Area B logic from:
         
         "Set B0 - go to step 2"
         to
         "Set Class B2 and set flag 30 and go to step 2" , 
         IF
         the applicant reports one or more of the four "out-of-state" indicator(s) in the application.
         
         NOTE: The out-of-state indicators include: paid taxes, or registered to vote, or attended college, or filed a lawsuit, outside of California within the last 2 years.
   2. Ensure the logic also advances the "If NO" column in Step 1 to Step 2  (which is critical to determine if the user has lived in CA for 2 yrs or not).
      
      

2. Create and add a new data downloadable field for new Integrity Flag 30 to the residency table in the submitted application database: integrity_fg_30. 
   
   a. Add "integrity_fg_30" to the download client for the standard application only.
   b. Add "integrity_fg_30" to the submitted application "Rules" area in the Administrator (a separate JIRA has been created for this task.)
   c. Add "integrity_fg_30" to the Education section of the Submitted Application data domain in the Report Center. 

   NOTE:  Integrity flags are two‐digit numeric codes, as defined in Table E. They are stored and downloaded in data element ‘residency: res_int_flags’, a string that can contain up to 26 flags. Refer to the CCCApply Standard Application Data Dictionary v.2016.1 for more information about this data element.

   
   Add New Integrity Flag 30

   30

   Applicant has reported one or more "out-of-state" indicators: 1) filed taxes; 2) registered to vote; 3) attended college; or, 4) filed a lawsuit - outside of California within the last 2 years.

   ca_outside_tax = 1 AND/OR ca_outside_voted = 1 AND/OR ca_outside_college = 1 AND/OR ca_outside_lawsuit = 1

   
   

   
   

3. Revise the "IF NO" column in Step 4 to include "go to step 12". The logic in the "If NO" column would read: "Set Class B0 and go to step 12"
   
   (B0 = Non-Resident for Area B).
   
   NOTE: Step 4 is the point in the logic that determines if a user is a Non-Resident. Prior to step 4, the user would either have a Class B2 set, or no class set at all.  Step 4 is the point in the logic that asks if the user "is a current or former foster youth and residing in California and under age 20."
    
   "IF Yes then "Set Class B2 and set flag 70 (foster youth) and go to step 5";
   OR
   "If NO, then "Set Class B0 and go to step 12"  
   
   NOTE: There is no change to the "If yes" column in Step 4 (set Class B2, set flag 70, and go to step 5).
   
    

4. ADD NEW STEP 12 to the Area B logic - which would serve as an additional final "Non-Resident, Class B0" classification point, just in case an edge case slips past step 4 (and  the user isn't reclassified with B2 along the way). By adding this new step between step 11 and 12, we have a safety net in place for Non-Residents.
   
   The new step 12 would read:
   
   "Has Class B0 been set?"  
   If Yes, then "Set Class B0 and END the logic calculation"
   OR
   If No, then, "Go to step 13"
   
   New Step 12 and 13 looks like this: 

Table of Logic Changes 

Use Case Test Matrix

BUG Case Matrix

The table below demonstrates the problem we are having with the Area B logic with this specific Use Case (California Resident for 2 Yrs  who has OOS Indicator)

Identifying Issues with Current Logic

Area B Logic Change Specifications

Table B. Outline of Area B (Stay and Intent) Criteria in Residency Algorithm

Notes

This issue was reviewed by the CCCApply Residency Review Sub-Committee on 7-14-16. A committee of residency experts, including Michael Quaioit from the Chancellor's Office, reviewed several examples and proposed adding a new step to the logic (between 11 and 12) to validate non-resident status before the final calculation. 

7-19-16: However, after reviewing the proposed logic with the developer, additional requirements were identified (revising the If No column in Step 1 and adding a flag).  The proposed requirements and change specs above reflect the final proposed logic changes. 

For testing, use the Current Area B Logic Table, which includes a new "If No" column.

Supporting Documentation