Mobile Support for All CCCApply Applications

All Applications

The first phase of the CCCApply mobile-makeover focuses on implementing a streamlined, mobile-responsive design to our current applications. 

Responsive design is an approach to web page creation that makes use of flexible layouts, flexible images and cascading style sheet media queries. The goal of responsive design is to build web pages that detect the applicant's screen size and orientation and change the layout accordingly. - (What is responsive design?  - A definition from Whatis.com?)

Bug Fix

Several colleges reported an issue with the new Race & Ethnicity values not mapping correctly to the original Race Group and Race Ethnicity fields, which are maintained until the CCCCO MIS data elements are updated to match the new expanded layout, implemented in December 2018 (Release 6.3.0).  These mapping issues have been corrected. 

For more information, or to report any continued problems, please contact College Support at staffsupportccctc@openccc.zendesk.com 

Fixed the discrepancy between the number of dependents response & the household size calculation in the Promise Grant application. 

Fixed an issue with the Date of Birth field miscalculated in reset downloads utility

A timezone error was the cause of this issue, in which we were seeing a discrepancy between the user's actual date of birth (per their OpenCCC Account) and the date displaying in the Reset Downloads utility in the Administrator. The timezone used during development of the Administrator 2.0 system in 2018 was causing the problem. All uses of the <birthdate> value is now consistent across all applications and admin configuration.

Fixed two issues with the Email Rules - one involving logic and the other involving data values issues incorrectly documented in the Promise Grant Data Dictionary.

Several issues regarding the Rules module have been reported since we implemented the new Administrator 2.0 system in September 2018.  

In one instance, a college reported problems with a rule that showed correct logic but wasn't displaying correctly in the Preview window. We had a hard time reproducing that particular issue, but that investigation uncovered some recurring problematic behavior that we have subsequently written tickets for and are now being investigated for next release.

Another issue that was reported as a BOG Rules logic issue, but ended up being a documentation error in the end. 

We found that a field that is documented as a boolean field in the Promise Grant DED, should have been documented as a character string.  The field was <tanf_calworks>.

Once we identified this, we started a review across the Promise Grant DED - confirming that all fields are documented correctly against the Promise Grant database. This is going to take us several weeks, so if you come across any other inconsistencies with data values in the Rules module, or in any process, please report these to CCCApply through College Support staffsupportccctc@openccc.zendesk.com

Fixed the recurring issue of a 500 Error displaying in the spam filter utility

Multiple colleges reported getting a 500 Error when landing on the Spam Filter Summary Table screen in the Administrator.  Unfortunately, this happened shortly after our Q4 release in June, which means it's been hanging around for a while.

This issue should be resolved. We believe that the Administrator system was holding on to connections too long, thus they became stale causing the 500 error. Although we provided a work-around to college (refreshing the page cleared the error), we apologize for this inconvenience and believe the issue is fixed. 

Fixed the recurring issue of a 500 Error displaying in the reset downloads utility

Two colleges reported experiencing a similar problem, getting a 500 Error when attempting to reset applications in the Reset Downloads utility in the Administrator. 

This issue should be resolved as well, and the fix was the same as the spam filter above - the system was holding on to connections too long and they timed out. 

We provided a work-around for this error as well (refreshing the page cleared the error), and, again, we apologize for this inconvenience.