This file provides important information about enhancements and fixes in webMethods EDI Module 6.5. For information about enhancements and fixes in previous webMethods EDI Module releases, see the readme for those releases.
1.0 Enhancements
2.0 Included Fixes and Service Packs
5.0 Added and Removed Services and APIs
6.0 Enhancements and Fixes in Previous Release
webMethods EDI Module 6.5 includes the following enhancements.
The EDIINT Module now supports the EDIINT Applicability Statement 3 (AS3). Using the EDIINT Module, users can exchange data securely using the File Transfer Protocol (FTP). Authentication and data confidentiality are obtained by using Cryptographic Message Syntax (S/MIME) security body parts.
1-K45WP
Adds the input variable “encoding” to the wm.b2b.edi.util.generateFA service.
In addition, the value of the input parameter "edidata" can now be
either a string or an inputStream.
1-I4OZP
The wm.b2b.edi.util.generateFA service can now accept a user-specified EDI
schema to validate the input parameter "edidata". If the user does
not specify an EDI schema, the service uses the schema specified in the default
path.
1-N9JUF
The wm.b2b.edi.util.generateFA service now supports the EANCOM, UCS, and VICS
Standards by using the corresponding format Functional Acknowledgement (FA).
1-JGW6D
The EDIINT Module now supports the resubmission of outbound EDIINT documents.
It also supports persisting relationships between an inbound EDIINT document
and its payload(s).
1-OO8SR
Adds the decimal point character to the input signature for the
addICEnvelopeEDIFACT service.
1-QOTVR
Adds the configurable envelope processing service wm.b2b.edi:envelopeProcess
for UN/EDIFACT.
1-NOD05
addICEnvelopeEDIFACT now provides valid
data for the "date" element.
webMethods EDI Module 6.5 includes the following fixes and service packs that were shipped since the last release.
1-PUVTN (WmEDI_6-1_Fix2)
In ANSI X12 version 4020 and higher, ISA11 has a different data type and
allowed values. This fix updates the webMethods EDI Module to support this data
type.
1-PWGHJ (WmEDI_6-1_Fix3)
The services in the wm.b2b.edi.util.formatServices folder (formatN0, formatN1,
formatN2, formatN3, formatN4, formatN5, formatN6, formatN7, formatN8, formatN9)
returned an incorrect value for the output parameter, formattedValue. The
output value is incorrect due to a "loss of precision" error. For
example, the value 2.55 as input to the service formatN2 results in 254,
instead of 255. This fix addresses the problem so that the format services
correctly format all values.
1-PXZ7O (WmEDI_6-1_Fix4)
When moving 4.x EDI templates to 6.x flat file schemas, the order of records
were not being migrated properly when a segment definition in the 4.x EDI
template has the attribute ARRAY value of "yes". A record was created
for the segment as a direct child of the document root. This record always had
a max repeat value of 1, regardless of the existence of the
ARRAY="yes" attribute in the 4.x schema. (Note that if the same
record is used inside a LOOP, then the order is set correctly.) This fix
modifies the migration process to create the top-level record with a maximum
repeat value of "unlimited" if the segment definition has an
attribute ARRAY value of "yes" or "true".
1-Q3WAC (WmEDI_6-1_Fix5)
The wm.b2b.edi:convertToString service creates the segment counts in the UNT
and SE segments with a value one greater than the actual segment count. This
fix allows the service to create the segment counts with the correct value.
(WmEDI_6-1_Fix6)
Adds support for UNEDIFACT versions 901, 902, 911, 912, 921.
1-QE39J (WmEDI_6-1_Fix7)
Migration from 4.x WmEDI templates to 6.x flat file schemas did not allow for
the migration of records containing no fields. It is valid to have a record in
4.x or 6.x that contains no fields, so this fix alters the migration process to
correctly migrate records that contain no fields.
(WmEDI_6-1_Fix8)
Adds support for ODETTE version 3, and fixes a generateFA multi-UCM segment
error.
1-Q2639 (WmEDI_6-1_Fix9)
Adds support for the following new versions of EDI standards:
X12: 5010
UNEDIFACT: 901,902, 911, 912, 01A, 01B, 02A, 02B, 03A
EANCOM: 01B (2002 V3)
ODETTE V3
1-QC6DJ (WmEDI_6-1_Fix9)
Edits EANCOM 96A to support 97V4D.
(WmEDI_6-1_Fix10)
EDI 4.6 templates supported both an ID and NAME attribute for the SEGMENT tag.
The ID attribute identified a record name and the NAME attribute identified an
alternate name for the record. EDI 4.6 templates that use the NAME attribute
for an alternate name cannot be converted to a flat file schema because the
WmFlatFile 6.1 package did not support alternate names. Fixes ID_6-1_Fix3 and
IS_6-1_Fix24 add alternate name support to the WmFlatFile 6.1 package. This fix
updates the EDI Module to take advantage of the alternate name support in those
fixes, enabling users to convert EDI 4.6 templates that use the NAME attribute
to a flat file schema. With this fix applied, the EDI Module properly converts
the segment NAME attribute from EDI 4.6 templates to the WmFlatFile 6.1 package
"Alternate Name" attribute for records in a flat file schema. The EDI
4.6 template SEGMENT tag NAME attribute is equivalent to the WmFlatFile 6.1
"Alternate Name" attribute.
1-QYXZT (WmEDI_6-1_Fix11)
Fixes a UCM code value problem for UNEDIFACT CONTRL generation.
1-QIFIG (WmEDI_6-1_Fix12)
Fixes ODETTE .SEF files for both version 94 and 3.
1-QVEXR (WmEDI_6-1_Fix13)
EDI 4.6 templates allowed the space character (' ') as a delimiter. This was
not allowed in 6.1 flat file schemas. This fix alters the 6.1 flat file schema
to allow the space character to be a delimiter.
1-RJKML (WmEDI_6-1_Fix14)
In a 4.x EDI template name, if the EDI standard begins with a digit, the
standard and version are migrated to invalid Integration Server namespace
names. For example, a 4.x EDI template with a standard "1Standard", a
version "1", and name "Template", will map to the illegal
namespace name of "1Standard.V1:TTemplate". If a standard begins with
a digit, this fix prefixes the standard name with a ‘_’ (underscore) character.
1-R5Q4C (WmEDI_6-1_Fix15)
Dictionary elements were not generated properly because the AK401 is a simple
element in the 997 document, but the WmEDI package only supports AK401 as a
complex element. This occurred in the following versions:
X12 2040, X12 3010, X12 3020, X12 3040
This fix adds support for simple elements for AK401.
1-RUX1A (WmEDI_6-1_Fix16)
When the EDITPA is configured with generateControlNumber =
"fromControlNumberTable", automatic generation of the FA did not
create the GS control number correctly. With this fix applied, automatic
generation of the FA correctly creates the GS control number.
1-RXRIL (WmEDI_6-1_Fix17)
When multiple transaction sets occurred under one group for an X12, the
wm.b2b.edi.util:generateFA service produced an incorrect segment count in the
997, resulting from processing a data file. With this fix, the Functional
Acknowledgement is now generated automatically, creating the correct segment
count for an SE.
1-RW1AH (WmEDI_6-1_Fix18)
The wm.b2b.edi:convertToString service did not use the input parameter
"spacePad". This fix enables the value "spacePad" to be
used.
1-S5T77 (WmEDI_6-1_Fix19)
The ISA11 element was a Code List validator. After applying WmEDI_6-1_Fix15,
the ISA11 element changed to a Length validator. This fix modifies the ISA11
element so that it is a Code List validator.
1-SW0PV (WmEDI_6-1_Fix20)
The EDI structure created by the wm.b2b.edi:envelopeProcess service differed
from WmEDI version 4.6 to WmEDI version 6.1. This fix modifies the UNH02
segment so that it is a Code List validator.
1-TCGJ0 (WmEDI_6-1_Fix21)
The value for the EDIMaxFATransactionErrors configuration parameter was not set
properly. This fix allows the EDIMaxFATransactionErrors value to be set
properly, without impacting the EDIBigDocThreshold property setting.
1-TZ4KD (WmEDI_6-1_Fix22)
The wm.b2b.edi.util:standardCheck service did not return correct values for
substandard and version. This fix identifies each segment first, then extracts
fields so the trailing field can be extracted correctly.
1-SW0PV and 1-UZSLH (WmEDI_6-1_Fix23)
The UNEDIFACT envelope structure created by the wm.b2b.edi:envelopeProcess
service differed from WmEDI version 4.6 to WmEDI version 6.1. This fix modifies
some UNB, UNG and UNH segments so they become Code List validators, the same as
in version 4.6.
1-VBZTG (WmEDI_6-1_Fix24)
Unable to install UCS 4020 880 after installing IS_6-1_Fix41. This fix provides
new .SEF files that fix minor errors with alternate code sets.
1-OAO1H (WmEDIforTN_6-1_Fix1)
When using a case-sensitive Trading Networks database (e.g., Sybase), users
could not use the EDI Module’s "non-standard" processing. Users could
not add interchange-level sender/receiver pairs from the webMethods EDI Module
home page. This fix allows interchange-level sender/receiver pairs to be
defined in case-sensitive databases. For more information about non-standard
processing see "Appendix A, Non-Standard Processing" in the webMethods
EDI Module User's Guide.
1-NXLJZ (WmEDIforTN_6-1_Fix1)
A Null Pointer exception occurred when deleting an interchange-level
sender/receiver pair information that has associated group pairs. When using
the EDI Module’s "non-standard" processing, and you attempted to
delete interchange sender/receiver pair information, a Null Pointer exception was
thrown if there were one or more group pairs associated with the
interchange-level sender/receiver pair that was being deleted. This fix
modifies the delete interchange-level sender/receiver pair operation to
function properly.
1-PLS80 (WmEDIforTN_6-1_Fix2)
Fixes a TN/EDI upgrade issue (missing "bizdoc" content).
1-PXQSJ (WmEDIforTN_6-1_Fix3)
Enables an equivalent WmEDIforTN_6-0-1_Fix23 to be ported on 6.1. This fix
addresses StringIndexOutOfBoundsException when calling getICDetail on EDI data
without a GS08 value.
1-Q946K (WmEDIforTN_6-1_Fix4)
Segments after the UNT segment in ANSI X12 transaction were ignored. The parser
considered the UNT segment to be a UN/EDIFACT UNT segment. This problem is
fixed by verifying that the standard is UN/EDIFACT before checking for a UNT
segment.
1-Q8PQP (WmEDIforTN_6-1_Fix5)
A batch process threw a Null Pointer exception when non-EDI data was submitted.
The problem is fixed by checking for content that is not marked as
"EDIdata".
(WmEDIforTN_6-1_Fix6)
Adds support for UNEDIFACT versions 901,902, 911, 912, 921.
(WmEDIforTN_6-1_Fix7)
Adds support for ODETTE version 3.
1-QG8BP (WmEDIforTN_6-1_Fix8)
The SplitOption from the Default TPA no longer overrides the value specified in
another TPA.
1-Q2639 (WmEDIforTN_6-1_Fix9)
Adds support for the following new versions of EDI standards:
X12: 5010
UNEDIFACT: 901,902, 911, 912, 01A, 01B, 02A, 02B, 03A
EANCOM: 01B (2002 V3)
ODETTE: V3
1-QC6DJ (WmEDIforTN_6-1_Fix9)
Enables EANCOM 96A to support 97V4D.
1-R6FS5 (WmEDIforTN_6-1_Fix10)
After resubmitting an EDIFACT document in Trading Networks, an extra UNE
segment appeared in the contents of the EDIFACT document. This fix removes the
extra UNE segment from the EDIFACT document.
1-RDGPX (WmEDIforTN_6-1_Fix11)
EDI instance ID queries failed for documents that Trading Networks considered
to be large. The EDI Module did not attempt to determine the instance ID of an
EDI transaction when the transaction exceeded the Trading Networks large
document threshold. The Trading Networks large document threshold was
configured using the tn.BigDocThreshold system property. With this fix applied,
when an EDI transaction exceeds the large document threshold, the EDI Module
will now attempt to determine the instance ID. The EDI Module performs the
instance ID query by reading the number of bytes indicated in the
tn.xml.xqlThreshold system property. If the instance ID is found within the
bytes read, the instance ID will be set, and used to create the conversation ID
for the Trading Networks BizDocEnvelope. If it does not exist where indicated,
the instance ID will not be set. This fix is identical to
WmEDIforTN_6-0-1_Fix24.
1-RK5WH (WmEDIforTN_6-1_Fix12)
The wm.b2b.editn:getTspace service resulted in inconsistent output data types.
At different times, the data type varied between String and InputStream. This
fix ensures that the data type of the output (edidata) is always InputStream.
1-RTC14 (WmEDIforTN_6-1_Fix13)
Allows the FTP services in the WmEDIforTN package to use the Trading Networks
TSpace for handling large files.
1-RYUK7 (WmEDIforTN_6-1_Fix14)
WmEDIforTN-UNEDIFACT 99B did not recognize the senderID after being migrated
from IS46 to IS6.1. This fix adds a new option (useReverseRoute) in the EDI
TPA, which enables reverse routing.
1-S8TX1 (WmEDIforTN_6-1_Fix15)
Enables WmEDIforTN to parse UNEDI/FACT 99B INVOICE when a test indicator is
missing from the envelope.
1-TE22K (WmEDIforTN_6-1_Fix16)
If the sender/receiver ID on the Add Interchange Information page of the EDI
Module home page included characters such as "#", the interchange
information did not display properly. This fix applies the URL encoding in the
dsp page, which sends the URL encoding information correctly when the link on
the Add Interchange Information page is clicked.
1-U0ZBP (WmEDIforTN_6-1_Fix17)
The getTspace service now uses/sets the proper encoding.
1-V0D48 (WmEDIforTN_6-1_Fix18)
The wm.b2b.editn.batch:batchProcess service now supports delimiters in the same
way that the wm.b2b.edi:convertToString service supports them.
1-VFDB2 (WmEDIforTN_6-1_Fix19)
The functional acknowledgement report did not function properly when specifying
"FA from date" and "FA to date" as report criteria. This
fix modifies the report to properly handle all report criteria.
1-VTXKN (WmEDIforTN_6-1_Fix20)
EDITPA now functions correctly when the ControlNumberManagement settings
duplicateControlNumberAction or outOfSequenceControlNumberAction are set to
"Error & Continue".
1-QH9N1 (WmEDIINT_6-1_Fix1)
EDIINT now supports partner-to-partner certificates that are retrieved from
Trading Networks 6.1. This fix uses Trading Networks’ service to obtain
alternate partner-to-partner certificates when the system property
"uccnet.ediint.multicerts" is set to "true".
1-RHY0D (WmEDIINT_6-1_Fix2)
EDIINT payloads are now properly submitted to Trading Networks.
1-RGQJ5 (WmEDIINT_6-1_Fix3)
Prevents an OutOfMemory exception from occurring when uncompressing a large
document. This fix also includes WmEDIINT_6-1_Fix1 and WmEDIINT_6-1_Fix2.
1-UG5ZH (WmEDIINT_6-1_Fix4)
The expiration date of the test certificates provided in \\WmEDIINT\pub\demo
has been extended to the end of 2005. This fix also includes WmEDIINT_6-1_Fix1,
WmEDIINT_6-1_Fix2, and WmEDIINT_6-1_Fix3.
For detailed information on these fixes and service packs for webMethods EDI Module, see the Knowledge Base on the webMethods Advantage Web site.
The issues listed below have been resolved in webMethods EDI Module 6.5 but were not previously released in any fixes or service packs.
1-W18JL
The wm.b2b.ediint:send service used an invalid pattern when it called
pub.date:getCurrentDateString service. The issue is resolved in 6.5.
1-W0JII
When the batch queue is of type MULTIOUTPUT, EANCOM data was created under a
UNEDIFACT Envelope. With this fix, the EANCOM data will be created under an
EANCOM Envelope.
1-V7M33
In webMethods 6.1, the wm.b2b.edi:envelopeProcess service did not report an
error for invalid EDI data. With this fix, an error will be reported.
1-UYXFE
In webMethods 6.1, the wm.b2b.editn.getICDetail service threw a Null Pointer
exception if the input data was missing composite S009. The issue is addressed
with this fix.
1-S9ESC
In webMethods 6.1, an X12 4010 810 data with code value "LB" for ISS04 failed validation. With
this fix, the data will pass validation.
1-QWYMR
Adds the ST03 element to ANSI X12 4020 and above. An X12 4020 data with a valid
ST03 element failed validation in webMethods 6.1. With this fix, that data will
not report a validation error.
1-QU5OY
In the documentation installation page of the webMethods EDI home page, the
duplicate or un-supported entries have been removed from the transaction set
drop-down list.
1-Q98ZR
Adds the EDIINT Module’s own external ID type to Trading Networks.
1-PMYRN
Adds a new input signature to the wm.b2b.edi.util.addICEnvelope service to set
the value for ISA11. With this fix, users have the flexibility to set the
character for ISA11 for X12 4020 and above.
The terms listed below have been changed as indicated.
None.
This release contains the following changes to built-in services and the APIs.
The following services and APIs have been added in this release.
wm.EDIINT:retrieveAS3Message
Downloads AS3 messages or MDNs from a partner’s remote FTP server and
submits the message to Trading Networks to be unwrapped, decrypted, and to have
its signature authenticated. The service locates the partner’s remote FTP
server using the values defined in the IS document type
wm.EDIINT.TPA:EDIINTAS3TPA. If the IS document type specifies that the
retrieved file(s) is to be deleted, the service deletes the file(s).
wm.b2b.editn.util.VersionSupport:addNewEDIVersion
Enables the EDI Module to support a new version of an EDI standard that the EDI
Module supports.
The following services and APIs have been removed in this release.
None.
To view information about the previous release of webMethods EDI Module, see the previous readme on the webMethods Bookshelf.
EDI-E&F-65-20050512