WFM maintenance 7.1.0.34 resolved issues
Total: 6 issues
POST-23498
Incident # 16456589
MR Long Term Publish does not remove some locks/shifts in ASV
When unassigning users on a Master Rotation, the long term publish task is not removing some shifts in the ASV. In addition, the dates are also locked.
Outcome
Fixed. The IDs of the unassigned employees are added to the list of employees whose locks are to be removed during the long term publish task.
POST-23836
Incident # 16354658, 16362122
Backport to 7.1.0x: Intraday graph is incorrect for the 2nd location when an employee is scheduled for two locations.
Intraday graph only shows the coverage for the first shift even if the employee has multiple shifts on same day. Issue is seen when an employee is scheduled for two different locations on the same day.
Outcome
Fixed. Modified the code to show coverage for shifts which are assigned to departments of schedule location when there is no preselect for staff requirement.
POST-24093
Incident # 16426625
Backport WFM-46318 to 7.1.0
Rounding options can be selected to adjust fixed shifts that do not align with schedule intervals in schedules generated using the Staff Groups model. The optimizer uses rounding to align fixed shifts that may have any start or end time with staff requirements that are divided among 15, 30, or 60 minute schedule intervals. The rounded times are used when displaying the shift in the LFSO Schedule screen and in the timesheet when the schedule is published.
You can select the rounding option in the SHIFT_PATTERN_ROUND_FOR_OPTIMIZATION registry parameter. For example, the DEFAULT option rounds down the start time of the shift to the start of its current interval, and it rounds up the end time of the shift to the start of the next interval. For example, the location has 15 minute scheduling intervals, and an employee assigned to a fixed shift from 9:05 AM to 4:55 PM. This option rounds the shift when generating the schedule to 9:00 AM to 5:00 PM. Other rounding options are available.
See "Rounding fixed shifts" in the Infor Workforce Management LFSO Implementation and Administration Guide.
POST-24120
Incident #
Backport POST-23095 to 7.1.0.x maintenance
The Custom Cost callout in LFSO can load all 12 custom data fields using one call. This can improve performance in the LFSO Schedule screen by removing the individual calls for each field that are required when the callout is triggered by schedule edits or other user actions.
The SCHEDULE_COST_CUSTOM_CALCULATOR_LOAD_ALL_FIELDS registry parameter can be set to true to configure the callout to load all custom fields using the same call. Customers using this option must update the class that implements the callout to implement the getCustomScheduleCostAll() method. A demonstration of this new method is included in the sample implementation class.
See "Custom Cost callout interface" in the Infor Workforce Management LFSO Implementation and Administration Guide.
POST-24121
Incident #
Backport POST-23130 to 7.1.0.x maintenance
Values for unscheduled employees are not included in calculations for the Custom Cost callout fields that are displayed in the LFSO Schedule screen.
Outcome
Fixed an issue where Custom Cost callout data was emptied for unscheduled employees before being loaded.
POST-24231
Incident # 16788439
Unauthorize Rule doesn't respect TREAT_TIMECODE_AS_ON
The Unauthorize Rule does not respect the TREAT_TIMECODE_AS_ON registry parameter. When the registry is set to TRUE and a time code clock occurs after an OFF clock, the timesheet is unauthorized.
The timesheet is unauthorized because the "Unauthorize If Clock Ons Not Equal Offs" parameter does not consider the TREAT_TIMECODE_AS_ON registry.
Outcome
Fixed. The Unauthorize Rule considers the TREAT_X_AS_ON registries when determining if a labor metric clock counts as an ON clock. The same fix was applied to the Authorize Rule.