Bytecurve360 (Scheduling & Dispatch, Time & Attendance)


New features:

  1. Integration with Parent App: when a vehicle assigned to a Route in B360 is swapped out in the Dispatch screen, the system checks for Keys that are assigned to the same vehicle in the Parent App and prompts the user to indicate if the same bus swap needs to be cascaded to the Parent App Keys.  Based on the user response, the vehicle re-assignment is applied to the selected Keys.   Read More about this feature in our Knowledge Base.


  2. Foundational changes to maintain audit information pertaining to changes made to dispatch and payroll related attributes of task data.  A report will be made available to view historical changes to such attributes with the username of the person making the change and the date-time the change was made.


Enhancements:

  1. Added provision to allow for ad hoc flat dollar amounts to be entered as payment to employee for work performed, up to $1000.  This does not include payments for bonuses, reimbursements, etc.  
    Note: if you have a need to include flat dollar amounts in your pay-file, please contact Bytecurve and we will work with you to update your pay-file generation process.  Until this is complete, you should not be entering any flat dollar amounts in the Verify Payroll screen.
  2. On the Schedule and Dispatch screens, when the user hovers over the Route (Task) name, the system will now display the names of the Runs that comprise the Route, if the Route includes any Runs.  Otherwise, the text 'No Runs assigned' is displayed. 
  3. When a de-activated employee is re-activated, the employee will be added back to the Overtime rule the employee belonged to at the time of re-activation.  If the employee never belonged to an OT rule or the OT rule he/she belonged to is no longer active, the employee will be added back to the default OT rule for the employee's location if one exists  This is to ensure that a re-activated employee does not miss any OT compensation due to staff oversight.
  4. When an Employee record is added or edited and the Corporate Employee ID or Employee Badge ID is not unique across the company, the error message displayed has been enhanced to include the Location where the duplicate exists.
  5. When a Vehicle record is added or edited and the Corporate Asset ID or the GPS Vehicle ID is not unique across the company, the error message displayed has been enhanced to include the Location where the duplicate exists.
  6. Added 'Fueling' as one of the late clock-out reasons when an employee punches out of his/her task from an electronic device.
  7. On the Manage Employee summary screen, an additional option has been added to filter the employee list based on Corporate Employee ID field.
  8. The maximum allowable pay-rate was set at $350.  This limit has now been updated to $500.
  9. In the Schedule screen, the option to view and change the departure and return yards has been added, for Indirect tasks that require a vehicle (such as Shuttle service, etc.).

Bug fixes:

  1. In the Tyler Onboard routing interface, there was an error in saving the lat/longs of stops.  This has been corrected.
  2. The 'Stop Exclusion' feature was not working as designed for the Traversa Run Import interface.  This feature has now been added to the interface.
  3. The  Route Import function is designed to include only two valid options: 'Add' and 'Delete'.  The system allowed an invalid option, 'Update', that did not actually perform any update function, and has been removed.
  4. When importing Routes from a Route import file that includes duplicate Routes, the error message displayed has been updated to provide more clarity to the user.
  5. On the Payroll->Verify Hours screen, when a task with an electronic punch out is split, the sign-out time of the second task is now indicated as an electronic punch-out and the sign-in time of the second task is indicated as a manual punch-in.  This was not the case before and has been corrected.
  6. The Vehicle Transfer API allowed current date as a valid transfer date, while the application functionality requires the transfer date to be in the past.  The error in the API has now been fixed.
  7. On the Change Password screen, an option has been added to allow the user see the typed text of the password.
  8. Issues with the school de-activation function have been resolved; users will now be able to de-activate any school that is not associated with any Run in the B360 system or with any Student in the Parent App.
  9. The pop-up window used to enable sharing of Employee or Vehicle included references to enable loaning of resources between locations.  Since the Loaning feature has not yet been implemented, this was causing some confusion among users and hence the fields related to this feature have now been removed.
  10. The display on the Dispatch screen was distorted when multiple task codes are selected in the task code filter on this screen.  This issue has now been fixed.
  11. On the Manage Schools screen, some of  the address fields did not allow hyphens or apostrophes.  This has been addressed.
  12. When an Employee who is a registered user of the DriveOn app is deleted, his/her DriveOn associations are now removed.  This will allow the Employee to register fresh on a different mobile phone at a later time if he/she were to be re-hired.
  13. When two overlapping HTS driving tasks have the same monitor assigned in Dispatch, the system did not allow the driver of either task to be changed.  This issue has been resolved.
  14. The Task Import feature has been corrected to use the Walk/Buffer time that's assigned to the default yard.  The default walk time assigned to the Location was being used for this purpose before, which was incorrect. 
  15. When a user successfully resets his/her password, the previously displayed unsuccessful login message was not removed, causing confusion among some users.  This has not been corrected.
  16. When an employee is re-assigned for a task that allows conflict, there was no provision to capture the reason for re-assignment.  The system now prompts the user to pick a reason for re-assignment and saves the entered selection.
  17. Under certain situations, the system did not allow the user to update an overtime rule that is flagged as the default OT rule for the given location.  This issue has been corrected.
  18. In the Schedule screen, when assigning an employee with a schedule conflict to a task that allows overlapping assignments, the warning message that is displayed did not show the start and end time of the conflicting task. This has now been addressed.

Known issues / additional information

            None


Release notes - Parent App

Enhancements:

  1. The Notification Settings tab of the Support Assistant screen does not currently list user created Zones that have no key mapping.  This screen has been enhanced to list such Zones as well, to help with analyzing support questions.
  2. The Bus Reassignments screen filter has been updated to allow filtering based on the Actual Vehicle column, in addition to the Planned Vehicle column that this filter currently works on.
  3. A GPS Status indicator has been added to the Support Assistant screen, to display a green, yellow or red dot based on the time difference between the current time and the last GPS data point received.  This will serve to alert the user to potential GPS issues if the color is yellow or red when the buses are known to be on the road, sending GPS messages.
  4. A suitable message has been added to the bread-crumb trail screen under Support Assistant, if no GPS data is available at source, for the selected date and time range.
  5. On the Support Assistant summary screen, an additional column has been included to display the date the parent user received his/her last notification.  This is to indicate at a glance how parents are doing with their notifications.
  6. Additional functionality has been added to the Support Assistant screen, to view parent accounts that have been deleted and to re-activate them from the Parent App portal.  This can now be done from the Support Assistant screen
  7. On the mobile app, when a Zone is added or edited, a message has been added to inform the user that notifications based on these changes will take effect from the following day.  A similar message will also be displayed when the user completes his/her addition of Zones as part of the onboarding process.


Bug fixes:

  1. On the Contact Support screen in the mobile app, the link to support documentation has been replaced by hyperlink in lieu of the full URL. Also, this was not working for Android phones, and this has been fixed.
  2. Message counter does not increment when the app is closed while push notifications are on, this has been addressed.
  3. Fixed an issue in the calculation of the active tracking window for students associated with a secondary bell time of a school, when that secondary bell time is deleted.


Known issues from this release:

            None


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