...
Table of Contents
This User Acceptance Testing (UAT) Guide is designed to help colleges understand the user interface and back-end data changes made to CCCApply Standard Application in the v.6.4.0 version release (Pilot environment release 2.19.19, and Production release 3.16.19) and provide acceptance criteria to support college implementation of those changes.
| Note |
|---|
Release notes for the CCCApply Release 6.4.0 include additional user interface enhancements and implementation guidelines that support this UAT plan. Background information about the CCCApply Redesign Project and other special implementations released in FY18-19 can be found in the CCCApply Redesign Project Dashboard. Data Dictionaries and User Guides have been updated for this release. |
UAT Goals & Objectives
...
Ensure college admissions and support services staff have all release notes, change specifications, and project implementation materials needed to update existing business operations and support services processes, data reporting requirements, and outreach activities based on the new user interface changes implemented as part of the CCCApply Redesign - Release 3 project enhancements.
...
- College admission and support staff have reviewed the CCCApply 6.4.0 release notes
- including the detailed Release 3 User Interface changes deployed as part of the CCCApply Redesign Project
- Colleges have bookmarked the CCCApply Redesign Project Dashboard and reviewed the Release 3 specific user interface changes
...
Ensure college IT staff have all required release notes, change request specs, and data spec documentation needed to update data downloads and Glue export processes for the updated Race & Ethnicity fields bug fixes resolved in the 6.4.0 release.
...
- Colleges have downloaded and reviewed the CCCApply 6.4.0 release notes including the section detailing the Race & Ethnicity Bug Fix specifications
- Colleges IT staff have downloaded the CCCApply Standard Application Data Dictionary v.2019.1, and reviewed the 6.4.0 updates documented in the Change Log
- Colleges IT staff have bookmarked the link to the online CCCApply Download Client User Guide v.2019.1 and reviewed 6.4.0 updates documented in the Change Log
- Colleges have updated their current Download Client with the 6.4.0 transfer-client.jar file.
...
- College admission staff have created a new email Rule and Message in the CCCApply Administrator based on the new Race & Ethnicity Full data field <race_ethnic_full> (v.6.3.0)
- College admission staff have run the Standard Application Full Application Report that includes the Spam Filter data fields (v.6.2.0), and the Race & Ethnicity Full field (v.6.3.0):
- Fraud Score <fraud_score>
- Race & Ethnicity Full <race_ethnic_full>
| Info |
|---|
| It is recommended that colleges update their CCCApply Download Client Jar file to the latest version for every pilot and production environment releases. Find the latest version here: CCCApply User Guides > Download Client Jar File. |
...
User acceptance testing with a limited number of pilot colleges will commence on or after February 20, 2019 (post 6.4.0 pilot release).
The following colleges have agreed to participate in Release 6.4.0 UAT activities:
- Santa Rosa College
- Bakersfield College
- Cerritos College
| Note |
|---|
All Changes Are Backwards Compatible - No Actions Required: All the front-end changes (user interface enhancements) and all back-end changes (bug fix for Race & Ethnicity Full field) being deployed in this release are designed to be backwards compatible with previous CCCApply release version code. |
UAT Implementation Steps
Follow the steps below to meet the expected success criteria for the UAT objectives.
...
- NOTE: The 'transfer-client.jar" file is the same as the Download Client Jar file.
- Refer to the Download Client User Guide for instructions on replacing and running the Jar file for each application in each environment (Pilot and Production).
...
| Info |
|---|
| Repeat this process for your Production application after the production release on December 7, 2018. |
Testing in the Pilot Environment
User acceptance testing and implementation support for colleges in the Pilot Environment can begin on November 20 upon the completion of the Pilot deployment activities.
/wiki/spaces/PD/pages/131465676
Data Field Specifications & Mapping
- General Requirements
- Release Information for Colleges
UAT FEEDBACK & RESOLUTION
- Feedback should be categorized as bugs and enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as release blockers.
- Reporting: User feedback should be noted in the result section. The following criteria should be followed and documented:
- Any identified bugs with severity and priority
- Enhancement requests with priority identified
Data Field Information
For detailed data specifications, please refer to the corresponding application Data Dictionary, as well as the breakdown of change specs in: 2018-18R: New Race & Ethnicity Implementation 2018.
...
Race Group
...
race_group
...
CSV string
...
Race Ethnicity
...
race_ethnic
...
bpchar, 22
...
Race Ethnicity
...
race_ethnicity
...
bpchar, 22
...
Race Ethnicity Full
...
race_ethnic_full
...
CSV string, no spaces
...
Race Ethnicity Full
...
raceEthnicFull
...
CSV string
...
| Note |
|---|
Race Ethnicity Full Data in Glue for Apply The new Race & Ethnicity values included in this release will be passed directly to colleges using the Glue for Apply feature. However, the new full Race & Ethnicity field is not yet available through Glue for Apply at this time. An upcoming release of the SuperGlue College Adaptor will include this new data. |
Hispanic
Data Field: hispanic
Data Element: <hispanic>
Notes: No changes, this field is a boolean true/false field that continues to work as in previous version
Example Format: boolean (true/false/null)
Race Group
Data Element: <race_group>
Notes: No changes, this field was intentionally left unchanged
Example Format: Apply: "04, 05, 08, 09, 14, 15, 17, 19, 20, 21", International: "04,05,08,09,14,15,17,19,20,21" (note lack of spaces for Intl)
...
Table of Contents
...
This User Acceptance Testing (UAT) Guide is designed to help colleges understand the user interface and back-end data changes made to CCCApply Standard Application in the v.6.4.0 version release (Pilot environment release 2.19.19, and Production release 3.16.19) and provide acceptance criteria to support college implementation of those changes.
| Note |
|---|
Release notes for the CCCApply Release 6.4.0 include additional user interface enhancements and implementation guidelines that support this UAT plan. Background information about the CCCApply Redesign Project and other special implementations released in FY18-19 can be found in the CCCApply Redesign Project Dashboard. Data Dictionaries and User Guides have been updated for this release. |
...
UAT Goals & Objectives
The objectives and success criteria for college user testing across the 6.4.0 release are detailed below.
| # | UAT Objectives | Success Criteria | Status |
|---|---|---|---|
| 1 | Ensure college admissions and support services staff have all release notes, change specifications, and project implementation materials needed to update existing business operations and support services processes, data reporting requirements, and outreach activities based on the new user interface changes implemented as part of the CCCApply Redesign - Release 3 project enhancements. |
| |
| 2 | Ensure college IT staff have all required release notes, change request specs, and data spec documentation needed to update data downloads and Glue export processes for the updated Race & Ethnicity fields bug fixes resolved in the 6.4.0 release. |
| |
| 3 | Ensure college staff and administrators are able to implement new business rules and messages and view and run reports in the Admin configuration and reporting tools using new data fields added to the CCCApply Standard Application in 6.4.0 and prior releases. |
|
| Info |
|---|
| It is recommended that colleges update their CCCApply Download Client Jar file to the latest version for every pilot and production environment releases. Find the latest version here: CCCApply User Guides > Download Client Jar File. |
UAT Pilot: Participating Colleges
User acceptance testing with a limited number of pilot colleges will commence on or after February 20, 2019 (post 6.4.0 pilot release).
The following colleges have agreed to participate in Release 6.4.0 UAT activities:
- Santa Rosa College
- Bakersfield College
- Cerritos College
| Note |
|---|
All Changes Are Backwards Compatible - No Actions Required: All the front-end changes (user interface enhancements) and all back-end changes (bug fix for Race & Ethnicity Full field) being deployed in this release are designed to be backwards compatible with previous CCCApply release version code. |
...
UAT Implementation Steps
Follow the steps below to meet the expected success criteria for the UAT objectives.
- Log in to your college MIScode branded version of the /wiki/spaces/PD/pages/131465676 and start a new CCCApply Standard application from your My Applications page.
- Complete the new application from the Enrollment page to the Needs & Interests page. Continue on to the Demographic Information page.
- Note: This includes the Account Information/Mailing, Education, Citizenship/Military, Residency pages.
- Complete the Gender/Transgender section;
- Complete the Parent/Guardian Education Level;
- Review the changes to the Education page
- Hispanic/Latino question: Select the Yes radio button to expand the Hispanic/Latino sub-categories. Select one or more checkbox options.
- Race Group categories: Select one or more of the race group checkboxes to expand the corresponding ethnicity sub-categories.
- Click Continue to go to the last page;
- Complete the remaining required portions of the application and submit the application
- This includes the Submission page sections: Review App, Consent to Release Information, and Submission
- After submission, note the application's Confirmation number (App_id) and your CCCID.
- Reference the CCCApply Standard Application Data Dictionary (v.2018.2) Pilot Version
- Jump to the Race & Ethnicity section from the Table of Contents (Race Group)
- Review the data element specifications for all four Race & Ethnicity section fields:
- Hispanic/Latino = <hispanic>
- Race Group = <race_group>
- Race Ethnicity = <race_ethnic>
- Race Ethnicity = <race_ethnicity> (Note: This field has a different name in the International application)
- NEW Race & Ethnicity Full = <race_ethnic_full>
- Add the new Race & Ethnicity FULL field to your Pilot environment Format XML (CCCApply Standard & International files must be updated separately)
- Follow the data specs for <race_ethnic_full> in the updated DED (CCCApply Standard Data Dictionary (v.6.3.0)
- For CCCApply & International: The new data field has the same name for both application: <race_ethnic_full>
- For help updating your Format Definition file, see the CCCApply Download Client User Guide
- Update your existing Download Client Jar File with new version (v.6.3.0)
- Find and replace the "transfer-client.jar" file in your CCCApply Download Client with the latest version for this release (v.6.3.0).
- NOTE: The 'transfer-client.jar" file is the same as the Download Client Jar file.
- Refer to the Download Client User Guide for instructions on replacing and running the Jar file for each application in each environment (Pilot and Production).
- Run a test download Job in the Pilot environment.
- Find and replace the "transfer-client.jar" file in your CCCApply Download Client with the latest version for this release (v.6.3.0).
- Repeat the process for the Production environment.
| Info |
|---|
| Repeat this process for your Production application after the production release on December 7, 2018. |
...
Testing in the Pilot Environment
User acceptance testing and implementation support for colleges in the Pilot Environment can begin on November 20 upon the completion of the Pilot deployment activities.
/wiki/spaces/PD/pages/131465676
...
Data Field Specifications & Mapping
- General Requirements
- Release Information for Colleges
...
UAT: Feedback & Support Process
- Feedback should be categorized as bugs and enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as release blockers.
- Reporting: User feedback should be noted in the result section. The following criteria should be followed and documented:
- Any identified bugs with severity and priority
- Enhancement requests with priority identified
...
New & Changed Data Fields
The table below provides an overview of the new or changed data fields in CCCApply Standard Application, and "Glue for Apply".
See these data specification changes in the CCCApply Standard Application Data Dictionary V.2019.1 in the Data Dictionaries space.
Description | Data Element | Type | Value / Response Options | Format / Length | Allows Null | Required | Notes |
|---|---|---|---|---|---|---|---|
| Declared Residency Outside California for Taxes | <ca_outside_tax> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | IF the question is displayed:
IF question is hidden:
NOTE: IF hidden, such as in the Non-Credit application, then default to NULL For a standard application, it will default to False, unless the user checks the checkbox. |
| Declared Residency at a College Outside California | <ca_outside_college> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | Same as Above. |
| Registered to Vote Outside California | <ca_outside_voted> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | Same as Above. |
| Lawsuit Filed Outside California | <ca_outside_lawsuit> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | Same as Above. |
| Public School Employee | <ca_school_employee> | Default value = Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | Required response If appears onscreen | |
| State College Employee | <ca_college_employee> | Default value = Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | Required response If appears onscreen | |
| Seasonal Agricultural Worker | <ca_seasonal_ag> | Default value = Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | Required response If appears onscreen |
Changes to the User Interface
The following changes to the Standard Application user interface are implemented to the v.6.4.0 pilot release for testing.
Page / Section | Description | Current UI State | New Revised UI State | Notes to Colleges |
|---|---|---|---|---|
| Residency | Revise the layout of the Residency page Reorder the questions and sections on the Residency Page for all users
| Currently the layout of the Residency page places the Special Residency section in the middle between the California Residence and the Out-of-State Activities sections. This layout prohibits the ability to implement skip logic to streamline the experience for CA residents. | The new order of sections/questions on the Residency page is:
| This is a layout change and there are no changes required by the college
|
| Residency | Hide three questions in the Special Residency section by default for all users
Add logic to Show the three questions as a group if user selects one or more Out-of-State activities and the most recent year is within 2 years of the RDD. | Currently, all Special Residency questions display to all users in Yes/No radio button format and a response to each question is required. | The Special Residency section now only displays the Homeless Youth Status and Foster Youth Status questions to all users with all existing validation and logic in place. If user selects (checks) one or more of the "Out-of-State Activities" with the most recent year of activity is within 2 years of the RDD, then the three hidden special residency questions will display as a group and responses will be required. | Note: The Homeless Youth and the Foster Youth questions ALWAYS display and each requires a response by all users. College needs to be aware that this field will now allow a null Note: In 2018, only 1% of all applicants responded Yes to this question. |
| Residency | Revise the "Out of State Activities" Section by combining four separate, required questions into one optional question with skip logic to shorten the Special Residency section Combine the four current "Out-of-State Activity" questions into ONE new question, and change the format of the response options from required, Yes/No radio buttons and set the default to "No". | Currently, the "Out-of-State Activities" section consists of four separate, required, Yes/No questions with conditional "Year" fields that appear if the user answers Yes to any of the specific questions. | The new "Out-of-State Activities" section now contains one question (onscreen text) with four optional checkbox response options (the original four OOS questions, revised). "As of <RDD minus 2 years>, have you engaged in any of the following activities? Check each activity that applies." [checkbox] I paid taxes outside of California [checkbox] I registered to vote outside of California [checkbox] I declared residency at a college or university outside of California [checkbox] I filed for a lawsuit or divorce outside of California All existing data fields would persist (no change to data output, downloads, etc.) | There is no change to the text, conditions, logic or data fields for the four, corresponding Out-of-State Activity Year fields section/questions. The four Out-of-State Activities questions/fields are now optional (responses are no longer required by default) and the data fields will now accept Null or blank. |
| Education | Hide the College Education Level and Add logic to the College Enrollment Status question to only show college sections if the user is NOT a first-time in college after leaving high school | Currently, the College Education Level section and the Colleges/Universities Attended sections are required questions/sections that appear to all users on the Education page, even for students who have never attended college in the past. | The College Education Status and Colleges/Universities Attended sections/questions will not display on the Education page unless the user indicates they have attended one or more colleges in the past. If the user selects "first-time in college after leaving high school" option in the College Enrollment Status question, do not show college questions and default field value to Null. |
...
Changes to "Glue for Apply" and the SuperGlue College Adapter
Description | Data Field | Format / Length | Required | Notes |
|---|---|---|---|---|
| Race Ethnicity Full | <raceEthnicFull> | CSV delimited Maximum Expected Width: 805 characters (201 * 3 character long values + 200 commas + 2 surrounding quote marks for CSV delimiting in the output format) | No |
| Note |
|---|
Bug Fix Solution Race Ethnicity |
...
Data Element: <race_ethnic> (Apply) / <race_ethnicity> (International)
Notes: No changes, this field was intentionally left unchanged
Example Format: YNYNNNNYNNNNNNNNNYNNN
...
Full Data in Glue for Apply The new Race & Ethnicity values included in this release will be passed directly to colleges using the Glue for Apply feature. However, the new full Race & Ethnicity field is not yet available through Glue for Apply at this time. An upcoming release of the SuperGlue College Adaptor will include this new data. |
Race Ethnicity Full
Data Element: <race_ethnic_full>
...
College Adaptor (SuperGlue) Data Element
For SuperGlue colleges, the new race_ethnic_full data element is called "raceEthnicFull"
...
UPDATING YOUR DOWNLOAD FILES
...
Data Dictionaries: CCCApply Standard Application Data Dictionary v.2018.2
Copy of UAT: Race & Ethnicity Implementation 2018
Update the Production Download Client Jar File
To update your Download Client Transfer file for the Production environment, the process is the same as the Pilot environment update. The same jar file is used for both environment.
In your installed Production Download Client directory, replace the following files:
...