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 10 Next »


Date

March 11, 2019

Issues

type key summary assignee reporter priority status resolution created updated due

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Build Date2019-03-XX XX:XX:XX

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. Improvements have been made to reconciling disbursements.  This change improved the overall performance of disbursements as well.
  2. Improved performance of closing popup windows.
  3. Implemented the ability to import monthly and fiscal cd archives from Classic.
  4. Vendor ledgers are being posted for prior calendar year voided disbursements.  Previously the ledger entry was removed when the disbursement was void.  Now void ledgers will be posted using the void date.  This will keep calendar year amounts from being changed, while accurately updating fytd amounts.
  5. Corrected the requisition approval status to display correctly.
  6. Activity ledgers are now being generated for advance repay transactions.  This means they will now be included on the Financial Detail reports and Activity Ledger grid.
  7. Remaining invoiceable has been removed from the PO header and item area, but is still reportable.
  8. Corrected the posting of Disbursements to specify the item order, previously this was determined by how the items were selected in the Payable grid.
  9. Corrected problem with mass loading accounts with regard to xref codes.
  10. The tax id and type have been restricted to the USAS_PRIVACY_TAXID permission to prevent those without the permission from seeing it.  However, users without the permissions could still see this information on reports.  We are working on a way to suppress the fields on reports as well.
  11. The asOfPeriod parameter has been added to various template reports to allow the user to generate a report as of a specific period without having to change the current posting period.  
  12. Corrected an error with the new hire report if the begin date is not populated on the vendor and the user did not select to calculate the begin date.


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. Purchase Order item entry 
    Error rendering macro 'jira' : Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  2. Loading report definitions  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Known Limitations

  1. Auto assign preferences for requisitions.    Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  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  Unable to locate Jira server for this macro. It may be due to Application Link configuration.  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.


Upcoming Features

  1. Schedulable report process to replace Classic's MonthlyCD program
  2. Continued performance improvements
  3. Import legacy monthly cd and fiscal cd archives


Issues included on this release

key summary type status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels