05/28/2025 Release Notes

5/28/25 - PakEnergy Transport Release Notes for May 28th 2025

Enhancements

Portal   

• Motive Integration
  • An integration with Motive ELD/Telematics has been completed.   The integration works very similar to Geotab and Samsara
    • Drivers, Trucks and Trailers can be setup within PakTransport and flow to Motive.  Any edits to these entities can be changed within PakTransport and Motive will be updated.
    • Odometers and Lat/Long data is pulled from Motive and used within PakTransport on the mobile and portal application.
    • HOS (Hours of Service) data is pulled from Motive and displays on the Dispatch Board and within the Mobile application. 
  • Future To Do: By the end of June, shipment logs will automatically post to the drivers log within Motive. 

• Finance
  • A new calculation component called "Scenario Loaded Miles" has been added.  The scenario loaded miles enables trucking companies to obtain the scenario miles for each pickup to drop off within a load.  Currently, if a load has 3 pickups and 1 drop off, all three tickets (pickup 1 to drop off 1, pickup 2 to drop off 1 and pickup 3 to drop off 1) will use the same loaded miles (pickup 1 to drop off 1).  The scenario loaded miles component will obtain the scenario miles from the load > manage scenario screen for pickup 1 to drop off 1, pickup 2 to drop off 1 and pickup 3 to drop off 1.  This component can be combined with loaded miles lookup (scenario loaded miles) to obtain unique rates per mileage ban for each unique scenario. 

• Time Off Buy Backs
  • On setup > driver screen, if a company is using PakTransport to manage time off requests and a driver wants to buy back all remaining/unused time off for the remainder of the year, a trucking company can add a buy back.  When adding a buyback, it will add total used days by the amount of time off buyback days or hours entered and reduce the total remaining days or hours.  This feature will NOT complete loads or tickets if this feature is turned on. 

Mobile

• NA

API

• On the setup > pickup api, tank reference no and tank reference ID are added to the outbound API.

Bugs/Issues

• On Finance > Contract screen, if a user clicked a contract which had a pricebook, the pricebook did not always load on first attempt.  This issue has been resolved. 
• On Dispatch > Dispatch Board, if a user defined an inline filter within a grid and then assigned a load, the inline filter would NOT hold.  This issue has been resolved
• On Dispatch > Dispatch Board, if a user had a driver selected in driver available grid or in working today section and then right clicked on open load and assigned load to selected driver OR dragged load down to this selected driver, after the screen refreshed this driver was NOT selected any longer.  This issue has been resolved. 
• Review > Ticket Import:  When tickets are being imported, the pickup depart date/time and completion date/time are required.  If driver accepted date/time, pickup arrival date/time are NOT provided in the excel file it will auto populate these fields with the pickup depart date/time.  If drop off arrival date/time is not provided, this field will auto populate with completion date/time. Currently it populates ticket import date/time for these fields if not provided. 
• When a user is adding a NEW ticket to an existing load and this ticket has a dependency form, the dependency form data/rows would NOT save properly on first save.  This issue has been resolved. 
• On setup > pickup, when user is adding tank strapping information and using the tab key, the cursor would move to the first row in some use cases.  This issue has been resolved.