Silverlining
- Changed the way high speeds are included in the Speeding reports: Before, all event data was dropped for speeds over 100 mph; now, we'll report those higher speeds, as long as the satellite count remains above 8.
- Fixed an issue that was preventing idling events from being reported.
- Removed several deprecated customer settings.
- For MDT customers, removed the Publish button from the Canned Messages screen, which doesn't apply to the current Synovia MDTs, as they pull in new and edited messages at startup.
Comparative Analysis - Silverlining
- For EDULOG SQL customers, refactored the method for collecting student stop data, which will improve performance time.
- For EDULOG SQL customers, created a new filter that will allow checkpoint stops to be ignored.
- Modified the parameters for starting job processing after imports to work with the ALK addresses/maps.
- Implemented a new method for checking the client status.
- For BusPlanner customers, fixed a bug that was causing some missing itineraries.
- Added an option to the Scan History SPED Ridership report's parameters to either ignore duplicate scans or include them in the results.
- Changed the Map Scan History results to not cluster the student scans on the map (which they have been doing since the ALK transition).
Synovia Site (https://login.synovia.com)
- For Chrome users, improved the performance of the site by handling an issue that was causing lag when Synovia tried to pull down new alerts, particularly for customers with a large number of unacknowledged alerts.
- For MDT customers, fixed an incorrect default setting that was preventing messages from being sent from the Fleet Tracking screen.
- Added the ability to make a message to an MDT be marked as "High Priority." If the customer has the latest version of the MDT app, the driver will be alerted to an urgent message.
- Fixed an issue that caused pop-up filters in reports to display a "Mixed Content" security warning.
- Fixed a bug that caused deleted locations to still appear when showing zones in Fleet Tracking.
Time and Attendance
- For customers using the Generic Individual Scans export, changed the method of exporting absences as a separate file (which was added in the 2018.01 release); now, users have the options of separating out absences and/or holidays in different rows and of including absences and/or holidays in the export as a whole (as appended shifts).
- Fixed an issue with the Daily Shift Summary by Job Code export that was reporting the same values for Job Type and Job Type ID.
- Fixed an issue in which users were selecting Include Inactive Employees for their exports, but no inactive employees were added.
- Fixed an issue with a misleading time format in emails that were telling employees their time cards were edited when absences were added or changed for them.
- Fixed an issue that was preventing some departments and employees from appearing on trees on various screens.
- Fixed a bug that was assigning a different job type to a new JobType level rounding rule than the one that was selected in the Assign Rounding Policy pop-up window.
- Fixed a bug on the Time Card screen that was displaying shifts to be in error (in red and diagonally striped), but there were no errors on the Time Card edit screen.
- Added logic that will email an employee their new password if their TAA Portal password is reset.
- Fixed an issue that threw an error if a user first tried to enter a value when resetting an employee's TAA Portal password and then switched to the employee ID.
- Fixed a bug that allowed one employee to be assigned multiple punch IDs (when assigning a new ID, the original one would also be attached to the employee's record), which caused creating new shifts for the employee to error out.
- Fixed an issue with Shift Analyzer carry over rules that caused errors when users applied rounding after the carry over shifts were added – in some cases, work time was missed, and in others, employees were given the time twice.
- Added logic that will email an employee if their time card is edited after they've approved it.
To see a video of some of these new features, go to 2018.03 TAA Updates.
Route Builder
- Added a right-click option to uncommit a snapshot so that the user can make changes, as long as the snapshot's start date is in the future. If the start date is today or before, changes to a committed snapshot are still not allowed.
- Changed the pop-up messages that appear when students are added to tiers to make what the dialog boxes do clearer; now when adding students to an AM tier, the message says, "Do you also want to assign these students to the School Drop-Off stop?" and when adding them to a PM tier: "Do you also want to assign these students to the School Pickup stop?"
- Fixed an issue that was preventing users from adding tiers to newly added schools.
- Fixed the Maximize Map feature on the Add Stops screen.
To see a video of some of these new features, go to 2018.03 Route Builder Updates.
Here Comes the Bus
- On the website's Notifications History tab, fixed the blank item in the Notification Type drop-down list to show the Calendar Exception option.
API
- Added Last Engine Report to the s0116 call (Get Last Position).
- Fixed an issue that was causing discrepancies between the API data and what was reported on the Hardware screen. In some cases, missing data was caused by unplugged ED cables.
Engine Diagnostics
- Added a method for better detection of hardware not being properly configured or plugged in.
- Added a raw output table for ODBII like the v144 raw table, which returns a day's worth of last value odometer/fuel values parsed out of packets (as requested by the user).
Micronet A317 MDT
- In Silverlining, removed the Publish button from the Canned Messages screen, which doesn't apply to the current Synovia MDTs, as they pull in new and edited messages at startup.
- In Synovia, fixed an incorrect default setting that was preventing messages from being sent from the Fleet Tracking screen.
- In Synovia, added the ability to make a message to an MDT be marked as "High Priority." If the customer has the latest version of the MDT app, the driver will be alerted to an urgent message.