WFM maintenance 7.0.0.41 resolved issues
Total: 10 issues
POST-17114
Incident # 14594044
Shifts still displayed after deleting unprocessed OTS row
Shifts are still displayed from a row in an unprocessed OTS after the row is deleted.
Outcome
Fixed.
POST-17122
Incident # 14622175
"ANY" Job appears on employee assigned shift when using Employee Call Window function
During the assigning process via employee call window, if the user removes the job from the schedule times and proceeds to submit, the application replaces the job to 'any' and is displayed for both the ASV and SAW.
The expectation is that there should be validation when a job title is missing.
Outcome
Fixed. Added missing job validation for shifts in both assign and reassign tabs of Employee Call Window, with proper tab labels in error message
POST-19386
Incident # 15207041
Mobility - My Schedule page not loading if there are a large number of available billboard shifts
The My Schedule page in the WFM mobility app is not loading when there are over one thousand shifts posted to the shift billboard per day.
Outcome
Fixed by batching the queries to load shift billboard shifts, which improves performance when loading the My Schedule page.
POST-20234
Incident # 15534996
Column length mismatch on Workbrain and Data Replication table
A large value stored in the WBITYP_DEL_OLDER_THAN table in the WFM application database causes a a "Numeric Overflow" error when the Data Replication task runs.
Outcome
Fixed by adding a script to update WBF_UI and WBF_UI_PARAM.
POST-20548
Incident # 15467401
Archiving task fails with unique constraint violation when default records are created again same as archived data
Default records are recreated in the workbrain schema during archiving. This is causing a unique constraint violation when running the Archiving task because the data is conflicted with the archived data that is already archived.
Outcome
Fixed by adding a condition with the hands-off date to restrict the creation of default records for employees.
POST-20625
Incident # 15612439, 15625772,15709802
Broken shift chain errors occurring from swapped shifts and floated swapped shifts
An application error occurs when loading an individual employee's schedule in ASV. This occurs when a rotation is re-processed and causes a broken shift chain by deleting details from a shift that was involved in a shift swap or time off request.
Outcome
Fixed by POST-20175.
POST-21484
Incident # 15856149
Null Pointer Error when adding Clock In punch on the Timesheet
A null pointer error occurs when adding Clock punches in the user's timesheet. This occurs due to bad time in overnight ad-hoc shifts created that overlap the fall DST time change.
Outcome
Fixed by updating the validation logic to accept smaller end times when shifts overlap the fall DST time change.
POST-21516
Remove 'Is Own Process' flag from Job Scheduler options
The "Runs in a dedicated process" option has been removed from all Job Scheduler tasks. The checkbox will be removed from all Job Scheduler tasks on upgrade and new installations of WFM will not have this option.
For more information on using Job Scheduler, see Infor Workforce Management Time and Attendance Implementation and Administration Guide.
POST-21635
Incident # 15901897
Notification Bar suddenly starts spamming DB causing 100% CPU usage
The notification bar will suddenly begin spamming the database, causing the DB CPU usage to run at 100%. This causes performance issues and unhealthy Docker states for the application containers and customers see 502 and 504 errors.
Outcome
Fixed with the following changes:
-A new registry (/system/widgetbar/MAX_DIRECT_EMPLOYEES) is introduced to stop polling notification bar items (Timesheet Alerts, Time Punch Alerts, My Employees) when the number of direct employees exceeds this limit. The default value is 200.
-Single query is executed instead of two to get the "Timesheet Alerts" and "Time Punch Alerts" count.
-Notification bar will not be updated when the WFM application is not shown in Mingle.
POST-21708
Incident # 15931460
Shifts from shift templates used are not consistently displayed in Self-Scheduling process
Shifts from a Shift Template are not created when another sub-team has generated a schedule containing the same shifts that were inherited from the parent team during the same date period.
Outcome
Fixed by comparing existing shifts based on the team and shift ID. Shifts should still be generated if the shift has previously been generated for a different team.