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.
Pilot College Participation
The CCCApply Release 6.4.0 UAT will consist of 3* district colleges from the CCCApply Redesign Workgroup.
Participating Colleges
Colleges from the CCCApply Redesign Workgroup will participate in Release 6.4.0 UAT activities:
- Santa Rosa College
- Bakersfield College
- Cerritos College
Minimum Participation Requirements
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:
- Complete all UAT Implementation activities and testing goals
- Provide feedback and support only as needed
- Optional: Contribute to the development of best practices and support materials
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.
Pilot UAT Plan
The user acceptance testing (UAT) plan, process and objectives for the CCCApply Release 6.4.0 Pilot are listed below.
- UAT Objectives & Success Criteria
- Required Documentation
- Getting to the Pilot Application
- IT Implementation Steps
- Data Fields & Downloads
- Admin Configuration
- Reports
- Feedback & Support Processes
UAT Objectives & Success Criteria
The objectives and success criteria for college user testing across the 6.4.0 release are detailed below.
# | UAT Objectives | Success Criteria |
---|---|---|
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. |
|
Required Documentation
The following documentation is required for the CCCApply Release 6.4.0 implementation plan:
- CCCApply Release 6.4.0 Notes Summary
- CCCApply Redesign Project
- CCCApply Redesign Project Dashboard
- CCCApply Standard Application Data Dictionary v.2019.1
- /wiki/spaces/PD/pages/758546724
- CCCApply Download Client User Guide v.2019.1
- CCCApply Redesign Project - Q3 User Interface Changes (PPT)
Additional Docs
- All CCCApply Data Dictionaries
- All CCCApply User Guides
Getting to the Pilot Environment
Pilot colleges can begin previewing and testing the CCCApply 6.4.0 pilot release items on February 19, 2019.
Pilot IT Implementation Steps
Follow the steps below to conduct user acceptance testing meet the expected success criteria for the UAT objectives.
- Using a new Chrome browser window, navigate to your college (MIS code-specific) version of the /wiki/spaces/PD/pages/131465676
- Start a new CCCApply Standard application from your My Applications page
- If you have a Pilot OpenCCC test account, click "Sign In". Landing in your My Applications page, click on "Start a New Application"
- If you don't have a Pilot OpenCCC test account, click on "Create an Account" and follow the three page account creation process
- From your My Applications page, click on "Start a New Application" and continue to the Enrollment page.
- From the Enrollment page, complete all required fields and continue to the Account Information/Mailing page:
- Select a Term
- Select an Education Goal
- Select a Major Category
- Select an Intended Major/Program of Study
- From the Account Information/Mailing page, complete all required fields and continue to the Education page.
- Review OpenCCC Account Information section and make any edits or changes are needed;
- Review the Current Mailing Address section and make any edits or changes as needed.
- UAT Activity: On the Education page, review user interface enhancements and test user iconfirm data field and skip logic changes:
- User interface change: Hide the two college sections until user's enrollment status response
- Hide the College Education Level section by default for all users
- Hide the Colleges/Universities Attended section by default for all users
- Add skip logic validation to the College Enrollment Status field to hide or show college sections based on College Enrollment Status response value
- T
- From the College Enrollment Status field, test the following display and logic behavior:
- select "1 = First time in college, after leaving high school"
- New expected results:
- College Education Level question/field remains hidden to user and response defaults to "Null"
- otherwise keep the sections hidden and default value to Null.
- If <enroll_status> = First time in college, after leaving high school then keep college sections hidden
- Add College Enrollment Status = First time in college, after leaving high school
- Complete the Enrollment page
- Complete the Account Information/Mailing page
- Complete the Education page
- Complete the Needs & Interests page (optional)
- Complete the Demographic Information page (optional)
- User interface change: Hide the two college sections until user's enrollment status response
- Complete all remaining required portions of the application and submit the application
- Review your application responses on the Submission page (optional)
- Complete the Consent to Release Information checkboxes (required)
- Complete the Submission requirements (required)
- After submission, note the application's Confirmation number (App_id) and your CCCID.
- Review the confirmation screen and note your confirmation number for the Non-Credit application version you just submitted:
- Note that the Confirmation number begins with a "NC-" preview
- Continue to the Student Satisfaction Survey and complete the survey (optional)
- Continue down the page and review the Special Links & Opportunities for your application
- Click "Finish & Sign-Out" or if MyPath college, click "Finish and continue to MyPath" (confirm)
- Return to the My Applications page and locate your submitted Non-Credit application in the submitted applications Table
- Note the confirmation number begins with a "NC-" prefix
- Sign out of My Applications
- Add new Non-Credit App data fields to existing CCCApply Standard Application Pilot download files
- Add the new data fields to your existing Standard Application Format Definition XML file for the Pilot environment:
- Non-Credit Status = <non_credit>
- Integrity Flag 81 = <integrity_fg_81>
- Note all specified data field changes (new values, formats, logic, etc.) as specified in the Change Log of the CCCApply Standard Application Data Dictionary v.2019.1
- Review data dictionary specification information for these fields
- For help updating your Format Definition file, see the CCCApply Download Client User Guide
- Add the new data fields to your existing Standard Application Format Definition XML file for the Pilot environment:
- Update your existing Download Client Jar File with new version (v.6.4.0 for Pilot release)
- Find and replace the "transfer-client.jar" file in your CCCApply Download Client with the latest version for this release (v.6.4.0).
- NOTE: The 'transfer-client.jar" file has the same as the download client jar file
- Refer to the latest version of the Download Client User Guide v.2019.1
- 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.4.0).
- Optional Admin Configuration Changes for Non-Credit Application
- Navigate to the Pilot CCC Administrator (CAP) and login using existing user account credentials
- Select "CCCApply Administrator" from the Applications menu on the homepage
- From the CCCApply Administrator home page, select "CCCApply" from the Applications menu
- Select your college from the College selection menu bar
- Select "Messages" from the Modules menu bar
- Click on Add new Message and create a custom Message using the new CCCApply Non-Credit Status field <non_credit>
- Save Message
- Select "Rules" from the Modules menu bar
- Click on Add New Rule button and create a custom rule using the new <non_credit> = True field in the code editor
- Reference the new Message created in the Messages module that includes the new non-credit status merge field
- Select the Majors module from the Modules menu bar
- Click on Add New Major button and complete a new test Major, populating the following fields:
- Major Code
- Major Name
- Major Start Date
- Major End Date (or select No End Date)
- Major Category = create new category called "Non-Credit Programs" and enable the tag for this new Major
- Save New Major
- From the Majors Summary Table, select a test major row and click "Edit Major"
- In the Major Category field, add "Non-Credit Programs" for this test major
- Repeat the process for 1-3 addition test Majors
- Click on Add New Major button and complete a new test Major, populating the following fields:
- Repeat steps 1 - 4 - start a new Non-Credit application and navigate to the Enrollment page
- Complete the Term field
- Select an Education Goal
- In the Major Category menu, confirm that "Non-Credit Programs" is a category in the list, and select that category
- In the Intended Major/Program of Student field menu, confirm that only the majors tagged with the Non-Credit Program tag are displaying in the Major Category filter/menu
- Select one of the majors tagged as a Non-Credit Programs
- Ensure the new Non-Credit Application data fields are appearing as reportable fields in the CCC Report Center
- Navigate to the CCC Report Center and login with your existing Pilot user account
- Navigate to "Create New Ad Hoc View" from the main menu on the homepage
- running reports Status Flag is running reports
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 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. |
New & Changed Data Fields
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 |
College Adaptor (SuperGlue) Data Element
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. |
Updating Your Download XML Files
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.
Update Your Pilot Download Client Jar File
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:
- Replace transfer-client.jar (V6.4) with: transfer-client-V4.jar
Follow the instructions in the Pilot CCCApply Download Client User Guide.
Caution
Please be sure to backup your files before downloading new ones.
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:
- Replace transfer-client.jar (V6.4.0) with: transfer-client-V4.jar
Follow the instructions in the CCCApply Download Client User Guide.
Bug Fix Solution 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.
College Adaptor (SuperGlue) Data Element
For SuperGlue colleges, the new race_ethnic_full data element is called "raceEthnicFull"
UAT Feedback & Resolution 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