WFM maintenance 7.1.0.23 resolved issues
Total: 16 issues
POST-18229
Incident # 14927304
Unwanted timesheet_lock exists when off-cycle payroll export is aborted
When using core payroll close wizard, if the user chooses an employee for off-cycle payment, but for some reason doesn't continue on to click on the submit button, the record in timesheet_lock stays. This prevents the users from editing the timesheet for the date range that is indicated in the record. If the user tries to delete the record, this error is displayed: "Modifications to timesheet locks cannot be performed for any payroll related timesheet lock type."
Outcome
Fixed.
POST-20088
Incident # 15493031
Unable to open specific core reports due to constraint error
Unable to open the Selection Parameters page for the following core reports:
- Daily Error and Exceptions Report
- Employee Overtime Report
- Employee Seniority Report
- Forecast Wage Cost Report
- Shift Pattern Detail Report
- Time Code by Employee Report
- Time Code by Team Report
- Unauthorized Records Report
On the Error Log Management, user sees a unique constraint error as system is trying to execute an update query.
Outcome
Fixed by updating the scripts.
POST-20175
Incident # 15229247
Broken shift chains occur when the original parent shift details are deleted upon republish
- Unassigning the employee in a different rotation
- Shift swaps
- Time off requests
Re-processing after performing these edits may create overlapping shifts. It can also lead to broken shift chains because details on shifts in the chain have been deleted.
Outcome
Fixed with these changes:
- When removing a queued shift in rotation conflict resolution, the shift is not removed if the queued shift was swapped. This would otherwise delete a shift and break a shift link.
- After removing a queued shift, set the removal status from REMOVED to NONE, so that REMOVED shifts are not processed on each subsequent processing.
- Data fixes have been added for MSSQL and Oracle that attempt to revive the deleted shift caused by the rotation processing described above and delete the overlapping replacement shift.
- Processing now considers skip decisions made by KeepQueueDecider to decide whether the existing processed conflicts are still applicable.
POST-20233
Incident # 15516639
Error is displaying when opening a Time Off in Mobility Time Off Approval Page
When logged in as any manager or system admin with access to Time Off Approval Screen in Mobility, clicking on dates from the Time Off Approval screen results in a 500 internal server error.
Outcome
Fixed by adding a null check.
POST-20701
Incident # 15625528, 15625772
"ORA-02291: integrity constraint (WORKBRAIN.FK_SDL_DEPT_ID) violated - parent key not found" on Short Term Publish task
The exceptions DataIntegrityViolationException and OracleDatabaseException: ORA-02291 occur when the Short Term Publishing Task is run.
Outcome
Fixed by POST-20175.
POST-20781
Incident # 15662850
Employees' age is not respected when determining the correct staff group when schedule is manually edited
Employees may receive the incorrect breaks when manually editing a schedule in the LFSO Schedule screen. This occurs when employees are divided into staff groups based on age, and the Reassign Break/Meal Automatically after Shift Edit check box is selected.
Outcome
Fixed by adding an age check when performing manual edits to determine the employee's staff group.
POST-20913
Incident # 15715247
Unable to book off shift from ASV with error "Shift label is not valid for team TEAM on date: DATE"
The error message "The Display Label has been used by one of the sub-teams" is incorrectly displayed when cloning and editing a shift configuration after booking off a shift using the same shift label in ASV. After cloning the shift configuration, ASV displays an error that the shift label is not valid for the team.
Outcome
Fixed with these updates:
- Validation has been added when saving shift configurations to avoid bad data.
- The shift label validator has been updated to handle shift configurations from parent teams that may have been cloned and edited for future dates.
POST-20926
Incident # 15717444
Assign, Unassign, and Place on LTA actions in MR do not trigger loading indicators leading to duplicate actions
Loading indicators are not displayed when assigning employees, unassigning employees, or placing employees on LTA in a Master Rotations or One-time Schedules. In larger rotations, users may be able to perform additional actions before the system completes their previous action.
Outcome
Fixed by displaying the busy indicator when users perform assignment actions or place employees on LTA.
POST-20942
Incident # 15664509
NullPointerException occurs by manually clearing start and end times and then clicking the delete button in LFSO schedule
A NullPointerException error occurs when the start time or end time of a shift activity is manually cleared and then the shift is saved in the LFSO Schedule screen.
Outcome
Fixed by adding a null check to prevent the exception.
POST-20980
Incident # 15729282
Job Scheduler Logs page display "Error: Page could not be found" after clicking Next then Return button
'Page could not be found' error appears after clicking Next and then Return button in the Job Scheduler's logs page. If Next is not clicked and only Return was clicked, there is no error.
Outcome
Fixed.
POST-21057
Incident # 15496991
Schedule Compliance Rule does not show Error Popup
Schedule compliance rule for "Latest End Time" does not show an error pop-up when saving a shift past the latest end time. However, the schedule compliance rule for "Earliest Start Time" displayed an error pop-up when saving a shift that is earlier than the stated time in the rule.
Outcome
Fixed.
POST-21154
Incident # 15760764
Print schedule not obeying registry setting to show location name rather than description
The printed schedule in LFSO is does not reflect the location description when the SHOW_LOCATION_NAME registry parameter is set to WBT_DESC.
Outcome
Fixed by adding code changes to ensure the printed schedule displays the team description when the registry parameter is set to WBT_DESC.
POST-21303
Intraday print result doesn't show employee's full shifts for a day as Intraday Display does under department view when the shifts are across different departments
The printed Intraday Schedule Report does not display shifts for different departments assigned to the same employee on the same date in the same department section.
Outcome
Fixed by filtering out the shifts to display shifts from different departments together when assigned to the same employee on the same date.
POST-21304
Incident # 15805846
ExportAccess not respecting WBIEXP_UTC_INSERT_DATE, WBIEXP_UTC_UPDATE_DATE
WBIEXP_UTC_INSERT_DATE, WBIEXP_UTC_UPDATE_DATE are not being considered in the insert method of ExportAccess. There is a mismatch of the number columns and the number of parameter "?" passed.
Outcome
Fixed. Two new columns were added to WBINT_EXPORT table as part of PLAT-9398. But changes were not made to INSERT query in EmployeeAccess.java file which caused this issue.
POST-21308
Incident # 14842282
Edit shifts/Mark for Swap/Mark for Float buttons should not be displayed for MROTS LTA shifts in central staffing
When an employee is put on LTA in a Master Rotation and the MR is published, the Edit Shift, Mark for Float, and Mark for Swap options are displayed in Central Staffing when a user right-clicks the LTA shift. Selecting these options causes a Javascript error.
Outcome
Fixed by ensuring these options are not displayed when right-clicking on a LTA shift that was created from an MR or OTS.
POST-21397
Incident # 15836821
Recalc job is creating error which goes away with manually
Majority of timesheet records are having an error related to a missing groovy script rule, while the script exists in the system and when manually recalculating the day on timesheet it goes away. However, at times recalc in the timesheet can result in the same error and the issue occurs at random. There are currently 71,9961 work summary errors recorded for this issue.
Outcome
Fixed. Java concurrency was not handled correctly, which is causing the issue randomly.