Objective
Executive summary
highlights the key
Objectives
Executive summary
highlights the key points, dates and deliverables.
Info |
---|
Designed in part to address the requirements called out key legislation passed in Assembly Bill 3101 - the new CCCApply " Non-Credit Application " path is a streamlined , "residency-free", version of the Standard Application, free of residency questions, with a unique, college MIS-code branded URL explicitly for students enrolling exclusively to support students planning to enroll exclusively in non-credit courses. More like a "workflow" than a completely separate application, the non-credit application uses the same infrastructure as the Standard Application - but without the questions, logic, and services (residency submission calculation service) of the "for credit" application.
|
Communication Plan Goals & Tasks
...
path piggy-backs on the existing user interface and back-end infrastructure of the Standard Application. |
Q3 Communication Plan Goals & Tasks
Goal | Timeline | Email Distribution | Support Site Post | Metric | Notes | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
6.4.0 Pilot Release | 2/19/19 | Feb 197 Feb 14 | Feb 9 Feb 8Successful pilot site deployment18 | Release Notes - Email distribution |
| Production Release | 3/15/19 | Mar 15 | ||||||
March 4
| 2/19/19 | Feb 7 Feb 14 | Feb 9 Feb 18 | Release Notes & Pilot Project Outline | ||||||||||
6.4.0 Production Release | 3/15/19 | Feb 7 - 1st | Feb 9 - 1st Feb 28 - 2nd Mar 11 - 3rd | Successful production deployment | See Release 6.4.0 Summary Notes | |||||||||
Communication Calendar | Jan 13 | Jan 13 | Feb 8 - Mar 15 | Publish calendar of comm events by Feb 8 |
| |||||||||
Product Announcement | Feb 8 | Feb | Release dates confirmed; Pilot release in-progress, Prod dates confirmed | Emphasis on the Non-Credit Application Workflow as part of the overall 6.4.0 Release scope | ||||||||||
Product Description > Components | Feb 8 | Feb 8 | Feb 8 | Release plan confirmed |
| |||||||||
Product Demo (Pre-Pilot / Test for PMs) | Jan 17 | TBD | Release 6.4.0 live in Test environment |
Internal demo held Jan 17 - all prod & project mgrs; ES, support, leadership | ||||||||||
Documentation Breakdown | ||||||||||||||
| Feb 8 | February 8 | Publish updated DED in Public Docs space | /wiki/spaces/OPENAPPLY/pages/826408986 | ||||||||||
| Feb 8 | February 8 | Publish updated DED in Public Docs space |
| ||||||||||
| Feb 8 | February 8 | Publish updated DED in Public Docs space |
| ||||||||||
| January 17 | Feb 8 |
| |||||||||||
| February 19 | |||||||||||||
Internal Implementation Plan ES | February 8 | February 8 | Ensure ES updates all college on boarding installation/implementation docs | |||||||||||
UAT & Pre-Release Testing | February 8 | February 8 | February 19 | Status | | colour | YellowNon-Credit UAT for Pilot is published
| |||||||
External PILOT Implementation Plan | February 8 | February 8 | February 19 | See above |
| |||||||||
User & Implementation Training | February 8 | February 8 | February 19 |
| ||||||||||
Product Marketing Materials |
| |||||||||||||
Jan 13 | Feb 14 | February 19 | FAQ page is published in Public Docs space |
| ||||||||||
| Jan 13 | Feb 14 | February 19 | DONE - Non-Credit Path - UAT Pilot Slides |
| |||||||||
| Jan 20 | Feb 14 | February 19 | NEED |
| |||||||||
| Feb 14 | February 19 | NEED |
|
...
The driver behind the CCCApply "Non-Credit" Application is AB3101 - which grants residency exemption for exclusively non-credit students
The application workflow was developed to address the legislation introduced in AB3101 calling for a residency-determination exemption for students who are enrolling exclusively in non-credit courses.
To comply with AB3101, this path does not include pages, questions, field logic calculations that determines residency status, including the residency submission calculation service, and will only display a set of questions that are required by the federal government, state law, or that are otherwise necessary to uniquely identify the student, during the application process.- The CCCApply Standard Application is used for Credit and Non-Credit applicants
The CCCApply Standard Application is used for all students: Credit and Non-Credit - The Non-Credit Application is really just a "workflow variation" of the Standard Application
The "Non-Credit Application" is really a workflow variation of the Standard Application - for all intents and purposes, this IS a custom version of Standard Application - residency free version - does NOT determine the residency status of the applicant. - NO custom administrative configuration for the Non-Credit Application - Not a separate application - It is a special workflow within the Standard Application
This means that the "Non-Credit Application" uses the same/cannot have different: Terms, Majors, Rules, Supplemental Questions - or any other admin configurable components - DIFFERENT URL for the Non-Credit Application (NC workflow is within the Standard Application BUTit has a unique URL to trigger the Non-Credit workflow)
The "Non-Credit Application" workflow has a unique URL - in order to distinguish this variation from the Standard "for Credit" application.
The new URL template is: http://<college_domain>.<environment>.openccc.net/apply-non-credit
Example: Bakersfield College: http://bakersfieldcollege.ci.openccc.net/apply-non-credit
Resources
External | Resource |
---|---|
CCCApply Noncredit Application Non-Credit Workflow Path Application - Change Request Breakdown PPT (PPT) 2018-24R: Revise CCCApply to Support Non-credit Students & AB3101 |
(Confluence Doc) |
Non-Credit Workflow Path Application - Change Request Breakdown PPT
2018-24R: Revise CCCApply to Support Non-credit Students & AB3101All Audiences | Resources |
LEGAL | AB3101 LEGISLATION |
Messaging & Positioning
...
Product description
The CCCApply Non-Credit Application is a streamlined, residency-determination-free version of the Standard Application, with a unique, college MIS-code branded URL intended explicitly for students enrolling exclusively in non-credit courses. More like a "workflow" than a completely separate application, the non-credit 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 Non-Credit URL.
Short positioning statement
The new CCCApply Non-Credit Application is a "workflow" variation of the Standard Application without residency questions or logic
Short positioning statement
Detailed positioning statement
...
, logic, collecting just the data required by state, federal and local laws and regulations.
Important Things Colleges Should Know:
- The Non-Credit Application IS the Standard Application; it's basically one and the same EXCEPT:
- The NC application has a separate, unique URL (front-door) which is the main identifier/indicator that the application is not a "standard" Standard Application and does NOT include residency questions, pages or logic
- The NC application does not go through the Submission Calculation Service (residency logic) and does not deliver a <res_status> residency status - this will be a blank or Null value in the download file
- The NC application does not include the Citizenship/Military page or the Residency page - all these fields will either be blank or Null in the download files and in the Report Center
- The NC application does not
- The Non-Credit Application IS the Standard Application; it's basically the same application including:
- Uses the same admin configuration setup in the CCCApply application in the Administrator that the Standard Application uses, including Terms, Majors, Rules, Supplemental Questions, Reset Downloads, etc.
- Admin configuration for the Non-Credit Application is the same as the Standard Application
- There is no separate admin confirmation for the NC Application -
- The NC Application is the same as the Standard Application in many ways:
- Same UI look & feel
- Same college branding
- No separate implementation/on-boarding process
- Same Admin, Report Center, Download Client, Download XML files
- This means - there are no unique Terms, Majors, Rules, SQs, etc. for the Non-Credit Application
- Uses the same reporting tool, CCC Report Center, and the same Public report templates created for the Standard (Submitted Applications)
- Colleges will login to the Report Center and can run reports on Non-Credit Application using their existing user accounts for the Report Center
- Colleges can run reports on NC applications using the same Views, Reports, and data fields as the Standard (Submitted) Applications folders
- A distinguishing factor is the Confirmation or App ID numbers
- Uses the same Download Client for the Standard Application
- Uses the same Format Definition XML
- Uses the same Job XML file
- Based on the same set of data fields used in the Standard Application
- The only different is that SOME of the data fields will not deliver values because those pages/questions are hidden in the NC application
- Uses the same data field sets as specified in the CCCApply Standard Application Data Dictionary
- Uses the same admin configuration setup in the CCCApply application in the Administrator that the Standard Application uses, including Terms, Majors, Rules, Supplemental Questions, Reset Downloads, etc.
- The NC Application uses the same
- NC Application goes through all the same post-submission web services and processes that the Standard App does EXCEPT THE RESIDENCY Submission Calculation Service
- Does use: Spam Filter
- Does use: CDE, CCGI, other post-submission services
- Does use:
- Colleges can identify NC applications from Standard Applications in the following ways:
- Confirmation Numbers for NC submitted applications begin with "NC-" - otherwise everything else is the sameApp ID #: Same distinction exists for App IDs, which begin with "NC-"
- Confirmation Numbers for NC submitted applications begin with "NC-" - otherwise everything else is the sameApp ID #: Same distinction exists for App IDs, which begin with "NC-"
...
- - otherwise everything else is the same
- - otherwise everything else is the same
...
Timeline
See Release 6.4.0 Summary Notes
...
Program | Quarter/Year | Owner | Dependencies | Notes |
---|
Budget
Total:
Quarter/Year | Program | Budget Allocation | Details | |
---|---|---|---|---|
Risks
Risks | Risk impact | Notes | ||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
FAQ: Issues & Key Points
# | Description / Issue | Note | Response / Resolution / Mitigation |
---|---|---|---|
Identifying Non-Credit students | |||
Removal of Residency Questions | |||
Removal of Residency Status Determination | |||
Removal of AB540 Eligibility | |||
Removal of Financial Aid Eligibility | |||
Removal of Admission Ineligibility | |||
Removal of Citizenship & Military Page | |||
Removal of Residency Page | |||
Removal of Athletic Interest Question(s) | |||
Removal of Other Needs & Interests Questions | |||
Logic to Allow Student to Re-Apply for Same Term, Same College for Credit Courses | |||
New URL and Non-Credit Flags | |||
Admin Configuration - Shared Data | |||
Reporting - Shared Reports | |||
Downloads - Shared Download Files |
Story/Need
As a "non-credit" student, identified as such by a college or high school, I need a user-friendly process within CCCApply that is free from residency questions and other unnecessary questions, and exempts me from the CA residency determination status/process (per AB3101). I should only have to answer questions required by state or federal regulations for someone enrolling exclusively in non-credit courses at the time of application. If my college credit status should change, I need to re-apply using CCCApply Standard workflow and will have to answer all residency questions that were hidden/exempt during the non-credit process.
...
- Has a unique, distinct URL (college-specific) - which can be used to quickly & easily identify/distinguish that the applicant completed the residency-exempt workflow after the application.
- Has a unique Confirmation number/App_Id - which can be used to quickly & easily identify that the application was completed from the Non-Credit path (number should start with "NC")
- Only displays a sub-set of existing Standard app pages & questions (detailed below) - there should be no change to the pages or questions themselves. The purpose of this requirement is to hide questions that are not required at the time of application.
- Exempt from Residency Determination process - this means that Non-Credit applications should bypass the residency algorithm and a default value should be added to the residency status field.
- Bypass the Submission Calculation Service
- Add new value to Residency Status field <res_status> = "0" zero = No status/Residency Exempt.
- Add and trigger a new integrity flag (81) to identify non-credit / residency exempt statusAdd and trigger a second new integrity flag (82) to alert Admissions about a transitioning student from non-credit back to Credit status, and a change to the Res Status Change field.) to identify non-credit / residency exempt status
- Add logic to only display specific, non-credit values in the Major Category menu so that the college can control the programs/majors that appear in the NC path. (This may be out of scope for the first iteration, but this is important to include in planning).
...
Questions & Issues to be Explored by Non-Credit Pilot Colleges
What else is needed in this critical components are missing from this application?
Will Non-Credit programs be satisfied with the functionality in this version of the application?
How can we improve the Majors and Categories fields in this version of the application?
Is the Residency Status Change field needed? Why?
...