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 | ||
|---|---|---|
|
...
|
...
|
...
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 | Area B Residency logic change for California homeless applicants. | Colleges should be aware that two minor changes were made to the Area B residency logic to ensure that California applicants who are homeless will not be flagged for residency as “possible residents” based on permanent and/or current mailing address alone.
| NoneN/A | ||||||
CCCApply Standard Application | Internationalization Optional internationalization i18n (Spanish Translation) in for CCCApply Supplemental Questions. | Colleges that have implemented custom, optional Supplemental Questions should be aware that if they want their questions to appear in Spanish when a user has set their lang setting to Spanish, then they will be required to manage responsible for managing the translation of their custom text questions, including translation of the 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 Download Client: Question: Highest Grade Completed
| 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) if they want to download the new Highest Grade Completed data field.
Colleges using Glue for CCCApply for data delivery will need to complete the required implementation tasks outlined by the SuperGlue team.
| Optional (Download Client is backwards compatible) - but no data will be delivered until you add the data to your download file. REQUIRED for Glue for Apply users | ||||||
CCCApply Standard Application | New Deprecated question & data field added to SuperGlue 3.7.0: Question: Highest Grade Completed | 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.
| Optional (Download Client is backwards compatible) | ||||||
OpenCCC Account System | Mobile support for OpenCCC student account system | The user interface in the OpenCCC student account system, including Create Account, Recover Account, and Edit Account pages have been redesigned for mobile devices.
| N/A | ||||||
OpenCCC Account | New layout and onscreen question text for the Social Security Number Question | The Social Security Number question has been completely redesigned with a new, streamlined layout and improved onscreen question text/language to minimize barriers and ambiguity that might cause confusion to some students, such as non-U.S. resident, ESL/Spanish-speakers, international students.
|
...
| N/A |
Product Documentation & Links
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.
...
Change to the CCCApply Residency Logic
One of the changes made in release A change was made to the Area B residency logic in the CCCApply 6.7.0 impacts release to remove an unnecessary barrier for homeless applicants who have indicated that they have no permanent address or mailing address because they are currently homeless, yet in every other way they are otherwise legal California residents . Issue: Colleges have reported that many of their California homeless applicants are faced with undue burden because the CCCApply residency logic is determining they are not residents and must provide proof to support their California residency. This is happening because they are not entering an address in their OpenCCC account and/or a mailing address in the CCCApply application. The current CCCApply residency algorithm flags each instance where the address provided (or not provided) includes a state other than Californiafor tuition purposes. The fact that they are not providing an address is the reason they are getting flagged. From now on, California homeless applicants will not be flagged in Area B based on their address alone.
| Tip |
|---|
There is no required task that the college needs to do that corresponds with this change. |
Legal Support: CCCApply worked with the Office of Legal Counsel at the CCC Chancellor’s Office to explore the best solution to this issue. According to the California Education Code, residency status for tuition purposes cannot be based on address alone. Therefore, If the
Solution: In this release (6.7.0) we have made an adjustment to the Area B residency logic so that it will only flag applicants who state indicate that their permanent address “state” and/or current mailing address “state” is not California AND they have not checked the box stating boxes indicating they are homeless. In other words, if the student has self-reported that they are homeless, the residency logic will not flag them for residencyNOT flag them based on the fact that their address “State” is not California.
An applicant’s address will only be used in the calculation of their residency status if they have left the “no permanent address homeless” and/or “no mailing address homeless” checkboxes EMPTY.
| Info |
|---|
For more information on the CCCApply residency Areas, see the CCCApply Standard Application Data Dictionary. |
...
Changes to the User Interface
The majority of this release consists of user interface enhancements that require no action on the part of the colleges. Additional information on the user interface changes is detailed can be found in the links below.
Internationalization: SpanishResponsive design: Mobile-device friendly
Internationalization (Spanish translation) for Supplemental Questions
...
Spanish Translation in All CCCApply Applications
The highlight of the CCCApply release v.6.7.0 is the internationalization of the code for all CCCApply applications AND the OpenCCC Account applications (Create, Recover). Internationalization allows the ability for multiple language parameters to be implemented for end users upon request.
The first language alternative to English is Spanish, based on a Spanish-Mexico dialect.
Users who would like to set their language preference to Spanish can do so by clicking on the Cambiar A Espanol button or link from any page - and have it persist from page to page throughout the user’s application experience. This functionality allows the user to toggle between Spanish and English as often as needed.
...
Implementing Spanish Translation in Supplemental Questions
Colleges that have implemented custom (optional) supplemental questions in one or more CCCApply applications, have the option to implement Spanish translation using the <translation> XML element in their Supplemental Questions XML file(s). If your college does not care to internationalize your supplemental questions, no action is needed.
Internationalization (Spanish Translation) in Supplemental Questions
Colleges that have implemented optional supplemental questions can
To implement Spanish translation using the <translation> element:
Follow the instructions to implement
...
the <translation> element
...
detailed on page 8 of the Working with Supplemental Questions User Guide.
| Info |
|---|
Colleges are responsible for all Spanish translation updates for their custom Supplemental Questions. If your college does not care to internationalize your Supplemental Questions, no action is needed. |
(Internationalization: The Optional <translation> Element)
Changes to the Data
Impact on the College
Impacts on the User
Required
Adding New Fields to the Download Client
...
| Note |
|---|
REMINDER: To implement custom Supplemental Questions, colleges must configure a Supplemental Questions XML file for each CCCApply application, even if the questions are the same in each of the applications. |
OpenCCC Mobile Support
...
One of the highlights of the CCCApply 6.7.0 release is the completion of the responsive design work that delivers a mobile-friendly user experience for mobile users.
Now a user can create an OpenCCC account, recover an account, reset their password, and start and submit a CCCApply application - on their mobile device.
To preview the mobile experience, visit your college website and navigate to the Admissions page to find your link to CCCApply. Click on their link to Apply and experience the process on your smart phone, tablet or desktop.
...
Changes to Data Fields
In the v.6.7.0 release, there is one new data field added to the CCCApply Standard Application data set <highest_grade_completed>, and one deprecated field <completed_eleventh_grade>.
New: highest_grade_completed
Deprecated: completed_eleventh_grade
CCCApply Data Delivery Methods
The CCCApply Standard Application data can be delivered in two formats:
...
CCCApply Download Client Method
In general, in order to download new and or changed data fields and values that get deployed in are implemented in the OpenCCC and CCCApply applications, you must first add and/1) add the new data field, or make required changes, to the fields in your application-specific Format Definition XML file(s) and 2) update the existing (transfer-client.jar) file for the current release. For the For more information, please see the Download Client section in the CCCApply public documentation site.
Add New <highest_grade_completed> Data Field to Standard Format Definition XML File
To download the new <highest_grade_completed> data in the CCCApply 6.7.0 Pilot release, update add the new field to your Standard Application Format Definition XML file with the data field changes specified in the New & Changed Data Fields table, above. using XML code.
For details on adding new fields to the Format Definition XML file, see the CCCApply Download Client User Guide.
Job and Format Definitions XML Templates
To ensure your CCCApply download files are always in synch with the latest release version, we recommend that all new and changed data fields be added to your download files (Format Definition XML) and replace/update the Download Client Jar file with each release. This should be done whether you plan to import the new fields to your college SIS system.
Running the 6.7.0 Download Client Jar File
When new fields are added to OpenCCC or any of the CCCApply Applications in one of the Annual Updates or a supplemental September release, they need to be manually added to your Application Format Definitions XML files (each application - CCCApply, BOG, International - has a unique one) AND you must update your Download Client with the release-specific Transfer-Client Jar file. A new 'transfer-client-jar" file is created for each release, including the Pilot releases. The latest transfer client jar files are always stored here with the Download Client User Guide.
| Note |
|---|
You must update your Download Client Jar file for each new release in order to download new data fields and other data. |
In your installed Download Client directory, replace the older files with the latest version files which are always stored with the Download Client User Guide:
Replace transfer-client-.jar with: <latest transfer-client.jar >
Replace conf/application-context.xml with: application-context.xml
Replace conf/ccctransfer.properties with: ccctransfer.properties
Update Your Pilot Download Client Jar File
After you've updated your Pilot Format Definition XML with new and changed data fields, you must replace your Pilot Download Client Jar file with the latest version.
In your installed Pilot Download Client directory, replace the following files:
Replace your existing transfer-client.jar (V6.5) with: transfer-client-V5.jarV.X.X.0) with: < PLACE LATEST DLC FILE HERE >
Follow the instructions in the Pilot CCCApply Download Client User Guide.
| Note |
|---|
Please be sure to backup your files before downloading new ones. |
Update the Production Download Client Jar File
To update your Download Client Transfer file for the Production environment, the process is the same as the Pilot environment update. The same jar file is used for both environment.
In your installed Production Download Client directory, replace the following files:
Replace your existing transfer-client.jar (V6V.X.5X.0) with: transfer-client-V4.jar < PLACE LATEST DLC FILE HERE >
Follow the instructions in the CCCApply Download Client User Guide.
| Note |
|---|
Please be sure to backup your files before downloading new ones. |
...
SuperGlue for CCCApply Method
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 | 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 | 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 | 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 | 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 | 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. |
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 | 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. |
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 | 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. |
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. |