| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
...
Bug Fixes
- Corrected the refund to prevent modifying the transaction if there is an associated check. Refunds with checks are not modifiable.
- If the refund/check need to be updated, instead the check can be void and a correct refund reissued.
- If the refund/check need to be updated, instead the check can be void and a correct refund reissued.
- Improved the Appropriation Resolution report "zero balance" option to ensure that accounts that sum or balance to zero are not being excluded. Only those accounts that have zero amounts for all fields are excluded. The FYTD Appropriation Carryover and Totals report was not properly applying the "Include Accounts with Zero Balances" option as accounts that summed to zero were also being excluded.
- Periodic > Appropriation Resolution Report
- Periodic > Appropriation Resolution Report
- Corrected a bug that allowed the July 1 cash balance to display as 0.00 in the specific case where June is closed and the system creates July (July doesn't exist before closing June).
- Corrected a bug on Proposed Amounts grid when attempting to Apply as Temporary or Permanent budgets for the next fiscal year. Error message indicated that it required the effective date on the initial transaction to be in the current fiscal year. That is not the case - Temporary or Permanent budget amounts can be posted for the next fiscal year while still in the current fiscal year. If July of the next fiscal year posting period does not exist, it will be created.
- When Applying proposed amounts as Adjustment type, the date IS required to be in the current fiscal year. This is intended to prevent issues with mis-keyed dates that we've had reported previously.
- When Applying proposed amounts as Adjustment type, the date IS required to be in the current fiscal year. This is intended to prevent issues with mis-keyed dates that we've had reported previously.
Improvements
- Improved the message displayed when scenarios are promoted to proposed amounts to include "ALL existing proposed amounts, both Expenditure and Revenue," for clarity.
...
- Corrected an error from a change made on the 1.33.0 release. When deleting transactions or splitting items (where original tag is deleted) it generated an errorrelated to constraints recently added to the audit table. This caused an error to occur when deleting an acquisition, disposition or transfer transaction. It also caused an error when attempting to split an item. error message. This was fixed on the 1.33.1 hotfix.
- System>Configuration>Migration Import - Corrected the Migration Importer for Acquisitions to allow importing multiple acquisitions for an item.
Improvements
Internal: Implemented intrusion detection in Inventory like exists in USAS and USPS. If an intruder is detected, the login attempt fails and this results in a generic "Bad credentials" response being returned to the user.
- Audit Reports>Audit Report performance improvements have been were made, which will also positively impact impacted the report bundle generation. Any district that migrated prior to April 2022 will see the most benefit (75-80%) as we are now excluding the initial migration audit entries for everyone. Additional improvements are underway on subsequent JIRA issues (INV-460 and INV-439).
New Features
N/A
Patches
N/A
...