2025-08-27 Release

Created by Brian Glick, Modified on Wed, 5 Nov at 5:38 AM by Brian Glick

New Features

?️ Speed Improvement: All flows have been migrated to our new processing engine reducing total processing time with no change in cost or action needed
?‍? The custom processor editors now support a fully functional code editor instead of plain text for improved coding experience. This includes the ability to pop-out the code editor to full screen.
? You can now download workspace metrics in Excel or CSV. This allows you to quickly download statistics on your flow volumes by status. For more information see this article.
?Custom processors now support Excel. The SheetJS library is available within all custom processors exposed as XLSX. You can both read and write all Excel formats including xls & xlsx within your custom processors. Learn more about custom processors here.
⌚EDI source and destination file types now allow you to configure the time format in the GS Headers. Use the Time Format For EDI Headers dropdown.
?The list of available flows on the new Integration pane now lists send and receive flows separately for improved readability

Bug Fixes

Fix for occasional EDI adapter timeouts related to running jobs which had not been run in a long time
Custom Mapper was failing when users uploaded bad input into the left pane.
EDI maps were sometimes not immediately available in the adaptor list

Adapter Updates

The Document Packet adapter now supports new options. Learn more here.
- You can exclude documents from the packet by file type of
- You can exclude old versions of the same document from the packet
CSV Parsers (like Product CSV & Order CSV) now handle Excel Binary (XLSB) format in addition to the more common XLSX format. This is handled by the adapter and you do not need to make any changes.
Standard Organization JSON now supports a Native Reference Numbers array for entering arbitrary reference numbers. Learn more here.
EDI
- The Custom Mapping Tool now supports ANSI EDI 846 Inventory Inquiry/Advice document types
- Outbound EDI Invoice Mapping (310, 210, 110) now includes fields for
  - invoice_category
  - location_identifier (from the party’s canonical owners_id)
  - invoice_line.converted_amount
  - pickup_estimated date & time
  - pickup_distance_kms, pickup_distance_original_uom, delivery_distance_kms, delivery_distance_original_uom
Cargowise
- Cargowise eAdaptor Next is now supported within Chain.io as a Host System. See this article for instructions on setting it up.
- New Adapter: Cargowise Native Organization Destination File Type is now available under the Master Data Management - Receive Organization flow. This supports creating and updating header level and address records for organizations.
- Cargowise XUT Source File Type maps the Category field to the canonical invoice_category field
- Cargowise XUT Destination File Type maps the PostingJournal/CostSource/Key from the parent object’s forwarder_reference to accurately set job numbers in posting journal entries
- Cargowise Native Rate Destination File Type now properly handles custom zones within the <DomesticZone> tag
- Cargowise XUS Source File Type now maps the pickup/delivery distance and unit from the PreCarriageShipmentCollection & PostCarriageShipmentCollection to new shipment canonical fields (pickup_distance_kms, pickup_distance_original_uom, delivery_distance_kms, delivery_distance_original_uom)
Freightos/WebCargo OpenFreight Shipment Update now supports package dimensions
All Infor Nexus Destination File Types (XML, 214, 315) are not available in receive event flows.
Mercury Gate Tender Reply Destination File Type is now available in the receive booking flow allowing you to auto-reply to load tenders without having to run them through your TMS first.