Issues Fixed in HR Management for Vista 2022 R5
The following issues were fixed in the HR Management for Vista R5 release.
To view customer suggestions and enhancements for this release, see the What's New page.
General
| Issues Fixed | Issue # |
|---|---|
| The portal update to version 22.4 failed for customers who attempted to update from versions prior to 22.2. The following error message was generated: Invalid column name 'DateCreated'. | 107790 and 108001 Note: Resolved in an update after release 22.4+. |
| Windows Authentication failed for users if the Active Directory domain had more than 1,000 user objects. | 107045 |
| Portal setting fields that allow rich text formatting are now limited to 20,000 characters. Previously, in rare cases in which customers had rich text entries beyond this limit, the web portal failed to launch and generated the following error message: Error during serialization or deserialization using the JSON JavaScriptSerializer. The length of the string exceeds the value set on the maxJsonLength property. | 107664 |
| Portal settings that have a password or an encrypted key now have a Clear button that you can use to clear an existing value from that setting. | 108002 |
Benefits
| Issues Fixed | Issue # |
|---|---|
| Attempting to elect a benefit code with a custom rate table resulted in an infinite spinner, and the Error Log showed the following message: An error occurred while reading from the store provider's data reader. See the inner exception for details. Conversion failed when converting character string to smalldatatime data type. |
Expenses
| Issues Fixed | Issue # |
|---|---|
| Users were unable to access the Edit Expense Item window. | 107791 Note: Resolved in an update after release 22.4+. |
When accessing the
portal on a mobile device, the following issues occurred when
the portal settings Default New Transactions
to Blank Date and Disable required fields
for expense type coding fields were enabled:
|
107849 Note: Resolved in an update after release 22.4+. |
| When editing a quick add expense on a mobile device, the Job field search was limited to the first 19 jobs in numerical sort order. | 107921 |
| Images taken in portrait mode on mobile devices (Android and iOS) were rotated 90 degrees and displayed sideways after they were uploaded to an expense item. | 107766 |
Onboarding / Applicant Tracking
| Issues Fixed | Issue # |
|---|---|
| When onboarding on a mobile device, if a new hire signed Form W-4 and then rotated the device, the signature was cleared, but the new hire was still able to submit the form. | 107820 Note: Resolved in an update after release 22.4+. |
| During onboarding, new hires were able to save Form W-4 without selecting a filing status. | 107800 Note: Resolved in an update after release 22.4+. |
| If the portal setting
Auto Assign PR
Employee to HRRef for Newly Initialized
Employees was enabled and a user entered an
Expected HR
Ref for a new hire, the PR Employee
field was left blank and onboarding records could not be
initialized to Vista. Setting location: . |
107809 Note: Resolved in an update after release 22.4+. |
| In Applicant Tracking, changing the stage for an applicant on the Applicant Details page generated the following Error Log message: An error occurred while executing the command definition. See the inner exception for details. You are not authorized to view this checklist instance. | 107731 |
| If the portal setting Initialize New Hires to Payroll was not enabled, social security numbers were not validated against HR Resource records when onboarding records were initialized to Vista. This could result in duplicate records in Vista. | 107873 |
| Direct deposit attachments added during onboarding could not be viewed from the Onboarding Dashboard, could not be exported from the Onboarding Details page, and were not sent to Vista. | 107911 |
| The veteran status was not showing in the HR Resource file in Vista for new hires who identified as veterans on the Voluntary Self-Identification form during onboarding. | 107850 |
| The Expected HR Ref field (if entered) was clearing when the new hire submitted the onboarding packet. | 107966 |
Performance Reviews
| Issues Fixed | Issue # |
|---|---|
| Duplicate performance
reviews were initialized for employees if a user selected the
Initialize
Review button multiple times on the Performance
Review Dashboard. Note: The
Initialize button is now unavailable during the
initialization process.
|
107690 |
Time Off
| Issues Fixed | Issue # |
|---|---|
| On the Manage My Time Off page, if a non-paid leave code displayed first in the sequence in the Select Leave Code drop-down, the leave code grid summary did not display at the top of the page. Instead, the following error displayed: No available leave data. | 107858 |
Timecards
| Issues Fixed | Issue # |
|---|---|
| The following error message displayed when making any changes on the Standard Timecard Settings page: An error occurred while executing the command definition. See the inner exeption for etails. --- Cannot insert the value NULL into column 'IsMobileJobEnabled', table 'KDS-HRIM.dbo.TimecardGroup'; column does not allow nulls. UPDATE fails. The statement has been terminated. | 108012 Note: Resolved in an update after release 22.4+. |
| Multiple PRCos were displayed on the Timecard Dashboard. |
Note: Resolved in an update after release 22.4+.
|
| Users in portal
setting User Group
To Restrict Line Edit / Add / Delete (Submit Only) on Grid
Timecard did not have the option to submit a
timecard in the Grid Timecard Actions drop-down. Setting location: . |
107775 Note: Resolved in an update after release 22.4+. |
| When portal setting
Filter
Existing Grid Timecard lines based on Logged In User's Job
Data Security was enabled, non-Job Grid Timecard
Lines could not be saved to non-Shared Grid Timecard Templates.
Setting location: . |
107851 Note: Resolved in an update after release 22.4+. |
| When Timecard Setting Enforce Pay Period Boundaries was enabled for the PRCo and PRGroup, the timecard Post Date for Australian customers was one day behind the Beginning date and Pay Period Ending date. | 107926 |
| When a UD field in the Values column was edited and saved, amounts were changed to zero. | 107648 |
| When a Closed Pay Period was selected, the Timecard Dashboard excluded Timecards that were not submitted. | 107913 |
| In Timecard Approval, the Review & Approve All button now displays if there is at least one timecard line to be approved. | 108014 |
