Page Comparison

...

The passage of AB 3101 gave us the latitude we needed to deliver a modified version of CCCApply for our non-credit 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 Non-Credit 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 confirmationconfiguration, such as: 

• The Non-Credit path uses the same reporting and admin configuration as the Standard Application:
  • Uses the same Terms that are setup for the Standard Application
  • Uses the same Majors and Major Categories that are setup for the Standard Application
  • Uses the same Supplemental Questions currently 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 Non-Credit 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 Non-Credit Application

There Although there are very few differences between these two applications because, for the most part, the Non-Credit application (path) IS THE STANDARD APPLICATION without residency questions and without the residency algorithm running (Submission Calculation Service) to determine calculate the "preliminary residency -status determination (NO submission calculation service; NO residency determination).

The other differences are primarily implemented to help colleges identify the Non-Credit Applications from the Standard Applications; such as:

...

determination", there are some differences that should be noted and have been documented in the Standard Application Data Dictionary. 

Post-Submission Algorithms Not Run in Non-Credit App

• 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 Non-Credit path from the Standard Application, such as:

• A different URL is used to get to the Application Non-Credit Application path
• A new "Non-Credit Status" field was added to help identify Non-Credit apps submitted. If the new Non-Credit URL is used, the new <non_credit> field is set to "True", otherwise it is "False"
• The Confirmation number for non-credit applications for Non-Credit apps that are started and submitted (or saved as In-Progress applications) using the Non-Credit 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 Non-Credit 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

...

Beginning with the soft-launch on February 19, a college pilot of six districts* will test the new non-credit 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.

*TBD. Depending on level of response by colleges

...

to participate, this number

...

may change.

Pilot Updates

Bugs and other issues will be prioritized for fix throughout the 12-week pilot project. A change deadline schedule is below (subject to change):    

...

Non-Credit Application Project Roadmap

...