WFM Changelog v1.8: Difference between revisions
Jump to navigation
Jump to search
Line 17: | Line 17: | ||
* DEV-393 - Added the ability to restrict the number of events per day cell | * DEV-393 - Added the ability to restrict the number of events per day cell | ||
* DEV-331 - Booked matched candidate instead of inviting | * DEV-331 - Booked matched candidate instead of inviting | ||
* DEV-372 - Allow requesting fields from candidate in the mobile app before/after shift start | |||
* DEV-393 - Allow limiting the number of events per day cell in the scheduler |
Revision as of 23:10, 4 December 2024
Fixes and Improvements
- DEV-281 - Shift/Expense times not matching in the mobile app
- DEV-352 - Bug fixes and refinements
- DEV-329 - Add support for file upload component (useful within timesheeting and clock app)
- DEV-315 - Issues with day assignment when shifts are created in some timezones
- DEV-326 - Moving events quickly might throw an error
- DEV-353 - Copy-paste of events could incorrectly set the day on an event
- DEV-368 - Add decorations to TS Approval and TS Submission shifts (similar to how we do it in the calendar)
- DEV-334 - Invitations count on the mobile app could be incorrect
- DEV-357 - Allow editing a shift from the home page in the mobile app
- Implemented a new method for getting, saving and deleting data (should see speed optimization)
- Added dynamic contexts (you can now access the contextRecord.Field_Name__c and use it in loaders, field defaults and selection clauses)
- DEV-394 - Show invitations once candidates are invited
- DEV-395 - Child forms (e.g. Site create) were not rendering correctly
- DEV-393 - Added the ability to restrict the number of events per day cell
- DEV-331 - Booked matched candidate instead of inviting
- DEV-372 - Allow requesting fields from candidate in the mobile app before/after shift start
- DEV-393 - Allow limiting the number of events per day cell in the scheduler