WFM Changelog v5.X

Version 5.2

Under Scheduling custom setting, we added Upsert/Delete/Query Batch Size number fields. These can be used to control the batching of requests to the server. Keep the default values unless otherwise requested.

Scheduler: When switching between views, the Scheduler wasn't loading the full definition for the contextual view. This could cause incorrect data to be loaded.
Scheduler: Avoid processing same items more than once if in the queue already
DEV-793 - Issue with filters where items with the same name would cause the filter to be incorrectly applied
DEV-851 - After applying a resource filter and then removing the filter, the rows could render incorrectly (too short).
DEV-852 - Dark mode OS setup could make some items difficult to read within the scheduler
DEV-881 - WFM - Context Menu not showing when selecting all shifts with Ctrl + A
DEV-886 - WFM - Shifts spanning across 2 days after being moved
DEV-887 - Shifts showing the date twice after TZ was changed
DEV-949 - TS Submission page - weekly view could show week dates incorrectly
DEV-919 - Shift times were not showing in 24 hr format when creating or editing, but 24h format is set in the definition
DEV-904 - First Day was not respected when changing Scheduling groups
DEV-892 - Bulk created shifts could show a discrepancy in the times

All sub-applications now use a new communications protocol, avoiding REST API apart from when files are uploaded through a record form.

Due to the new communications mechanism, you can no longer define "LIMIT" in your SOQLs within the WFM application (e.g. definitions or data loaders)