The following are the changes in the upcoming release
Bytecurve360 (Scheduling & Dispatch, Time & Attendance)
New features:
- Ability to transfer employees and vehicles from one location to another provided B360 is implemented on both the 'transfer from' and the 'transfer to' locations. Click to Read More
- Added integration with the Gatekeeper telematics device
Enhancements:
- When a shared employee performs tasks for a borrowing location, the employee can now be paid from his/her home location by changing the task code to a home location task code. This task will also be included in guarantee and overtime calculations, based on the task code assigned to the task performed by the employee at the borrowing location. Click to Read More
- A filter option on the Manage Employee and Manage Vehicle screens to filter All / Shared / Unshared employees/vehicles. The icon that indicated that an employee was shared has been removed.
- Sharing of vehicles and employees can now be set up to be effective on the same day (instead of having to wait a day for it to be effective).
- The Payroll->Verify Hours screen has been modified to display one day's data at a time. This is primarily to enhance the response times of the screen and also to enable the display of tasks performed by transferred employees coming in to the location in the middle of a pay-week. Click to Read More
- UI enhancements to the pay-file transmission process: (i) Added a 'Transmit' button on the pay-file review screen to make the user aware of the step required to complete the transmission process. (ii) When transmitting the pay-file, a message to indicate when and who transmitted the pay-file if it has already been transmitted previously.
- Enhancements to the Payroll->Pay periods screen to show the number of times a given location has generated the pay-file with the goal of transmitting the file and how of these were actually transmitted.
- The upper limit of employee pay rates has now been increased from $100 to $300. This is to enable 'Flat rates' to be saved in addition to hourly rates, since flat rates can go up to $300 per task.
- When a task in the Master Schedule does not have a start or end time, the option to create additional driving or monitor tasks for this task are now disabled. This is to prevent the creation of Daily tasks with missing task attributes.
- The School Details screen has been updated to capture multiple bell times for a school, but this has no functional impact on the Bytecurve360 product.
Bug fixes:
- For Runs that have been imported from a third party routing software, the RPS ID is used as the key to uniquely identify if the Run is a new addition or an update to an existing Run. The system was using a combination of Run name, Dispatch and Days of the Week, which is not as reliable since users update Run names in the routing software for an existing Run.
- There was an issue with the geofence definition of schools when different fences were drawn for pick-up and drop-off, where one of the fences was not saved under certain situations. This issue has now been addressed.
- 'Get Daily Task' reporting API did not return guarantee tasks when using the 'created / updated after' parameter. This has been addressed.
- In the Transfinder PLUS routing interface, when a school returned is missing in B360, none of the stops returned for that Run are saved. This has now been addressed such that all stops including the missing school stop are saved as 'regular' stops.
- When there is a shift in daily tasks times due to a school calendar entry, the task start and end times do not get updated when the flag to 'auto-update task start/end times' is not checked. A change has been made to ignore this flag if the change in task start/end times is triggered by a school calendar entry.
Known issues / changes to existing behavior from this release:
- When a new employee is added to a location in the middle of a pay-period, the employee cannot be assigned to any tasks prior to the date the employee was added or the 'hire date' of the employee, whichever is earlier. For the hire date to apply, it must be entered at the time the employee is added to the system; updating the hire date after the employee has been added to the system will not have the same effect.
- The Payroll Report off the Reports menu is not functional at this time and has temporarily been removed from your menu items. A separate notification will be sent out when this report is available again and the report has been added back to your role.
Release notes - Parent App
New features:
- Enable tracking of mid-day routes. To support this feature, the system now allows multiple bell times to be captured for schools, since the parent app uses school bell times to define the time window for bus tracking.
Enhancements:
- When viewing the GPS datapoints on the breadcrumb trail of the bus in the Support Assistant->Notification settings screen, the user will be able to see when the datapoint was collected by the device as well as when it was saved in the Telematics provider's backend database. This will help identify cellular latency issues in the GPS data being available to the Bytecurve Parent App, that may have resulted in missing or delayed notifications. Click to Read More
- In the email generated when the parent customer sends a support question, the user's first and last names are now added.
Bug fixes:
- When a mobile app user has not defined any alert zone and has also not given the app permission to access the phone's location, the map view on the Home screen centers around the city of Lebanon, KS. This has now been addressed to center around the school district address.
- When the AM and PM keys are assigned to different buses and all school notifications are turned on, both vehicles are displayed on the map during the school's active window. This has been corrected to display either the PM or the AM key depending on whether the bus is going 'To school' or 'From school'.
- There was an issue with the geofence definition of schools when different fences were drawn for pick-up and drop-off, where one of the fences was not saved under certain situations. This issue has now been addressed.
- In the Support Assistant->Notification settings screen, under the breadcrumb trail view of the bus going to/from school, in incorrect fence was displayed under certain conditions. This has now been corrected.
Known issues from this release:
- When the school geofence is a circle, the fence boundary does not show up in the bread-crumb trail screen. If bread-crumb data is available for the default date and time window, this will be displayed when the user clicks on 'Submit'.
The work-around for this is to cross-reference the geo-fence in the 'School detail' screen and then change the geo-fence to a polygon. This will be fixed in the next release, in July 2022.
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