Versions Compared

Key

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

...

  • Corrected the ability to use the "Create New" feature when adding Refund transactions.  Previously if a refund with a check had been created, the check information on the new refund was populated with the data from the previous transaction.

Improvements

  • Implemented the ability to print 1099s (MISC & NEC) on pressure seal forms.  In order to print on the pressure seal forms you'll need to select the new Output File Type option "Printer/Sealer Copies".  Once you click "Generate Submission File" the printable 1099s will be generated and a PDF will be available to send to the printer.  Please note, currently if you select both NEC and MISC "Type of Returns" a single file will generate containing both NEC and MISC 1099s.  This is not ideal for printing on the separate forms and we have updated USASR-5027 to ensure separate files are generated.
      • A couple of things to note.  During test printing we found that if the vendor's contact info is entered in mixed case it will print on the 1099 that way.  We are updating the generation of the print forms to force all name and address information to be in all CAPITAL letters.  We also found that if the Organization & Vendor's name and address fields are too long (beyond 45 characters) they will not display properly on the printed document.  We will be correcting these issues on USASR-5027 as well.
      • Reminder, SSDT is supporting ONE blank pressure seal form for each of the 1099 types.  The forms are 8 1/2 X 11 Z-Fold.
  • Ability to change a vendor on a "new" PO without reopening the posting period associated with the PO date.  You cannot change a PO to remove a vendor, making it a multivendor PO.
    • To change the Vendor, select the Repair option on the PO.  From the vendor tab modify the vendor to a new/different vendor.  Again, this can not be modified to a blank vendor.

New Features

Internal

  • Created a service layer for Cash Reconciliation.  This is an internal change only with no impact to the current Cash Reconciliation UI.
  • Refactored failing tests related to recent service layer changes.
  • Created a service layer for Civil Proceedings.  This is an internal change only with no impact to the current Civil Proceedings UI.
  • Created a service layer for Scenarios.  This is an internal change only with no impact to the current Scenarios UI.

Patches

  • Patch for a specific district to correct POs that had been improperly updated as a result of an account change.  The bug in the account change process was corrected previously on the 8.46.0 release published on May 5, 2020.

USPS-R Releases

DateVersionType

 

6.72.0Regular

 

6.72.1Hotfix

 

6.72.2Hotfix

 

6.73.0Regular



...

  • Correct a query used to determine the max amount for a payroll item
    • issue was employee had multiple missed deductions due to not enough funds for that payroll item with a max amount, it was still adding those up in the max amount as it went, so when she did have enough money, it wouldn't take the missed deductions out, thought it met it's max amount.
  • Fix missing method exception in Payroll Detail View when attempting to remove a pay group from a payroll
  • Hotfix - both bugs introduced on 6.72.0 release - Prevented districts from initializing payroll 
    • Correct null pointer exception that could be caused by a null rate value in a payroll item (employee or employer). This null rate value would prevent payroll from calculating, which would cause issues with initialization, reports, posting, etc.
    • Correct missing method exception the payroll report. If a message needed to be displayed on the pay report, a missing method was returned. This prevented pay report from completing.
    • Prevented districts from initializing payroll
  • ABS101Hotfix
    •  ABS101
      • Correct issue with user stored parameters preventing user from navigating to the ABS101
      view
      • view 
      • Prevent error in the report when no adjustments or accumulations are found for a given employee
        • Prevented districts from running ABS101.txt report
        • Now it will just give a blank report, if no employee's are found
  • Employer Distributions - Account mapping updated to handle alphanumeric character when applying mapping configuration
    • Districts getting an error when running, it was due to having an alphanumeric character in the payroll account: Example: "905B"

...