Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Colleges should be aware of the following technical changes and potential impacts to one or more CCCApply applications implementations in the Version 6.7.0 release.

Table of Contents
maxLevel2
minLevel2

Summary of Change Impacts &

...

Technical Tasks

Each item in the table below describes an impact or a change to OpenCCC or CCCApply that may require colleges to make a technical update. Technical tasks or action items are detailed below.

Application Impacted

Impact or Change

Technical Tasks

Required or Optional

CCCApply Standard Application

Residency change for California homeless

California homeless applicants will not be flagged with a residency status of “2 = possible resident” or “3 = non-resident” based on address alone. Address will only be used to determine residency for tuition purposes in combination with other residency flags if the “no permanent address homeless” or “no mailing address homeless” checkboxes are EMPTY.

There is no task required that corresponds to this change.

Colleges should just be aware that the Area B residency logic was revised slightly to ensure homeless applicants that are otherwise California residents will no longer be flagged.

N/A

CCCApply Standard Application
Noncredit Application
International Application

Optional internationalization i18n (Spanish Translation) for CCCApply Supplemental Questions

Colleges that have implemented optional Supplemental Questions should be aware that they will be required to manage the translation of their custom text and add it to their Supplemental Questions XML file.

Optional

CCCApply Standard Application

New Highest Grade Completed question & data field has been added to the HS Transcript Information section in CCCApply Standard App only.

For CCCApply Download Client: Data Field: <highest_grade_completed> For SuperGlue for Apply: Data Field <HighestGradeCompleted>

Colleges using the CCCApply Download Client for data delivery will need to add the new data field to their Standard Application Format Definition XML file and run the Download Client Jar v.6.7.0

Colleges using Glue for CCCApply for data delivery will need to follow the implementation tasks outlined by the SuperGlue team in Glue for Apply 6.7.0.

Optional (Download Client is backwards compatible)

REQUIRED for Glue for Apply users

CCCApply Standard Application

Deprecated question & data field: The new “Highest Grade Completed” is REPLACING the existing “Completed Eleventh Grade” question and data field: <completed_eleventh_grade>

Colleges using the CCCApply Download Client for data delivery should be aware that the <completed_eleventh_grade> field and question will no longer be downloading data through the Download Client.

SuperGlue for Apply 3.7.0 - should note short term implementation.

Optional (Download Client is backwards compatible)

...

...

Deprecated: completed_eleventh_grade

Image RemovedImage Added

CCCApply Data Delivery Methods

...

  • Replace your existing transfer-client.jar (V.X.X.0) with: < PLACE LATEST DLC FILE HERE >

Follow the instructions in the Pilot CCCApply Download Client User Guide.

...

  • Replace your existing transfer-client.jar (V.X.X.0) with: < PLACE LATEST DLC FILE HERE >

Follow the instructions in the CCCApply Download Client User Guide.

...

For step by step implementation instructions, please see the Glue for CCCApply 6.7.0 page.

...

CCCApply Pilot Environment Release

...

CCCApply maintains a separate Pilot environment for the CCCApply applications, admin configuration, reporting tools, and data delivery (including the CCCApply Download Client and the SuperGlue for Apply process)- for college implementation, testing, and previewing pre-production release changes for each of the following applications: 

  • CCCApply Standard and Noncredit Application

  • OpenCCC Student Account System

  • CC Promise Grant Application

  • CCCApply International Application

  • CCCApply Administrator 2.0 (including the System Administrator > User Manager)

  • CCCApply Report Center 

  • Download Servers (Download Client and Glue for Apply) 

Pilot Application URLs

Find your end-to-end test environment for your college's CCCApply implementation.

Getting to the Pilot Environment

Colleges can begin previewing and testing the CCCApply 6.7.0 changes in the Pilot environment on March 4, 2020.  

Reporting Issues & Feedback

Colleges are encouraged to follow the response processes below to report system issues and bugs (S1 and S2) as well as non-critical bugs, change requests, and other general feedback (S3, S4) using the processes below.

Tip

College Support Services via the Staff Support email:  staffsupportccctc@openccc.zendesk.com


Bugs & Issue Resolution During Pilot Preview

Incidents encountered during Pilot Project testing in the Pilot environment - especially during a pre-production release period - should be reported immediately to the College Support Services team - to be resolved as quickly as possible.    

Severity Levels

  • S1 - Application / service is unavailable.  

  • S2 - Required business process is prevented from being used.  No workaround is available

  • S3 - Less important business process is impacted and/or workaround is available.

  • S4 - Low impact or cosmetic issue

Level

Issue Type

Description

Operations Priority

Feedback Process

S1

Application / service is unavailable.  

Pilot college cannot access the Noncredit application in the Pilot environment using their custom URL

24-48 hr response 
Hot Fix resolution TBD

Email details to College Support Services: staffsupportccctc@openccc.zendesk.com

S1

Application / service is unavailable.  

Pilot college cannot access the Noncredit application due to error message

24-48 hr response
Hot Fix resolution TBD

Email details to College Support Services: staffsupportccctc@openccc.zendesk.com

S2

Required business process is prevented from being used.  No workaround is available

Pilot college identifies a critical bug in the Noncredit app user interface or backend systems that prevents implementation or testing 

24 - 72 hr response
Set priority level TBD

Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com 

S3

Less important business process is impacted and/or workaround is available.

Pilot college identifies a non-critical bug in the Noncredit app user interface or backend that does not prevent implementation or testing 

1 week response
Set priority level TBD

Email bug information to College Support Services: staffsupportccctc@openccc.zendesk.com 

S2

Must Have Requirement

Required business process is prevented from being used.  No workaround is available

Pilot college identifies a missing IT or business requirement per state, federal or local mandate (example: AB 3101)

1 week response
Set priority TBD

Use Change Requirement template

Pilot college documents requirement(s) via Change Requirement form template; sends as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda.
Email:  pdonohue@ccctechcenter.org 

S4

Nice to Have Request

Low impact or cosmetic issue

Pilot college identifies a med/high-priority change enhancement to the MVP application 

2 week response
Set priority TBD

Pilot college submits change requirement(s) using Change Request form template; send as link or attachment to Pilot Project Manager to be prioritized for bi-weekly meeting agenda.
Email:  pdonohue@ccctechcenter.org 

S4

Delighter Enhancement

Low impact or cosmetic issue

Pilot college identifies an enhancement to the user interface or backend service(s) that includes unauthorized feature development (Out of FY scope)

2 - 4 week response
Set priority TBD

Pilot college submits change request(s) using Change Req form template; send as link or attachment to Pilot Project Manager to be prioritized for committee review.
Email:  pdonohue@ccctechcenter.org 

S5

Request for Implementation Support

Pilot college requests advice and/or general support for IT implementation, operations, best practices, and/or additional help from Product management, support services, other college pilots, or general colleges - in support of the new project.

24 - 48 hr response

Depending on item; TBD

POST FEEDBACK or QUESTIONS on the CCC Support Site

Pilot colleges should review all CCCApply community board discussions before posting a new support request or question on the College Support Site: CCCTechnology.info

Issue Resolution During Pilot 

Incidents encountered during Pilot Project testing in the Pilot environment - especially during a pre-production release period - should be reported immediately to the College Support Services team - to be resolved as quickly as possible.    

College Support Services via the Staff Support email:  staffsupportccctc@openccc.zendesk.com

NOTE: If you report an issue to the Support team by email, please cc: Patty Donohue, CCCApply Product Manager, pdonohue@ccctechcenter.org

to keep the product team aware of incidents and bugs.