USAS v2025.4.0 Release Notes
Date | Mar 14, 2025 |
---|---|
Issues | Getting issues... |
Build Date | Mar 12, 2025 4:09:20 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 ability to mass post Requisitions via CSV has been implemented. A new Import button available on the Requisition grid will allow uploading a CSV file, similar to the Import button on the PO grid. The user documentation for this feature along with a template CSV load file will be available soon.
Users that do not have the ADMIN role, but have been granted the permission to allow changing user passwords can no longer change the password for a user with the ADMIN role.
Bug Fixes/Patch
Refund import corrections
updated to properly handle posting period violations. The posting periods associated with both the refund date and check date must be open to import transactions.
updated the importer to require the check date if the refund has an associated check. The import option will not provide a default check date value if a check is to be created.
updated the importer to cope with invalid bank account values
Corrected the handling of Payables when unvoiding a void disbursement. When a disbursement is marked void but the invoices are not voided, those invoices are visible in the Payable UI. If the disbursement is then unvoided, the associated payables are again linked to the outstanding disbursement and will no longer show in the Payable UI. The initial implementation of unvoiding disbursements handled this properly, but a subsequent change broke this behavior. The offending code has been corrected.
Internal
Add Public Rest API key filters and authentication providers