Issues Fixed in HR Management for Vista 2022 R12
The following issues were fixed in the HR Management for Vista R12 release.
To view customer suggestions and enhancements for this release, see the What's New in 2022 R12 page.
General
Issues Fixed | Issue # |
---|---|
After updating to version 22.10, users could not log in due to a system memory error. | 109483 Note: Resolved in an update after release 22.10+. |
Clearing certain portal settings and
then entering new settings resulted in the following error
messages:
|
109409 Note: Resolved in an update after release 22.10+. |
After successfully updating their password using the Reset Password link on the login page, users were again prompted to change their password. | 109566 |
On mobile devices, HR Management users could access Financial Controls and Field Tools modules even without having permissions for these modules. | 109521 |
Benefits
Issues Fixed | Issue # |
---|---|
If an employee benefit group was generated using a custom SQL query and that query returned a PRCo with no value, employee names would not show when viewing benefit group membership. |
Expenses
Issues Fixed | Issue # |
---|---|
For customers who process credit card
expenses through Accounts Payable, charges included on a credit
card statement were separated into individual invoices,
preventing users from being able to validate statement totals. Note: In the
current version, posting credit card expenses creates
one invoice per statement. As a result of this change,
the expense package and the portal setting Use Transaction
Date for Invoice Date in Vista are
ignored for credit card expense items.
|
109662 Note: Resolved in an update after release 22.10+. |
When the portal setting Use Transaction Date for Invoice Date in Vista was enabled, expense packages were duplicated in AP Transaction Entry. | 109466 Note: Resolved in an update after release 22.10+. |
Expense items under different expense packages were listed on the same invoice after they were posted to an AP batch. | 109482 Note: Resolved in an update after release 22.10+. |
When moving expense items to a batch,
if any of the items could not be validated, the batch was not
posted to Vista and users received the following error message:
Note: Expense
items that cannot be validated are now excluded when
moving expense items to a batch.
|
109631 Note: Resolved in an update after release 22.10+. |
If an expense packet contained two transactions that canceled each other out (for example, $10.00 and -$10.00), those transactions did not display in the Expense Submission History in . | 109468 |
In Expense Posting, credit card expense items can no longer be bulk coded to an earn code when bulk editing in Process Mode P. | 109359 |
If multiple reviewers were in a sequence, all reviewers had to approve the expense for the status to show as Approved in Expense Posting. Only one approval per sequence is actually required. |
109577 |
Corrected the error message on the Expense Posting Dashboard that displayed when moving Unapproved or No Approval Assigned expense items to a batch. The updated message now reads:
Previously, the error message stated that the manager(s) of the unapproved employees would be notified. |
109283 |
Resolved Expense Posting Dashboard timeout for specific PRCo and PR Group combinations. | 109575 |
When processing expenses through Accounts Payable, expense packets with the same AP Reference number generated an error when a user attempted to validate them in Vista AP Transaction Entry. To correct this issue, if expense packets have the same AP Reference, sequential numbers are now added to those AP references when those items are moved to a batch (for example, December Transactions 1, December Transactions 2). | 109530 |
For users creating a New Expense Item on the Expenses page, expense items duplicated when selecting Save and Close or Cancel after entering information to fields in the following order: dropdown. | 109800 |
Onboarding / Applicant Tracking
Issues Fixed | Issue # |
---|---|
On the External Careers page, the Filter by Location option was not showing any check boxes, preventing users from being able to filter jobs by a specific location. | 109534 |
In Onboarding and Update Info, the Account number for direct deposit accounts is now limited to 17 characters to match the character limit for the bank account number in Vista. | 109399 |
When completing I-9 step 2 for an employee, if a user selected the Generate Signature button, the button was removed from the screen and a signature was not generated. | 109476 |
If the portal setting Initialize New hires to Payroll was enabled, a W-4 / I-9 error displayed when updating profile settings for a job category. | 109907 |
Paystub Tools
Issues Fixed | Issue # |
---|---|
In some cases, paystub notifications and group messages were sent to employees multiple times. | 109863 |
Performance Reviews
Issues Fixed | Issue # |
---|---|
For employees with self-reviews to complete, the blue reminder banner on the home page failed to respond when users clicked it to open the My Performance page. | 109591 |
If multiple managers were assigned to the reviewer group for an employee's performance review, the blue reminder banner did not display on the home page for any of the managers in that reviewer group with reviews to finalize. | 109664 |
Personal Information
Issues Fixed | Issue # |
---|---|
In Update Info and Onboarding, the Account number for direct deposit accounts is now limited to 17 characters to match the character limit for the bank account number in Vista. | 109399 |
Time Off
Issues Fixed | Issue # |
---|---|
If all extended leave codes were configured to Show in Grid and Show Projection, but not to Allow Request, the Manage My Time Off page failed to load. | 109171 |
Timecards
Issues Fixed | Issue # |
---|---|
For users installing HR Management / Field Management for the first time and who were already on Vista version 2022 R1 or greater, using batch timecard move to move grid timecard lines resulted in clearing the grid timecard template. | 109692 Note: Resolved in an update after release 22.10+. |
In Grid Timecards, the Class lookup list would not populate when a Craft code that had letters in the name was also selected. | 109456 Note: Resolved in an update after release 22.10+. |
Users with custom Earnings reports in the portal setting Timecard SSRS Report override (include .rdl in filename) could not export submitted timecards without experiencing an error. | 109488 Note: Resolved in an update after release 22.10+. |
Even with the portal setting
Allow zero
hour lines
to be saved and
submitted enabled, bulk adding lines to the grid
timecard with hours entered as zero (0) resulted in the
following error:
|
109429 |
Even with the portal setting Format employee name as LastName, FirstName in Timecard lookup (Requires Refresh Synonyms) enabled, employees in the grid timecard Employee lookup were still listed by employee number. |
109405 109495 |
For grid timecards with Start and Stop times, bulk adding lines now requires only an Hours entry. Start and Stop times are removed from the bulk add modal. | 109620 |
When generating processed timecard reports on the Timecard Dashboard, expense amounts from amount-based Earn Codes were added to the processed hours. | 109351 |