USPS-R 5.18.0 Release Notes
Date | Oct 12, 2018 |
---|---|
Issues | Getting issues... |
Build Date | 2018-10-11 05:07:51 |
Summary
This release of USPS-R contains new features, improvements and patches as detailed in the full release notes below.Â
Important highlights from this release
USPSR-3782 Corrects a problem that affected using the payroll item refund screen to refund an annuity deduction originally honored by a city for an employee that had job level city withholding configured. In this specific scenario no city tax was being withheld when the annuity was refunded.
If you used the payroll item refund screen to refund an honored annuity for an employee with city by job withholding in USPS-R posting manual adjustment journal entries may be needed.Â
This did not affect refunds handled as error adjustments in the payroll process. It only affected refunds done using the payroll item refund screen for the specific scenario detailed above. Â
USPSR-3770 Adds the ability to mass load adjustment journal entries. This may prove very beneficial for certain things sometimes required at calendar year end, such as loading W2 related adjustments that existed as override fields on the federal tax deduction in classic USPS.Â
USPSR-3798 Reporting capabilities have been added to the leaves grid.
USPSR-3828 The job scheduler UI has now been exposed in the application. This will allow users to view scheduled e-mail direct deposit jobs and determine if they ran successfully.Â
Please Note: the create and edit functions of the job scheduler are not currently fully implemented, so for now this is meant to be used for reviewing system scheduled jobs only.
USPSR-3382 If the USAS Integration module is enabled the application will now automatically schedule a nightly account sync job with a start time of 4:00 am. This should greatly reduce the need for users to execute manual account syncs.
The creation of this account sync job and the cron expression used to execute it (i.e. the time it runs) can be modified through docker environment variables or directly via the configuration option. We assume 4:00 am is a reasonable start time. The only other known process we want to avoid is your nightly updates that are pulled from the SSDT. We assume most of these are beginning around the 12:00 - 2:00 am time frame and should be completed by 4:00am.Â
Documentation on this feature is forthcoming, but if you feel you need to adjust the start time or have other questions please enter a SSDT Jira Service Desk request.Â