...
Goals for the CCCApply Non-Credit Pilot Project are listed below with proposed success criteria.
| Goal | Success Criteria |
|---|---|
Ensure MVP product complies with residency-exempt requirements in AB 3101 Ensure the design and |
development of the Non-Credit workflow path feature & functionality meets minimum viable product requirements for use with non-credit students as mandated in AB 3101 |
|
|
Using Standard Application Download Client & XML files
Using SuperGlue staging process
Using SuperGlue SIS import process
| |
Ensure IT implementation is simple and fully compatible with existing Standard Application implementation Ensure IT implementation of the new Non-Credit workflow path feature & functionality includes minimal risks and requires minimal reporting and admin configuration changes, and compatible data downloads changes to the CCCApply Standard Application IT setup (including pre- and post-application processes and web services) | Using Standard Application Download Client & XML files Using SuperGlue staging process Using SuperGlue SIS import process Standard Application Download Client and Format Definition XML file, college download and import process requirements implementation (admin configuration, reporting, application data fields (formats, values, validation logic) are compatible with all pre-existing download and export processes for the Standard Application process requirements |
| Develop & implement bEnsure IT & business operational implementation processes have been identified and documented for the Non-Credit Application workflow path all new Non-Credit Application data fields, as well as all changes to existing Standard Application data fields (formats, values, validation logic) are compatible with all pre-existing download and export processes for the Standard Application process requirements | Using Standard Application Download Client & XML files Using SuperGlue staging process Using SuperGlue SIS import process Standard Application Download Client and Format Definition XML file, college download and import process requirements |
Identify (generic) best practices for support and implementation of the new Non-Credit feature Identify, test, and document best practices for support and/or implementation of the Non-Credit workflow feature functionality in (general) college admissions non-credit programs. | |
Identify and document production version implementation requirements & processes | |
| Gather requirements and implement ability to 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
...
| 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:
...