CCCApply Noncredit Application - UAT Implementation Checklist
Last update: January 2022
Overview
This implementation guide is intended to provide college IT staff and other key stakeholders with a checklist of set up requirements and optional tasks, admin configuration options, and other notes to support a successful CCCApply Noncredit Application implementation for your college in both the CCCApply Pilot and Production environments.
REQUIREMENTS
College must be live on the CCCApply Standard Application (end-to-end implementation)
College must direct users to their custom Noncredit Application URL to access the "residency determination exempt" noncredit application
College must reconfigure their existing "Majors" - currently set up for their Standard Application - in order to use the Noncredit Application (see below)
CONSIDERATIONS
College should be aware that…
the Noncredit Application is a modified version of the Standard Application and uses most of the same admin configuration, data delivery methods, and reports
they will use the same data delivery process for the Noncredit Application as they currently use for the Standard Application
they must configure and import a separate set of Supplemental Questions for the Standard and Noncredit Application if they wish to display supplemental questions in the Noncredit application
there are hidden questions (and pages) in the Noncredit Application
there were changes made to the residency process, the new values added to the "Residency Status" and area calculations for Noncredit Application
a student should only submit a Noncredit Application if they are enrolling exclusively in noncredit courses; otherwise they should submit a Standard application
the "High School Transcript Information" - the self-reported multiple measures questions on the Education page, do NOT appear in the Noncredit Application
the Social Security Number question is no longer collected in the Noncredit Application (as of SSS release v.1.0)
College/Business Operations Tasks
Tasks for College IT & Admissions Staff
The following requirements are provided to help prepare your college to implement the Noncredit Application for student use. The tables are organized in the order they should be completed:
- 1 College/Business Operations Tasks
- 2 Implementation (Set Up) Requirements
- 3 Configuring Downloads for Noncredit Application Data
- 4 Running Reports: Identifying Noncredit Application Data in the Report Center
- 5 Understanding the Noncredit Application User Experience
- 6 Standard Application Implementation Information
- 7 Business Operations Tasks
- 8 Deployment Tasks - Production Environment
Setting Up the Noncredit Application in the Pilot Environment
Before using the Noncredit Application in Production with students, your college must have the CCCApply Standard Application configured in both the Pilot and Production environments. The complete end-to-end implementation of the CCCApply Standard Application includes college configuration within the CCCApply Administrator and a functional data delivery process setup via the CCCApply Download Client or SuperGlue for Apply.
For information and documentation on the complete implementation of the CCCApply Standard application, visit the Implementation Documentation Home page on the CCCApply Public Documentation space.
Getting to the Noncredit Application and Admin Tools
Area | How the Noncredit App should be set up in the Pilot environment for testing | How the Noncredit App should be set up in the Production environment for students |
---|---|---|
Getting to the Noncredit Applications | ||
(Customized for each college MisCode) | Use the PILOT version URL. https://pilot.opencccapply.net/cccapply-welcome?cccMisCode=XXX&nonCredit=true | Colleges must use the PRODUCTION Noncredit URL. This is the URL that should be made available to students (end-users). https://www.opencccapply.net/cccapply-welcome?cccMisCode=XXX&nonCredit=true |
| College authorized admins must use their OpenCCC PILOT Account to test / access their branded Noncredit Application. | College authorized admins must use their OpenCCC PRODUCTION Account to test / access their branded Noncredit Application. |
Getting to the CCCApply Administrator 2.0 | ||
(Customized for each college/district) | Find your PILOT CCCApply Administrator 2.0 URL here | Find your PRODUCTION CCCApply Administrator 2.0 URL here |
| College authorized admins must use their existing CCCApply Administrator 2.0 PILOT user accounts to configure their branded Noncredit Application. To identify your college authorized Administrator user account, please contact your college IT or Admissions Office director. | College authorized admins must use their existing CCCApply Administrator 2.0 PRODUCTION user accounts to configure their branded Noncredit Application. To identify your college authorized Administrator user account, please contact your college IT or Admissions Office director. |
Getting to the CCCApply Report Center | ||
(Customized for each college/district) | Find your CCCApply Report Center PILOT URL here | Find your CCCApply Report Center PRODUCTION URL here |
| College authorized admins must use their existing CCCApply Report Center PILOT user accounts to configure their branded Noncredit Application. To identify your college authorized Report Center user account, please contact your college IT or Admissions Office director (or contact the CCC Tech Center Enabling Services team: crms@ccctechcenter.org ) | College authorized admins must use their existing CCCApply Report Center PRODUCTION user accounts to configure their branded Noncredit Application. To identify your college authorized Report Center user account, please contact your college IT or Admissions Office director (or contact the CCC Tech Center Enabling Services team: crms@ccctechcenter.org ) |
Setting Up Admin Configuration for the Noncredit Application
IMPORTANT
The CCCApply Noncredit Application IS a modified version of the Standard Application. Therefore all admin configuration specific to the Noncredit Application is configured through the CCCApply (Standard) application in the CCCApply Administrator.
Implementation (Set Up) Requirements
*NOTE: Features and functional elements currently part of the Standard and Noncredit applications, may need to change in the future based on testing, use, and legislation. For the initial release (v.1.0) these implementation steps are the necessary requirements for colleges using the Noncredit application. If changes are identified, the college pilot project will determine the need and set the expectation for future enhancements.
MODULE | Areas - Tasks | How it's set up now in the Pilot & Production Standard Applications | How it should be set up for the Pilot Noncredit Application | Is the same setup required for the Noncredit Production application? |
---|---|---|---|---|
TERMS | Ensure that Terms are set up correctly and open for your noncredit application. | Colleges must set up Terms in the CCCApply Administrator for the Standard Application. | The SAME Terms will be used for the Noncredit Application in version 1.0*. | Yes. Terms are set up in BOTH environments by the college. The same Terms will be used for Standard and Noncredit, in the pilot and production environments. |
MAJORS | Ensure that Majors/Programs of Study are set up for your Noncredit Application and that each individual item is tagged correctly with an "Application Type" in the "Majors" module in the Administrator | Colleges must set up "Intended Majors / Programs of Study" in the CCCApply Administrator for the Standard Application. | REQUIRED TASK: In order for colleges to implement the Noncredit Application, they must reconfigure their existing Majors file in the Majors module in the CCCApply Administrator 2.0. For more information, see New "Application Type" Menu Added to the Majors Table in the Administrator for Noncredit Application See the CCCApply Administrator 2.0 User Guide for instructions and guidance. | REQUIRED TASK: In order for colleges to implement the Noncredit Application, they must reconfigure their existing Majors file in the Majors module in the CCCApply Administrator 2.0. For more information, see New "Application Type" Menu Added to the Majors Table in the Administrator for Noncredit Application See the CCCApply Administrator 2.0 User Guide for instructions and guidance. |
| ||||
MAJOR | Major Categories | The "Major Category" filter is ONLY available in the Standard Application. | The Major Category feature is NOT available in the Noncredit Application. | The Major Category feature is NOT available in the Noncredit Application. |
RULES | Rules | Rules are optional. Rules are created and set up by colleges in the CCCApply Administrator. | Rules can be configured for the Noncredit Application in the CCCApply Administrator (in the Pilot and Production environments). See the CCCApply Administrator 2.0 User Guide for instructions and guidance. | Rules can be configured for the Noncredit Application in the CCCApply Administrator (in the Pilot and Production environments). See the CCCApply Administrator 2.0 User Guide for instructions and guidance. |
MESSAGES | Messages | Messages are used with the optional Email Rules configured by colleges in the CCCApply Administrator. | Messages are configured for use in Email Rules for the Noncredit Application in the CCCApply Administrator (in the Pilot and Production environments). See the CCCApply Administrator 2.0 User Guide for instructions and guidance. | Messages can be configured for the Noncredit Application in the CCCApply Administrator (in the Pilot and Production environments). See the CCCApply Administrator 2.0 User Guide for instructions and guidance. |
SUPPLEMENTAL QUESTIONS | Supplemental Questions | Supplemental Questions are optional - the college decides if they want to ask additional questions to their end users. These questions are displayed IF the college uploads a custom-configured XML file in the CCCApply Administrator. Supplemental Questions are available for the Standard, Noncredit, and International Applications. | Supplemental Questions can be displayed in the Noncredit Application through a unique XML file that is configured to display in the Noncredit Application. For more information on implementing supplemental questions in the Noncredit Application, see: New "Application Type" Menu Added to the Supplemental Questions Module in the Administrator See the CCCApply Working with Supplemental Questions User Guide for instructions and guidance. | Supplemental Questions can be displayed in the Noncredit Application through a unique XML file that is configured to display in the Noncredit Application. For more information on implementing supplemental questions in the Noncredit Application, see: New "Application Type" Menu Added to the Supplemental Questions Module in the Administrator See the CCCApply Working with Supplemental Questions User Guide for instructions and guidance. |
RESET | Reset Downloads | The Reset Downloads utility module in the CCCApply Administrator allows colleges to reset individual or multiple downloaded applications to be re-downloaded. Each CCCApply application has a "Reset Downloads" module in the Administrator. | The SAME Reset Downloads module used for the CCCApply Standard Application, will be used for the Noncredit Application in the Pilot Administrator. If a college needs to reset a submitted Noncredit Application application that was previously downloaded through their Standard Application downloads, they will enter the "Noncredit Application Confirmation number" into the Standard "Reset Downloads" module in the CCCApply Administrator. College admin users should NOT add the NC- prefix when resetting Noncredit Applications for download. That would cause them errors. | The SAME Reset Downloads module used for the CCCApply Standard Application, will be used for the Noncredit Application in the Production Administrator. If a college needs to reset a submitted Noncredit Application application that was previously downloaded through their Standard Application downloads, they will enter the "Noncredit Application Confirmation number" into the Standard "Reset Downloads" module in the CCCApply Administrator. College admin users should NOT add the NC- prefix when resetting Noncredit Applications for download. That would cause them errors. |
SPAM FILTER | Spam Filter | The Spam Filter web service was implemented and deployed on the CCCApply Standard post-submission service, which means every Standard Application - which includes every Noncredit Application - is subject to the fraud detection model and prediction service. If a Noncredit Application is suspected of fraud based on the model, it will be CHECKED_FRAUD and suspended in the Spam filter for the college to process. To process spam applications suspended in the spam filter, a college staff user, authorized to access the Administrator, should review the application and confirm whether it is fraud (Confirm Spam) or if it has been suspended in error and needs to be released back to the Download Client for download. | There is no "set up" to implement the Spam Filter web service; however, all colleges must manage their Spam Filter suspension folder (similar to a spam filter for your email account) which resides in the CCCApply Administrator. Click on the "Utilities" module to find your Spam Filter suspension folder interface. For information on how to process an application that is routed to the Spam Filter suspension folder, see the "CCCApply Administrator 2.0 User Guide" or other articles posted here: Administrator 2.0 Implementation Home | |
COLLEGE & | College & District Information | |||
DOCUMENTATION | Documentation: | |||
Configuring Downloads for Noncredit Application Data
# | Areas - Tasks | How it's set up now in the Pilot & Production Standard Applications | How it should be set up for the Pilot Noncredit Application | Is the same setup required for the Noncredit Production application? |
---|---|---|---|---|
1 | Format Definition Download XML The download files used in for the Noncredit Application are the same files used in your Standard application. | The Standard Application Format Definition XML file is used to define the data fields and formats that are to be downloaded. When new fields are added, or existing fields are changed, the latest version of the Download Client Jar file is run to ensure the download file is current (see below). | Since the Noncredit Application is simply a modified version of the Standard Application, the same Pilot environment version of the Format Definition XML file is used to download new or changed fields. To download the new <non_credit> and <integrity_fg_81> fields, run the 6.5.0 version of the Jar file (see below). | Since the Noncredit Application is simply a modified version of the Standard Application, the same Production environment version of the Format Definition XML file is used to download new or changed fields. To download the new <non_credit> and <integrity_fg_81> fields, run the 6.5.0 version of the Jar file (see below). |
2 | Add Optional Noncredit Data Fields to Existing Standard Download Files Add the new Noncredit Application fields to your existing Standard application download files (Format Definition XML) and use the same Job XML file to run the job. (See New & Changed Data Fields below) | Add the new fields to your existing CCCApply Standard Format Definition XML file, run the new Jar file, and use your existing Job XML file to begin downloading the new data fields and changed values. | Add the new fields to your existing CCCApply Standard Format Definition XML file, run the new Jar file, and use your existing Job XML file to begin downloading the new data fields and changed values. | Add the new fields to your existing CCCApply Standard Format Definition XML file, run the new Jar file, and use your existing Job XML file to begin downloading the new data fields and changed values. |
3 | Run the Latest Download Client Jar File After adding the new fields to your Format Definition XML file(s), run the new 6.4.0 or 6.5.0 Download Jar files to begin downloading the new and changed data fields for the Noncredit application. | Update your existing Download Client Jar file < transfer-client.V6.5.jar > | Update your existing Download Client Jar file < transfer-client.V6.5.jar > | The SAME JAR FILE IS UPDATED FOR PRODUCTION Update your existing Download Client Jar file < transfer-client.V6.5.jar > |
The following data fields have been added or changed in the CCCApply 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.5.jar > 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 |
---|---|---|---|---|---|---|---|
Noncredit Status | <non_credit> | New Field | 1 = True 0 = False | Boolean, 1 | Yes | No | Optional; Value set to "True" if applicant applies using the new Noncredit 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 Noncredit 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 Noncredit 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. | |
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 Noncredit 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 Noncredit 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 Noncredit 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 Noncredit 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 Noncredit 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 Noncredit 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 Noncredit 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 Noncredit 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 Noncredit Application workflow this question is hidden; value stored = Null |
Running Reports: Identifying Noncredit Application Data in the Report Center
For more information, see the CCCApply Report Center User Guide.
Areas - Tasks | How it's set up now in the Pilot & Production Standard Applications | How it should be set up for the Pilot Noncredit Application | Is the same setup required for the Noncredit Production application? |
---|---|---|---|
Noncredit Applications will immediately download to the CCCApply Report Center - just like Standard applications. | |||
Noncredit |
Understanding the Noncredit Application User Experience
For more information, see Changes to the User Interface from the Release 6.5.0 Notes Summary documentation.
# | Areas - Tasks | How it's set up now in the Pilot & Production Standard Applications | How it should be set up for the Pilot Noncredit Application | Is the same setup required for the Noncredit Production application? |
---|---|---|---|---|
| All users must have a Pilot OpenCCC Account and must sign in | All users must have an OpenCCC Account and must sign in | Everything is the same for the Production version. | |
| The Account Recovery is a process in the OpenCCC system. https://pilot.openccc.net/cccacct-proxy/recoverAccount? https://www.openccc.net/cccacct-proxy/recoverAccount? NOTE: There are separate recovery processes for Pilot and Production. See the "pilot" environment denoted in the URL above. | The OpenCCC Account Recovery process is the same for all CCCApply applications, including the Noncredit application path in the Standard Application. | The Production OpenCCC Account Recovery process is the same for all CCCApply applications, too. | |
| See Account Recovery above. | The Pilot Password Reset process is in the Account Recovery process | The Production Password Reset process is in the Account Recovery process. | |
| Edit Account is the name of a module within the CCCApply | |||
| Each student has a "My Applications" page for each of the three different CCCApply applications (if applicable to them) that stores all of their current (in-progress) and previously submitted CCCApply applications history. Most students are familiar with their "My Applications" page for their Standard Applications (and possibly their BOG/Promise Grant Applications) - which they see each time they start a new (second) Application to CCCApply. | Note: Although the Noncredit Application path technically has a different URL than the Standard Application - nearly every other aspect of the Noncredit application processes will be the same as the Standard application processes. This is very important. This includes all pre- and post-application processes, such as:
| See NOTE in the adjacent cell. All production Noncredit applications are bundled in with your production Standard Applications. Noncredit will share the same production "My Application" page with Standard Application "My Applications" for Pilot and Production. | |
| Submitted Standard Applications appear in a table on the "My Applications" page - below the "In-Progress Applications" table on the same page. These tables appear when a student submits a Standard Application to one or more CCC colleges. | Submitted Noncredit Applications are bundled in with, and stored in, your Submitted Applications in your Standard My Applications page. Reminder - Pilot environment vs. Production. | Same description, but in the Production environment. | |
| See above row referring to "My Applications". In-Progress Standard Applications appear in a table on the "My Applications" page - above the "Submitted Applications" table on the same page. These tables appear when a student signs in to CCCApply to manage their applications. | In-progress Noncredit Applications are bundled in with, and stored in, your In-Progress Standard Applications in your Standard My Applications page. Reminder - Pilot environment vs. Production. | Same process, but in the Production environment. | |
| Confirmation numbers for all CCCApply applications, including the Standard Application, are assigned to each application that is "Saved" or when the application is submitted. Confirmation numbers will appear in the In-Progress or Submitted Application tables in your "My Applications" page. Confirmation number is a CCCApply data field =<confirmation> and can be downloaded by colleges and used in reports in the Report Center. Colleges can find more information about this data field in the Standard Application Data Dictionary | Confirmation numbers for Noncredit Applications will have a prefix "NC-" added to the beginning of the number. Example: NC-123456 | Same. | |
| A PDF copy of each Standard Application submitted is available to download by the applicant from their Standard Application "My Applications" page. This feature is available for all CCCApply applications (BOG/Promise Grant and International Apps) in the pilot and production environments. | A PDF copy of each Noncredit Application submitted in the pilot environment is available to download by the applicant from their Standard Application "My Applications" page. This feature is available for all CCCApply applications in the pilot and production environments. | A PDF copy of each Noncredit Application submitted in the production environment is available to download by the applicant from their Standard Application "My Applications" page. | |
| First-time applicants - regardless of the application or the environment - must first create an OpenCCC Account before applying to a California Community College. To simplify the student's first-time experience, immediately following Account creation the applicant is auto-directed to the first page of the Application. | Auto-direct works the same way for first-time Noncredit applicants in Pilot. | Auto-direct works the same way for first-time Noncredit applicants in Production. | |
| Existing law requires each student to be classified as a resident or nonresident at a California community college. The CCCApply Standard Application includes a comprehensive algorithm that calculates a preliminary residency determination status upon submission. The residency status <res_status> only exists in the Standard Application. | Per the new changes to existing residency regulations outlined in AB 3101, students enrolling exclusively in noncredit courses are exempt from mandatory residency classification. However, if the applicant ends up taking one or more credit courses, they must adhere to the residency determination process. CCCApply recommends that the college direct the student to submit a Standard Application in order to comply with the law. | ||
Application Workflow | The current Standard Application workflow | The Pilot Noncredit Application workflow | The Production Noncredit App workflow | |
| The enrollment page includes the following questions and validation logic:
| The enrollment page includes the following questions and validation logic:
| The enrollment page includes the following questions and validation logic:
| |
| Questions on the Account Information / Mailing page:
| Questions on the Account Information / Mailing page:
| Questions on the Account Information / Mailing page:
| |
| Questions that appear on the Education page:
High School Transcript Info (Multiple Measures)
Colleges/Universities Attended
| Questions that appear on the Education page:
Colleges/Universities Attended
| Questions that appear on the Education page:
Colleges/Universities Attended
| |
| Questions that appear on the Citizenship & Military Page
Military Status
| None | None | |
| Questions on the Residency Page
| None | None | |
| Questions on the Needs & Interests Page
| Questions on the Needs & Interests Page
| Questions on the Needs & Interests Page
| |
| Questions on the Demographic Information Page:
|