| Request No. | 2019-13 |
|---|---|
| Date of Request | 3.15.19 |
| Requester | Omid Pourjanzani, Vice Chancellor, CCCCO |
| Application(s) | Standard |
| Section / Page | Needs & Interests Page |
| Steering Hearing Date | Approved |
| Proposed Change to Download File | Backwards compatibility only |
| Proposed Change to Residency Logic | N/A |
Problem / Issue
As part of the response to comply with AB 3101, the CCCApply Redesign Workgroup has determined that the Needs & Interests page should be removed from the Application workflow by default because - though the questions are valuable to the college and the system - the questions are not required to be asked at the time of application.
Proposed Solution
Remove the Needs & Interests page from the Standard Application workflow for all colleges by default, but allow them to opt-in (continue to display the page) upon written request. Do not implement the ability for admin configuration for "Show/Hide" in the Administrator (in the short-term) until the form builder platform - which is on the roadmap for early FY2019-2020 - is designed and we better understand how admin configuration will work for that backend platform.
Add a spike story to understand if we offer colleges two short-term options:
- Remove the full page of Needs questions from the Application by default for all colleges
- Remove the full page of Needs questions from the Application and display the full page upon request
- Remove the full page of Needs questions from the Application and display just the Programs & Services section upon request
- Remove the full page of Needs questions from the Application and allow the colleges to display individual questions upon request.*
- Remove the full page of Needs questions from the Application and implement the ability for colleges to control display of individual questions through some mechanism implemented in the Administrator
- Implement the new backend, form builder platform for the purpose of giving colleges full admin control over all individual questions/fields in the application (admin config controls would be implemented based on the backend form builder platform architectural design).
Several options were discussed for implementing this change, including waiting for the next phase of the Redesign project which calls for the implementation of a new, backend form builder platform, which is on the roadmap for FY2020. Unfortunately, waiting for the backend redesign is not an option and the Chancellor's Office is calling for an immediate response/solution.
Dependencies, Risks and/or Reporting Requirements?
Question | Yes | No | Which data field(s)? | What/How? |
|---|---|---|---|---|
| Would this change affect an existing question or data field on the Standard Application? | ||||
| Would this change affect an existing question or data field on the International Application? | ||||
| Would this change affect an existing question or data field on the Promise Grant Application? | ||||
| Would Account (OpenCCC) data be affected by this change? | ||||
| Does the question or data field align to an MIS reporting requirement now? | ||||
Does this change affect any other state or federal regulations or requirements? | ||||
| Would this change affect existing residency logic? | ||||
| Would any other data fields be affected by this change? | ||||
| Would students users be affected by this change? | ||||
| Would colleges be affected by this change? | ||||
| Would the Download Client be affected by this change? | ||||
| What other tech center web services will be affected by this change? | i.e., Glue staging table? Multiple Measur | |||
| Other dependencies? | ||||
| Other implementation considerations? |
Supporting Documentation
| Description | File Type | URL | Notes |
|---|---|---|---|