USAS-R v7.34.1-7 Release Notes

Summary

This is the first hotfix release for version 7.34.  This hotfix includes the following:

• The account change process has to reopen and then close the posting periods in the current fiscal year in order to make the requested account changes.  The newly added monthly report bundle is triggered by the closing of posting periods.  We updated the code to ignore the closing of the posting period if it is due to the account change process.

• A correction to the calendar year report bundle to ensure the starting date is January 1 of the calendar year being closed.  The reports included the correct date range but the event that triggers the report bundle to run inadvertently overrode the start date to the first day of the posting period (12/1) instead of using the first day of the calendar year.  See below for steps to recreate the CYE report bundle.

• A correction to a method that retrieves the default 1099 location.  Previously this method would throw an exception if the vendor did not have a default PO or 1099 location because the 1099 extract requires it.  However we moved the code that requires the locations to a new method so the Vendor Listing report in the monthly report bundle would not fail if vendors did not have locations.  This problem revealed itself with "Template Vendors", which are vendors imported from Classic because there were transactions posted against them, but the vendor was no longer on file.

• A discovery patch is included in this hotfix to determine if any districts have problems with encumbrances related to a patch that went out in December.  We had a district report problems due to the patch that updated more POs than it should have.  This edge case may have impacted other districts, so this discovery patch will run for all districts and send back information to SSDT if there are problems detected.  If so, SSDT will be in contact with the ITC so corrections can be implemented for the district.

Steps to generate the SSDT Calendar Year End Report Bundle if December was already closed.  This is a one time step in order to regenerate the 2019 Calendar Year End Report Bundle due to the reported bug.  This will require reopening the period, which we typically do not encourage for the sake of running bundles.  If the district does not want to reopen December, a future change will allow running bundles for specified periods without reopening them.

1. In order to generate the CYE bundle and not rerun the December Monthly Report bundle, the SSDT Monthly Report Bundle will need to be temporarily disabled.  To do this the ADMIN_REPORTS permission is required.  If the user who will be disabling the report bundle does not currently have the ADMIN_REPORTS permission, a new role should be created with this permission.  Then, this role can be assigned to the user who will need to disable and then re-enable the bundle.  

2. Disable the SSDT Monthly Report Bundle

   1. If you wish to delete the December archive and rerun the calendar and monthly report bundles to avoid duplicates, do not disable the monthly report bundle.

3. Reopen the December posting period and make sure the process finishes.  This shouldn't take long, you'll just want to make sure the blue process indicator (line) is not flashing and is not visible.

4. Close the December posting period.  This will trigger the event that runs the Calendar Year End Report Bundle.  Once complete, the reports will appear in the Monthly File Archive along with the December monthly reports.  These reports are prefaced with"Calendar Year End" in the name.  For example "Calendar Year End 1099 Vendor Report.pdf"

5. Edit the user to remove the newly granted permission.

A hotfix or quick-fix is typically a single change that addresses a problem in the software.  Hotfixes are made to address a specific concern and provide a quick solution.

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 Documentation. There is a section in the documentation that also details the significant changes between USAS-R and classic USAS. 

Issues included on this release