Summary
This release contains bug fixes and report improvements as detailed in the release notes below.
Important Highlights
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.
- Transfer/Advance improvements
- The time frame for repaying Advances that restricted users to the same or next fiscal year has been removed. Per AOS, it is the district's responsibility to know when and how the advance is to be repaid.
- Restrictions per AOS on the accounts to be used when processing Advances (In and Out). The AOS USAS manual specifies the accounts to be used and the software now enforces that. Districts will no longer be able to "back out" an Advance in order to repay it. Please see the AOS USAS Manual for Advance Account dimensions for details. We are still waiting to hear from AOS on the use of the 910 and 920 object codes, so until we hear otherwise those object codes can be used.
- The ability to link the Advances to their Repays that were posted in Classic prior to migrating to the Redesign. The documentation for this new feature will be available soon and a link will be provided here when it's ready. Users will view an Advance and via a table on the transaction be able to link existing Repays to that Advance by clicking on the button.
- We've also created a template report to assist districts in linking their Classic advances and repays in the Redesign. Remember, Repays are no longer visible from the Transfer/Advance grid, Please see the SSDT Transfer Advance Activity report for a list of your Transfer, Advance and Repay transactions. This report is organized by Cash Account.
- AP Invoice (Legacy) has been removed from the application.
- Recent FY20 Subject Code changes have been implemented in Redesign.
- Corrected a problem when attempting to filter by properties on the InvoiceItem. This corrects problems reported when running the SSDT Inveotry Pending Extract and filtering Invoice reports by created user.
- Improvements to canned reports:
- The ability to include an options summary page has been added to canned reports. When "Show Report Options" is checked the report generation will include an options summary page showing the parameters selected. This option is checked by default on the canned reports.
- The ability to choose the report format style has been added to the canned reports available from the Report menu. This was available on other canned reports previously. Please be advised, due to the way these canned reports were written, we were unable to make the following formats available at this time: Excel-DATA, Excel-FIELDNAMES, Comma Separated Values (CSV) and Tabbed Separated Values.
- Corrected a problem with rules that were causing the Account Change process to fail. These rules have been updated to not run during Account Change as they have no impact on this process.
Reported Performance Problems
We are working to improve performance in the following areas as reported through feedback.
- Districts with a large number of accounts experiencing slowness Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
- Improve the performance of the Appropriation Resolution report generation
- The report button on the Activity Ledger grid does not produce the report generation popup as quickly as other grids
- Improve the time it takes to generate the Revenues and Expenditures report
- Budget Summary report generation performance needs to be improved
- Financial Detail July 1 Cash Balance report generation performance needs to be improved
Upcoming Features
- Mass change definitions will be available in the documentation to update your invoice item received dates to equal either the invoice date or the vendor's invoice date.
Issues included on this release