4/1/24 Weekly Status Report

2.3.4.1 Financial Aid Integration

at risk - based on college feedback, current plan may not work and may need to redesign solution.

2.3.4.5 CSU/UC Student Management

On Track

2.3.4.5 Preferred Name

On Track

2.3.4.2 Student Eligibility Checker

On Track

2.3.4.3 Refining Searches

Some Risk - CVC has not seen a demo of this yet and deliverable to end of July.

2.3.4.4 eTranscripts Reporting To Colleges

On Track

1.

Severe: Affects Financial Aid Integration

N

Financial Aid Pilot:

• Issues with Workflow

• Peoplesoft college dropped out of pilot

• At CISOA, colleges expresses concerns about marker courses and how it will negatively affect the A&R process.

Parchment

• We may need to deviate away from the original architecture that has been because of the pushback from colleges.

• In process with Allan Hancock for the P2 Teaching College Implementations

• CVC leadership is investigating a possible new path.

high

https://cvc-oei.atlassian.net/browse/BLQ-1015

4/5/24

2.

Moderate: Users Were Not Able to Authenticate to CVC via Proxy

Yes

On Friday, Dec 15th, all student attempts to authenticate to our platform via the proxy seem to be failing. No one was been able to sign in. We've seen 100% failure rate on all attempts from every user who has tried at every college since about 6 AM Friday morning.

CVC reached out to CCCTC support team but they didn’t seem to have any insight into what could be causing this as they have shared that no one else has reported any issues.

However, we kept receiving a 403 Forbidden error message when we try to connect to any college via the Proxy. This is impacting both production and pilot and began failing around the same time on Friday. Whenever a user selects any college where we would normally route them to the appropriate SSO page, we instead are getting this error.

CVC Exchange - Sign In - Powered by Quottly (select any college)

• CVC and CCCTC

• We escalated this to Mike Caruso at the CCCTC and he advised they were able to log in with no issues.

• After further research, it looks like the CCCTC had some additional IP restrictions and our IP was possibly whitelisted.

• This issue was resolved same day, but we are working with the CCCTC and Parchment to ensure this does not happen in the future.

• CVC and Jason from Parchment are working to investigate to ensure this doesn't happen again in the future.

  Jason has provided the following update about next steps and continuing research with the CCCTC: “I've gotten some additional information on this, the net of which is that this part of our application isn't capable of being configured on a guaranteed static IP. There's work we can do to make it semi-static, meaning it still may change with some, but even so change of the outbound IP can happen for reasons outside our control. 

  A "more static IP" change is not something we can implement immediately, given the holidays and that such a change may impact other users.

  I can't speak to if this was also a risk in the Heroku infrastructure days or not, but I'm slightly concerned as in our current state, as this could happen again based on factors we can't really control.

  So, I have these questions for the Tech Center:

  • Is this a new practice? If so, can it be rescinded until we have time to ensure there's a lesser risk configuration on our side?

  • Can the Tech Center whitelist by fqdn, rather than by IP? On our end, this is the best solution because we can implement what we have in the rest of the platform, which ensures traffic will always be sourced from 

  egress.parchment.com even though the IP addresses assigned to that may change in a way we can't control.

  As an aside, we don't have great logging of this on our side, so normally we'd put a monitor in place that fires the moment we start seeing it. We're not in a position to do that yet.”

1. The CCCTC 'pushed pause' on this particular element of that security update, but they are unblocked in terms of continuing to make improvements via consistent security-focused deployments. It is something they need to resolve, but that work has just started, and there isn't a firm ETA yet.

2. CVC and CCCTC are meeting on 4/17/24 to discuss.

high

https://cvc-oei.atlassian.net/browse/BLQ-1041

4/5/24

3.

Severe: Will Affect All eTranscripts Sending Colleges Who Are on SaaS

Y

Manage The CCCTC/Ellucian SaaS Shared Application Staging Tables In Conjunction With The GLUE Data Model - SaaS Migration Process

Mike V.

For colleges who are either a SaaS client or migrating over to SaaS, the current Ellucian APIS will not support eTranscript CA sending infrastructure. This affects colleges that are already live with eTranscript sending through Parchment/XAP as well as the ones who are migrating.

• Parchment submitted requirements to Ellucian.

• Ellucian received and is actively looking into this and advise if this is configurable or if they need to do development.

high

https://cvc-oei.atlassian.net/browse/BLC-138

4/5/24

1.

Weekly Combined Requirements Meeting Notes & Recordings

• We meet every Tuesday to discuss items that need attention, analysis, escalated, or enhanced. All recordings, notes, and next steps can be found on the running combined requirements meeting agenda.

• Next meeting is 4.2.24

high

https://docs.google.com/document/d/1S3zLxqu6CLDmIO6Eq1YmOlo-gPG_Hwn6-lyaEiTpkQE/edit

4/5/24

2.

CVC Support Cases

• Attached is the monthly report for the CVC support cases provided from Parchment.

4/5/24

3.

Canvas Solution for ILP Colleges

• Database access to ILP team today

• Test environment is not updated for Kern, so will work to get this updated.

• Development will be done by 12/19/23.

• No new updates this week.

high

4/5/24

4.

Parchment Weekly Sprint Jira Status Updates

Lane 1: Major Functional and Implementation Blockers

• Financial Aid Integration Workflow BLQ-1015 - Call with Copper Mountain has been postponed. CVC shared concerns raised by the colleges regarding marker courses. Additional conversations to be had.  

• System time zone for CVC Test and Prod sites PICE-537 - Parchment team to review and find solution in coming weeks.  

Lane 2: Renewal Enhancements

• Financial Aid implementations  - Next steps to be determined following discussions on marker courses.  

  • BLQ-952 

  • BLQ-920 

  • BLQ-972

• Document search result output sorting methods BLQ-979 & BLQ-1008 - Questions regarding whether this will be elastic search or something similar have been raised. CVC is hoping for a demo of the planned changes during the week of April 15th to prepare for a meeting on April 26, 2024. 

• Student Eligibility Checker - Parchment testing in the Banner sandbox. 

  • BLN-729 N2N To Create API Specs, Place on Conf, And Send To Parchment

  • BLN-745 Parchment To Develop Feature Flag To Enable College Rollout Enablement

  • BLN-746 Parchment To Develop Progress Bar

  • BLN-748 Parchment To Develop Ability To Consume eligibilityStatus = and eligibilityStatusReason =

  • BLN-837 Parchment to Add/Display CVC Provided URL To Student Ineligible Page

Lane 3: Prioritized Enhancements and Research

1. Parchment to Analyze and Provide Results for Expected APIs and Final States BLQ-1067 -  (This is also related to Complete application/integration diagram - BLQ-673 Diagram to be shared with CVC when available.) Parchment shared a document with CVC to review. Parchment researching a question from Donna, additional feedback pending. 

2. Session Management Changes BLQ-1026 and  UI Changes for Open Registration Dates and Inventory Imports BLQ-967 - This has been reprioritized given CVC feedback for Q4.  

3. Parchment to Provide Technical Requirements for SaaS eTranscripts Compatibility BLQ-1061 - this has been provided to Ellucian. Next steps are TBD. 

4. Determine Method to Identify Students Who Exist in the Teaching College Canvas Instance BLQ-572 - Additional information provided by CVC team. Parchment team to review and determine next steps. 

5. Enrollment Report - Include C-ID as a downloadable field BLQ-1073 - newly prioritized for Q4. 

6. Change drop email notifications for FA admins BLQ-1080 - To be reviewed by the Parchment team.

7. Show Message in UI for Users When We Get CCCID Invalid Errors | contactInfo API Only BLN-775 - Next steps to be determined. 

8. Show "Withdrawn" Status in Student Dashboard and Admin Dashboard BLQ-988 - reprioritized for Q4. 

9. Need Address Validation on the AER Form BLQ-1029 - Next steps to be determined. 

10. Payment Status, Errors, and Reconciliation BLQ-724  - CVC has provided updated language, Parchment work pending.

11. Add Additional Text To The Drop Email Notification BLQ-1031 - In the work queue.  

12. Course Audit Needs to Still Run if the Student Dropped BLQ-1056 - Parchment team corrected the issue causing incorrect dates to appear in the display. CVC has provided additional questions for review.  

Change The Text and Adjust The Layout in the Home California College Section oncvc.eduBLQ-1038- This is still being discussed with the Parchment team.

high

4/5/24

5.

eTranscript Implementations & Follow up with colleges

Below is the latest updates on where we are with each college:

• Allan Hancock: 3.20.24: Met with the college and from a XAP and Parchment perspective, the infrastructure is in place and transcripts should be trickling in. Amanda requested a call to go over how the CVC unsolicited transcripts will work. Once they provide dates, I'll schedule a meeting.

• Barstow 3.28.24: Met with Barstow and got their XAP communicator installed. Next steps is for Parchment to respond after they send over the pathways.

• Cabrillo CCD - 3.5.24: Emailed Parchment back advising that we are blocked on moving forward with Cabrillo until we have a SaaS solution in place. I will keep them informed with updates.

• Compton CCD - 4.4.24: Contract is in place. Users accounts are set up. Sean set up sample transcripts to the college and we went through the process or how it flows. After our call, they are ready to go live. Sean will need to change their name on his side and he will then go live next week. For sending, they are blocked bc they are a SaaS college. We are working on a resolution for that.

• Copper Mountain CCD (ECA) - 4.1.24: I sent them a follow up email on 3.27.24 to get a meeting on the books for May. no response so Amanda to follow up with them the week of April 22nd to get a calendar invite on the books.

• College of the Desert CCD (ECA) 3.25.24: Florantine from the college responded that Sonia and Noelle need to reply to the the email thread when they complete their review of the XAP Communicator process and test files on each folders (//dccdsys/XAP).

• Feather River CCD (ECA) -4.1.24: Sent flw up email for them to advise their availability on when we can meet.

• Grossmont-Cuyamaca CCD (ECA) -3.21.24: Sent email to college asking for us to meet next week. Will follow on 4/4 if not response.

• Marin CCD - 3.21.24: emailed Jon at the college and asked to set up a kickoff meeting to get this process started. No cohort established yet.

• Merced CCD (ECA) 4.1.24: College and Parchment troubleshooting back and forth via email.

• Napa Valley CCD - 4.4.24: Met with Napa and they want to test this week. They plan to be ready for go live by 4.11.24. If I have not heard from them by then, I'll email them to get a status.

• Porterville - Kern CCD: 4.3.24: College asked for dates/times. Amanda sent cal invite for us to meet on 4.8.24 for sending discussions.

• Palo Verde CCD - 3.25.24: College emailed me back stating, " I currently use parchment for sending electronically, will this satisfy those requirements perhaps?" Amanda responded back that no, it wont meet the reqs. She asked that I send her some dates of availability. Amanda sent email with date and will schedule when she responds.

• Peralta CCD (ECA) 3.25.24: College responded that she will provide my availability once she hears back from their IT department as to where we are with this project. She will be back in touch with you and your team within the next 2-weeks to setup a meeting.

• Riverside CCD (ECA) 4.4.24 - Call with XAP and college resolved error and they will be ready to go live in the next week. Will work on a date.

• San Diego CCD (ECA) 4.2.24: Met with college and they are going to move fwrd with Parchment set up. Amanda sent email with dates/times for us to meet to set up XAP communicator. Will schedule when they respond. Should be live with sending close to mid-end May.

• San Francisco CCD 3.25.24: The college emailed me back asking if they had to be a part of an active cohort to set up for sending. I emailed them back with the explanation.

• San Joaquin Delta CCD (ECA) 3.25.24: College responded with I’m following up with Aubrey. Shawna needed to know how to get to the sample review and had asked Aubrey to assist. Not sure if that was successful." Will flw up with them end of first week of April if no response."

• San Mateo County CCD - 3.21.24 - Sent email to demellon@smccd.edu to schedule meeting to do a kickoff call. No cohort established yet and they are not a home college.

• Santa Monica CCD - 11.2.23 - Per Mike- hold off on reaching out.

• Shasta-Tehama-Trinity Joint CCD (ECA) -3.18.24: Update from Parchment...Kevin Klemke, from Parchment let me know that he resent our test transcripts this morning. He noticed that our initial test files were still in the upload folder, and that the data was malformed. This has been corrected and new transcripts have been sent. The files from today will have overwritten the previously sent data. When you are able, please start the XAP communicator so that it can process these files. The hope is that they will process as expected and move into the success folder.

• Sierra Joint CCD - 11.2.23- no cohort established, hold off on sending until then.

• Siskiyou Joint CCD (ECA) 4.3.24 - College reached out to XAP and asked to start the process for the sending set up. Sean sent out dates/times. When they respond, Sean will schedule a meeting.

• Solano CCD - 11.14.23 - Parchment sent email to Solano advising they need a status update. The college emailed us back stating: "Yes – our SaaS go-live date is April 8th, 2024. As noted by Amanda, I believe we have Parchment sending on pause until we have our integrations set up for SaaS. Our new timeline to become a “Teaching” College is to be part of the Fall 2024 Cohort. Once SaaS has been implemented with the given timeline, we can revist our setup for Parchment sending. I apologize if any of these plans have changed, as I am going off my previous meeting notes documented at the time. Parchment responded that they have canceled this project and will pick it back up when they are ready.

• Victor Valley CCD (ECA) 9.16.23: Victor Valley is going to switch to SaaS in April 2024, so we will be placing this one on hold until after that migration.

• West Hills - 4.3.24: pre-UAT session went well. Scheduled to go live for sending 4.16.24

• West Kern CCD (ECA) 2.19.24: Sent email to Kyle and asked how testing is going/see if they will be ready to go live this week or next.

• West Valley-Mission CCD (ECA) 7.12.23 - Sent flw up email to college to check in on how things are progressing. They dont have a cohort established yet, so if no response follow up in end of Aug.

• Yuba CCD (ECA) 3.4.24: Met to set up XAP communicator. Next steps is for them to set up process internally. Amanda to check in 3 weeks from now to check on progress.

• Amanda and Sean to continue reaching out to colleges next week to continue getting them set up on sending and receiving.

high

In Process

Tracking HC and TC transcripts here: Teaching Colleges Sending Transcripts

https://cvc-oei.atlassian.net/wiki/spaces/CVCOEI/pages/1749647361

https://cvc-oei.atlassian.net/wiki/spaces/CVCOEI/pages/1731002371

Weekly Meeting Notes and Action Items will be here each week: https://drive.google.com/drive/folders/12_-PObf7ii0hgvV3g4S-EfWzUamAi8zd

Weekly Status Call Recordings Here: https://drive.google.com/drive/folders/1LF4RbCkYhAdKjPwhoEw2SdArlvo4-u9i

4/5/24

https://cvc-oei.atlassian.net/browse/PICF-338

MEDIUM

4/26/23

https://cvc-oei.atlassian.net/browse/PICE-471

medium

9/14/23

https://cvc-oei.atlassian.net/browse/PICF-388

medium

10/17/23

https://cvc-oei.atlassian.net/browse/PICE-494

medium

11/9/23

https://cvc-oei.atlassian.net/browse/PICF-402

medium

11/13/23

https://cvc-oei.atlassian.net/browse/PICF-416

medium

12/10/23

https://cvc-oei.atlassian.net/browse/PICF-423

medium

1/11/24

https://cvc-oei.atlassian.net/browse/PICF-408

medium

11/20/24

https://cvc-oei.atlassian.net/browse/PICE-537

medium

3/5/24

https://cvc-oei.atlassian.net/browse/PICF-438

medium

3/12/24

https://cvc-oei.atlassian.net/browse/PICF-439

medium

3/13/24

https://cvc-oei.atlassian.net/browse/PICE-542

high

3/13/24

https://cvc-oei.atlassian.net/browse/PICE-543

high

3/15/24

https://cvc-oei.atlassian.net/browse/PICF-440

medium

3/24/24

https://cvc-oei.atlassian.net/browse/PICF-441

medium

3/25/24

https://cvc-oei.atlassian.net/browse/PICE-544

high

3/29/24

https://cvc-oei.atlassian.net/browse/PICF-443

medium

4/5/24

https://cvc-oei.atlassian.net/browse/BLQ-1067

High

Analysis & Documentation

2.29.24

https://cvc-oei.atlassian.net/browse/BLQ-1026

High

Session Management

11.21.23

https://cvc-oei.atlassian.net/browse/BLQ-967

High

Session Management

11.21.23

https://cvc-oei.atlassian.net/browse/BLQ-1064

High

Financial Aid Integration

2.29.24

https://cvc-oei.atlassian.net/browse/BLQ-952

High

Financial Aid Integration

4.19.23

https://cvc-oei.atlassian.net/browse/BLQ-920

High

Financial Aid Integration

2.22.23

https://cvc-oei.atlassian.net/browse/BLQ-1061

High

SaaS

2.9.24

https://cvc-oei.atlassian.net/browse/BLQ-979

High

Search Engine

6.12.23

https://cvc-oei.atlassian.net/browse/BLQ-572

High

Canvas

2.13.24

https://cvc-oei.atlassian.net/browse/BLQ-1003

High

eTranscripts

9.12.23

https://cvc-oei.atlassian.net/browse/BLQ-1073

High

C-ID

3.21.24

https://cvc-oei.atlassian.net/browse/BLQ-1080

High

Drop Email Notifications

3.26.24

https://cvc-oei.atlassian.net/browse/BLQ-1002

High

eTranscripts

9.12.23

https://cvc-oei.atlassian.net/browse/BLQ-1010

High

Financial Aid Integration

9.14.23

https://cvc-oei.atlassian.net/browse/BLQ-673

High

Documentation

12.3.21

https://cvc-oei.atlassian.net/browse/BLQ-988

High

Admin Dashboard

7.12.23

https://cvc-oei.atlassian.net/browse/BLQ-1015

High

Financial Aid Integration

10.16.23

https://cvc-oei.atlassian.net/browse/BLQ-1029

High

Address Verification

11.2.23

https://cvc-oei.atlassian.net/browse/BLQ-724

High

Payment Processor

11.17.24

https://cvc-oei.atlassian.net/browse/BLQ-1056

High

Course Audit

2.6.24

https://cvc-oei.atlassian.net/browse/BLN-835

High

Program Code

2.27.24

https://cvc-oei.atlassian.net/browse/BLN-789

High

Term Activate

11.21.23

https://cvc-oei.atlassian.net/browse/BLN-280

High

Student Eligibility Checker

4.22.21

https://cvc-oei.atlassian.net/browse/BLN-845

High

API

4.14.24

https://cvc-oei.atlassian.net/browse/BLN-775

High

API Errors

11.8.23

https://cvc-oei.atlassian.net/browse/BLN-799

High

Search Match

11.28.23

https://cvc-oei.atlassian.net/browse/BLN-841

High

API

3.11.24

https://cvc-oei.atlassian.net/browse/BLN-848

medium

Research

3.26.24

4.4.24

https://cvc-oei.atlassian.net/browse/BLQ-991

medium

ASSIST

4.1.24

https://cvc-oei.atlassian.net/browse/BLQ-845

medium

Course Units & Seat Counts

7.25.22

https://cvc-oei.atlassian.net/browse/BLQ-1031

medium

Emails

11.6.23

https://cvc-oei.atlassian.net/browse/BLQ-1036

medium

UI Text Updates

11.21.23

https://cvc-oei.atlassian.net/browse/BLQ-286

low

Accessibility

2.2.24

https://cvc-oei.atlassian.net/browse/BLN-842

medium

Person Match

3.11.24

https://cvc-oei.atlassian.net/browse/BLN-739

medium

Documentation

8.14.23

https://cvc-oei.atlassian.net/browse/BLN-727

medium

Error Improvements

7.5.23

https://cvc-oei.atlassian.net/browse/BLC-139

High

Duplicate CCCIDs

2.20.24

https://cvc-oei.atlassian.net/browse/BLC-140

medium

CVC Website

2.29.24

Q1: July 1-Sept 30

Q2: Oct 1-Dec 31

Q3: Jan 1-March 31

Q4: April 1-June 30

Q1: Jan 1-March 31

Q2: April 1-June 30

Q3: July 1-Sept 30

Q4: Oct 1-Dec 31

Q1: Jan 1-March 31

Q2: April 1-June 30

Q3: July 1-Sept 30

Q4: Oct 1-Dec 31