Workforce Rostering - Release 4.06.00

Updated the TIME section so that any miscellaneous variances that are marked as “affects cover” will be treated as an absence and the user will not be expected to clock in and therefore no exception will be raised.

Updated the integration for new users, so that if a user is created by a 3rd party system, they will not receive a welcome email at the point of creation. This prevents users receiving login details before the organisation is ready for them to login.

Added caching to the WorkSuite Homepage to improve loading times. The last successfully loaded results will now load instantly while the system refreshes the results for subsequent page loads.

Added some performance improvements to the MyTime Calendar page that specifically improves the user search functionality.

Fixed an issue with announcements. When set to be dismissible, messages were being deleted for all users instead of being dismissed for the individual user.

Added a warning when adding a comment and the role settings require the user to enter a comment, as this wasn’t clear to the user that a comment was required before saving.

Fixed an issue with the PEOPLE page. Occasionally, when loading the page, the page incorrectly displayed a “no employees found” message before loading all users.

Fixed an issue affecting some TOIL accounts. When adding additional hours to be accrued as TOIL, some users were getting a “Too many used” error. Users will now be able to correctly accrue hours in this situation.

Fixed an issue preventing users from manually clocking in on MyTime on the home page. The save button was non responsive.

Added some improvements to the TIME screen to deal with a “Race condition”. A race condition in this context is when one request to return results using a filter is not yet complete and a new request using the filters is actioned, then occasionally results from both filters are returned at the same time.

Fixed an issue with deleting/removing secondments. Occasionally the user was presented with an unknown error and could not remove the secondment.

Fixed an issue deleting holiday variances Variance that have been applied, followed by a republish of shifts and then deleted were erroring with an unknown error was often experienced when trying to delete these variances.

Fixed an error with the group change functionality. Making a group change and then changing calendars to make another group change, was returning the previous calendar’s users incorrectly.

Resolved a problem in the integration layer where cancelling a variance was not being sent when a shift was republished and changed from a working day to a rest day. This scenario was incorrectly identified as having no change, preventing the expected cancellation from being processed.

Resolved an intermittent issue where the “Make a Change” dialog would occasionally appear empty due to a browser rendering problem during page load. Enhancements have been made to better detect and recover from this scenario, ensuring the dialog loads correctly.