USAS v2025.8.0 Release Notes
Date | May 9, 2025 |
---|---|
Issues |
|
Build Date | May 7, 2025 12:41:01 PM |
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 updated to include a Running Fund Balance (RFB) column. This column will appear when the start date is either the first day of the current posting period (cpp/01/yy) or the first day of the fiscal year (7/1/FY). The RFB column will replace the Remaining Encumbrance column.
Note: additional refinements will be released in the future to allow the RFB column to be displayed when the starting date is the first day of any posting period. We also plan to update the RFB column to be labeled as Ending Balance when the summary report is generated, and we will increase the amount columns to ensure values up to $999,999,999.99 will display properly without wrapping.
Implemented a user hard lockout in USxS. The User record now contains a new read only field called “Failed Attempt” which is incremented each time a user logs in with bad credentials. When the user account is locked they will receive an error message stating: “Login Failed. Your account has been locked.”
Permissions: only a user with edit permissions for the User can lock or unlock a user account from the new grid button on the User grid.
User record changes: the new read only “Failed Attempt” field is visible and the “locked” boolean is now read only. The only way to unlock the account is via the button on the grid.
Grid button: a new lock/unlock button is on the grid. This button displays as a closed padlock if the user account is locked or an open padlock if the account is unlocked.
Failed Attempt behavior: once a user account is unlocked, the value of “Failed Attempt” is reset to zero. If the Failed Attempt value is less than 5 and a user logs in successfully, the Failed Attempt counter will reset to zero.
If a user account is locked, the user will not be able to change the password on the account until the account has been unlocked.
Date Range validations have been added to calendar date fields. Any calendar date value will now be validated to ensure the entered value is a valid date. A valid date is any date that falls in the range of 01/01/1900 and 12/31/2100. If a value that falls outside of that range is entered (01/01/21025), the date field will display in red. A tool tip is available which states: “Date must be between 01/01/1900 and 12/31/2100”.
We have refactored the code related to updating distributions, refunds and interfund cash transactions (transfer and advances) when processing an account change to improve the performance of updating these transactions.
Bug Fixes/Patch
Standard USAS users now have the ability to process an account change. Previously they could apply the account change job but it would fail with access denied errors.
The account code selection on the Account Change Request is now properly filtered for the type of account the Account Change Request is being created for. If you create an expenditure account Account Change Request, the “to” and “from” account selection drop down boxes will only contain Expenditure accounts. The same holds true for Revenue as well.