Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Page Properties
idjirareport


Date

July 11, 2019

Issues
Jira Legacy
serverSSDT JIRA
jqlQueryproject = USASR AND fixVersion = v7.21.0 ORDER BY key ASC
counttrue
serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca


Build Date

18:10:05


Summary

This release contains bug fixes, exciting new features and various report and performance improvements as detailed in the release notes below.

Important Highlights

  1. Performance improvements have been made to posting payables, budget scenario promotion to proposed amounts and accounts.
  2. Added a rule to prevent posting payroll disbursements if the accounts are inactive.  This rule is not mandatory but is enabled by default.
  3. Restrict requisition only users from seeing the ACH fields on the vendor.
  4. Canceled items on the printed PO will now display with a "C" before the item as they did in Classic.
  5. Corrections to totals on the Spending Plan Comparison report.
  6. The remaining balance calculation in the Fund UI has been corrected.Performance improvements have been made to posting payables, budget scenario promotion to proposed amounts and accounts.
  7. Corrected problem with Mass Load accounts.
  8. Updated downloadable report link to be shareable with others.
  9. The Listing of Transactions by Account report has been corrected to include received amounts.

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


Reported Performance Problems

We are working to improve performance in the following areas as reported through feedback.

  1. Cash Reconciliation 
    Jira Legacy
    serverSSDT JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSASR-3654
  2. Grid loading 
    Jira Legacy
    serverSSDT JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSASR-3123

Known Limitations

  1. There are several reported issues with the new AP Invoice UI.  We are leaving it in the application so users can take advantage of the grid but suggest using the AP Invoice (Legacy) option until the following issues are resolved:
    1. The invoice and canceled totals don't populate until after the invoice is saved.  
      Jira Legacy
      serverSSDT JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
      keyUSASR-3806
    2. An error is occurring unless you invoice all items on the po.  The items that do not have a status (because you aren't invoicing them) are being caught by a rule that is preventing the posting of the invoice.  
      Jira Legacy
      serverSSDT JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
      keyUSASR-3861
    3. If an item is canceled and then changed to a non-canceled status prior to saving the invoice the outstanding flag is not being updated properly.  This results in an invalid outstanding value and the user will receive a severe error and will be unable to save the invoice.  
      Jira Legacy
      serverSSDT JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
      keyUSASR-3840
  2. The SSDT Revenue and Expenditures by Cash Account and by Fund reports have a grand total that sums the Revenue and Expenditure amounts, which is not accurate for this report.  The Classic FNDREVEX shows a difference (Revenue - Expenditures).   These reports cannot include a difference as template reports.  We will need to create a canned report in order to "correct" the grand totals and include the difference. USASR-3693 - Correct totals on both SSDT Revenue and Expenditure reports (FNDREVEX) NEW

Upcoming Features

  1. The ability to mass add accounts, for example taking an existing grant account and copying the account hierarchy to a new account. 
    Jira Legacy
    serverSSDT JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSASR-596
  2. Recreating Classic's PAYABL report.  This will be implemented as a canned report because the query required is too complex for it to be a template report.  
    Jira Legacy
    serverSSDT JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSASR-2570
  3. Removal of Legacy Requisitions 
    Jira Legacy
    serverSSDT JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSASR-3843
  4. Various improvements to the new AP Invoice UI. For details see "Known Limitations" above.
  5. Schedule-able report process to replace Classic's MonthlyCD program


Issues included on this release

Jira Legacy
serverSSDT JIRA
columnskey,summary,type,status,resolution
maximumIssues20
jqlQuerykey in (USASR-3522,USASR-3571,USASR-3642,USASR-3656,USASR-3728,USASR-3737,USASR-3741,USASR-3747,USASR-3750,USASR-3760,USASR-3765,USASR-3771,USASR-3775,USASR-3782,USASR-3784,USASR-3787,USASR-3790,USASR-3804,USASR-3805)
serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca