Releases Since Our Last Meeting (3-18-2020)

Corrections to Transfers and Advances
- A problem viewing these transactions that were created in the Redesign before January. We implemented posting the created date on Transfers and Advances with the 7.32.0 release. Transactions posted prior to that release do not have a created date populated. This resulted in a null pointer exception when attempting to view these transactions which has now been corrected.
- A problem repaying Advances that were created in Classic. Advances posted in Classic have a slightly different transaction type associated with them vs Advances posted in the Redesign. When repaying the Advance we were incorrectly looking for the type associated with being posted in the Redesign instead of both Classic and Redesign types. We've updated the code to check for both types allowing users to repay their Advances regardless of which application they were posted in.
Corrections to the Appropriation Resolution report. The report was not displaying the correct values for the Appropriated amounts and has been corrected. The report options page was showing the default values instead of what the user selected when generating the report. The report options page will now correctly show the options selected by the user when the report was generated.

Refactored Budgeting transactions to better handle temporary and permanent transactions.
Clear user parameters when switching between saved report runs.
Include the district name and date range in report header.
Improved the column widths on the Budget Summary report to help prevent wrapping of amount values.

A correction to the ledgers that are posted when repaying advances. The ledger entries created as a result of the posted repay transaction were incorrectly being negated when posted. This has been corrected and any ledgers that were previously posted incorrectly will be deleted and reposted with this hotfix.

Improved the message results when reconciling checks to better distinguish between warnings and errors. Also corrected a problem with the vendor tax id rule so that it no longer inaccurately produces an error when reconciling, un-reconciling or voiding disbursements.
Adding all US territories to the valid list of 'state' abbreviations.
Corrected a problem that prevents the application from restarting if the application configuration is modified.
Implemented the requires budgeting flag, formerly known as "budget bypass" flag in Classic. This will allow districts to override balancing checking at the fund level. The field is available from the Cash Account but wasn't previously implemented.
Improved performance of the account sync process between USPS and USAS by 83%.
Improved performance of the Account/Fund UI grid loading and data retrieval by 90%.

Upcoming Releases

2

Corrected the permission on the retreival of the Organization name. The permission previously required was preventing cron jobs from generating.

USAS-R v7.40.0

Performance improvements to the Appropriation Resolution report.
Correct erroneous GLJournalEntry ledger from being created for advances repaid in Classic prior to migration. The additional ledger is inflating expended amounts for repays linked in the current fiscal year.
Implement a "Generate and Submit" button to allow districts to auto send the file directly to TOS instead of manually uploading the file.
Update rules to be ignored when processing Account Change.
Correct the amount being shown in the negative cash balance warning when reconciling a disbursement. The amount was being removed twice, inflating the negative value being shown in the rule warning. The amounts on the accounts and transactions were correct.

...

Improve the performance of posting POs from Pending Transactions
Implement a "Generate and Submit" button to allow districts to auto send the file directly to TOS instead of manually uploading the file.
Correct problem with Reporting Period displayed on report headings
Write a custom rule to prevent back dating Requisitions
Vendor Ledger improvements
Correct problem with expended and expendable amounts being stored on the Budget History
Correct problem with cron job execution related to Organization name security