USAS v2025.10.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 canned Financial Detail report has been improved to include a selection option so the end user can choose to display the Running Fund Balance or the Encumbered amount on the report. In order to include the Running Fund Balance, the start date for the report run must either be the first day of the current posting period or the first day of the current fiscal year. If the option to Display Running Fund Balance is selected but the start date is other than what was specified in bold above, the option to display the Running Fund Balance will be disabled and the Encumbered amount will be displayed. Tooltips have been added to the UI for clarification.

• The canned Purchase Order Detail report has been updated to include the following fields when generated in Excel-data format only. This was done to assist with records requests.

  • unit price

  • quantity

  • vendor number

  • attention

• Improvements have been made to validating accounts with respect to AOS controlled dimensions (fund, function, receipt, object, IL and job). When AOS releases changes to the account code dimensions, we can now specify start and stop dates on those dimensions to control/prevent usage based on those dates.

  • Accounts with FY restricted dimensions will be able to be created in advance of the intended FY and users will see a warning informing them of when the account is available to be used. Creation of accounts containing a code dimension with a date range defined will require a start/stop date to be defined. The account start/stop dates will be populated by default with the latest start date and the earliest stop date from the code dimensions. If none of the code dimensions are date restricted, the start/stop dates will not be automatically populated.

  • Date-restricted accounts will not appear in the user’s account drop downs when selecting accounts on transactions unless the transaction date falls within the account’s usable date range.

Internal

• Upgrade Gradle version, standardize directory structure and use JVM TestSuite for integration tests

Issues included on this release