Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Releases Since Our Last Meeting (04-17-2019)

  • USAS-R V7.19.0 Release (4/25/19)
    • Implemented State Treasurer's Online Checkbook export file 
    • Various improvements to the Budget Scenario interface including the ability to clone scenarios.  Any new scenarios created after this release will be able to be cloned.  Scenarios created prior to this release cannot be cloned.
    • Updated the budgeting worksheets to put each prior year's amounts in separate columns.
    • Improved the Five Year Forecast extract to include expendable and receivable amounts.  We've also improved the grid sorting so that within forecast line number the lines show in account code order.
    • Added username to the Activity Ledger.
    • Corrected a problem with the CSV format with regard to commas.  Commas in item descriptions was causing data to shift and not appear in the appropriate columns.  We've also updated the CSV option to use data from the extended report properties, overriding column names for example.
    • Updated the USAS_MANAGER role to include permissions for the Mass Load option and Transaction Configuration.
    • Corrected a problem with the check number not printing on Refund checks, PDF and XML formats.
    • Improvements to the Financial Detail Reports.
      1. Improved report titles so user can easily distinguish between the three available versions.
      2. Corrected the ending balance on the Financial Detail Report July 1 Cash Balances.
      3. Corrected a problem with encumbrances not appearing on the Financial Detail report.  This was due to the PO transaction type incorrectly being excluded.
    • Improved performance of posting payables to disbursements.  Users should see a significant improvement with performance.
  • USAS-R V7.19.1 Hotfix (5/1/19)
    • Allows the user to determine which bank account will be the default bank account.  The bank account permissions are available to the group manager role and higher.  The standard user role does not include the bank account permission.
    • Allows the user to select the bank account they wish to use when processing a Refund with a Check.  The bank account drop down will initially be populated with the bank account that is selected to be the default bank account.  The user can select another bank account if desired.  The bank account selection will be read-only unless "Create Check" is selected.
  • USAS-R V7.19.2 Hotfix (5/6/19)
    • 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 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.  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. 
      • The Admin role will 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.
  • USAS-R V7.19.3 Hotfix (5/9/19)
    • corrects a problem with the CSV report format option with regard to the handling of double quotes.  Users are including double quotation marks (") in the item description of the Requisition and it's causing problems with the RAM extract.  We attempted to fix this on the previous hotfix, but ended up breaking the CSV report format.  This problem has been corrected.

Upcoming Scheduled Releases

  • USAS-R 7.19.4 Hotfix (anticipated later this week)
    • Improvements to the usasimport.log and System/Monitor Status tab to properly report job status.  We've also added a message to the Posting Period tab to report on the health of the application.  If an import or post import job did not successfully complete, the following warning message will display:  "There was a problem during the post import process; not all jobs completed successfully.  Check the import log for errors."
  • USAS-R 7.20.0 Release Scheduled Issues (anticipated next week)
    • Adding the "as of period" parameter to all applicable objects to allow adding this user parameter to additional reports, including account summary and the financial detail report.
    • AP Invoice has been rewritten into the new Vaadin format
    • Implement reporting levels for account code dimensions
    • Apply account filters to all detail reports, regardless of entity.  
    • Implement vendor tax identification number configuration
    • Implement auto assign preferences for requisitions
    • Implement balance validations for future year requisitions and purchase orders
  • No labels