This User Acceptance Testing (UAT) Guide is designed to help colleges understand the user interface and back-end 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.
The CCCApply Release 6.4.0 UAT will consist of 3 district colleges from the CCCApply Redesign Workgroup.
Colleges from the CCCApply Redesign Workgroup will participate in Release 6.4.0 UAT activities:
The minimum number of pilot participants to provide validation is 3. Pilot project activities are scheduled between February 19 - March 16, 2019.
Participation activities and requirements include:
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. |
The user acceptance testing (UAT) plan, process and objectives for the CCCApply Release 6.4.0 Pilot are listed below.
The objectives and success criteria for college user testing across the 6.4.0 release are detailed below.
# | UAT Objectives | Success Criteria | College UAT Results |
---|---|---|---|
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 - if applicable (optional). USER INTERFACE ENHANCEMENTS CCCApply Redesign Project Objective: Implement changes and enhancements to the user interface to "shorten & simplify" the application process" to meet the requirements in AB 3101. |
| |
2 | Ensure college IT and support staff have all the release notes, data and technical specifications, updated user guides, and implementation information needed to implement fixes and solutions to data fields, downloads, and user interface bugs (as needed); and replace temporary workarounds in place with viable functionality and code fixes - which have been preventing efficient business operations, data reporting, and admin/utilities functionality. BUG FIXES & iSSUE SOLUTIONS |
| Confirmed with colleges who reported the bugs that we have fixed those bugs and have no further need for the workarounds. Colleges: Coastline College Sanat Rosa College Sierra College |
3 | Ensure college admissions and IT staff have ability to perform admin configuration and reporting activities with new data fields and values from 6.4.0 and previous releases in the Administrator and Report center. MAINTAIN ADMIN & REPORTING TOOLS |
| Colleges have confirmed that the new and previous release fields (Race & Ethnicity, Spam fields, etc.) now appear on the Full Application Report and are displaying correct results. Colleges confirmed: Santa Rosa College Sierra College |
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. |
The following documentation is required for the CCCApply Release 6.4.0 implementation plan:
Additional Docs
Pilot colleges can begin previewing and testing the CCCApply 6.4.0 pilot release items on February 19, 2019.
STEPS TO TEST CHANGES: The outline below walks you through steps to conduct user acceptance testing of the changes deployed in release 6.4.0.
EXPECTED RESULTS: To help confirm changes meet the proposed success criteria for the UAT objectives.
Repeat this process for your Production application after the production release on March 16, 2019. |
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 the Colleges/Universities Attended questions on the Education page by default for all users 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. |
The table below provides an overview of the new and/or changed data fields being deployed in the CCCApply 6.4.0 release (Standard Application and "Glue for Standard Apply" Only).
See these data specification changes in the CCCApply Standard Application Data Dictionary V.2019.1 in the CCCApply 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 |
For SuperGlue colleges, the new Race & Ethnicity Full data element is called "raceEthnicFull".
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 | See the CCCApply Standard Application Data Dictionary v.2019.1 for the data element specification table. |
In general, in order to download new and changed data fields and values that get deployed in CCCApply applications, you must first add and/or make changes to the fields in your application-specific Format Definition XML file(s) and update the existing (transfer-client.jar) file for current release.
For the 6.4.0 Pilot release, update your Standard Application Format Definition XML file with the data field changes specified in the New & Changed Data Fields table, above.
To ensure your CCCApply download files are always in synch with the latest release version, we recommend that all new and changed data fields be added to your download files (Format Definition XML) and replace/update the Download Client Jar file with each release. This should be done whether you plan to import the new fields to your college SIS system. |
After you've updated your Pilot Format Definition XML with new and changed data fields, replace your Pilot Download Client Jar file with the latest version.
In your installed Pilot Download Client directory, replace the following files:
Follow the instructions in the Pilot CCCApply Download Client User Guide.
Please be sure to backup your files before downloading new ones. |
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:
Follow the instructions in the CCCApply Download Client User Guide.
During a CCCApply pilot release (30 days between pilot release and production release), colleges are encouraged to follow the response processes below to report system issues and bugs (S1 and S2) as well as non-critical bugs, change requests, and other general feedback (S3, S4) using the processes below.
Severity Levels
S1 - Application / service is unavailable.
S2 - Required business process is prevented from being used. No workaround is available
S3 - Less important business process is impacted and/or workaround is available.
S4 - Low impact or cosmetic issue
Level | Issue Type | Description | Operations Priority | Feedback Process |
---|---|---|---|---|
S1 | Application / service is unavailable. | Pilot college cannot access the Non-Credit application in the Pilot environment using their custom URL | 24-48 hr response Hot Fix resolution TBD | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
S1 | Application / service is unavailable. | Pilot college cannot access the Non-Credit application due to error message | 24-48 hr response Hot Fix resolution TBD | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
S2 | Required business process is prevented from being used. No workaround is available | Pilot college identifies a critical bug in the Non-Credit app user interface or backend systems that prevents implementation or testing | 24 - 72 hr response Set priority level TBD | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
S3 | Less important business process is impacted and/or workaround is available. | Pilot college identifies a non-critical bug in the Non-Credit app user interface or backend that does not prevent implementation or testing | 1 week response Set priority level TBD | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
S2 | Must Have Requirement Required business process is prevented from being used. No workaround is available | Pilot college identifies a missing IT or business requirement per state, federal or local mandate (example: AB 3101) | 1 week response Set priority TBD | Use Change Requirement template Pilot college documents requirement(s) via Change Requirement form template; sends as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda. |
S4 | Nice to Have Request Low impact or cosmetic issue | Pilot college identifies a med/high-priority change enhancement to the MVP application | 2 week response Set priority TBD | Use Change Request template Pilot college submits change requirement(s) using Change Request form template; send as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda. |
S4 | Delighter Enhancement Low impact or cosmetic issue | Pilot college identifies an enhancement to the user interface or backend service(s) that includes unauthorized feature development (Out of FY scope) | 2 - 4 week response | Use Change Request template Pilot college submits change request(s) using Change Req form template; send as link or attachment to Pilot Project Manager to be prioritized for committee review. |
Request for Implementation Support | Pilot college requests advice and/or general support for IT implementation, operations, best practices, and/or additional help from Product management, support services, other college pilots, or general colleges - in support of the new project. | 24 - 48 hr response Depending on item; TBD | POST FEEDBACK or QUESTIONS on the CCC Pilot colleges should review all CCCApply community board discussions before posting a new support request or question on the College Support Site: CCCTechnology.info |
Incidents encountered during Pilot Project testing in the Pilot environment - especially during a pre-production release period - should be reported immediately to the College Support Services team - to be resolved as quickly as possible.
College Support Services via the Staff Support email: staffsupportccctc@openccc.zendesk.com
NOTE: If you report an issue to the Support team by email, please cc: Patty Donohue, CCCApply Product Manager, pdonohue@ccctechcenter.org - to keep the product team aware of incidents and bugs. |
Change Request Form Templates