...
The objectives for the pilot project are designed to ensure that the new Non-Credit workflow feature path meets the minimum viable feature functionality and implementation data collection requirements to support colleges comply with changes to the state residency requirements for non-credit students .Additional pilot as passed in AB 3101
- Ensure the initial design meets MVP (minimum viable product) requirements for use with students
- Ensure the code is free of bugs, issues and errors
- Ensure the pre- and post-application workflow meets the needs of non-credit programs
- Identify "must have" features required to meet MVP acceptable standards for majority of non-credit programs
- Review requirements for collecting "Intended Major/Program of Study" question data to meet the needs of most non-credit programs?
- Do the majority of non-credit programs require Supplemental Questions? What types of questions would the majority of non-credit programs ask?
- What other enhancements are required for the MVP implementation?
Participating pilot colleges objectives:
- Approved pilot colleges will commit two staff representatives to participate in the full 12-week project (One admissions office and one IT staff participants) and complete minimum UAT activities
- Participants should contribute to meeting project goals, objectives, and timelines in order to meet proposed success criteria
- Participants will attend scheduled meetings and provide feedback on development and implementation requirements and processes to ensure compliance with AB 3101
- Pilot project management will document and share college feedback and track progress of overarching goal to meet production phase timeline
...
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 |
...
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 workflow feature 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>
- Review all data field changes (new values, formats, logic, etc.) shown in the New & Changed Data Fields Table below.
Note: All changes are also detailed 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 major
- 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
- Repeat the process for the Production environment.
...
Changes to the CCCApply Download Client
...
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.jar v.6.4.0 > For more information, please see the CCCApply Download Client User Guide > User Guides
New & Changed Data Fields
The table below provides an overview of the new or changed data fields in CCCApply Standard, and "Glue for Apply".
See these data specification changes in the CCCApply Standard Application Data Dictionary V.2019.1 in the Data Dictionaries space.
Description | Data Element | Type | Value / Response Options | Format / Length | Allows Null | Required | Notes |
---|---|---|---|---|---|---|---|
Non-Credit Status | <non_credit> | New Field | 1 = True 0 = False | Boolean, 1 | Yes | No | Optional; Value set to "True" if applicant applies using the new Non-Credit Application URL; otherwise it is "False" |
Confirmation Number | <confirmation> | Changed Value | IF non_credit=True then | String | No | System | IF an application is submitted using the Non-Credit URL then the value for <confirmation> = "NC-" |
Integrity Flag 81 | <integrity_fg_81> | New Field | 1 = True Null | Boolean, 1 | Yes | No | Flag triggered if applicant applies with the new Non-Credit Application URL; otherwise it is blank. NOTE - this is consistent with how we have all the other integrity flags structured. |
Residency Status | <res_status> | New Value | New NC default value = N 1 = resident | bpchar, 1 | No | Residency status is calculated at submission for Standard Application only. For the new Non-Credit Application path (in the Standard Application) if applicant applies using the new Non-Credit URL then: <non_credit> status is set =True and <res_status> status is set ="N" | |
Residency Area A | <res_area_a> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
Residency Area B | <res_area_b> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
Residency Area C | <res_area_c> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
Residency Area D | <res_area_d> | New Value | New NC default value = 9 | Boolean, 1 | No | Residency area status defaults to "9" when (non_credit =True) | |
Declared Residency Outside California for Taxes | <ca_outside_tax> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | IF the question is displayed:
IF question is hidden:
NOTE: IF hidden, such as in the Non-Credit application, then default to NULL For a standard application, it will default to False, unless the user checks the checkbox. |
Declared Residency at a College Outside California | <ca_outside_college> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | Same as Above. |
Registered to Vote Outside California | <ca_outside_voted> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | Same as Above. |
Lawsuit Filed Outside California | <ca_outside_lawsuit> | Default values = False / Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | No | Same as Above. |
Public School Employee | <ca_school_employee> | Default value = Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | Required response If appears onscreen | |
State College Employee | <ca_college_employee> | Default value = Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | Required response If appears onscreen | |
Seasonal Agricultural Worker | <ca_seasonal_ag> | Default value = Null | Values = True / False / Null 1 = True 0 = False Null | Boolean, 1 | Yes | Required response If appears onscreen | |
Citizenship Status | <citizenship> | New Value | Default to value = X when (non_credit = True) | character(1) | No | Required to have non-null value in DB. | In the new Non-Credit Application workflow, the Citizenship status question is hidden; value stored = "X" |
Military Status | <military_status> | New Value | New NC default value = X Default to value = X when (non_credit = True) | character(1) | No | Required to have non-null value in DB. | In the new Non-Credit Application workflow, the Military status question is hidden; value stored = "X" |
Comfortable with English | comfortable_english | Allow Null | NC default value = null | Boolean, 1 | Yes | No | In the new Non-Credit Application workflow this question is hidden; value stored = Null |
Financial Assistance | financial_assistance | Allow Null | NC default value = null | Boolean, 1 | Yes | No | In the new Non-Credit Application workflow this question is hidden; value stored = Null |
TANF-SSI-GA | tanf_ssi_ga | Allow Null | NC default value = null | Boolean, 1 | Yes | No | In the new Non-Credit Application workflow this question is hidden; value stored = Null |
Athletic Interest: Intramural | athletic_intramural | Allow Null | NC default value = null | Boolean, 1 | Yes | Required response If appears onscreen | In the new Non-Credit Application workflow this question is hidden; value stored = Null |
Athletic Interest: Intercollegiate | athletic_intercollegiate | Allow Null | NC default value = null | Boolean, 1 | Yes | Required response If appears onscreen | In the new Non-Credit Application workflow this question is hidden; value stored = Null |
Athletic Interest: No | athletic_not_interested | Allow Null | NC default value = null | Boolean, 1 | Yes | Required response If appears onscreen | In the new Non-Credit Application workflow this question is hidden; value stored = Null |
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
...
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:
...