...
| Date | Description | Release |
|---|---|---|
| February 19 | CCCApply 6.4.0 release to the CCCApply Pilot environment (see Release 6.4.0 Summary Notes) | CCCApply 6.4.0 Pilot |
| February 19 | Non-Credit Application 1.0 - Soft launch release to the CCCApply Pilot environment | Non-Credit v.1.0 Pilot |
| February 20 | Non-Credit Pilot Project commences | |
| February 20 - 28 | First recurring Non-Credit Pilot Project meeting is held | |
| March 15 | CCCApply 6.4.0 Production release (see Release 6.4.0 Summary Notes) | CCCApply 6.4.0 Prod |
| April 8 | Non-Credit Application (v.1.x) Pilot Update (Tentative) | Non-Credit v.1.1 Pilot |
| April 15 | Deadline for development changes and bug fixes (Tentative) | |
| May 19 | Code freeze for CCCApply 6.5.0 Pilot Release and Non-Credit App v.1.2 | |
| May 1531 | CCCApply 6.5.0 Pilot release Non-Credit Application 1.2 Pilot release | CCCApply 6.5.0 Pilot Non-Credit v.1.2 Pilot |
| June 1528 | CCCApply 6.5.0 Production release Non-Credit Application 1.2 Production release | CCCApply 6.5.0 Prod Non-Credit v.1.2 Prod |
...
| Goal | Success Criteria |
|---|---|
| Ensure Pilot v.1.0 meets minimum viable product requirements | |
| Ensure Pilot v.1.0 data field changes meet existing college download and import process requirements | Using Standard Application Download Client & XML files Using SuperGlue staging process Using SuperGlue SIS import process |
| Identify and document production version implementation requirements & processes | |
| Gather requirements and implement ability to configure separate filter "majors / programs of study" and/or "major categories" for non-credit application | The objectives for college user testing are:
|
| Gather requirements and implement ability to configure separate supplemental questions for non-credit application |
...
Feedback & Support Process
TBD
...
College Participation & Requirements
...
| Note |
|---|
All Changes Are Backwards Compatible - No Actions Required: All the front-end changes deployed in the Non-Credit Application path within CCCApply Standard Application (user interface changes, hidden pages and questions, disabling of web services, etc.) should NOT AFFECT YOUR STANDARD APPLICATION. All Non-Credit Application back-end changes are optional and not mandatory for colleges to implement. Admissions, Financial Aid, and IT staff can rest assured there are no action REQUIRED by colleges that do not wish to implement the Non-Credit Application. |
...
Implementation Setup Steps
...
| Data Field Name | Type | Data Element | Format / Length | Downloadable | Report Center / Admin Rules | Application |
| Non-Credit Status | New data field | <non_credit> | Yes | Yes | CCCApply Standard & Non-Credit | |
| Integrity Flag 81 | New flag | <integrity_fg_81> | boolean, 1 | Yes | Yes | CCCApply Standard & Non-Credit |
| Note |
|---|
Non-Credit Application - Full Data Set in Glue for Apply The new Non-Credit Application data values will be included in this release, passed directly to colleges using the Glue for Apply feature. |
...
Updating Your Download Files
...
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:
...