PakEnergy Transportation Release Notes 02/19/2025

 

Portal Enhancements

Recompute Gross/GSV/Net and Corrected Gravity Via API              

  1. API users who are creating or updating CRUDE commodity tickets via the API can now include the following parameter usePakEnergyStrappings = TRUE.  
    1. When this parameter is sent as True, the Gross Barrels, GSV, NET and Corrected Gravity will recalculate based upon the tank strappings stored in the system.  
    2. This works the same as Review > Ticket Import when a company selects Gross Barrels/Net Barrels = PakEnergy.  If this parameter is sent as false or not provided then we will consume the Gross Barrels, GSV, NET and Corrected Gravity provided for these fields in the request.


 Mobile Enhancements

  1. Setup > Code > Photo Type > Before Depart: If the photo type requirement has been turned on for "Before Depart", the driver can now click Sign and Print and when they click the Depart button we will ask the driver to take required photos. 

 

  1. ELD Integration Odometer - When driver is on login, Pickup, Drop Off or Submit Shift and Logout, if the odometer we received from the ELD provider was lower than the last known odometer, we were disregarding this value.  
    1. Moving forward we will always update last known odometer with the latest odometer from the ELD provider.   


  1. Last Known Odometer - On login > shift or DVIR/Shift > Shift screen, the last known odometer/system odometer will populate to the right of the driver edited odometer.  When the shift form loads or when the truck is selected, both values will be the same. The driver can edit the odometer and if they do this will be stored as the DRIVER EDITED odometer on the submit shift screen.  The read only odometer on the right will be the system generated login odometer on submit shift screen. 
    • undefined


 Sneak Peak/New Feature Coming 3/5 - Load Requirements

  1. Load Requirements is a new feature which enables a company to input various requirements for Pickup and Drop Off locations and verify if the driver, truck or trailer can meet these requirements.  Outlined below are several examples:
  • If a Drop Off location requires training.  A requirement can be created with the Drop Offs name + Training.  This requirement can be added to the Setup > Drop Off screen.   As drivers are trained at this Drop Off location, this requirement can be added to the Driver on the Setup > Driver screen.
  • If a Drop Off location requires a TWIC card.  A requirement can be created named TWIC CARD.  This requirement can be added to the Drop Offs which require a TWIC CARD on the Setup > Drop Off screen.   For drivers who have a TWIC card, the TWIC CARD requirement can be added to the drivers who have a TWIC CARD on the Setup > Driver screen.
  • If a Pickup location requires a 30-foot hose to reach the header and extract the oil.  A requirement called 30ft Hose can be created and added to the Pickup locations with this requirement on the Setup > Pickup screen.  For all trailers which have a 30ft Hose, this requirement can be added to the trailer on the Setup > Truck/Trailer screen. 
  • If a Pickup location requires a Day Cab truck to access it.  A new requirement can be created called Day Cab.  This requirement can be added to all Pickup locations which require a Day Cab on the Setup > Pickup screen.  For all trucks which are a Day Cab, this requirement can be added to all trucks on the Setup > Truck/Trailer screen.
  1. Load Requirements is NOT included in this build but is planned for our 3/5 release.  


 

Bugs

  • On the Finance > Invoice and Finance > Payroll screen, the Clear Sort button will properly clear all sorts from all columns.
  • On the Finance > Invoice and Finance > Payroll screen, the last modified Date/Time properly displays the value from the ticket rating-values table.
  • When generating Run Tickets, if a Drop Off ticket has been OMITTED, it will NOT print a page for this Drop Off.