USAS v2024.12.0 Release Notes

Summary

This release of USAS-R contains the following improvements detailed in the release notes below.  Please keep in mind these release notes only reflect the changes included in this release.  There are many other features of the software that were previously released that will not be reflected in these release notes.  General information about all of the features available in USAS-R can be found in our USAS-R Documentation.  There is a section in the documentation that also details the significant changes between USAS-R and Classic USAS. 

Important Highlights

Improvements 

• The Accounts Payable Report can now be generated in CSV and Excel-data formats.  The CSV fieldnames format has been removed.

• The ability to unmerge vendors has been implemented.  This process will effectively undo previously merged vendors.  The vendor(s) that were previously merged will become active and unmerged.  Transactions that were previously merged will be updated to restore the original vendor.  Vendor amounts will reflect the changes to the transactions.  Documentation for this new feature will be available soon.

• Five Year Forecast has been updated to remove lines eliminated by ODE in 2019.  The following lines have been removed:

  • 21.010,,,,0.0 

  • 21.020,,,,0.0 

  • 21.030,,,,0.0 

  • 21.040,,,,0.0 

  • 21.050,,,,0.0

  • 21.060,,,,0.0

Bug Fixes

• A problem with the Save button on the Report Scheduler has been corrected.  The button did not appear as enabled when it should have.

Internal

• REST Controller for Civil Proceedings

Please be aware of a potential caching issue with carryover encumbrances.

We recently discovered a problem with caching that may impact the value you see for carryover encumbrances.  The value stored in the application is correct, however the value stored in the cache may be stale or out of date.  If you suspect a problem an easy way to flush the cache is via the System/Monitor/Cache tab.  You can delete the calcPriorYearEncumbrance cache (near the bottom in the list) which will remove the cached value.  

We have created a Jira issue to fix the caching problem and will release that change via hotfix next week.

The only use case for the cache to become stale: If a district is in FY 24 and the carryover is cached, meaning it was retrieved by viewing an account or running a report that includes carryover. Then the districts updates the current posting period to FY 25 and runs reports or views a cash/appropriation/expenditure account without processing any encumbrance related transactions.  

Issues included on this release