Purpose
Enhance the functional interconnectivity between the CCCApply, the CC Promise Grant application and Project Glue, which automates the delivery of student data with colleges' student information systems (in support of AB-19).
| Table of Contents | ||
|---|---|---|
|
Purpose
Enhance the functional interconnectivity between the CCCApply, the CC Promise Grant application and Project Glue, which automates the delivery of student data with colleges' student information systems (in support of AB-19).
Functionality is being built to allow for user-triggered electronic delivery of the student information required for the California College Promise (which is currently collected by the CC Promise Grant Application (BOG) directly to the college SIS via Project Glue functionality.
Development Goal
The goal of this project is to facilitate the process of pre-filling and auto-populating new Promise Grant applications with as much pre-existing student data as possible from the applicant's previously submitted application within the last 12-24 months in order to streamline the process and enhance the student experience applying for the Promise Grant.
In other words - when a student starts a new Promise Grant application for 2018-2019, the system will first look to see if the student has previously submitted an application within the past 2 years and if so, auto-populate as many fields as possible so as to simplify and shorten the process for the student.
Before we auto-populate previously existing data, we must get the student's consent ("Yes, I would like my previously submitted Promise Grant application data auto-populated into my 2018-2019 application."
Finally, we will facilitate development effort to integrate this data with the Project Glue infrastructure to satisfy the requirements for the California College Promise Grant.
Definition:
- CC Promise Grant is now the new and official name associated to the previously known name of Bog Fee Waiver (BOGFW).
Scope:
- CA Promise Grant - Auto-population of applicable data from student’s previously submitted CC Promise Grant application (within the past 24 months) into the new CC Promise Grant application student is attempting to fill out.
- CCCApply Application - Auto-population into the CC Promise Grant from the most recently submitted CCCApply application (within the past 24 months), leveraging any data fields that are applicable/relevant.
| Note |
|---|
This Requirements section is a working section to define page and section level details for the following. This macro will be removed when the requirements are final and approved by the Product Owner. |
Requirements
1. Opt-In Disclaimer
User Stories:
Seeing Opt In/Opt-Out:
...
for the California College Promise (which is currently collected by the CC Promise Grant Application (BOG) directly to the college SIS via Project Glue functionality.
Development Goals
The goal of this project is to facilitate the process of pre-filling and auto-populating new Promise Grant applications with as much pre-existing student data as possible from the applicant's previously submitted application within the last 12-24 months in order to streamline the process and enhance the student experience applying for the Promise Grant.
- When a student starts a new Promise Grant application for 2018-2019, the system will first look to see if the student has previously submitted an application within the past 2 years and if so, auto-populate as many fields as possible so as to simplify and shorten the process for the student.
- Before we auto-populate previously existing data, we must get the student's consent ("Yes, I would like my previously submitted Promise Grant application data auto-populated into my 2018-2019 application."
- Finally, we will facilitate development effort to integrate this data with the Project Glue infrastructure to satisfy the requirements for the California College Promise Grant.
Definition:
- CC Promise Grant is now the new and official name associated to the previously known name of Bog Fee Waiver (BOGFW).
Scope:
- CA Promise Grant - Auto-population of applicable data from student’s previously submitted CC Promise Grant application (within the past 24 months) into the new CC Promise Grant application student is attempting to fill out.
- CCCApply Application - Auto-population into the CC Promise Grant from the most recently submitted CCCApply application (within the past 24 months), leveraging any data fields that are applicable/relevant.
...
Requirements
1. Opt-In Disclaimer
User Stories:
Seeing Opt In/Opt-Out:
- As a student who has never submitted a CC Promise Grant application, I should not see the option for opt-in/opt-out auto-population because the auto-population functionality does not apply to me.
- As a student who has never submitted a CCCApply application, I should not see the option for opt-in/opt-out auto-population because the auto-population functionality does not apply to me.
| Info | ||
|---|---|---|
| ||
The system should will look for and auto-populate whatever data is available. If only an Apply app is found, display that information. If only a BOG app is found, display that information. Then make the The Yes/No opt-in question as generic as possible - basically "Do you want us to pre-populate any/all data found within the last 24 months?"is generic and refers to whatever data has been previously submitted within the past 24 months. The Yes/No question is set to "yes" by default. |
Selecting Opt In/Opt-Out:
- As a student who is submitting a new CC Promise Grant application and who has submitted either an Apply and/or CC Promise Grant application within the past 2 years, I need the ability to opt-in to the auto-population functionality so that I can navigate more efficiently through the application.
- As a student who is submitting a new CC Promise Grant application and who has submitted either an Apply and/or CC Promise Grant application within the past 2 years, I need the ability to opt-out of using the auto-populate functionality if I don't want the system to populate certain data on my behalf so that I am forced to enter in the data on the application.
...
Below is a mockup for how the CC Promise Grant Opt-In Disclaimer should look and read text wise if a CCC Promise Grant and/or CCCApplication was submitted in the past 24 months. Patty - please review this mockup below and advise of any changes you would like to make.in the past 24 months.
Opt-In Requirements
...
| Note |
|---|
This is a working section to define page and section level details for the following:
|
CA Promise Grant/BOGFW
The following table shows each tab/page in the CA Promise Grant, along with what fields need to have auto-population logic associated and what fields do not. Business rules are also listed, if they apply.
Page | Field Name/Label | Field Name/Label Functionality Requirements | Special Business Rules |
|---|---|---|---|
| Introduction Page | N/A |
|
|
Application Year Page |
|
| |
| Edit Account Page | N/A |
|
|
| Account/Mailing Information Page |
2. My current mailing address is outside the United States is enabled. (non_us_address, city, postalcode, province, state, streetaddress1, streetaddress2, country)
3. I have no current mailing address because I am currently homeless. (no_mailing_address_homeless) |
| Current Mailing Address Section:
|
| Dependency Status Page |
Dependency Status Questions: 3. As of today, are you married or in a Registered Domestic Partnership (RDP)? (married_or_rdp) 4. Are you a veteran of the U.S. Armed Forces or currently serving on active duty for purposes other than training? (us_veteran) 5. Do you have children who will receive more than half of their support from you between July 1, 2017 - June 30, 2018, or other dependents who live with you (other than your children and spouse/RDP) who receive more than half of their support from you, now and through June 30, 2018? (dependents) 6. At any time since you turned age 13, were both your parents deceased, were you in foster care, or were you a dependent or ward of the court? (parents_deceased) 7. Are you or were you an emancipated minor as determined by a court in your state of legal residence? (emancipated_minor) 8. Are you or were you in legal guardianship as determined by a court in your state of legal residence? (legal_guardianship) 9. At any time on or after July 1, 2016, did your high school or school district homeless liaison determine that you were an unaccompanied youth who was homeless? (homeless_youth_school) 10. At any time on or after July 1, 2017, did the director of an emergency shelter or transitional housing program funded by the U.S. Department of Housing and Urban Development determine that you were an unaccompanied youth who was homeless? (homeless_youth_hud) 11. At any time on or after July 1, 2017, did the director of a runaway or homeless youth basic center or transitional living program determine that you were an unaccompanied youth who was homeless or were self-supporting and at risk of being homeless? (homeless_youth_other) Variable Question: 12. If your parent(s) filed or will file a ${ bogForm.taxYear } U.S. Income 13. Do you live with one or both of your parent(s) and/or his/her RDP? (living_with_parents) or both of your parents? (dependent_on_parent_taxes) 13. Do you live with one or both of your parent(s) and/or his/her RDP? (living_with_parents) |
| |
| Special Eligibilities Page |
|
| |
| Eligibility Methods | Method A Enrollment Fee Section
Method B Enrollment Fee Section5. How many persons are in your household? (Include yourself, your spouse, and anyone who lives with you and receives more than 50% of their support from you, now and through June 30, 2018). (dep_number_household/ind_number_household)Student and Spouse’s/RDP 2015 INCOME INFORMATION Section6. Adjusted Gross Income (dep_gross_income/ind_gross_income) 7. All Other Income (dep_other_income/ind_other_income) 8. Total Income for <year> (dep_total_income/ind_total_income) _total_income) |
| |
| Certification Page | Applicant Certification Statement
I hereby swear or affirm, under penalty of perjury, that all information on this form is true and complete to the best of my knowledge. If asked by an authorized official, I agree to provide proof of this information, which may include a copy of my and my spouse/registered domestic partner and/or my parent's/registered domestic partner's 2016 U.S. Income Tax Return(s). I also realize that any false statement or failure to give proof when asked may be cause for the denial, reduction, withdrawal, and/or repayment of my waiver. I authorize release of information regarding this application between the college, the college district, and the Chancellor's Office of the California Community Colleges. (confirmation_applicant)
|
| |
| Review Application Page | N/A |
|
|
| Submission Page | N/A |
|
|
Non-Autopopulated Fields
Below are the CCPG Data Elements that are not going to be a part of the auto-population feature. Patty please review these and let me know if you agree/disagree and have any edits to any of these fields.
| CCPG Data Elements | Reasoning |
|---|---|
| app_id | This is a system generated field that is auto generated and custom for each independant application. Not applicable for auto-populate. |
| app_lang | This is the language button. It's saved in the DB. Not applicable for auto-populate. |
| birthdate | Already populated from Account. Not applicable for auto-populate. |
| born_before_23_year | Calculated on backend. this field is what is determined on the dependency status page and is used in conjunction with dependecy page questions so the other DB fields cover this. Not applicable for auto-populate. Logic is tied to this field and used to to display last 2 questions. |
| campaign1 | Passed in from the college when they have a link to the application to their website. Not applicable for auto-populate. |
| campaign2 | Passed in from the college when they have a link to the application to their website. Not applicable for auto-populate. |
| campaign3 | Passed in from the college when they have a link to the application to their website. Not applicable for auto-populate. |
| ccc_id | Passed in from student account. Not applicable for auto-populate. |
| college_id | Set by which college the student is applying to. Not applicable for auto-populate. |
| college_name | Set by which college the student is applying to. Not applicable for auto-populate. |
| confirmation_number | This is a system generated field that is auto generated and custom for each application. Not applicable for auto-populate. |
| dependency_status | Calculated based off questions the student answers on dependency status page. Not applicable for auto-populate. |
| elig_bogfw | Calculated field based on student answers on the application. Not applicable for auto-populate. |
| elig_method_a | Calculated field based on student answers on the application. Not applicable for auto-populate. |
| elig_method_b | Calculated field based on student answers on the application. Not applicable for auto-populate. |
| elig_method_d | Calculated field based on student answers on the application. Not applicable for auto-populate. |
| Value is passed in from the student's account. Not applicable for auto-populate. | |
| firstname | Value is passed in from the student's account. Not applicable for auto-populate. |
| ip_address | Captured from header when the student first starts the application. Not applicable for auto-populate. |
| last_page | Saved each time in the aplication as the student completes a page. Not applicable for auto-populate. |
| lastname | Passed in from student account. Not applicable for auto-populate. |
| mainphone | Passed in from student account. Not applicable for auto-populate. |
| mainphone_auth_text | Passed in from student account. Not applicable for auto-populate. |
| mainphone_ext | Passed in from student account. Not applicable for auto-populate. |
| middlename | Passed in from student account. Not applicable for auto-populate. |
| no_perm_address_homeless | Passed in from student account. Not applicable for auto-populate. |
| preferred_firstname | Passed in from student account. Not applicable for auto-populate. |
| preferred_lastname | Passed in from student account. Not applicable for auto-populate. |
| preferred_middlename | Passed in from student account. Not applicable for auto-populate. |
| preferred_name | Passed in from student account. Not applicable for auto-populate. |
| otherfirstname | Passed in from student account. Not applicable for auto-populate. |
| othermiddlename | Passed in from student account. Not applicable for auto-populate. |
| otherlastname | Passed in from student account. Not applicable for auto-populate. |
| othername | Passed in from student account. Not applicable for auto-populate. |
| ssn | Passed in from student account. Not applicable for auto-populate. |
| ssn_exception | Passed in from student account. Not applicable for auto-populate. |
| ssn_hash | Passed in from student account. Not applicable for auto-populate. |
| ssn_last4 | Passed in from student account. Not applicable for auto-populate. |
| ssn_no | Passed in from student account. Not applicable for auto-populate. |
| ssn_type | Passed in from student account. Not applicable for auto-populate. |
| status (Download status) | System generated based on status of appkication. Not applicable for auto-populate. |
| tstmp_create | System generated based on status of appkication. Not applicable for auto-populate. |
| tstmp_download | System generated based on status of appkication. Not applicable for auto-populate. |
| tstmp_submit | System generated based on status of appkication. Not applicable for auto-populate. |
| tstmp_update | System generated based on status of appkication. Not applicable for auto-populate. |
| year_code | Year the application is being filled out for. Not applicable for auto-populate. |
| year_description | Year description the application is being filled out for. Not applicable for auto-populate. |
...