Please note, the Bytecurve applications are fully tested in the Chrome browser and are certified to work in this browser.
If you use the Edge browser, you may continue to do so as we are not aware of any issues with this at this time. However, if you run into any issues, please switch to Chrome.
Bytecurve360 (Scheduling & Dispatch, Time & Attendance) - version 23
Features:
No new features included in this release
Enhancements:
- The routing interface definition screen has been enhanced with the ability to create a copy of an existing interface. This will help speed up the creation of new routing interfaces, and will also allow users to create their own routing interfaces if they have all the required parameter values.
- The nightly 'generate' process to create the daily tasks in the Dispatch screen has been streamlined to kick off based on the local time-zone, between 9:00 PM and 3:00 AM. This is to ensure the tasks are generated accurately within the available nightly batch window.
Bug fixes:
- The Locate Bus function under the Frequently Used link in the Dispatch screen did not work as expected when a Location had a large number of buses (around 400 or more). This has been fixed.
- BusPlanner interface had an issue where the 'databaseGUID' parameter specified in the interface definition was not applied when pulling route data. This prevented a location from pulling routes from more than one BusPlanner database at any given time and failed to pull Stop data unless the Run belonged to the default database. This has been addressed.
- In the Route Import function, when a task in the import file includes the task-code to be set and this task-code has its 'Hours Worked' attribute set to 'No', this system incorrectly assigns this task-code to the task. This has been corrected to apply the Location's default task code instead.
- In the Route Import function, when a task in the import file includes the task-code to be set and this task-code does not allow overlap, the system incorrectly assigns the location's default task-code to the task. This has been corrected to apply the task-code provided with the record in the file.
- When Runs are refreshed through a routing interface to an external route planning system, the yard departure time was not calculated properly under certain circumstances. This issue has been fixed.
- When a task includes both driver and monitor assignments, and a drive-time adjustment time is entered for yard departure or return, the system applies this adjustment only to the Driver task. This has been corrected to apply to both the Driver and Monitor tasks.
- When Runs are added or removed to/from a route and this triggers a recalculation of the the yard departure/return times, any drive-time adjustments defined for the task are ignored. This has now been addressed.
- When the yard assigned to a driving task is changed in the Schedule screen, the yard 'Estimated drive time' from / to the yard selected was displayed incorrectly if the task has any drive-time adjustment values defined. This has been corrected.
- The 'daily generate' process has been updated to help sequence the generate process such that the Eastern time-zone locations go first, then the Central time-zone locations and so on. This is to take advantage of the time-zone differences across locations to extend the batch window available to complete the generate process for all locations in a timely manner.
Known issues from this release
None
Bytecurve Parent app (MyView, Safestop, Where's my kid) - version 22
(The changes listed here impact only the Parent App portal. There is no change to the parent app facing mobile app)
Features:
A new feature has been added to enable nightly batch refresh of student data from an student file to be provided at a customer provided external secure FTP server. For more information please contact support@bytecurve.com.
Enhancements:
- The Student import process has been enhanced to improve error handling, performance and overall ease of use. For more information see article here.
Bug fixes:
- The provision to re-activate an inactive vehicle->key mapping has been removed, as this was at times resulting in more than one vehicle being mapped to a given key.
Known issues from this release
- When a student data file is submitted for import from the UI, the system displays a message directing the user to check the 'Parent App Notifications' screen for updates. This message pop-up closes automatically after ten seconds or so, and this may not be enough time for some first-time users to fully process the message. The persistence window of this message will be increased in a future release.
- On the 'Parent App Notifications' screen, a listing of all the completed Student Import submissions is displayed. This is currently displayed in the increasing chronological order such that the most recent run of the import is last in the list. The sort order will be corrected in a subsequent release, so that the order of the listing is in the reverse chronological order