Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Import Link Fixer



Page Properties
idjirareport


Date

January 22February 17, 2019

Issues

Jira Legacy
serverSSDT System JIRA
jqlQueryproject = USASR AND fixVersion = v7.16.0
counttrue
serverId925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6

Build Date2019-0102-22 14 10:0743:0201


Summary

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

Important Highlights

  1. Legacy views have been removed: Refund, Adds/Deducts and Show Sessions.
  2. Corrected the missing comma in the vendor name on the 1099 report and XML extract.
  3. Improved positive pay to allow for full checkdate field and commas in vendor names.
  4. Updated various reports
    1. Outstanding Disbursement report will now provide date defaults and will show only outstanding disbursements.
    2. Listing of Transactions by Account report has been modified to remove redundant encumbrances.
    3. The Spending Plan Summary report has been updated to indicate required user parameters.
    4. The SSDT 1099 Vendor report displays the taxable ytd amount for the vendor.
    5. The Financial Detail report will now be available in two options.  The first (existing version) will allow users to enter a date range to generate the report for and will NOT include beginning and ending balances.  The new version, Financial Detail Report for Current Period, will include beginning and ending balances but will only generate for the current period.
  5. Implemented the Classic FNDREVEX report as 2 template reports.  Note: see known limitations below.
    1. SSDT Revenue and Expenditure report by Fund
    2. SSDT Revenue and Expenditure report by Cash Account
  6. Allow user to link payee id from usps pending transaction to usas vendor.  If the pending transaction contains a payee id it can be linked to a usas vendor, if not a usas vendor can still be selected to apply to the transaction being posted as a result of accepting the pending transaction.
  7. Updated the requisition import to not import requisitions that were converted to POs in Classic but then the PO was deleted.  These requisitions were imported into the Redesign as "open" and were impacting preencumbrance amounts.  In Classic these requisitions shown as "closed" and did not impact preencumbrance amounts.
  8. Updated to allow all "open" requisitions in archived periods be modifiable and deletable, regardless of posting period.
  9. Report tagging is now user based.  This means you can edit any report and add tags to it, even SSDT versionsproblem with page break option that previously prevented template reports from generating.
  10. Improved the import process by removing the posting of encumbrance ledgers.  This should shorten the time it takes to import the data.  Encumbrance ledgers are posted during the post import process.
  11. Created the Appropriated Amounts by Cash Account report which includes the percent expended/encumbered.
  12. Created report to show budget modifications: SSDT Budget Transactions
  13. Removed legacy code for printing Requisitions, Purchase Orders, Receipts and Refunds and replaced with the ability to print as xDocReports.
  14. Implemented the ability to batch print pdf Receipts for HCC OnBase implementation.
  15. Corrected an error that prevented generating a report from the Payable grid.
  16. Improvements were made to the descriptions on the receipt template reports so it's clear to the user which transactions will be included.
  17. Created a new interface System/Configuration/Application Manager to provide a way of disabling 'external notification' on a test or support instance.  For example, a backup instance of a district's database running on a test instance for support purposes.  The database could contain scheduled jobs, like RAM for example.  In order to prevent external notifications from a test instance, you can modify the docker-compose.override.yml to set the following environment variable: APPLICATION_INSTANCE_TYPE=support.  You can also set this by modifying the Application Manager within the application.  Please be aware that the environment variable will be overridden by changes made via the Application Manager.  The instance type defaults to 'production' unless otherwise modified, either via the docker-compose.override.yml or via the Application Manager.


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. 

Known Limitations

Restricting uses to specific requisition prefixes is currently broken.  


Reported Performance Problems

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

  1. Disbursements
    1. Navigating from Payables to Disbursements
    2. Reconciling/Unreconciling 
      Jira Legacy
      serverSystem JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId6d21ed14-3f48-3cc2-ad28-6548879d10d6
      keyUSASR-3582
  2. Purchase Order item entry 
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6d21ed14-3f48-3cc2-ad28-6548879d10d6
    keyUSASR-3508
  3. Closing windows 
    Jira Legacy
    serverSystem JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId6d21ed14-3f48-3cc2-ad28-6548879d10d6
    keyUSASR-3272
  4. Loading report definitions 
    Jira Legacy
    serverSSDT System JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6
    keyUSASR-3547
    The Inventory Pending Extract does not currently contain all invoice items that it should.  We are working to correct the problem and have reached out to all ITCs that have districts on the Redesign to determine who may be using it.
    3128

Known Limitations

  1. Auto assign preferences for requisitions.   
    Jira Legacy
    serverSSDT System JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6
    keyUSASR-352
  2. The Expense/Receipt worksheets, while they provide 3 years of history, those amounts are not currently being subtotaled by control breaks.  We've created Jira issue 
    Jira Legacy
    serverSSDT System JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6
    keyUSASR-3275
     to allow those amounts to be subtotaled.  This issue will also allow the data to display in separate columns if included on the budgeting spreadsheets via the Budget Scenarios.
  3. The SSDT Revenue and Expenditure reports that are based on the Classic FNDREVEX report have user parameters that appear to allow you to limit the report by fund or fund-scc depending on the version of the report you are running.  These user parameters do not work properly and should not be used.  Also, when choosing to collapse accounts, the descriptions you are used to seeing, such as "Salaries", are not the same.  These issues will be fixed on the 7.15.3 hotfix release shortly.  
    Jira Legacy
    serverSSDT JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSASR-3550
    1. These reports also have  grand total that is incorrectly adding the revenues and expenditures.


Upcoming Features

  1. Schedulable report process to replace Classic's MonthlyCD program
  2. Continued performance improvements
  3. Rewriting old print classes, allowing for extracting PDF versions of transactions for OnBase
  4. Import legacy monthly cd and fiscal cd archivesRemoving legacy code and menu options


Issues included on this release

Jira Legacy
serverSSDT System JIRA
columnskey,summary,type,status,resolution
maximumIssues20
jqlQueryproject = USASR AND fixVersion = v7.16.0
serverId925ea1db6d21ed14-0df83f48-3e913cc2-bcfbad28-6b1c8a04f6ca6548879d10d6