Schedule

Scope

Contents

Summary  

Back to Top

Release Summary & Strategy

The purpose of this release is to deploy the highly anticipated Ethnicity-Ancestry Expansion Project implementation - approved and sponsored by the Chancellor's Office in support of the Student Equity Planning workgroup's research to close the gap in student equity. This feature enhancement was scheduled to be included in the September 2018 release (6.2.0) as part of the initial CCCApply Redesign deployments; however it was postponed in order to honor our commitment to implement this change free from any impact to the colleges IT staff.  The new Race & Ethnicity Implementation 2018 includes: one new, optional data field to collect all the new response options included in the expansion (Race Ethnicity Full); a new streamline layout to the Race & Ethnicity section in the Standard & International applications; and 194 new race and ethnicity-ancestry checkbox options in an accordion-style format.

• To read the approved change request: 2018-18R: New Race & Ethnicity Implementation 2018

• To reach the research background information: Ethnicity/Ancestry Expansion Project

• For step by step UAT guide: UAT: Race & Ethnicity Implementation 2018

Also in this release:

• User-interface styling upgrade across OpenCCC and all CCCApply applications for the purpose of aligning our look and feel to the CCCMyPath student portal.

• The annual CC Promise Grant Application for 2019-2020 is also being deployed, which will be active for colleges on January 1, 2019.
  
  
  

Pilot Preview

Due to the short timeline for this release, the Pilot preview period - the period in which our two external-facing CCCApply environments are not aligned, providing colleges user preview and implementation support prior to an upcoming production release - will begin Monday, November 19 through December 7, 2018. The CCCApply Support Services team will be monitoring feedback on the CCCTechnology.info support site and additional online support documentation and training will be available.

Release Schedule & Timeline

• November 20 - 9:00AM - 4:00PM (Note the Pilot Site will be down during this release).

• December 14 - 6:00PM - 11:00PM - Production Maintenance Window

Back to Top

Changes to the CCCApply Standard Application

The following changes and enhancements were approved for development and implemented in the 6.3.0 release code.

Changes to the International Application (BOG)

The following changes were approved and implemented in the 6.3.0 release code.

Changes to "Glue for Apply" and the SuperGlue College Adapter

Changes to the Promise Grant Application (BOG)

The 2019-2020 CC Promise Grant Application was updated and deployed to the BOG database in this release. It will be enabled automatically on January 1, 2019 for those colleges who've adopted the online Promise Grant Application. 

Changes to the CCCApply Download Client

 The following data field has been added to the CCCApply Standard & International submitted_applications databases. Please see specific implementation steps to update your Format XML files and download client below.

Back to Top

CCCApply Data Field Information  

The table below provides an overview of all the Race & Ethnicity section data fields in CCCApply Standard, International, and "Glue for Apply".

*NOTE: The new Race Ethnicity Full field will not be available in the "Glue for Apply" SuperGlue application in this release 6.3.0.

User Acceptance Testing (Pilot)

User acceptance testing and implementation support for this release is focused on the Race & Ethnicity Implementation 2018. Colleges are encouraged to preview the new implementation in the Pilot Environment on November 20 upon completion of the Pilot deployment activities.  For all release announcements and system alerts, please follow "CCCApply System Alerts" on CCCTechnology.info.

• UAT GOALS & OBJECTIVES 

• UAT SUCCESS CRITERIA

• UAT STEPS

  • Testing in the Pilot Environment

  • Data Field Specifications & Mapping
    
    

Feedback & Resolution Process 

• Feedback should be categorized as bugs and enhancements. Only Severity 1 issues (issues that prevent critical business functions from being accomplished) will be considered as release blockers.

• Reporting: User feedback should be noted in the result section. The following criteria should be followed and documented:

  • Any identified bugs with severity and priority 

  • Enhancement requests with priority identified

Back to Top

Data Dictionaries & Release Documentation

The following links point to the most current versions of the CCCApply Data Dictionaries and User Guides.