Release Schedule
Description | Date & Time |
|---|---|
Release No. | 6.5.0 |
Pilot Release | 05.31.19 - 9:00AM PST |
Production Release | 06.28.19 - 6:00PM PST |
| Release Type | Maintenance Window | Major Release |
Release Scope
| Description | Scope |
|---|---|
| Applications | CCCApply Standard Application (Apply) |
| Changes to Residency Logic | Yes |
| Changes to Download Client | Yes - (Download Client Jar 6.5.0) |
| Changes to Documentation | Yes - Data Dictionaries & User Guides |
Contents
Release Scope
| # | Change Requirement | Application | Notes & Change Request Docs |
|---|---|---|---|
| 1 | CCCApply Noncredit Application Path (Phase 3: Production Release) | CCCApply Standard Application only | CCCApply Noncredit Application |
| 2 | CCCApply Redesign Project - User Interface Enhancements - Release 4 (Q4) | CCCApply Standard Application | See "Changes to User Interface" section |
| 3 | Approved Change Requests | CCCApply Standard Applications | |
| 4 | Maintenance & Support (Admin Support, Tech Updates, and Bug Fixes) Bug Fixes | CCCApply Standard Application | See "Maintenance & Support" section See "Bug Fixes" section |
| 5 | Java Upgrade | All CCCApply Applications | See "Java Upgrade" section |
Release Summary
This is the third release of the CCCApply Redesign Project under the guidance of the CCC Chancellor's Office, the CCC Technology Center, and the CCC Foundation to revise the CCCApply application in compliance with AB 3101. Read more about the CCCApply Redesign Project, including the project objectives and project release schedule for the first phase of the project and future long-term plans to rebuild the application (holistic redesign). Also included in the redesign project, CCCApply Non-Credit Application - Phase 1: Development, and information about the soft-launch of the College Pilot Project.
Pilot Release
The Pilot environment release is scheduled for February 19, 2019. This period is for colleges to preview interface changes and test bug fixes and prepare for new or changed data fields prior to the production release (March 15). The CCCApply Support Services team will be monitoring feedback on the CCCTechnology.info support site, and additional online support information will be available.
Release Schedule & Timeline
- May 31 - 9:00AM - 1:00PM (Note the Pilot Site will be down during this release).
- June 28 - 6:00PM - 11:00PM - Production Maintenance Window
Stay Informed! For news, release announcements, updates, and CCCApply System Alerts, follow us on "CCCApply System Alerts" on CCCTechnology.info.
New Noncredit Application Path in the CCCApply Standard Application
| Description | Notes & Links | ||
|---|---|---|---|
| Noncredit Application | See the CCCApply Noncredit Application See the Noncredit Application Path Requirements | ||
Workflow Path in the Standard Application: | The Noncredit Application is a workflow path within the CCCApply Standard Application, but does not have any residency questions and does not calculate a preliminary residency determination via the Submission Calculation Service. For students enrolling exclusively in noncredit courses; no credit is given. | ||
Noncredit App URL | The Noncredit Application "path" has a different URL than the Standard Application. Each college has a unique URL, based on their MIS code, just like the Standard Application. See the CCCApply Noncredit Application URLs (Alternately, use the template URL below and replace the XXX with your college MIS code.) Noncredit URL: https://pilot.opencccapply.net/cccapply-welcome?cccMisCode=XXX&nonCredit=True | ||
Noncredit Confirmation Number | To identify Noncredit applications and distinguish them from Standard applications, a prefix has been added to the confirmation number for all in-progress and submitted Noncredit Applications. Confirmation numbers for Noncredit Applications begin with "NC-" | ||
Hidden Pages | The following pages have been hidden in the Noncredit Application:
See Changes to User Interface below. See changes to field values in Changes to Downloads below. | ||
Hidden Questions | The sections on the Needs & Interests page can be removed (by request from each college):
| ||
New Data Fields | Two new "optional" data fields were added to the CCCApply Standard Application data set to identify the Noncredit Application. If you plan to download this data (optional) they must be added to your download files and the Download Client Jar file must be updated to the latest version (6.5.0).
Read about the new data fields in the following sections: See New & Changed Data Fields section | ||
Changed or New Values to Data Fields | A number of data fields were revised to include a "Null" value - or some other reconfiguration to compensate for the fact that they are not appearing in the Noncredit Application. Read about the data fields that have new values: See New & Changed Data Fields section | ||
Change to Majors / Programs of Study Menu | Colleges may choose to display different majors or programs of study in their Noncredit Application. To have a different set of options display in the "Intended Major / Program of Study" drop down menu, colleges must complete a setup task in the Majors module in the CCCApply (Standard) Administrator. For more information, see the Noncredit Application Implementation Checklist A new "Application Type" toggle has been added to the Majors table in the CCCApply (Standard) Administrator. Setting the application type for each major/program will be required for all colleges who wish to implement the Noncredit Application. | ||
Change to Supplemental Questions Feature | Colleges may choose to display different supplemental questions in their Noncredit Application. This is optional. To have a different set of custom supplemental questions display to users, colleges must complete a setup task in the Supplemental Questions module in the CCCApply (Standard) Administrator. For more information, see the Noncredit Application Implementation Checklist | ||
| Allow Noncredit Student to Re-Apply Using the Standard Application for the Same Term at the Same College | Add logic to allow student's who submitted a Noncredit application using the Noncredit URL to re-apply to the same term, same college using the Standard Application See Noncredit Path Change Requirements | ||
| Auto-population Expanded for Noncredit Application | Implement auto-population for fields hidden in the Noncredit Application if student re-applies using the Standard Application within 2 years. Noncredit students may want/need to re-apply to enroll in credit courses. They should re-apply using the Standard Application to get residency-determination status. | ||
New Residency Status Value Added to Identify Noncredit User | Add new value to "Residency Areas" status fields to identify "noncredit / exempt" status | ||
Changes to the CCCApply Standard Application
The following changes and enhancements were approved and deployed in the 6.5.0 release code.
| # | Change Specification | Additional Info | |
|---|---|---|---|
| 1 | CCCApply Redesign - User Interface Enhancements | Approved changes intended to shorten & streamline the Standard App | |
| Streamline the Account Information/Mailing page for first time applicants | No changes for colleges or students | ||
Make the Needs & Interests Page Optional | A change was made to allow the Needs & Interests page to be removed from the CCCApply Standard (and Noncredit) Applications - upon request by the college or district. IMPORTANT NOTE: If you choose to remove/hide the Needs & Interests page in the Standard Application, it will also be hidden in the Noncredit Application. See Changes to User Interface section below. See changes to field values in Changes to Downloads below. | ||
Make each section on the Needs & Interests Page Optional in the Noncredit App/Path
| A change was made to allow each section on the Needs & Interests page to be hidden in the CCCApply Standard (and Noncredit) Applications - upon request by the college or district. IMPORTANT NOTE: Whichever sections you decide to hide - will be hidden on both the Standard and Noncredit Applications. In order to support the colleges who are using specific questions or sections on the Needs & Interests page to trigger custom email rules, and for MyPath colleges who rely on the Programs & Services section to trigger custom rules and notifications within MyPath, each section on the Needs & Interests page can now be shown or hidden - upon request - by the college. | ||
| 3 | Maintenance & Support Changes | ||
Bug Fixes
| # | Bug Description | Fix Details | |
|---|---|---|---|
| Visa Types Table in Standard Application is not displaying Residency page as required | |||
| CSFC birthdate Rule Failing - Rule Preview Works | |||
| Applicants Allowed to Submit Multiple Applications for Same Term | |||
| Resuming an application is taking me to Demographic Information instead of Education | |||
| HelpDesk SSN Lookup Does Not Find Accounts | |||
| When applicant(s) enters a family size in the supplemental questions section the value entered is not populating on the application | |||
Issue Resolution: Java 11 Upgrade
Types of Issues Reported
Immediately following the 6.30 release, we received requests for support from 6 colleges related to:
Problems with bad data interrupting download processesBad data appearing in Report Center reports
Work-arounds proposed and documented
We do not have a proposed work around at this time. The issue is that the affected applications have bad data in them, the best we can suggest is to maintain a record of the affected apps downloaded, and we can provide instructions for how to translate the race_ethnic value to the correct format if necessary.For colleges affected by this, if they maintain a record of the affected applications they could potentially wait until we run the script to fix the values in the submitted application DB, and then reset those apps for download again so they can load them into the service they have that consumes the submitted applications. Each colleges process is probably too different and customized to be able to provide a concrete work around however.
Solution: Fix to the Translation Logic and Data
The first is to put the translation logic back in at submission time. If an application is submitted without the MIS formatting, then it will be properly translated before it is submitted.The second approach is we have built a small script that will connect to the submitted application database, search for the affected applications, and perform the translation of any race_ethnic values that have the improper format.
Changes to the CCCApply Download Client
The following data fields have been added or changed in the CCCApply applications. For updated data specification documents, please see the CCCApply Data Dictionaries and User Guides space.
Update Your Download XML Files: In order to download new or revised data fields, they must first be added or updated in the CCCApply Format Definitions XML file(s) and the download client jar file must also be updated with the latest version = < transfer-client.V6.4.jar > For more information, please see the CCCApply Download Client User Guide > User Guides
New & Changed Data Fields
The table below provides an overview of the new or changed data fields in CCCApply Standard, 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 |
|---|---|---|---|---|---|---|---|
| Noncredit Status | <non_credit> | New Field | 1 = True 0 = False | Boolean, 1 | Yes | No | Optional; Value set to "True" if applicant applies using the new Noncredit Application URL; otherwise it is "False" |
| Confirmation Number | <confirmation> | Changed Value | IF non_credit=True then | String | No | System | IF an application is submitted using the Noncredit URL then the value for <confirmation> = "NC-" |
| Integrity Flag 81 | <integrity_fg_81> | New Field | 1 = True Null | Boolean, 1 | Yes | No | Flag triggered if applicant applies with the new Noncredit Application URL; otherwise it is blank. NOTE - this is consistent with how we have all the other integrity flags structured. |
| Residency Status | <res_status> | New Value | New NC default value = N 1 = resident | bpchar, 1 | No | Residency status is calculated at submission for Standard Application only. For the new Noncredit Application path (in the Standard Application) if applicant applies using the new Noncredit URL then: <non_credit> status is set =True and <res_status> status is set ="N" | |
| Residency Area A | <res_area_a> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
| Residency Area B | <res_area_b> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
| Residency Area C | <res_area_c> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
| Residency Area D | <res_area_d> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
| 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 Noncredit 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 | |
| Citizenship Status | <citizenship> | New Value | Default to value = X when (non_credit = True) | character(1) | No | Required to have non-null value in DB. | In the new Noncredit Application workflow, the Citizenship status question is hidden; value stored = "X" |
| Military Status | <military_status> | New Value | New NC default value = X Default to value = X when (non_credit = True) | character(1) | No | Required to have non-null value in DB. | In the new Noncredit Application workflow, the Military status question is hidden; value stored = "X" |
| Comfortable with English | comfortable_english | Allow Null | NC default value = null | Boolean, 1 | Yes | No | In the new Noncredit Application workflow this question is hidden; value stored = Null |
| Financial Assistance | financial_assistance | Allow Null | NC default value = null | Boolean, 1 | Yes | No | In the new Noncredit Application workflow this question is hidden; value stored = Null |
| TANF-SSI-GA | tanf_ssi_ga | Allow Null | NC default value = null | Boolean, 1 | Yes | No | In the new Noncredit Application workflow this question is hidden; value stored = Null |
| Athletic Interest: Intramural | athletic_intramural | Allow Null | NC default value = null | Boolean, 1 | Yes | Required response If appears onscreen | In the new Noncredit Application workflow this question is hidden; value stored = Null |
| Athletic Interest: Intercollegiate | athletic_intercollegiate | Allow Null | NC default value = null | Boolean, 1 | Yes | Required response If appears onscreen | In the new Noncredit Application workflow this question is hidden; value stored = Null |
| Athletic Interest: No | athletic_not_interested | Allow Null | NC default value = null | Boolean, 1 | Yes | Required response If appears onscreen | In the new Noncredit Application workflow this question is hidden; value stored = Null |
Changes to the User Interface
| Page / Section | Description | Current UI State | New Revised UI State | Notes to Colleges |
|---|---|---|---|---|
| Noncredit Application | Add a Prefix to the Confirmation Number for Noncredit Applications | The Confirmation number (as well as the App_ID) will include a prefix of "NC" if the application is started and submitted using the Noncredit URL. | Example: NC-4140067 | |
| Noncredit Application | Hide the Residency Page in the Noncredit Application path | When a student applies to your college using your Noncredit URL, the user interface and the user experience will be very similar to the Standard Application but the residency page is not included in the workflow. No residency page questions are required at the time of submission. | ||
| Noncredit Application | Hide the Citizenship & Military Page in the Noncredit Application path | The Citizenship & Military page of questions do not appear in the Noncredit Application workflow | ||
| Noncredit Application | Hide questions from the Needs & Interests Page in the Noncredit Application path: | |||
| Noncredit Application | Auto-population of Noncredit Application responses in the Standard Application | Note: Auto-population will pre-fill previously submitted responses from the last application submitted within 2 years of current date. | ||
| Noncredit App | Add logic to allow applicants to re-apply to the same college and the same term when transitioning from Noncredit to Credit status | Currently, the Standard Application prevents a user from submitting two applications to the same college for the same term. This | With the implementation of the Noncredit Application path, a student who submits a Noncredit Application to college (A) for term (A) is now able to re-apply with the Standard Application to college A for term A. This logic has been modified for Noncredit > Standard Application only. | (NOTE: This means that a student who has submitted an application to a college (example: College A, Term A) using the Noncredit Application, can now re-apply (submit a Standard Application to the same college for the same term A). However, this only applies to students transitioning from Noncredit status to Credit status; otherwise they will be blocked from submitting a second Standard Application to the same college, same term.) |
Changes to "Glue for Apply" and the SuperGlue College Adapter
Description | Data Field | Format / Length | Required | Notes |
|---|---|---|---|---|
| Noncredit Status | <non_credit> | Boolean (True/False) | No | Optional field set to "True" if applicant applies with the new Noncredit Application URL; otherwise it is "False" |
| Integrity Flag 81 | <integrity_fg_81> | Boolean (Y/N) | No | Flag triggered if applicant applies with the new Noncredit Application URL; otherwise it is blank. |
| 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 | NOT AVAILABLE in the Release 6.3.0. |
User Acceptance Testing (Pilot)
User acceptance testing for this release involves previewing the user interface changes that are being deployed as part of this release. Other than the two new (optional) data fields being added for the Noncredit Application, as well as the other data field revisions being made for that application, there are no new fields being added.
Colleges are encouraged to log in to their CCCApply Pilot environment and review the Standard application, as well as the new Noncredit Application path, after the release on May 31, 2019.
UAT Plan: CCCApply Release 6.5.0
UAT Feedback & Resolution Process
- Gathering Feedback: Feedback should be categorized as bugs, issues or enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as production release blockers.
- Reporting Feedback: 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
- Issues that prevent critical business functions
Preview & Send Us Feedback: During the Pilot release preview, your feedback supports our commitment to continuous improvement. If you find a bug or experience any issues, please let us know by posting in the CCCApply Support category on CCCTechnology.info.
Data Dictionaries & Release Documentation
The following links point to the most current versions of the CCCApply Data Dictionaries and User Guides.
| Description | Version / FILE | Format | Release | Date Published |
|---|---|---|---|---|
| CCCApply Standard Application Data Dictionary | V.2019.2 | Release 6.5.0 | ||
| Download Client Jar File V.6.5.0 | transfer-client.V6.5.jar | jar | Release 6.5.0 | |
| CCCApply Download Client User Guide | V.6.5.0 | ONLINE | Release 6.5.0 | |
| 2019-2020 CC Promise Grant Data Dictionary | CCPG-V2019 | 2019-2020 | 11.20.18 | |
| CCCApply International Application Data Dictionary | V.2019.2 | Release 6.5.0 |