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) |
Contents
Release Scope
| # | Change Requirement | Application | Notes & Change Request Docs | |
|---|---|---|---|---|
| 1 | CCCApply Noncredit Application (Production Release) | CCCApply Standard & Noncredit | See New CCCApply Noncredit Application | |
| 2 | CCCApply Redesign Project - Release 4 (Q4) | CCCApply Standard & Noncredit | See the Contents for anchor link | |
| 3 | Approved Change Requests & Updates | CCCApply Standard & Noncredit | See "Changes to the CCCApply Standard Application" section | |
| Spam Filter Web Service | CCCApply Standard & Noncredit | |||
| Glue for International Application (Staging Table) | CCCApply International | |||
| 4 | Maintenance & Support: Java Upgrade | CCCApply Download Client | See "Maintenance & Support" section | |
| 5 | Bug Fixes | CCCApply Standard & Noncredit | See "Bug Fixes" section | |
Release Summary
The CCCApply v.6.5.0 Pilot release will deploy on Friday, May 31 beginning at 9:00 am PST. The Pilot environment will be offline during the release. College staff can stay informed on the progress by following the CCCApply category page on CCCTechnology.info.
During the 30-day pilot period, colleges are encouraged to preview all changes to CCCApply, including the new Noncredit Application, and take advantage of the support that is offered by the Enabling Services division, now offered by the CCC Tech Center.
Schedule & Timeline
- Pilot Release (30-Day Preview): May 31 - 9:00AM - 1:00PM (Note the Pilot Site will be down during this release).
- Production Release: Friday, June 28 - 6:00 pm - 11:00 pm PST
Stay Informed During the Pilot Release! Follow the "CCCApply System Alerts" page - and any other category, page or individual post, on CCCTechnology.info.
CCCApply Noncredit Application
Development is complete on the first version of the CCCApply Noncredit Application. Colleges are invited to preview their college-branded version at any time following the May 31st pilot release. Getting started steps are available in the Noncredit Application Implementation Guide.
About the Noncredit Application
The CCCApply Noncredit Application is a workflow path within the CCCApply Standard Application - which shows only the pages and questions required for students enrolling exclusively in noncredit courses at a California Community College.
For colleges, the Noncredit Application path leverages your existing CCCApply Standard application infrastructure, admin tools, and download mechanisms. Colleges that choose to implement should contact the CCCTC Enabling Services staff at enablingservices@ccctechcenter.org.
Get Started on the Noncredit Application
Colleges that are interested in implementing the new CCCApply Noncredit Application should contact CCCTC Enabling Services to schedule an implementation kick-off call.
New Noncredit Application Features Added in 6.5.0 Release
| # | Feature Description | Release Notes |
|---|---|---|
New Application Type Display Setting Added to the Majors Table in the Administrator Implement "Application Type" identifier menu to the Majors module to set conditions for display in the "Intended Majors/Programs of Study" menu for CCCApply Standard & Noncredit Applications Implement "Application Type" identifier menu to the Majors module to set conditions for display in the "Intended Majors/Programs of Study" menu for CCCApply Standard & Noncredit Applications | Need: Colleges need the ability to display different "Intended Majors/Programs of Study" in the Noncredit Application. Benefit: Colleges control if and when an individual major, course, or program of study displays in each application, even if the offering should appear in both applications. What: "Application Type" menu added to the Majors configuration module, which must be set for each individual major or program of study with one of the following settings:
Where? Authorized CCCApply Administrator users maintain your list of "Intended Majors/Programs of Study" in the Majors module for your college(s). Implementation support and user guide documents are provided in the CCCApply Noncredit App - UAT Implementation Checklist. in the CCCApply Administrator. An authorized admin user CCCApply Administrator 2.0 User Guide Requirement: In order to use the Noncredit Application path, you MUST RECONFIGURE YOUR EXISTING "MAJORS" FILE even if you intended to display the same set of Majors in both applications. | |
New Application Type Display Setting Added to the Supplemental Questions Module in the Administrator | Need: Colleges using the Noncredit Application need the ability to display different/unique "Supplemental Questions" to noncredit applicants. Benefit: Colleges control if different supplement questions should display in the Noncredit Application versus the Standard Application, neither or both. What: "Application Type" menu added to the Supplemental Questions XML code which tells the system the page of questions should display in the Noncredit Application; otherwise it will default to the Standard Application.
Where? Authorized college users maintain the ability to configure Supplemental Questions via XML file upload in the Administrator. Unlike the Majors table, supplemental questions are not added or edited individually to the Administrator user interface; instead an XML template is used to define the questions and formats, as well as other database information. For more information about setting up Supplemental Questions, see the Working with Supplemental Questions User Guide. | |
| New Noncredit Application Title Page | ||
Noncredit Application: Key Development Features
Description | Notes & Links | |
|---|---|---|
CCCApply Noncredit Application - Overview Information | Read the overview here: CCCApply Noncredit Application and here: Noncredit Application Path Requirements | |
| Noncredit Application - No Residency Status Determination | The Noncredit Application does not include any residency questions (see Hidden Pages & Questions below) and does not generate a residency status (the Submission Calculation Service (algorithm) is not run at time of submission); therefore this application should only be used by students enrolling exclusively in noncredit courses. See "Transitioning from Noncredit to Credit for the Purposes of Establishing Residency Status" below. | |
Noncredit Application URL (Customized for each college) | 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. Find your college's PILOT site URL: CCCApply Noncredit Application URLs | |
Noncredit Confirmation Numbers | To distinguish between Noncredit and Standard applications submitted to your college, we've added a prefix to the Confirmation number to help you easily identify which is which. This applies to all in-progress and submitted Noncredit Applications. | |
Hidden Pages | The following pages ARE hidden - not displayed to end users - in the Noncredit Application:
| |
Hidden Questions | The following questions CAN BE hidden - not displayed to end users - in the Noncredit Application upon request by your college. See "Changes to the Needs & Interests Page" below for more details.) one or more sections CAN BE HIDDEN to the end user:
| |
New Data Fields | Two new data fields have been added to the CCCApply Standard Application data set for the Noncredit Application. Reminder: The Noncredit Application is just a workflow path within the Standard Application, therefore it uses the same Download Client files (or Glue for CCCApply data set) as the Standard Application. Read more about the Noncredit Application Data Downloads here.
Read more about the new data fields in the sections below. See New & Changed Data Fields section For complete data element specifications, see the CCCApply Standard & Noncredit Application Data Dictionary (v.2019.2). To download the new Noncredit data fields, you must add them to your CCCApply Standard Application Format Definition XML file and update your Download Client Jar file. See "Java Upgrade" section for important information about backwards compatibility notes for the CCCApply Download Client relative to Java 7 and previous versions reaching end-of-life. CCCApply Java Upgrade work completed and deployed in this v.6.5.0 release. Colleges must be running CCCApply Download Client v.6.4.0 or later in order to get those requirements 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). | |
IMPORTANT - NEW JAVA VERSION REQUIREMENTS for CCCApply Download Client the CCCApply v.6.5.0 release (pilot and production) The CCCApply Download Client no longer supports Java 7. CCCApply college users are strongly encouraged to is no longer supported bAs of the CCCApply v.6.5.0 release, colleges must be running CCCApply Download Client Jar v.6.5.0 in order to download any/all all CCCApply applications, tools, and services must geSee "Java Upgrade" section for technical requirements related to the CCCApply Java Upgrade work completed and deployed in this v.6.5.0 release. Colleges must be running CCCApply Download Client v.6.4.0 or later in order to get those requirements | ||
New Data Field Values | The Noncredit Application is a modified version of the CCCApply Standard Application - with a number of pages and questions hidden from display to the end user. This means that...
Therefore, a breakdown of all new or revised data fields is shown below to ensure you are aware ofor Since questions and/or pages are not displayed to the user, no responses are collected or stored in the database for data fields, and your downloads to not contain values for those fields/responses questions; thus (hidden) a "Null" value two applications a questions and pages are hidden (i.e., or hidden or The Noncredit Application has a 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 | |
New Logic has been implemented that will allow a Noncredit student to submit a Noncredit Application, then re-apply using the Standard Application for the Same Term at the Same College (but not the other way around) | 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 | |
Self-Reported Multiple Measure Questions Not Included in the Noncredit Application | The Chancellor's Office and the AB705 Advisory Committee have required that the self-reported, multiple measures questions should not appear in the Noncredit Application. | |
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. In addition, each "section" within the Needs & Interests page has also been reconfigured to be optional relative to being displayed to end users (and thus, the data fields would not be downloaded if you choose to opt-out). 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. To learn more about this reconfiguration, see Changes to the Needs & Interests page in CCCApply. 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. | ||
| New "Non-binary" Value Added to the Gender Field | New value added | ||
| Update Foster Youth Status Question Language & Values Per SB 906 | Priority registration eligibility is now 16 years old. | ||
| Add Language to the Parent/Guardian Information Section to Support Foster Youth Minors | |||
| Add Visa Types to Standard Application That Are Eligible for Residency Determination | New values added | ||
| New Spam Filter Retraining Model | Deployed May 10; Next (pii) model update 6.5.0 (June 28) | ||
| 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 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. The section below pertains specifically to the CCCApply Download Client; see below for information related to data fields being added to SuperGlue. 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.5.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 |
|---|---|---|---|---|---|---|---|
| Visa Type | <visa_type> | New Values | E2C = E-2C SIV = Special Immigrant Visa T6 = T-6 | ||||
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 |