Extra OeBolFil Placeholder Records Created When Backing Out Shipments
When backing out a shipment—specifically for ,LTL shipments, or when ,Agility Shipping, was enabled—the system was incorrectly creating additional ,placeholder records, in the ,OeBolFil, table. These records were not needed and caused inconsistencies in shipment data. This behavior has been corrected
BOL information not writing back OEBOLORD_sql table
When shipping from the ,Shipping Tree,, users entering Bill of Lading (BOL) information and clicking ,Ship, found that the data was only being written to the ,oebolfil_sql, table. The ,oebolord_sql, table was not receiving the updated BOL information as expected. This issue has been corrected. BOL details entered during the shipping process are now properly written to ,both, ,oebolfil_sql, and ,oebolord_sql,.
Added 64-Bit Compatibility for Agility Product Suite
Agility Products have been updated to support 64-bit architecture. This upgrade enhances performance, stability, and compatibility with modern operating systems and environments. It also enables larger memory utilization for improved scalability and prepares the platform for future enhancements.
Update FedEx Service Type Enum for International Priority Shipping
Some international shipments were failing, and others were not generating the correct labels due to an incorrect API service type code being passed to FedEx. The FedEx documentation lists in incorrect service type. The mapping has now been corrected in the ship mapping database from ,FEDEX_INTERNATIONAL_PRIORITY, to ,INTERNATIONAL_PRIORITY,, ensuring proper label creation going forward.
Agility Shipping FedEx International Broker Country Code error when no broker
When shipping internationally with FedEx, some users received an error BROKER.COUNTRY.INVALID if no broker information was provided. This has been corrected so that blank broker requests are no longer sent to the FedEx API.