Changes to the User Interface
Impact on the College
Impacts on the User
Required Documentation
Release notes for the CCCApply Release 6.5.0 include additional user interface enhancements and implementation guidelines that support this UAT plan. Background information about the CCCApply Redesign Project and other special implementations released in FY18-19 can be found in the CCCApply Redesign Project Dashboard. Data Dictionaries and User Guides have been updated for this release. |
Changes to the Residency Logic
Impact on the College
Impacts on the User
Required Documentation
The objectives and success criteria for college user testing across the 6.5.0 release are detailed below.
# | UAT Objectives | Success Criteria | College UAT Results |
|---|---|---|---|
Changes to the Data
Impact on the College
Impacts on the User
Required
Adding New Fields to the Download Client
Required Documentation
Required Documentation
The following documentation is required for the CCCApply Release 6.5.0 implementation plan:
CCCApply Standard & Noncredit Application Data Dictionary v.2019.2
CCCApply Administrator 2.0 User Guide
CCCApply Download Client User Guide v.2019.2
Additional Docs
All CCCApply Data Dictionaries
All CCCApply User Guides
Getting to the Pilot Environment
Pilot colleges can begin previewing and testing the CCCApply 6.5.0 pilot release items on May 31, 2019.
Updating Your Download XML Files
In general, in order to download new and changed data fields and values that get deployed in CCCApply applications, you must first add and/or make changes to the fields in your application-specific Format Definition XML file(s) and update the existing (transfer-client.jar) file for current release.
For the 6.5.0 Pilot release, update your Standard Application Format Definition XML file with the data field changes specified in the New & Changed Data Fields table, above.
To ensure your CCCApply download files are always in synch with the latest release version, we recommend that all new and changed data fields be added to your download files (Format Definition XML) and replace/update the Download Client Jar file with each release. This should be done whether you plan to import the new fields to your college SIS system. |
Update Your Pilot Download Client Jar File
After you've updated your Pilot Format Definition XML with new and changed data fields, replace your Pilot Download Client Jar file with the latest version.
In your installed Pilot Download Client directory, replace the following files:
Replace transfer-client.jar (V6.5) with: transfer-client-V5.jar
Follow the instructions in the Pilot CCCApply Download Client User Guide.
Please be sure to backup your files before downloading new ones. |
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:
Replace transfer-client.jar (V6.5.0) with: transfer-client-V4.jar
Follow the instructions in the CCCApply Download Client User Guide.
Pilot Release: Feedback & Support
During a CCCApply pilot release (30 days between pilot release and production release), colleges are encouraged to follow the response processes below to report system issues and bugs (S1 and S2) as well as non-critical bugs, change requests, and other general feedback (S3, S4) using the processes below.
Severity Levels
S1 - Application / service is unavailable.
S2 - Required business process is prevented from being used. No workaround is available
S3 - Less important business process is impacted and/or workaround is available.
S4 - Low impact or cosmetic issue
Level | Issue Type | Description | Operations Priority | Feedback Process |
|---|---|---|---|---|
S1 | Application / service is unavailable. | Pilot college cannot access the Noncredit application in the Pilot environment using their custom URL | 24-48 hr response | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
S1 | Application / service is unavailable. | Pilot college cannot access the Noncredit application due to error message | 24-48 hr response | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
S2 | Required business process is prevented from being used. No workaround is available | Pilot college identifies a critical bug in the Noncredit app user interface or backend systems that prevents implementation or testing | 24 - 72 hr response | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
S3 | Less important business process is impacted and/or workaround is available. | Pilot college identifies a non-critical bug in the Noncredit app user interface or backend that does not prevent implementation or testing | 1 week response | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
S2 | Must Have Requirement Required business process is prevented from being used. No workaround is available | Pilot college identifies a missing IT or business requirement per state, federal or local mandate (example: AB 3101) | 1 week response | Use Change Requirement template Pilot college documents requirement(s) via Change Requirement form template; sends as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda. |
S4 | Nice to Have Request Low impact or cosmetic issue | Pilot college identifies a med/high-priority change enhancement to the MVP application | 2 week response | Use Change Request template Pilot college submits change requirement(s) using Change Request form template; send as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda. |
S4 | Delighter Enhancement Low impact or cosmetic issue | Pilot college identifies an enhancement to the user interface or backend service(s) that includes unauthorized feature development (Out of FY scope) | 2 - 4 week response | Use Change Request template Pilot college submits change request(s) using Change Req form template; send as link or attachment to Pilot Project Manager to be prioritized for committee review. |
Request for Implementation Support | Pilot college requests advice and/or general support for IT implementation, operations, best practices, and/or additional help from Product management, support services, other college pilots, or general colleges - in support of the new project. | 24 - 48 hr response Depending on item; TBD | POST FEEDBACK or QUESTIONS on the CCC Pilot colleges should review all CCCApply community board discussions before posting a new support request or question on the College Support Site: CCCTechnology.info |
Issue Resolution During Pilot
Incidents encountered during Pilot Project testing in the Pilot environment - especially during a pre-production release period - should be reported immediately to the College Support Services team - to be resolved as quickly as possible.
College Support Services via the Staff Support email: staffsupportccctc@openccc.zendesk.com
NOTE: If you report an issue to the Support team by email, please cc: Patty Donohue, CCCApply Product Manager, pdonohue@ccctechcenter.org
|
Change Request Form Templates
High-Priority Change Requirement Form
Change Request Form