Page Comparison

Release Plan

Release Summary

Below is a high-level summary of the priority enhancements that will be released, which will be followed by technical release notes when the code is deployed to the Pilot (test) system on August 26, 2016.

For more information, expand the “Read More” link below each item (where applicable). 

Release Highlights

Release Plan

30-Day Pilot Site Preview

In order to give colleges time to review and implement the changes and enhancements being released to students on September 30, we will release the code to the Pilot environment for 30 days in advance, on September 1, 2016 at 6:00PM.  Technical specifications will appear in Pilot versions of the Data Dictionaries & User Guides, along with the notes and links in this document. 

REMINDER: The production release is scheduled for September 30, 2016 at 6:00PM PST. The 30-day Pilot site preview begins on September 1st at 6:00PM.

Update the Download Client Jar Files

Pre-Release Notes Summary

Below is a high-level summary of the enhancements that are planned as part of the 5.5 release.  

Anchor
openccc-changes openccc-changes

OpenCCC Account

The following enhancements are planned for the OpenCCC Account system. There are no actions required by colleges.

New Data Fields to Support Multiple Measures (SB1456)

In support of state legislation AB743, which calls for an systemwide assessment system be developed to include multiple measures for placement, and SB1456, which calls for the gathering of multiple measures data, the Common Assessment Initiative (CAI) has requested a series of data field questions be added to the CCCApply Standard Application in order to collect self-reported, high school transcript information for assessment placement purposes for the CCCAssess program. Seven (7) new questions and downloadable data fields will be added to the Education page of the Standard Application only.
 

Anchor
standard-app-changes standard-app-changes

CCCApply Standard Application

The following enhancements are planned for the CCCApply applications.   

Click on the Change Specification / Technical Notes hyperlinks in the table below to see the detailed change specifications planned for each item. A "Pilot" version of the CCCApply Standard Application Data Dictionary will accompany the release to Pilot on 9.01.16, and will be published in the Production Data Dictionary on September 30, 2016.

Back to Top

Anchor
new-data-fields new-data-fields

New Data Fields & Changes to the Download Client

The following data fields have been will be added to the Download Client. To download these fields, your college IT staff must add them to your download file, update your the Download Format XML files, as indicated.

The data fields included in the Multiple Measures for Assessment Placement - the “opt-in implementation” - are being added to the Download Client, as well as and the Report Center.  All new fields are optional and do not have to be added to your download file; however, if you want to collect this dataAll fields will also be available in the Report Center.  Data Fields for Assessment Placement

Definitions XML file for the application(s) they pertain to. This process is described in the CCCApply Download Client User Guide.
 

Anchor
change-to-logic change-to-logic

Changes to Residency Logic

Update to Area B Residency Logic

The Area B residency logic is being updated to fix a problem with non-resident and “possible” residents being incorrectly classified as “residents” in certain use cases, including the California resident who has also answered “yes” to one of the four “out-of-state” indicators on the residency page in the standard application.  The correction will change the “IF NO” column of Step 1 from “B0 and go to step 2” to “Set B2 and go to step 2”. We will also add a new integrity flag (30) to alert Admissions that the user has an “out-of-state” indicator (such as they paid taxes outside of California within the past two years).  This change will ensure that these applicants end up as “B2 = Possible Resident. Proof required” or “B0 = Nonresident. Does not meet residency criteria” when they reach the final classification (Step 13).  To see

What action does the college need to take?
There is no required action on the part of the college. However, you may want to review any rules created to ensure this change will not adversely affect any processes previously set up by your college. This change does not affect any data field calculations.Documentation

identified around California residents who answered "Yes" to one or more of the "out-of-state activity" questions within the past year. The majority of the problems identified pertain to California residents that reported that they paid taxes outside California last year, yet they've also lived in the state for the past two years.

Expand

The solution is to change Step 1 from: "Set Class B0 - Non-resident > Go to Step 4"  to  "Set Class B2 > Set flag (30 > Go to Step 2" which is the point where California residency for 2years is identified. If the answer is "No" at step 2, the "B0" classification is then set, and the logic advances to step 3 and 4. At step 4, unless the student with the "B0" classification is determined to be a current or former Foster Youth, they keep the "B0" classification and skip to the end for final B0 classification. If the user is a Foster Youth, the class is set back to "B2", a flag is set, and they advance through the rest of the logic with that classification.   Please review the Change Specification for detailed information and a Use Case Matrix to ensure all scenarios are tested against the new logic.

What action does the college need to take?
No change is required by the college (unless you have custom residency calculation forms that need to be updated with the new step and change to Step 1). Otherwise, the residency algorithm will continue to do its job calculating the "Preliminary Residency Status". Admissions staff should be aware that there is a new integrity flag for "Out-of-State Activities" to help identify these cases and collect proof when needed.

Questions? Please add questions and comments in the support site: CCCTechnology.info.

Anchor
bugs bugs

Bug Fixes

The following bug fixes are planned for this release. No action is required by the colleges.

Accessibility Fixes

One of the objectives of this release is to fix a series of accessibility issues in the CCCApply applications which were identified in a third-party accessibility review conducted in February 2016. Issues that can be fixed in the current version of CCCApply will be fixed; however, issues that require significant re-writes to the application code or user interface are being deferred to the next version of CCCApply (3.0). Development for V.3.0 is slated to begin in Fall 2017.

The issues below were determined to be mandatory or feasible fixes for the current version of CCCApply.
 

The PILOT Site

During the 30 Day Pilot Preview period, we encourage college Admissions staff to review the changes and alert your IT department staff to add the new data fields to your Download files. (See New Data Fields & Changes to the Download Client section for new fields being added and the application they are being added to). NOTE: All other changes, including the new step added to the Area B residency logic, require no action by the college. 

Getting to the Pilot Applications

Remember to include your college's MIS code to the end of each application URL. 

Documentation

A Pilot version of the CCCApply Standard Application and User Guides will be posted and announced with the Pilot release on September 1, 2016.