WFM maintenance 7.0.0.40 resolved issues
Total: 9 issues
POST-20576
Incident # 15586878
Locks appearing on the ASV when employees team changed
When moving an employee to another team, locks display for that employee on the ASV.
Outcome
Fixed by changing the period end date time and set the time to default while comparing.
POST-20582
Incident # 15061780
Invalid UI after selecting team in relief queue
This item covers these issues:
1. An Invalid UI error is displayed on the Team field in the Relief Calling Area (RCA) when a team is selected as the sourceKeyField (given 'DEPARTMENT_ID' is part of case keyword).
2. An OutOfBound error occurs in the RCA when the EMP NAME is too long and has a skill.
Outcome
Issue #1 is fixed by an update to the field configuration. Issue #2 is fixed by adding a simple skill check before returning a skill string.
POST-21277
Incident # 15754712
Meal Confirmation Pay Rule causing NULL on Timesheet
The timesheet shows a null pointer error when the Meal Confirmation rule is configured to apply code based on a previous OFF clock and there is only 1 OFF clock punch for the day.
Outcome
Fixed.
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-20963
Incident # 15724260
Cannot deactivate MR "Cannot change shift because existing shift 8H1400 is send to relief" then upon unassign row another error is thrown violationsexception is java.sql.SQLSyntaxErrorException: ORA-01795: max num of expressions in a list is 1000
Exceptions occur when a user inactivates an MR with Inactivation Violations caused by shifts that were previously sent to the relief queue.
Outcome
Fixed by batching the summary IDs.
POST-20693
Incident # 15362130
ETM Clock In/Out Not Matching the Actual Punch Time AGAIN after SECOND Fix
ETM Clock Widget is off by an hour when clocking in/out.
Outcome
Fixed by calculating server time based on the client time and server timezone.
POST-19672
Incident # 15153162
Blackout period not working when Scheduling Range set to past date
Blackout period is not working when scheduling range is set to past date.
Outcome
Fixed. Added the logic to store the blackoutDates correctly in the database.
POST-21189
Incident # 15728948
Monday Availability Not Displaying Correctly in Advance Schedule View
Availability overrides are not displayed on the first day of the week when viewing a weekly schedule in ASV.
Outcome
Fixed.
POST-20175
Incident # 15229247
Broken shift chains occur when the original parent shift details are deleted upon republish
An application error occurs when loading a team schedule in ASV after a rotation is re-processed. These shift edits performed in-between rotation processing runs can cause this error:
- 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.