Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

The CCCApply Noncredit Application is LIVE in production and available to preview in the CCCApply pilot environment. Click here for links and implementation information


Existing California education code law requires residency determination for every student that submits an application for admission to a California community college. However, the recently passed Assembly Bill 3101 (AB3101) mandates that students seeking to enroll exclusively in career development, college preparation, and other noncredit courses would be exempt from residency classification requirements.

The passage of AB 3101 gave us the latitude we needed to deliver a modified version of CCCApply for our noncredit student population. Lifting the requirement for uniform residency determination for all students allows us to look at other questions and steps that might be omitted at the time of application. Our goal is to find balance in what is asked of the student that is applying for college while still collecting all of the information required for state and federal reporting purposes.

The CCC Chancellor’s Office is driving changes to ensure CCCApply supports students through the community college application and enrollment process, and is targeting development and implementation of the redesigned system in fall of 2019. Activities such as reducing the number of questions in CCCApply and creating a simpler application for noncredit students which began last fall 2018 has been bolstered by the passage of Assembly Bill 3101. The Noncredit Application Workflow path is a project of the CCCApply Redesign Project.

Product Description

The CCCApply Noncredit Application is a streamlined version of the Standard Application, with a unique, college MIS-code branded URL intended explicitly for students enrolling exclusively in noncredit courses. More like a "workflow" than a completely separate application, the Noncredit Application uses the same infrastructure as the Standard Application - but without the residency questions or the residency algorithm.  The residency status field will automatically default to "N" and a new "non_credit" flag will default to "True" for all applicants who enter the Standard Application via the new Noncredit URL. 

Read more:  Noncredit App Path Requirements

Noncredit Application: Key Characteristics

  • Shorter, more streamline version of the Standard Application workflow

  • Unique URL, customized for each college based on MisCode

  • In-Progress and submitted application Confirmation numbers are modified with a prefix: "NC-" (Example: "NC-794033")

  • Colleges have the option to display different Majors/Programs of Study in the Noncredit Application (versus their Standard Application)

  • Colleges have the option to display different Supplemental Questions in the Noncredit Application (versus their Standard Application)

  • Students that apply using the new Noncredit URL, certain data fields and actions will default to the following:

    • New "non_credit" status field = True

    • New "Integrity-flag-81" field is triggered

    • Residency Status field = "N"  (new value)

    • Residency Area status fields = "9"  (new value)

  • Students that need to re-apply for credit courses after submitting the Noncredit application, will be allowed to submit a Standard Application for the same term, same college

  • Students that need to re-apply for credit courses using the Standard Application after submitting the Noncredit application will only have to answer the questions that were hidden in the Noncredit application (this is also true when applying to any term, any college within 2 years of submitting a Noncredit Application). Auto-population functionality is still in place and will function as it does today.

See the full set of requirements for the noncredit user interface here:  CCCApply Noncredit Path Change Requirements  

Noncredit Application: User Interface

The Noncredit path DOES NOT include the following pages and questions:

  • Citizenship & Military Status page

  • Residency page

Colleges can opt to display or hide the entire Needs & Interests page or individual questions, including:

  • Are you Comfortable with English?

  • Financial Assistance

  • Athletic Interest

  • Programs & Services

The Noncredit path WILL include the following pages and questions:

  • Enrollment page

  • Account Information/Mailing - including the Dependency Status for minors

  • Education page

  • Demographic Information

  • Review, Consent, & Submission

Noncredit Application: Admin Configuration & Downloads

The Noncredit path is embedded in the Standard Application, which means that much of the admin configuration, implementation, and downloads functionality is already setup in your Standard Application configuration, such as: 

  • The Noncredit Application uses the same admin configuration and reporting tools as the Standard Application; although some defaults and minor set up tasks will be required. 

    • Uses the same Terms that are setup for the Standard Application

    • Uses the same Rules & Messages modules for the Standard Application

    • Uses the same databases as the Standard Application ("In-Progress" and "Submitted Applications")

    • Uses the same Report Center, reports, views, charts, and dashboards

  • The Noncredit path uses the same DOWNLOADS process and XML files

    • Uses the same Format Definitions XML file for specifying which data fields should be downloaded from the Standard Application Download Server

    • Uses the same Job XML file 

    • Uses the same Download Client that you currently have installed now

    • Uses the same Glue for CCCApply process that you currently have installed now (if applicable)

Differences Between the Standard Application & the Noncredit Application

Although there are very few differences between the Standard Application and the Noncredit Application, colleges that choose to implement the new Noncredit Application will have several required setup tasks, and should be aware of the following defaults and requirements.

Application URL

The Application Gateway to the Noncredit Application has a unique URL for each college based on their college MIScode.


Terms can be configured in the CCCApply Administrator to display differently in each application.  An "Application Type" toggle has been added to the Terms table which allows the college to set for: "Standard"  or  "Noncredit"  or  "Both".

Intended Major / Program of Study

The "Intended Major/Program of Study" field can also display different majors/programs for each application. An "Application Type" toggle has been added to the Majors table in the Administrator which requires the college to set a setting:  "Standard"  or  "Noncredit"  or  "Both".  Each major or program must be configured with one of the available settings. These are set up in the "Majors" module in the Administrator.

Read more about the rules and requirements for Majors in the /wiki/spaces/PD/pages/758546724

REQUIRED:  New "Application Type" Toggle Must Be Set for Noncredit Majors/Programs of Study

If your college is planning to implement the Noncredit Application, you will be required to reconfigure all your Majors - for both applications - in order for them to display to end users.

must identify which application each Major/Program should appear in by setting the new "Application Type" indicator for each line item.  MUST manage their list of majors/programs of study in order for that field to be populated in the Noncredit Application.  that currently appears to end users in the "Intended Majors/Programs of Study" menu on the Enrollment page. Each major or program of study must be configured with an "application Type" setting  that currently appears in your Standard Application, as well as the Noncredit Application. During implementation, a college admin must login to the CCCApply Administrator (both for Pilot and Production environments) and specify whether each individual major / program of study should appear in the "Standard", "Noncredit", or "Both" applications.  This setup task is REQUIRED.  If this task is not managed correctly, NO majors/programs will appear in your Noncredit Application; thus, blocking your students from submitting their application.

Even if you plan to offer the same Majors/Programs of Study in both applications, you must set the Application Type setting to "Both" for each individual major or program. 

Supplemental Questions

Colleges have the option to configure unique supplemental questions for each application (Standard vs. Noncredit). The process for configuring and uploading supplemental questions are documented in the /wiki/spaces/PD/pages/758546724, as well as the Working with Supplemental Questions User Guide.

Post-Submission Algorithms Not Run in Noncredit Application

  • Residency Status Determination (Submission Calculation Service)

    • Does not run at time of submission

    • <res_status> = field defaults to new value = "N"

  • AB540 Eligibility algorithm 

    • Does not run at time of submission

    • <elig_ab540> = defaults flag to Null

  • Ineligible for Admission Status algorithm

    • Does not run at time of submission

    • <adm_ineligible> = defaults flag to Null

  • Financial Aid Eligibility algorithm

    • Does not run at time of submission

    • <fin_aid_ref> = defaults to Null

The other differences between the two paths are primarily to help colleges identify and distinguish the Noncredit path from the Standard Application, such as:

  • A different URL is used to get to the Noncredit Application path

  • A new "Noncredit Status" field was added to help identify Noncredit apps submitted. If the new Noncredit URL is used, the new <non_credit> field is set to "True", otherwise it is "False"

  • The Confirmation number for Noncredit apps that are started and submitted (or saved as In-Progress applications) using the Noncredit URL will have a "NC" prefix added to them

  • A new Integrity Flag 81 was added. When the new <non_credit> field is set to "True", Integrity Flag 81 is triggered which sends an email to the college admissions office with the message, "Applicant applied using the Noncredit URL"

  • There will be blank and/or null values appearing for a lot of existing fields, including the Citizenship, Military, and Residency fields, in your download files and in the Report Center

Project Phases

Development and implementation of the Noncredit Application will roll out in phases.  The first phase, development, has already begun and a soft-launch release to the Pilot environment is scheduled for February 19, 2019 as part of the CCCApply 6.4.0 release. Below is a breakdown of the project plan. 

Phase 1:  Development & Soft Launch

Development of the Noncredit Application path within the Standard Application (MVP requirements) began in September 2018 and the initial version will soft-launch in February 2019. 

Development requirements for the minimum viable product for release (MVP) are here

Phase 2: Pilot Project

Beginning with the soft-launch on February 19, a college pilot of six districts* will test the new noncredit application to work out the bugs, identify issues, and ensure all post-submission data and workflow processes are ready for production release. Pilot colleges will be required to participate in extended user acceptance testing and IT staff must support the effort with full implementation and integration with their SIS systems. Bi-weekly feedback meetings will be recorded and shared with colleges.

For the full Pilot project plan with UAT requirements, please see: Pilot Project Plan: CCCApply Noncredit Application:

Phase 3: Production Release

The production release for the Noncredit Application is tentatively planned for June 15, 2019, which is the production release for the 6.5.0 release.

Project & Development Information

CCCApply Noncredit Application Change Request:  2018-24R: Revise CCCApply to Support Noncredit Students

Noncredit Workflow Path PPT

Noncredit Application Requirements Review

  • No labels