![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() | ![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
EDI Connect User's Guide
APPENDIX E
The purpose of this new tag "choice" is to allow for implementation-specific processing. The structure of the metadata is based on matching.
The EDI connector allows you to process a new tag to the metadata only during Inbound Transmissions. If it is detected on an Outbound Transmission, the conversion fails with an exception. The tag has the following format:
<CHOICE id="HL"> <SegmentGroup id="HL" match=XXX> <SegmentGroup id="HL" match=XXX> <SegmentGroup id="HL" match=XXX> </CHOICE>
Processing is as follows:
If the metadata appears as above, the converter detects a choice block and shows the next segment using the data element delimiter. It publishes each element to a local evaluator using the Segment ID plus a logical expression based on the values of the fields (i.e. HL01, HL02, etc.) or true/false as the key. The converter than evaluates the match attribute of each Segment Group. If it evaluates to "true" (first match it finds), that segment group is used to convert the EDI transmission. Note that choices may be nested.
Copyright © 2004 Novell, Inc. All rights reserved. Copyright © 1997, 1998, 1999, 2000, 2001, 2002, 2003 SilverStream Software, LLC. All rights reserved. more ...