This release provides updates and improvements to:
It also includes minor bug fixes.
| easyemployer |
|
easyemployer integration processes and logging have been refined for better management of information in the event of network outages.
|
|
Notifications will now be sent when an easyemployer session fails to synchronise. In the first instance, the session owner will be notified and the session will retry. If there is a second failure, this will be escalated to the system administrator for resolution. Both will be notified if an automatic retry resolves the issue.
|
|
Worker availability records will now be updated so that rosterers can view them and assign shifts in easyemployer.
|
|
Top
|
| Mobile app functionality |
|
Goal achievement plan (GAP) records can now be attached to case notes.
|
|
When a worker is unable to complete a shift and cancels, team leaders will now be able to use the mobile app to view which workers are available for reassignment to the shift.
Team leaders will only be able to view and assign workers who are available for the full day of the shift and for all sessions and all regions relating to the shift.
The flexibility of this functionality will be expanded in future releases.
|
|
Top
|
| Service delivered objects |
|
Service delivered objects have been modified so that they can be refined by system administrators to improve the clarity and flexibility of managing lookups.
|
|
Top
|
| Worker Availability |
|
Workers can now indicate spans of time when they are unavailable. These spans will be greyed out on their calendar.
|
|
Workers cannot be assigned to sessions that overlap periods where they have indicated that they will not be available.
|
|
Top
|
| Bug Fixes |
|
Minor bug fixes have been applied to resolve issues affecting:
- cancellation extract calculation
- easyemployer integration
- service agreement funding schedules and
- TechOne integration.
|
|
Top
|
How and When These Features Become Available
Lumary will install the release package into your sandbox for a piloting phase period of 6 weeks. Your organisation’s primary contact(s) are notified of this sandbox upgrade approximately two weeks prior.
Following the sandbox period, the application upgrade will be automatically installed into your production environment, and the release will then be available to all users in your organisation. Communications will be made to primary contacts about the upcoming sandbox and production upgrades.
Consider communicating these changes to your users beforehand so that they are prepared.