UCPath 1.3-1.10

UCPath Changes & Enhancements:  January 03, 2024 – January 10, 2025

 UCPath recently implemented the change listed below.  Refer to the  UCPath Changes & Enhancements link on the Location Support site for additional detail.

 Cognos Reports

Summary

Date

Change Request Number

Developed a Cognos report for Corporate Accounting to determine employer Social Security and Medicare tax rates on vacation earnings, as required by GASB No. 16.

01/09/25

UCP-154194

 General Ledger

Summary

Date

Change Request Number

Updated the Labor Ledger process (E-714) so the journal line reference for systemwide assessments is run Id and for uc_burst_bu to populate for all assessments.

01/06/25

UCP-159366

 Payroll and Compensation

Summary

Date

Change Request Number

Created an interface to capture GSR annual reporting data from UCPath and transfer it to TAB services for the 1098-T end process.

01/06/25

UCP-151768

 Systemwide Reporting

Summary

Date

Change Request Number

Added a position number column to the Escalation/Reminder of Approaching Job End Dates (R-384) report.

01/08/25

UCP-158584

 Workforce Administration

Summary

Date

Change Request Number

Renamed the patent amendment pages in the UCPath portal pages to "Patent/IP Acknowledgment."

01/08/25

UCP-150781

Updated code to the IDM – CUSTOM UC ID (I-262) process to allow the new external system ID with a unique effective date and ID type.

01/06/25

UCP-159522

 The following changed will be visible on Saturday, January 11, 2025.

Salesforce

Summary

Change Request Number

Included a "cancel inquiry" button throughout the Updated the SOBO Case Submission form.

UCP-149514

Enhanced the AskUCPath main home page with "My Open Inquiries" and "My Closed Inquiries" directly from "My Inquiries."

UCP-137787

Updated the email threading method for inquiries from Ref ID strings to a secure Thread ID.

UCP-113593

Did You Know: Using "xx/xx/9999" as the Expected Job End Date can cause downstream impacts that affect critical processes, such as benefit eligibility. To ensure smooth processing and avoid errors:

  • Do not use "xx/xx/9999" as the Expected Job End Date.
  • If an employee has an indefinite end date, proceed to leave the field blank. This will help ensure smooth batch runs and prevent errors.
By following this best practice, you'll help prevent downstream issues, improve data integrity, and maintain accurate benefit eligibility processing.