Francis Reat 468f63b334 Merge branch 'develop-1.2' into ftl-1.2-for-release1.12
# Conflicts:
#	README.md
#	RFXtoRP_HliPrepaL.ftl
#	RFXtoRP_HsaCons.ftl
#	RFXtoRP_HsaDispute.ftl
#	RFXtoRP_HsaItmLv.ftl
#	RFXtoRP_HsaLstCarSta.ftl
#	RFXtoRP_HsrCarrierApt.ftl
#	RFXtoRP_HsrPrepa_GoodsPrepared_HandlingUnitMetadata.ftl
#	RFXtoRP_HsrPro_ExecutionflowDetected_HeaderMetadata.ftl
#	RFXtoRP_HsrReceiptList_ExecutionflowDetected_HeaderMetadata.ftl
2025-12-18 08:15:17 +01:00

1.1 KiB

HARDIS SC NETWORK Core FTLs

Overview

The HARDIS WMS Connector is a set of FreeMarker templates (FTL) designed to transform outgoing JSON flows from HARDIS WMS into flows compatible with HARDIS SC NETWORK.

The HARDIS WMS Connector is a set of FreeMarker templates (FTL) designed to transform outgoing JSON flows from HARDIS WMS into flows compatible with HARDIS SC NETWORK.

This connector does not contain any standalone executable code: it is intended to be used by Reflex integration engines or data exchange pipelines, where it applies the mapping rules defined in the .ftl files.

Role of the FTL Files

  • Each .ftl file corresponds to a flow type (order, stock, receipt, shipment, etc.).
  • These templates use the FreeMarker syntax to:
    • Extract the required fields from the WMS source flow.
    • Apply transformation rules (mapping, conversions, enrichments).
    • Generate a final structured JSON for HARDIS SC NETWORK.

Useful Resources