BOG type D but not homeless
edited November 2017 in CCC Promise Grant Application
Since going live with the latest upgrade to OpenCC and BOG we have received 8 BOG applications that have been identified as BOG type of "D". However, all of these people have a home address and none of the other homeless questions were checked. I'm a little confused.
Please send me confirmation numbers, and CCCID's for those 8, in an email to [email protected] Need more investigation0
Please give me a call at 530-936-7410. This sounds like it might be a Bug, but need more information to investigate.0
Kyle_Mack MemberWas this resolved? We're seeing this here as well. I can send confirmation numbers and CCCID's if needed.0
The only piece of code in the system that sets the eligibility to method D basically translates as:
If dependent_homeless is true, then set elig_bogfw = 'D', else continue
The system is not looking at income levels, the address status, or anything of that nature (which I definitely would agree would also make sense to indicate homeless status), it's just looking at whether they check the radio box on the Application Year page saying that they were determined homeless within the last 24 months.
From what I can determine it looks like the BOGFW Application is operating as expected with setting these fields and I'd be curious to know why that screenshot is not properly showing the appropriate values for determined_homeless or elig_method_d that are saved in the actual database.
Also I'd like to clarify if this is an issue in that the users have reported that they were inappropriately classified as homeless, or if the college feels like they were reported inappropriately based on the data they are seeing (e.g. would it be possible to get in contact with one of these students and see if they did check the determined_homeless radio button?)
Kyle_Mack MemberIt seems like there should be a delivered validation rule that stops an applicant from proceeding if they provide an address and check the determined_homeless button. Those two seem mutually exclusive.0
For an enhancement request you will need to:
The process isthat the College writes up what they believe the enhancement is that theywant. This would also includes how this enhancement would benefit all 113 CollegeDistricts. If they have technical solutions / or input please includethat in their document. Send the document to the Product Manager, [email protected].
The ProductManager then schedules the enhancement request for vetting by the SteeringCommittee. Once they have either approved / disapprove the enhancement itthen is added as Jira ticket system for the appropriate Dev Team.
The current list of enhancement / change requests can be found here: https://cccnext.jira.com/wiki/display/PD/Change+Requests0
- 1.5K All Categories
- 196 CCCTC System Alerts
- 784 CCCApply
- 129 CCCApply Report Center
- 7 CCCApply Administrator
- 12 CCC Data Warehouse
- 8 CCC Glue: College Adaptor
- 75 CCC MyPath
- 18 OpenCCC Student Account
- 29 CCC Promise Grant Application
- 37 CCCApply International Application
- 63 CCC Accessibility Center
- 2 Enabling Services
- Implementation Project Managers (IPM)
- 1 College Relationship Managers (CRM)
- 47 Multiple Measures Initiative
- 46 Library Services Platform
- 11 Career Coach
- eTranscript California
- 4 C-ID
- 17 COCI
- 9 CCC ConferZoom
- 5 Best Practices for ccctechnology.info