CalAmp K-12 Mobile App


  • Fixed an issue that wouldn’t load all the routes and runs for drivers.


Comparative Analysis


  • For customers who are using the Overwrite Bell Time feature for their school locations, changed the Arrival Summary by School Legacy report (in the School Arrival [Bell Time] category) to use the manually entered bell times and the new processing for displaying more accurate Missed statuses.
  • Changed the Arrival Summary by Tier Legacy and Arrival Detail by Vehicle Legacy reports to limit the Program column results to only programs active in the specified date range (not historical ones as well).
  • On the Add/Edit School screen, fixed a bug that would allow users to save the AM and PM bell times but would actually store values an hour off.


Here Comes the Bus


  • Changed the Contact Support page to make the Student Name, Student ID, and Description of Issue fields required.
  • Expanded our PIN (personal identification number) support to include Versatrans API customers. (In release 2023.18, we added the ability for school districts to allow only authorized account holders to add students to their HCTB accounts via a district-provided PIN.) The PINs can be included as part of the nightly import process.

    In addition, added an admittedly redundant “PIN Number” field to the student Information screen for all customers.
    Note: You can contact your customer success manager (CSM) to enable this for your account.
  • In CalAmp K-12, for customers with the HCTB Activities license, fixed an issue with the Activity Monitor that was leaving the page data static if the user left it, went and made a change on a different screen, and returned. (For example, if they left the Activity Monitor, went to the Activities screen and added a new activity, and returned to the Activity Monitor, the new activity wouldn’t appear in the list.)


JSON API


  • Added four new optional input parameters to the event/VehicleHistory and event/VehicleEventHistory methods: processedStartDateUTC, processedEndDateUTC, startEventHistoryId, and endEventHistoryId, which will return the start and end dates of the processed time in UTC (when the event was stored in the database) and the start and end event IDs. We added logTimeUtc, processedTime, and processedTimeUTC values to the response.