Release Notes

2026-09-29

GraphQL — Range Filters on a Single Field

  • All list queries support combining multiple operators on the same field in one where condition. For example, to query shipments in a status range:

    where: { status_id: { gte: 0, lt: 17 } }
    

GraphQL — Date/Time Format Simplified

  • Time zone: all date-time values (both output and filter input) are in the time zone configured for your current company branch — not UTC, and not the API server's time zone. Make sure your branch's time zone setting is correct.

  • Output: all date-time fields now return plain local time in yyyy-MM-dd HH:mm:ss format, e.g. 2026-04-15 23:53:33. The misleading "Z" (UTC) suffix has been removed — returned values are local business time, not UTC.

  • Filter input: date filter parameters accept all of the following formats — the T separator and any trailing Z or numeric offset (e.g. +08:00) are accepted and simply ignored; the wall-clock value is used as-is:

    Accepted input Interpreted as
    2026-04-15 23:53:33 2026-04-15 23:53:33 local
    2026-04-15T23:53:33 2026-04-15 23:53:33 local
    2026-04-15T23:53:33Z 2026-04-15 23:53:33 local (suffix ignored)
    2026-04-15T23:53:33+08:00 2026-04-15 23:53:33 local (offset ignored)
    2026-04-15 2026-04-15 00:00:00 local

2026-09-18

Bug Fixes

  • Charge/Cost Vendor Matching — Vendor matching on charge/cost items is now more accurate: company-name matching also takes the country code into account, and each submitted item is always matched to its corresponding charge/cost line. When no matching customer/vendor is found, the submitted company name is no longer carried over into the saved record — the vendor is simply left blank.

  • House Charge/Cost Validation — House charge/cost groups submitted without items no longer cause a validation error; they are simply skipped.

GraphQL Query Fixes

  • Air Export house (AehHouse): the delivery-to party field is now correctly exposed as deliverTo (previously DeliveryTo).
  • Ocean Export master (OemMaster): the hbls house-count field now correctly returns a number instead of a boolean.
  • Ocean Export house (OehHouse): fixed the also_notify_name field, which previously returned a query error.

2026-09-11

Ocean Import — New Master Fields

  • OIM master creation (POST /api/oim, POST /api/oim/with-details, and the corresponding GraphQL mutations) now accepts two new optional date fields:
    • carrier_eta_date — carrier-confirmed ETA at port of discharge
    • vessel_arrive_date — actual vessel arrival date at port of discharge

Document / Note API — Header Node Removed

  • The header node has been removed from the request payloads of the Document Upload (/api/document) and Note Upload (/api/note) APIs. Group code and branch code are now derived automatically from the authenticated API user and no longer need to be supplied in the request body.
  • Backward compatible: existing integrations keep working without any changes. Requests that still include the header node are accepted; the node is simply ignored.

2026-08-21

Air / Ocean Import Re-import Support

  • Air Import and Ocean Import creation endpoints now allow re-submitting data for existing shipments in EDI Import status. The existing shipment record is preserved and its details are refreshed with the new submission.
  • Default branch settings now apply to inbound Air/Ocean shipments for fields such as freight terms, load type and SCAC code.

Ocean Import / Ocean Export Load Type

  • Ocean Import and Ocean Export master creation now expose a dedicated load_type field. The consignment_type field is deprecated and will be derived from load_type when not provided.

Customer Entity Mapping Update

  • Customer address mapping has been switched to CvmAddressInput. A new cvm_address_seq_no field is supported so customer addresses can be matched more precisely, especially when company names are duplicated or historical records need to be referenced.

2026-08-17

GraphQL Preview Status Removed

The Preview indicator has been removed from all GraphQL interfaces. All GraphQL queries and mutations have completed testing and are now treated as production-ready.

GraphQL — Air Export (AE) Interface Testing Completed

  • AE GraphQL interfaces (MAWB / HAWB creation, etc.) have been completed and tested.

Adjustments

  • When creating data via Mutations, the charge/cost field names have been changed.
  • Fixed some bugs.

2026-08-11

GraphQL — OI & AI Delete Mutations

Mutation Module Key In
DeleteOimMaster Ocean Import id or masterBlNo
DeleteOihHouse Ocean Import id or houseBlNo
DeleteAimMaster Air Import id or mawbNo
DeleteAihHouse Air Import id or hawbNo
  • Deletes run in a single transaction; rolled back on failure. Returns the deleted record ID.
  • Condition: record must be in EDI Import status. For Master deletes, all child houses must also be EDI Import, or the request is rejected.
  • Cascade: child houses, containers, PO xrefs, charge/cost items, manifests, and extensions are all deleted together.

Input Model Refinements

  • Customer → CvmAddressInput — CvmCustomerDto replaced by CvmAddressInput across all GraphQL types. Key changes:
    • address split into address1 + address2
    • Removed: sub_division_name, country_name, phone_area, operation_email
  • Bug Fix — Fixed vendor mapping on master/house charge/cost creation: vendor is now matched by cvm_address_id first (when provided), with company-name lookup as fallback, and input items are correctly aligned to PLM items by index.

Note: All Create mutations retain the same semantic behaviour. If your integration references removed input fields, update to the new field names listed above.


2026-08-05

GraphQL Mutations & Corresponding REST APIs

A new batch of GraphQL Create mutations has been added, mapped one-to-one with existing REST write endpoints.

Module GraphQL Mutation Description Corresponding REST API
Customer / Vendor CreateCvmAddress / UpdateCvmAddress Create / partially update customer, vendor, or primary address (s_cvm_address) POST /api/cvm (GET /api/cvm/search for lookup)
Domestic CreateDomMaster Create a domestic shipment master with multi-mode legs, POs, and charge/cost items POST /api/dom
Ocean Import CreateOimMaster Create an ocean import master (Master BL) POST /api/oim
Ocean Import CreateOimMasterWithDetails Create master + containers + house bills in a single transaction POST /api/oim/with-details
Ocean Import CreateOimContainer Create a container under a master POST /api/oim/container
Ocean Import CreateOihHouse Create a house bill under a master POST /api/oih
Ocean Import CreateOimMasterChargeCosts / CreateOihHouseChargeCosts Batch create charge/cost items for master / house POST /api/charge-cost/ocean-import
Air Import CreateAimMaster Create an air import master (MAWB) POST /api/aim
Air Import CreateAimMasterWithDetails Create master + house (HAWB) in a single transaction POST /api/aim/with-details
Air Import CreateAihHouse Create a house bill under a master POST /api/aih
Air Import CreateAimMasterChargeCosts / CreateAihHouseChargeCosts Batch create charge/cost items for master / house POST /api/charge-cost/air-import
Charge/Cost (see OI / AI rows above) Cross-module charge/cost writes POST /api/charge-cost/{ocean-export,ocean-import,air-export,air-import,domestic}

GraphQL — Domestic Master Delete

Added the DeleteDomMaster mutation, which deletes a domestic shipment master by either id or hbl_no.

Argument Type Description
id Long Master ID (choose one of id or hblNo)
hblNo String HBL No / PRO number (choose one of id or hblNo)
  • Only Open status masters can be deleted; non-Open statuses return BUSINESS_ERROR.
  • Deletion cascades to related multi-mode legs, containers, PO cross-references, and charge/cost records within a single transaction.
  • On success, the deleted master's dom_master_id is returned.

Note: GraphQL mutations currently expose Create and Delete (Domestic Delete is new; CVM also has one Update). REST write endpoints such as ShippingInstruction, Note, and Document are not yet exposed as GraphQL mutations.


2026-07-15

Domestic & OIH Import — Response Enhancement

Domestic (/api/dom) and Ocean Import House Bill (/api/oih) import endpoints now return structured output data (DomesticShipmentOutput / OceanImportHouseBillOutput) in the Swagger response, including action, document code, and master ID fields.

Domestic Import — Re-submit Support

When a domestic shipment is in Open status, re-submitting the same data via /api/dom will trigger a replace operation, updating the existing shipment rather than creating a duplicate.


2026-07-13

BaseTable — PLI Charge/Cost Item Query (Preview)

Added GraphQL queries for the PLI charge/cost item, supporting lookup by ID and paginated list queries. Available in Preview for partner testing.

ISF Filing Removed

ISF Filing endpoints have been removed.


2026-07-10

GraphQL — Charge/Cost Field Expansion

The ChargeCosts field is now exposed on Air Import GraphQL types, joining the existing Ocean Import support. You can now query charge and cost line items for both master and house air import shipments.

Module Type Field Description
Air Import AimMaster chargeCosts Charge/cost line items for the master AWB.
Air Import AihHouse chargeCosts Charge/cost line items for the house AWB.

2026-07-08

GraphQL — Booking Query (Preview)

Added GraphQL booking queries for air export and ocean export shipments. Shipper booking (AEB/OEB) and carrier booking (AEC/OEC) queries support lookup by ID or document code, plus paginated list queries with filtering and sorting. Available in Preview for partner testing and feedback.


2026-06-04

Charge / Cost Import

New REST API POST /api/charge-cost/import for importing charge/cost items into existing OI, AI, and DO shipments. Supports master-level (cost) and house-level (charge + cost) items with automatic vendor matching and status validation.

OIH / ISF Import Enhancement (Preview)

  • OIH import now supports update mode for existing house bills.
  • ISF filing logic refined for better status handling.
  • OIH (/api/oih) and ISF (/api/isf/*) APIs remain in Preview for partner testing and feedback.

2026-05-25

GraphQL — Customer Search Enhancement

Added prefix search for customer addresses by normalized company name, with optional filters for country, city, and postal code.

GraphQL — AR / AP Invoice Field Review

Completed field review and cleanup for AR (ArmInvoice) and AP (ApiCostInvoice) GraphQL types. Duplicate and internal-only fields were removed; exposed fields now align with the domain model for partner queries.


2026-05-21

Domestic WebAPI — Official Release

The Domestic Shipment Import REST API (/api/dom) is now officially released to production. The endpoint supports importing domestic shipment data including shipper, consignee, container details, and multi-mode transport legs.

GraphQL Enhancement

The House type across all operational modules now exposes a poXrefs field, allowing queries to retrieve purchase order data associated with a house shipment.

Module House Type Field Description
Ocean Import OihHouse poXrefs PO numbers for ocean import house bills.
Ocean Export OehHouse poXrefs PO numbers for ocean export house bills.
Air Import AihHouse poXrefs PO numbers for air import house AWBs.
Air Export AehHouse poXrefs PO numbers for air export house AWBs.
Domestic DomMaster poXrefs PO numbers for domestic shipments.

Available Fields

GraphQL Field Description
po_no Purchase order number.
sales_order_no Sales order number.
net_wgt_kg Net weight in kilograms.
po_qty Purchase order quantity.
po_carton_count Purchase order carton count.

2025-05-19

Preview Release

The following endpoints are now available in Preview for partner testing and feedback:

REST APIs

Category Endpoint Description
Ocean Import /api/oih House Bill Import -- Import ocean import house bill of lading data with routing, container, and customer information.
ISF Filing /api/isf/isf-05 ISF-05 Filing -- Submit Importer Security Filing (5+2) with manufacturer and HS code data.
ISF Filing /api/isf/isf-10 ISF-10 Filing -- Submit ISF-10 filing with importer, ship-to, seller, buyer, and consolidator details.
Domestic /api/dom Shipment Import -- Import domestic shipment data including shipper, consignee, container, and multi-mode transport legs.
Customer /api/cvm/search Customer Search -- Search customers by name, country, city, postal code, and other criteria.

GraphQL Queries

Category Description
Domestic Query domestic shipments with pagination, filtering, and sorting.
Customer Search customers by name, country, city, postal code, and other criteria.
AR Invoice Query accounts receivable invoices with related shipment and customer data.
AP Invoice Query accounts payable cost invoices with vendor and cost breakdown details.

Notes

  • All Preview endpoints require JWT authentication.
  • GraphQL queries share a single POST /graphql endpoint using schema-based routing.
  • Feedback on data models and field coverage is welcome during the Preview phase.