Workforce Rostering - Release 4.10.00

Introduced the ability to remove available shifts directly from the Manage page using the “Make a change” menu. When a shift is removed, one of two outcomes applies: if a matching shift exists in Plan, users can re‑enable it at any time by editing the shift in Plan and marking it as available again; if no matching shift exists in Plan, a new shift will need to be created if it is required later. Removing shifts from the Manage page does not delete any shifts already assigned to users, whether in the past or future, it only affects the list of selectable shifts. To use this feature, assign the “Edit shift list” role, which should only be granted temporarily and when needed.

Updated the shift bids feature to allow a customisable time frame before the shift start that rostered users can accept the bid. To enable this feature apply the role permission “Restrict bids before shift start” and set a time limit.

Fixed a display issue that was preventing February 2027 Calendar from displaying correctly in MyTime.

Fixed an issue with Demand management using Percentage. When including absence in the percentage allowed on leave, and an absence was applied, then the system was incorrectly recalculating the percentage allowed on leave. For example if 20% of 10 staff are allowed on leave and 1 person is placed on an absence, then the system was updating the calculation to 20% of 9 staff, when it should have been including the absence in the 20%.

Fixed an issue in the integration layer when sending holiday variance cancellations that was not including the variance reason.

Fixed an issue with the “Make a change” dialogue appearing empty intermittently. Additional logic will check for an empty dialogue and force a reload of the content.

Fixed a visual error in MyTime when adding a variance request that briefly showed an error message before allowing the user to request the variance.

Fixed an issue with the Reciprocal shift swap feature that allowed auto approval when one user had self authorise but the other did not. Self approval requires both users to have self authorise enabled to auto approve.

Upgraded the integration layer for our clocking solution. This has resulted in a more stable solution and has solved at least one error that involved user details not being sent back through the integration.

Fixed a visual error on the demand management screen that was preventing the colours displaying correctly on the hourly rows. Colours should match the main graph exactly.

Fixed an issue in Pattern design when editing an existing calendar's details, the start date would skip one day ahead when saved.

Fixed an issue on the MyTime home page that resulted in shifts not being clickable.

Fixed an issue with being able to add overlapping periods of additional hours multiple times. Periods of additional hours should only be added once and subsequent periods should be blocked.

Fixed an issue with the Tasks feature. When using a permission to ensure the project name shows instead of the shift name, this wasn’t being consistently applied in the system.

Fixed an issue with a warning displaying correctly for Notice period restrictions when applying the restricted variance in Manage.

Fixed an issue with the incorrect form appearing when entering additional hours. For users that only had a single permission of “Add additional hours” as the only variance types to add in MyTime, the incorrect form was displayed.

Fixed an issue with the “Allow Holiday on Misc” permission that when combined with a variance rule that prevented requests, was incorrectly showing an escalate option that didn’t actually escalate.

Fixed an issue when publishing users in Plan, intermittently, some users were shown an error of a publishing job in progress, when no publishes were currently running.