The following are the changes in the upcoming release:
Bytecurve360 (Scheduling & Dispatch, Time & Attendance)
New features:
- Ability to import tasks into Dispatch from an excel file. This can be used to bulk import field trips and charters, among other day to day daily tasks. Knowledge Base: Importing Tasks In Bulk
- Added integration with the Samsara Telematics device
Enhancements:
- The Operations Settings screen includes flags that allow the user to configure which Dispatch alerts are to be displayed for the given location. This was not fully functional before and has now been fixed, except for the flag corresponding to 'Routes running late' (this will be removed in a future release as the system is not currently aware of routes that were late initially but caught up along the route).
- Ability to transfer vehicles and employees from one location to another through the vehicle and employee API respectively. More information will be provided upon request.
- Added a 'Show' button for password fields, that the user can click on to see the password value in clear-text if/when they need to.
- When resetting the password or when entering one's password for the first time, the system displays the rules the password must conform to.
- The Dispatch Clock version number has been added to the Timeclock registration screen. This is to help the Bytecurve back-end team diagnose issues, if any is reported.
- One-time tasks created from the Dispatch screen can no longer be created in 'Payroll verified' status at the time of creation, since this function is for Dispatch staff and only a Payroll admin is allowed to create 'Payroll verified' tasks.
- In the Employee Transfer screen, the system now displays the Corporate Employee ID of the employee being transferred when the user hovers the mouse over the employee name. This is to help the user identify the correct employee when two or more employees share the same first and last names.
Bug fixes:
- Vehicles added through the API are unavailable for assignments. This issue has been fixed.
- In the 'Operations' tab of the 'Operational Settings' screen, the 'Active' checkboxes for Dispatcher Threshold Alerts have now been enabled. This will allow the user to turn on/off the alerts that appear on the Dispatch screen.
- In the Dispatch screen, the 'Locate buses' function under the 'Frequently used' link includes a 'School' filter. This filter was not working properly and has been addressed.
- Under certain conditions, the 'calculate guarantee' function creates duplicate guarantee records, and this issue is now fixed.
- In the 'Payroll Weekly View' and the 'Payroll Detailed View' screens, when the task code of a task that was created for the selected location is being updated, the corresponding operational task code should also update. This was not the case before, and has been fixed.
- In the 'Dispatch' screen, when the task code of a task assigned to a local employee is updated, the corresponding payroll task code should update but was not updating. This issue has been corrected.
- Task codes updated through the 'Mass Task Code Update' function are not correctly reflected in the Dispatch screen due to a bug introduced with the Transfer/Sharing functionality, and this has been addressed. Also, as part of this fix, only tasks assigned to employees belonging to the selected location that was completed for the selected location will be listed in the 'Task code update list', tasks performed by their employees for a borrowing location will not be included.
- In the 'Location settings' screen, the checkboxes labeled 'GPS enabled' and 'Clock in/out Device Enabled' have been removed, as there is no function tied to these checkboxes in the system.
- There was an issue in the Drive-On app where a task started on a given day was not visible for sign-out the next day, resulting in employees not being able to sign-out of tasks that went past midnight. This has now been addressed.
- In the Drive-On app, notifications (and messages) were not received on certain situations for Android users. This has been fixed.
- In the Drive-On app, the 'Forgot password' screen displays the message 'Need content for the screen', and this has been replaced with a suitable message related to the password reset function.
Known issues / additional information:
- The Import Task feature being added in this release does not support importing tasks that are assigned to a shared vehicle or employee belonging to a location other than the one for which the tasks are being imported.
- The Import Task feature does not allow to import multi-day tasks at this time.
- In the 'Operations' tab of the 'Operational Settings' screen, the user needs to enter some minutes in the alert thresholds columns even if the user does not check any of the boxes to display alerts on the Dispatch screen. If not, the Locate function under the Frequently Used link does not work properly.
- System returns a 400 error when trying to edit a task performed by a shared employee at a borrowing location when employee's home location has its pay-period locked. This will be fixed to return a meaningful error message.
- During re-assignment of employee on the dispatch screen, if the incoming employee has a conflict but one of the tasks allows overlapping assignments, the system displays a warning message. If the user decides to proceed with the assignment, the system should now prompt the user to select a reason as to why the original assignee cannot do the task, and this prompt for selecting the reason is missing in this case.
- Employee Transfer API: the system returns a 500 error if the API is called again to transfer an employee that has already been transferred. This will be fixed to return a valid error message.
- When a new employee or vehicle is created in the system the resource is not available for same-day assignments if the time is past 12:00 AM GMT. This will be fixed to use the local time instead of the GMT.
Release notes - Parent App
Bug fixes:
- When the school geofence is a circle, the fence boundary was not displayed in the bread-crumb trail screen under the Support Assistant function. This has been addressed.
- When a parent user submits feedback (when the user is randomly selected for feedback request), the user's customer information (i.e. School District information) is not captured, making it difficult to reach the parent with a response to the feedback provided. This information is now being captured.
- Fixed a bug that resulted in School Arrival notifications when the student was associated with only a 'From school' key (which should trigger only School Departure notifications).
Known issues from this release:
- When a parent user follows a student with a mid-day bell time and another with a regular bell time in any school, and if there is a calendar entry for the regular bell time, the zone active windows are not calculated correctly. This will be addressed in a later release.
If you experience any issues accessing the system after the release, please clear your browser cache and try again. You can follow the link below for instructions on how to clear your cache:
Chrome:
https://bytecurve.freshdesk.com/a/solutions/articles/44002154521
Firefox:
https://bytecurve.freshdesk.com/a/solutions/articles/44002154552