WFM Changelog v3.0
Revision as of 10:11, 7 April 2025 by Admin (talk | contribs) (Created page with "== New == * Mobile App - improved loading times * Timesheet Submission - improved loading times * Timesheet Approval - improved loading times * Client Shift Scheduler - improved loading times * Scheduler - improved loading times * Complete rebuild of the timezone handling engine * Mobile App - Shifts and Availability are now displayed in a daily calendar. We can also support monthly/weekly calendar in a future release * Mobile App - Added "canEdit" and "canDelete" selec...")
New
- Mobile App - improved loading times
- Timesheet Submission - improved loading times
- Timesheet Approval - improved loading times
- Client Shift Scheduler - improved loading times
- Scheduler - improved loading times
- Complete rebuild of the timezone handling engine
- Mobile App - Shifts and Availability are now displayed in a daily calendar. We can also support monthly/weekly calendar in a future release
- Mobile App - Added "canEdit" and "canDelete" selectors for availability - you can now create conditionals to determine if availability is editable/deletable
- Mobile App - Added "canEdit" and "canDelete" selectors for shifts
- Mobile App - added "background" property support for shifts displayed in the app (use the same background matcher as for the internal scheduler)
- Added next day notice to the time input field if the end date crosses over to the next day
Changes
- When bulk-editing shifts, we will only save the changed values
Fixes
- Removed UI quirks when saving/updating shifts. These could make for a poor user experience.
- Context menu / Manage Record (record edit pop up) could show wrong date or create a shift/request/expense on the wrong date
- File upload component was not correctly disabled by the disabled flag
- Stability improvements for Client Shift Manager
- Stability improvements for Mobile App
- Fixed an issue where past invitations weren't filtered out in the mobile app
- Fixed an issue where Timezones weren't handled correctly in the applications (mostly affecting the Clock app, but the fixes will apply for all apps)
- Fixed support for user vs local timezonePreference. Previously, we were ignoring the preferences in a few locations
- General bug fixes and stability improvements in timerange input, hours input and times input
- Fixed a bug in bulk shift editing logic that could result in incorrect shift assignment
- Fixed an issue where some shifts could be displayed crossing multiple days, when in fact they are entirely on 1 day
- Fixed an issue where global scheduling without Groups could break
- Fixed an issue with dates misalignment
Breaking Changes
- Please ensure that the scheduler definition, clock app, client scheduler, timesheet submission and timesheet approval has the following defined:
"startFieldPath": "b3s__Scheduled_Start_Time__c" - usually the scheduled times
"endFieldPath": "b3s__Scheduled_End_Time__c",
"actualStartFieldPath": "b3s__Actual_Start_Time__c" - usually the actual times
"actualEndFieldPath": "b3s__Actual_End_Time__c",
"absoluteStartFieldPath": "b3s__Absolute_Start_Time__c" - usually fallback set of times
"absoluteEndFieldPath": "b3s__Absolute_End_Time__c",
Please read the article Timezone Handling for more information on the topic.