The user acceptance testing (UAT) process and objectives for the CCCApply Noncredit Application Pilot project are listed below.
See Noncredit Application UAT Plan Slide Deck
|
Getting to the Pilot EnvironmentPilot colleges can begin previewing and testing the new Noncredit Application feature after the CCCApply 6.4.0 pilot release on February 19, 2019.
|
Required DocumentationTechnical specifications for the Noncredit Application workflow feature are included in the CCCApply Standard Application Data Dictionary.
Project Docs
Additional Docs
|
See more CCCApply product information in the CCCApply Public Documentation space.
Noncredit Application URLAccessing the Noncredit application workflow path within the Standard Application requires a separate, college-specific URL. This unique, college-specific URL is one of the key characteristics that partitions the noncredit workflow path within the Standard Application, as well as distinguishes the submitted applications that started from the Noncredit URL from those started from the original Standard Application URL. See here for the list of College Noncredit Application URLs. When a user starts and submits a Noncredit Application (using the college-specific URL) the new Noncredit Status flag is set to True, which is appended at the end of the URL. |
Follow the steps below to setup the Noncredit Application workflow feature to conduct user acceptance testing:
|
The following data fields have been added or changed in the CCCApply Noncredit applications. 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.4.jar For more information, please see the CCCApply Download Client User Guide > User Guides New & Changed Data FieldsThe table below provides an overview of the new or changed data fields in CCCApply for the Noncredit Application. For detailed data specifications, see the CCCApply Standard Application Data Dictionary V.2019.1 in the Data Dictionaries space.
Updating Your Existing Download FilesTo download the new Noncredit Application data fields and new values in existing CCCApply download files, you must add the new fields to your CCCApply Standard Application Format Definition XML and update the (transfer-client.jar) file for the Noncredit v.1.0 Pilot release.
Update the Pilot Download Client Jar FileWe recommend adding the new Noncredit Application path data fields and updating your Download Client Transfer file in the Pilot environment whether you plan to implement the Noncredit application path or not. The Pilot DLC jar file should be updated first, then repeat the process for your Production downloads. In your installed Pilot Download Client directory, replace the following files:
Follow the instructions in the Pilot CCCApply Download Client User Guide. Update the Download Client Jar FileTo 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 environments. In your installed Production Download Client directory, replace the following files:
Follow the instructions in the CCCApply Download Client User Guide. |
The new CCCApply Noncredit Application data set values can be passed directly to colleges using the College Adapter for SuperGlue. For more information, please contact CCCTC Enabling Services or Support Services at ccctcstaffsupport@openccc.zendesk.com. |
During the Pilot Project (see pilot schedule above), pilot colleges will meet bi-weekly to provide feedback and discuss pilot objectives with the Pilot committee and CCCApply product manager. Non-critical bugs, change requirements, and change enhancements will be reviewed and prioritized during each meeting. 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 Below is a breakdown of the pilot support and change management process and response times.
Issue Resolution During Pilot Project
BUG Prioritization Levels
Change Request Form Templates
|