Page Comparison

2.3.4.1 Financial Aid Integration

2.3.4.5 CSU/UC Student Management

2.3.4.5 Preferred Name

2.3.4.2 Student Eligibility Checker

2.3.4.3 Refining Searches

2.3.4.4 eTranscripts Reporting To Colleges

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.

3/28/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.

https://search.cvc.edu/users/sign_in (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.”

• Mike Caruso advised the workaround is still in place, but what you described was an idea that was never implemented. We rolled back the security update that affected you guys and have not re-released it. Separately, we’re working on some stuff that will allow us to push it (and future updates) out to protect against bad web traffic without affecting our APIs.

• CVC has added this to the 4.2.24 CRM meeting.

3/2228/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.

3/28/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

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

3/28/24

2.

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.

• CVC is actively working to expand the ILP testing group to Lassen to complete testing of the logins workaround with a Colleague client. Meeting with Lassen IT on 2/23.

• No new updates this week.

• No new updates this week.

3/2228/24

63.

Parchment Weekly Sprint Jira Status Updates

Lane 1: Major Functional and Implementation Blockers

• Financial Aid Integration Workflow BLQ-1015 - Moving forward with Copper Mountain College and Allan Hancock College as meetings are scheduled. Will update if there are any new blockers. 

• 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  - Allan Hancock KO meeting was on 3/4/2024. Copper Mountain meeting scheduled for 4/1/24. Next steps to be determined as AHC is available.   

  • 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 - Ongoing, in processParchment 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-749 Parchment Work for Term Rule Requirement

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

Lane 3: Prioritized Enhancements and Research

1. Add The Student's Teaching College SIS ID To Congratulations Page BLQ-1023Mock up was approved, will going into staging on Friday, 3/22 for CVC to review for promotion This has been moved to production. 

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

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

4. Determine Method to Identify Students Who Exist in the Teaching College Canvas Instance BLQ-572 - In progress. Parchment to CVC to provide language to be displayed to students when a duplicate canvas account is created.

5. Parchment to Analyze and Provide Results for Expected APIs and Final States BLQ-1067 - Ongoing, goal to have completed by end of this week.  (This is also related to Complete application/integration diagram - BLQ-673 Diagram to be shared with CVC when available.)

6. Session Management Changes BLQ-1026 and  UI Changes for Open Registration Dates and Inventory Imports BLQ-967 - No change. 

7. Course Audit Needs to Still Run if the Student Dropped BLQ-1056 - We believe this is a UI issue and are investigating further. Will correct as needed. If it is found that this is more than a UI discrepancy, we will adjust our plan at that time.  This has been moved into the in progress queue for the Parchment team. 

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

9. Prevention Solution/Future Proofing For Issue That Occurred Where Users Were Not Able to Authenticate to CVC via Proxy BLQ-1041 - Mike believes we need to reconnect to finalize a permanent solution between Parchment and the Tech Center. Next steps TBD.  

10. Change The Text and Adjust The Layout in the Home California College Section on cvc.edu BLQ-1038- This is still being discussed with the Parchment team. 

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

3/2228/24

74.

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.2028.24:Sent email to Barstow and Parchment team asking for a status update. They are meeting with Parchment, Kevin Klempke on Monday 3.25. I asked that they provide us an update after the call 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 - 3.2025.24: Reached out to Richette and asked to get the next call scheduled for receiving. She responded that she is including her Administrative Assistant, Tynay, on this email. She will assist with scheduling this meeting Tynay sent an email and she is going to schedule the call for us on APril 4th from 1-2 PST. She will send out my zoom link in the invite for everyone to join.

• Copper Mountain CCD (ECA) - 34.211.24: Sean and I met with Copper Mountain today on eTranscripts and they are set up in beta and everything is working as expected. They want to wait to roll to prod in May for eTranscripts so they can go live as a P2 TC and XAP at the same time. I am going to go ahead and schedule a meeting in early May to get their XAP communicator installed in prod and then another call when they go live as a P2 to roll to prod with XAPI 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.2025.24: Sent email asking for a status update from college/parchment. Parchment responded that Samples were sent on 12/11/2023, we shared 28 files and if the XAP communicator is working currently they can then be uploaded and reviewed after processing. We are looking for the College of the Desert Registrar team to verify those 28 transcript files as accurate once the upload is completed with XAP and that processing is completed. If they are not approved, then we will be looking for feedback and can make any adjustments or schedule follow up. If they are approved, we are ready to schedule go live. Then we can get Florante some assistance on bulk upload formatting verification, as this is not part of what my team handles directly, but we'd be ready to move forward with our last steps if samples are approved." Will wait to see what the college responds with.Feather River 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.2021.24: Sent email again asking for a call to get kicked off. Contact Scott advised he is a CISOA and will respond when they get back.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) 3 4.141.24: Met with Merced/Parchment/XAP and there are still issues with them getting sample files. Parchment will attempt to get those resent and when they do they want to give the school ime to review and then meet with them again. Todd when then schedule a meeting. Will flw up by April 4 if no response. Also - college brought up the lived name and preferred name new assembly bill. Amanda/Sean/Courtney to work on this as we have time to get this implemented.Napa Valley CCD - 3.5.24: Napa Valley College and Parchment troubleshooting back and forth via email.

• Napa Valley CCD - 3.5.24: Napa Valley reached out and advised they are ready to meet for next steps. Amanda scheduled meeting for April 3rd.

• Porterville - Kern CCD: 3.2125.24: Emailed the A&R team to inquire about how they are sending transcripts. IT appears they have stopped sending. 25: College responded with this, "Marie will be leading this and will follow up." If no respond by 2nd week of April - Amanda to flw up."

• Palo Verde CCD - 3.2125.24: Sent email to Shelly at the college and requested a meeting for kickoff.

• Peralta CCD (ECA) 3.21.24: Sent email to Dominique to advise we need to meet/get this project back on track since they are a live P2 teaching college. If no response, will have Mike escalate by 4/4.

• Riverside 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.2125.24: Met with Nicholas and Sean answered the questions but needs to consult with the IT staff on one question. Sean to get back to them. Emails still going back and forth with troubleshooting questions.

• San Diego CCD (ECA) 3.21.24: Sent follow up email to see when everyone can meet. From there, Amanda to schedule.

• San Francisco CCD 3.21.24: Sent email to the college to schedule a call to go ahead and start the process for setting up eTranscripts. As soon as they respond, I'll schedule a call.

• San Joaquin Delta CCD (ECA) 3.21.24: Sent email to college and Parchment asking them to provide status/update/next steps

• 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 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.1.24 - Sent email to college and XAP to see if we need to meet to get the issues taken care of.

• San Diego CCD (ECA) 3:25.24: Colleges responded and I sent out a calendar invite for April 2nd to meet to have the kickoff meeting with Parchment.

• 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) 3.11.24: Received signed contract and sent to Sean. Emailed Sean and the college to ask if Sean sent test files yet/needs users set up for accts or password resets. Amanda to flw up on 3.14 if no response.

• 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 - 3.18.24: Parchment/college are actively testing. Error with the log file on the Parchment side. Will continue to follow.

• 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) 11.2.23 - Per Mike - hold off since they dont have a cohort established.

• Yosemite CCD (ECA) -3.20.24: Live for sending eTranscripts via XAP!

• 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.

Tracking HC and TC transcripts here: https://docs.google.com/spreadsheets/d/1e3Nq1Kt3qACJLqN4nWfmP-mWjdgK8_fSLiQb_ufBjdE/edit#gid=48089342

/wiki/spaces/CVCOEI/pages/1749647361

/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

3/22/24

• 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.1.24: Todd from Parchment emailed college to check on status/updates.

• 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.

Tracking HC and TC transcripts here: https://docs.google.com/spreadsheets/d/1e3Nq1Kt3qACJLqN4nWfmP-mWjdgK8_fSLiQb_ufBjdE/edit#gid=48089342

/wiki/spaces/CVCOEI/pages/1749647361

/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

3/28/24

4/26/23

9/14/23

10/17/23

11/9/23

11/13/23

12/10/23

1/11/24

411/2620/2324

93/145/2324

103/1712/2324

113/913/2324

113/13/2324

123/1015/2324

13/1124/24

113/2025/24

3/29/24

idP/EPPN

4.27.23

4.1.24

Financial Aid Integration

6.8.23

1.23.24

Product Maintenance

1.18.23

1.18.24

Reverse Import

5.17.23

2.6.24

eTranscripts

3.2.23

1.23.24

Financial Aid Integration

6.12.23

3.14.24

Preferred Name

10/10/23

1.16.24

idP/EPPN

4.27.23Preferred Name

10/10/23

2/22/24

Financial Aid Integration

2.22.23Seat Counts

10/16/23

2/23/24

3.28.23

Financial Aid Integration

Program Code

7/6/23

2.6.24

6.8

Financial Aid Integration

Sync/Asynch

7.13.23

12.2314.24

Product Maintenance

1.18.Admin Panel

11/28/23

1.184.24

System Enhancement

7.26.22

12/21/23

Preferred Name

10/24/23

1.10.24

Reverse Import

5.17.Sandbox

12/19/23

2.6./22/24

eTranscriptsPreferred Name

36.26.23

1.239.24

Error HandlingFinancial Aid

76.512.23

1.9.24

ASSIST FileFinancial Aid

711.242.23

2.13.24

4.22.23

Student Eligibility Checker

UI Language update

10/18/23

3.28.24

Documentation

12.3.21

Seat Filter

11.9.23

3.1.24

6.12

Financial Aid Integration

eTranscripts SaaS

3.5.23

3.1427.24

Financial Aid Integration

10/10/23API

3.18.24

3.20.24

Preferred Name

10/10/23

1.16Search

3.15.24

3.25.24

Admin Panel/Reporting

10/10/23

Accessibility

10/12/23

UI Updates

3.18.24

3.29.24

Analysis & Documentation

2.29.24

Session Management

11.21.23

Session Management

11.21.23

Financial Aid Integration

2.29.24

Financial Aid Integration

4.19.23

Financial Aid Integration

2.22.23

SaaS

2.9.24

Search Engine

6.12.23

Canvas

2.

13.24

eTranscripts

9.

12.23

C-ID

3.21.24

Drop Email Notifications

3.26.24

eTranscripts

9.12

.23

Financial Aid Integration

9.14.23

Documentation

12

.3.21

Admin Dashboard

7.12.23

Financial Aid Integration

10.16.23

Address Verification

11.

2.23

Payment Processor

11.

17.24

Course Audit

2.6.24

Program Code

2.

27.

24

Term Activate

11.

21.

23

Student Eligibility Checker

4.22.21

API

4.

14.