...
CCCApply has created a new, optional non-credit workflow feature in the CCCApply Standard Application. Development requirements for the first version of the new feature were designed under the guidance of the CCCApply Redesign Workgroup, the CCCApply Advisory sub-committee for Non-Credit application;
...
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 - 28 | Non-Credit Pilot begins 12-Week Pilot Activities | |
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 9 | Code freeze for CCCApply 6.5.0 Pilot Release and Non-Credit App v.1.2 | |
May 15 - 22 | Non-Credit Pilot officially ends - last meeting | |
May 31 | CCCApply 6.5.0 Pilot release (includes the Non-Credit Application 1.2 Pilot release) | CCCApply 6.5.0 Pilot |
June 28 | CCCApply 6.5.0 Production release (includes the Non-Credit Application 1.2 Production release) | CCCApply 6.5.0 Prod |
...
- City College of San Francisco
- Coastline College
- Foothill College
- North Orange CCD
- Santa Rosa College
- Sierra College
- Cerritos College
...
The user acceptance testing (UAT) plan process and objectives for the CCCApply Non-Credit Application Pilot project are listed below.
- UAT Objectives & Success Criteria
- Required Documentation
- Getting to the Pilot Application
- IT Implementation Steps
- Data Fields & Downloads
- Admin Configuration
- Reports
- Feedback & Support Processes
UAT Objectives & Success Criteria
See Non-Credit UAT Plan Slide Deck
UAT Objective | Success Criteria |
---|---|
IT Implementation Steps & Testing |
|
Data Fields & Downloads Configuration Testing |
|
MVP Admin Configuration (Optional) Testing |
|
Modifying & Running Non-Credit App Reports Testing |
|
Using the Pilot Feedback & Support Process |
|
...
Note |
---|
The Non-Credit Application workflow path feature is an Optional special implementation in the CCCApply Standard Application - 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. |
...
Required Documentation
Technical specifications for the Non-Credit Application feature in the Standard Application are included in the CCCApply Standard Application Data Dictionary.
...
Follow the steps below to setup the Non-Credit Application workflow feature to conduct user acceptance testing:
- Paste your college-custom Non-Credit App URL for the Pilot enviornment into a new Chrome browser window and navigate to the CCCApply sign-in page
- If you have a Pilot OpenCCC test account, click "Sign In". Landing in your My Applications page, click on "Start a New Application"
- If you don't have a Pilot OpenCCC test account, click on "Create an Account" and follow the three page account creation process
- From your My Applications page, click on "Start a New Application".
- Land on the Enrollment page and complete the required fields:
- Select a Term, Education Goal
- Select a Major Category and Major/Program of Study
- Land on the Enrollment page and complete the required fields:
- Complete the required pages in the Non-Credit app workflow
- Complete the Enrollment page
- Complete the Account Information/Mailing page
- Complete the Education page
- Complete the Needs & Interests page (optional)
- Complete the Demographic Information page (optional)
- Complete all remaining required portions of the application and submit the application
- Review your application responses on the Submission page (optional)
- Complete the Consent to Release Information checkboxes (required)
- Complete the Submission requirements (required)
- After submission, note the application's Confirmation number (App_id) and your CCCID.
- Review the confirmation screen and note your confirmation number for the Non-Credit application version you just submitted:
- Note that the Confirmation number begins with a "NC-" preview
- Continue to the Student Satisfaction Survey and complete the survey (optional)
- Continue down the page and review the Special Links & Opportunities for your application
- Click "Finish & Sign-Out" or if MyPath college, click "Finish and continue to MyPath" (confirm)
- Return to the My Applications page and locate your submitted Non-Credit application in the submitted applications Table
- Note the confirmation number begins with a "NC-" prefix
- Sign out of My Applications
- Add new Non-Credit App data fields to existing CCCApply Standard Application Pilot download files
- Add the new data fields to your existing Standard Application Format Definition XML file for the Pilot environment:
- Non-Credit Status = <non_credit>
- Integrity Flag 81 = <integrity_fg_81>
- Note all specified data field changes (new values, formats, logic, etc.) as specified in the Change Log of the CCCApply Standard Application Data Dictionary v.2019.1
- Review data dictionary specification information for these fields
- For help updating your Format Definition file, see the CCCApply Download Client User Guide
- Add the new data fields to your existing Standard Application Format Definition XML file for the Pilot environment:
- Update your existing Download Client Jar File with new version (v.6.4.0 for Pilot release)
- Find and replace the "transfer-client.jar" file in your CCCApply Download Client with the latest version for this release (v.6.4.0).
- NOTE: The 'transfer-client.jar" file has the same as the download client jar file
- Refer to the latest version of the Download Client User Guide v.2019.1
- Refer to the Download Client User Guide for instructions on replacing and running the Jar file for each application in each environment (Pilot and Production).
- Run a test download Job in the Pilot environment.
- Find and replace the "transfer-client.jar" file in your CCCApply Download Client with the latest version for this release (v.6.4.0).
- Optional Admin Configuration Changes for Non-Credit Application
- Navigate to the Pilot CCC Administrator (CAP) and login using existing user account credentials
- Select "CCCApply Administrator" from the Applications menu on the homepage
- From the CCCApply Administrator home page, select "CCCApply" from the Applications menu
- Select your college from the College selection menu bar
- Select "Messages" from the Modules menu bar
- Click on Add new Message and create a custom Message using the new CCCApply Non-Credit Status field <non_credit>
- Save Message
- Select "Rules" from the Modules menu bar
- Click on Add New Rule button and create a custom rule using the new <non_credit> = True field in the code editor
- Reference the new Message created in the Messages module that includes the new non-credit status merge field
- Select the Majors module from the Modules menu bar
- Click on Add New Major button and complete a new test Major, populating the following fields:
- Major Code
- Major Name
- Major Start Date
- Major End Date (or select No End Date)
- Major Category = create new category called "Non-Credit Programs" and enable the tag for this new Major
- Save New Major
- From the Majors Summary Table, select a test major row and click "Edit Major"
- In the Major Category field, add "Non-Credit Programs" for this test majorymajor
- Repeat the process for 1-3 addition test Majors
- Click on Add New Major button and complete a new test Major, populating the following fields:
- Repeat steps 1 - 4 - start a new Non-Credit application and navigate to the Enrollment page
- Complete the Term field
- Select an Education Goal
- In the Major Category menu, confirm that "Non-Credit Programs" is a category in the list, and select that category
- In the Intended Major/Program of Student field menu, confirm that only the majors tagged with the Non-Credit Program tag are displaying in the Major Category filter/menu
- Select one of the majors tagged as a Non-Credit Programs
- Ensure the new Non-Credit Application data fields are appearing as reportable fields in the CCC Report Center
- Navigate to the CCC Report Center and login with your existing Pilot user account
- Navigate to "Create New Ad Hoc View" from the main menu on the homepage
- running reports Status Flag is rnning reports
- Repeat the process for the Production environment.
...
New & Changed Data Field Information
...
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 |
Residency Status | ||||||
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 Existing Download Files
...
- Replace transfer-client.jar (V6.4) with: transfer-client-V3V4.jar
Follow the instructions in the Pilot CCCApply Download Client User Guide.
...
Update the 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:
...
Below is a breakdown of the pilot support and change management process and response times.
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
Severity Level | Issue Type | Description | Resolution Operations Priority | Feedback Process |
---|---|---|---|---|
High - S1 | Critical Issue | Pilot college cannot access the Non-Credit application in the Pilot environment using their custom URL | 24-48 hr response Hot Fix resolution TBD | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
High - S1 | Critical Issue | Pilot college cannot access the Non-Credit application due to error message | 24-48 hr response Hot Fix resolution TBD | Email details to College Support Services: staffsupportccctc@openccc.zendesk.com |
High - S2 | Bug: Critical | Pilot college identifies a critical bug in the Non-Credit app user interface or backend systems that prevents implementation or testing | 24 - 72 hr response Set priority level TBD | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
Med- S2 | Bug: Non-critical | Pilot college identifies a non-critical bug in the Non-Credit app user interface or backend that does not prevent implementation or testing | 1 week response Set priority level TBD | Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com |
Med - S4 | Must Have Requirement | Pilot college identifies a missing IT or business requirement per state, federal or local mandate (example: AB 3101) | 1 week response Set priority TBD | 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. |
Med - S5 | Nice to Have RequirementRequest | Pilot college identifies a med/high-priority change enhancement to the MVP application | 2 week response Set priority TBD | 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. |
Low - S5 | Delighter Enhancement | 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. |
High Varies | 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 | Pilot college should review existing community discussions for self-serve support, or post new question or topic in any CCCApply or System Alerts category on the CCCTechnology.info support site: CCCTechnology.info |
...
- Feedback will be categorized as bugs, MVP requirements, or change enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as release blockers.
- Pilot colleges should include the following information in the support request email:
- Identification of issue
- Reporting: User feedback should be noted in the result section. The following criteria should be followed and documented:
- Any identified bugs with severity and priority
- Enhancement requests with priority identified
...