WFM maintenance 7.1.0.31 resolved issues

POST-20730

Incident # 15578051

Error retrieving Unauthorized timesheets for ALL employees

A system error occurs when a user tries to retrieve all unauthorized timesheets. The error occurs when trying to load more than 2100 employees.

This issue only occurs on SQL Server.

Outcome

Fixed. When trying to load more than 2100 employees, the "Please select additional criteria to limit the number of employees" message is displayed.

POST-21964

Incident # 15979489, 16356868

WBException preventing ASV from loading

When trying to load the ASV for a specific team, a KotlinNullPointerException occurs. The error only occurs on one date.

Outcome

Fixed.

POST-22180

Incident # 16089639

Forecast Wage Cost Report produces a Proxy Error when processing a large amount of data.

The Forecast Wage Cost Report fails with a proxy error when processing a large amount of data.

Outcome

Fixed by implementing multi-threading.

POST-22764

Incident # 15805537

On call shifts not available if FTE set to < 1.0

Users cannot self-schedule on-call shifts when their FTE is less than 1.

Outcome

Fixed.

POST-22803

Incident # 16273280

Error upon submitting timesheet: java.lang.IllegalStateException: The amount of work detail minutes is not matching the range defined by the work detail start time and end time.

An error occurs upon submitting a timesheet:

java.lang.IllegalStateException: The amount of work detail minutes is not matching the range defined by the work detail start time and end time.

Europe DST validation was missing, which caused the data inconsistency issue.

Outcome

Fixed by adding Europe DST validation.

POST-23356

Incident # 16470323

Fixed shift with more than 3 shifts assigned, the schedule fails to generate correctly.

When a fixed shift is defined with more than three segments (jobs), the schedule is not generated correctly.

Duplicates for the same shift were observed in the shift choices file, which could cause the optimizer to remove the shift.

Outcome

Fixed by refactoring the code to avoid generating duplicates of shift choices.

POST-23402

Incident # 16473680

Mobility Time Code is not being displayed

When setting up a new query in mobility, the time code is not displayed if any of these options are used:

• searchColumns='TCODE_LOC_NAME'
• searchColumns='TCODE_NAME'
• searchColumns='TCODE_LOC_DESC'

Outcome

Fixed.