Page Comparison

...

Summary

This is the second hotfix release for version 7.19.  This hotfix contains the following improvements:

• The budgeting worksheet reports have been updated to move the account code and description into a detail header to allow for more room for the amount columns.  We've also summed the next year proposed amount as this was previously missed.
• Users should now be able to re-open a PO by amending and canceling a charge, deleting invoices or voiding a disbursement (with or without removing invoice items)that was imported from Classic.  When a user cancels a charge, deletes an invoice or voids a disbursement the encumbrance amount should adjust to reflect the action and the PO will be at an invoiceable status once again.  The user should We have also added a view option to the purchase order charge that will allow users to see the impacts on encumbrance created for that charge.  
  • The Group Manager and Standard USAS roles will have the ability to view the encumbrance impacts for all charges and also view the legacy PO status and legacy outstanding values if it is a legacy charge, meaning the charge was created in Classic and imported into the Redesign. 
  They
  • The Admin role will
  also
  • be able to add/remove adjustment impacts if the charge is a legacy charge and the effective date of the impacts are in an open posting period.  The ability to see and modify encumbrance impacts on the charge is specific to the USAS_ENCUMBRANCEIMPACT permissions.  This has been put in place to assist with balancing Redesign to Classic after import when no other cleanup option is available.  It is recommended that ITCs should consult SSDT before adding or removing adjustment impacts on encumbrance.
• The RAM extract has been updated to properly cope with quotation marks when used in the item description.
• The purchase order remaining encumbrance was not properly updating after posting disbursements due to a recent performance improvement.  The accounts reflected the correct amounts, but the purchase order totals were incorrect.  
• A problem caused by the previous hotfix that prevented standard usas users from processing positive pay.  The permission needed was removed from the standard usas user role, but has been corrected.

...

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

Issues included on this release