The EdiMessageTransform model is used to enable transforms of EDI messages before they are processed or delivered. This can be helpful when a new EDI requirement comes in with similar but non-identical segments as an existing EDI interface. In such a scenario, instead of creating different interfaces, we can reuse the same interface and alter the inbound/outbound EDI message using the EdiMessageTransform model depending upon the sender or receiver.
Table 16.25. EdiMessageTransform Fields
|Unique Id for the EdiMessageTransform. (KEY field)
|Edi Format used in the EdiMessageTransform. Example : X12, EDIFact, etc.
|Any valid transaction number for which the transform is to be applied. For e.g. 850, 855, ORDERS, etc.
|Direction of the EDI - Inbound or Outbound.
|Sending organization of the EDI.
|Receiving organization of the EDI.
|Groovy conditionScript for the transform. Only if the conditionScript evaluates to true will the transformScript be executed. If conditionScript is not provided, the transformScript is always applied (defaults to true).
|Groovy transformScript which is applied on the EDI to implement the transformation.
|Fully qualified path of the class extending com.transcendsys.platform.server.edi.EDITransform which contains the transformationScript. This can be provided as an alternative to TransformScript. If both are provided, the TransformScript is ignored, and only TransformClass will be used.
|Precedence for the transforms. The transform with the least precedence is given prioirty over other matching transforms and will be executed first. But all matches will be executed.