4/16/25 - PakEnergy Transport Release Notes for April 16th

 

 

Enhancements

 

Portal   

Capturing Loaded Miles: A new feature is being released to make it easier for dispatchers to define loaded miles when creating a load or editing a scenario.  When a dispatcher is creating a load, they will be able to click a map view which will launch a popup and display the route between the load's Pickup and Drop Off.  A user can request a hazmat route as well.  The user can adjust the route if needed and when they confirm the route it will save the loaded miles and the scenario URL based on the route created.  This should really streamline the flow of capturing loaded miles or needing to make an adjustment to a scenario's loaded miles

  • Setup > Admin > Commodity - Hazardous Route Yes/No and Substances selected have been added to the commodity level.  When a user is creating a load with a brand-new scenario, when they are defining the scenario route and loaded miles on the map, we will leverage what is defined at the commodity level to prepopulate a hazardous route based on Hazardous Route turned on and the type of Substance selected (if any) at the Commodity level.  

A screenshot of a computer AI-generated content may be incorrect.

 

 

  • On the Load > Manage Load screen, when a user is creating a load with a new scenario, they can click on the following button next to the loaded miles input.  This map icon is also visible next to Rerouted Miles inputs.  When a user clicks on the map icon, a popup will occur which will show the user the Pickup location Lat/Long, Drop Off location Lat/Long and the recommended route between the two locations.  A dispatcher can drag or edit the route which will adjust the loaded miles and time.  The user can also adjust the hazardous route and substances which could impact the route.  When the user clicks OK, we will populate the mileage between Pickup and Drop Off in the loaded miles field and store the defined route in the scenario URL.  The same functionality exists for rerouted miles except the data will be stored in the Rerouted miles field and stored as a secondary scenario. 

 

  • On the Load > Manager Scenario screens (Primary or Secondary), users can click on the MAP icon and make edits to loaded miles and the scenario URL. 

A white rectangular object with a black stripe AI-generated content may be incorrect.

 

A screenshot of a computer AI-generated content may be incorrect.


 

 

 

 

 

 

  • On Setup > Admin > Company tab, DOT number has been added as an available field to input.  This field is being added for our Motive ELD integration which will be released in the coming weeks.

A screenshot of a computer AI-generated content may be incorrect.

 

Mobile

  • No Updates

 

API

  • Setup > Driver API.  The following fields have been added to both inbound and outbound APIs.

applicationDate

licenseNumber

hiringDate

licenseCountry

terminationDate

licenseIssueState

birthDate

licenseIssueDate

mvrDate

licenseExpirationDate

drugTestDate

hazmatIssueDate

medCardIssueDate

hazmatExpirationDate

medCardExpirationDate

oshaIssueDate

twicCardExpirationDate

oshaExpirationDate

cdlClass

 

 

  • Ticket API: Reviewed/Audited Notes have been added to the outbound ticket API as an available field to consume. 
  • Load and Ticket API.  API users can create loads and tickets using historical dates

 

Bugs/Issues

  • Load Manage Load and Review Screen.  If a Pickup or Drop Off location was associated to a contract with an operator change the correct operator was not displayed in the grid. 
  • On Setup > Pickup API or Setup > Drop Off API, if a user attempted to add or edit Lat/Long, the information was not being saved.  This issue has been resolved.