Skip to main content
J. J. Keller Support Center

Encompass Release (12/18/2024)

Area Description Reference ID
HOS Log Entry

This feature is to add a 'click experience' when adding HOS logs. Some users in Classic Encompass today are used to using

a grid to enter their logs as opposed to the 10-key entry.  They find it is faster for them to implement.

  • We will roll out the feature selectively at first and then after some feedback will roll out to all customers.
  • Detailed documentation will be provided also.
150962
ELD

Data Diagnostics and ELD Malfunctions

  • To comply with FMCSA ELD Mandate requirements we added a new Data Diagnostics and ELD Malfunction capability.
  • Documentation is required to describe all the changes and functions and will be provided.
  • We will roll out the feature when all launch materials are ready.
150214
IFTA Tax Rates Modified the IFTA Tax Tables for jurisdictions for Q4 2024. 155974
Disconnected Driving

A change was discovered that prevented the disconnected driving messages from being processed and alert emails sent out

due to being stuck in the event queue.  This change was deployed prior to the release as a hot fix.

157013
One-Time PMs

For a PM that is not recurring and is entered and completed, it was showing on past due and shouldn’t be.  The following are

the rules for display:

  • Roster - No PM should show up in the PM Roster tabs past due, Due in 30, or Due in 60 if it is the only PM for the Unit,. 
  • Roster - If the unit has multiple PMs and at least one is active (is recurring or is not recurring with no completed date),

             this completed PM should show up in the PM Roster tab all but not be highlighted even if it is within the PM Alert range

            (Due,Due in 30, or Due in 60). 

  • Roster - This PM should not show up in the PM Due, Due in 30, or Due in 60 tabs.
  • Maintenance Card - The PM should not be highlighted within the Unit Maintenance Card
156506
PM Date Equals Current Date

Logic was improperly including PMs in the Due in 30 when the due date was the current day.  It will now not be part of Due in 30

and then will display and be highlighted in RED as due in the PM Roster and Unit Maintenance.  Also corrected an issue that was

causing due in 30/60 to not display all PMs.

156433 &

157079

Training Refresh

Page was changed so that the Next Due field updated after employee is enrolled in a course without having to refresh the page.

148898
FMCSA PSP

In Settings/Applicants/Hiring Process/Third Party Providers the option to enable the FMCSA PSP was not displaying in the

UI and has now been added for selection.

112872
Training Tab

Corrected and error in the enrollment service when there are no enrollments in Training on Demand for a company.  In this

situation, a 404 error was erroneously displayed instead of the training tab for these employees.  Problem happened more

prevalently when employees were enrolled and then unenrolled from all training courses.

157174
Classic Reporting 

Corrected an internal technical issue that caused 4 reports in Classic to not run.  The reports impacted and now executing

correctly are: Trip Information, State & Province Tax Report, Violation Summary, Violation History.

156637
Date Entry

A user was allowed to erroneously enter future dates for the DQ prequalification, maintenance areas, and Training areas.

 Entering a future date on a prequal checklist item can cause Encompass to flag the driver as having an incomplete DQ file.

  Changes made to not allow future date entry in Driver/Prequalification Checklist and Maintenance Checklist and Training/Initial

Training and Last Completed.

155431
InfoMart MVR An error was fixed that prevented requesting an MVR via InfoMart.  The error was Invalid test SSN. 157694
ELD Output File

A minor change was made to include the driver’s previous duty status to the time period requested.  This is required by FMCSA

regulation.

150604
HOS Audit

A problem was fixed where a log was created with a violation and then when the audit was run it tried to create the same

violation and the 2 records collided causing a failure.

154935
  • Was this article helpful?