Components. Some
components are no longer installed by the product or runtime installers,
which should make Framework EDI easier to deploy and manage. The
following components are obsolete and are no longer used.
Edidev_Comm.dll
Edidev_Core.dll
Edidev_Dictionary.edb (This file is still installed if the product is
in evaluation).
Edidev_Service.dll
Edidev_USA.dll
Runtime Installers. The
runtime installers have changed due to some components no longer being used in
this version of Framework EDI. The manner in which system and shared files
are updated have also changed to better protect client machines from having
essential file inadvertently replaced when deploying
Framework EDI. Also, these
installers are now compatible with Windows Vista,
Windows 7 and 64-bit machines.
Utilites enhanced. The eFileManager, eAnalyzer and
SefManager utilities have been enhanced. The user should be able to view
the data in multiple ways for reporting and easier management.
Forward-Write cursor streamlined. The generation of EDI
documents using the forward-write cursor has been improved. EDI files
should be faster to generate. There were problems with the previous
operation, mainly: 1) objects like the ediInterchange, ediGroup,
ediTransactionSets were still being accumulated and paged which decreased
performance significantly, and 2) the temporary file created was extremely
large relative to the actual file being generated. These are no longer
problems in this version: the engine scales better, and you should see
performance increase about three times.
Persistent Connection. Connection established with
the remote server will continue to stay alive on an
ediTransport object (for so long as the server does not
disconnect). The same connection will be used for every atomic
transaction (send, receive, etc.) made with the server. This prevents the
multiple connect/disconnect operation with the server.
Automatic Enumeration Disabled. The enumeration of
system security resources has been disabled for situations when it is not
needed. Previously, enumeration was done even though no security
operation was required. Enumeration will be done, however, whenever
enumeration-related methods are used, like the GetFirst..() and GetNext..()
methods.
Objects, Properties & Methods
Constants Added .
ediAcknowledgment. The following
properties have been added to better control the error code that
indicates action the receiver has taken after receiving the document.
These properties are set/get using the
Property method of the object.
PropertyAck_X12_ErrorCodeAcceptWithError
PropertyAck_X12_ErrorCodeReject
PropertyAck_X12_ErrorCodeAccept
PropertyAck_X12_ErrorCodePartial
PropertyAck_UN_ErrorCodeAcceptWithError
PropertyAck_UN_ErrorCodeReject
PropertyAck_UN_ErrorCodeAccept
PropertyAck_UN_ErrorCodePartial
PropertyAck_EndingIMailbagControlNum
PropertyAck_EndingInterchangeControlNum
PropertyAck_EndingGroupControlNum
PropertyAck_EndingTransactionSetControlNum
mailDocument. The following
properties have been added to better control MIME and/or AS2/AS3
processing. These properties are set/get using the
Property method of the object.
Property_WrapLength
MailDocProp_Boundary
MailDocProp_BoundaryMdn
MailDocProp_BoundaryEncrypt
MailDocProp_BoundarySign
MailDocProp_ContentTypeSignedData
MailDocProp_ContentTypeEnvelopedData
MailDocProp_ContentTypeAuthenticatedData
MailDocProp_ContentTypeMultPartSigned
MailDocProp_ContentTypeMultPartEncrypted
MailDocProp_ContentTypeCompressedData
MailDocProp_EncodeQP_MaxLineLen
MailDocProp_EncodeBase64_MaxLineLen
MailDocProp_Encode_Mechanism_Binary
MailDocProp_Encode_Mechanism_X12
MailDocProp_Encode_Mechanism_Edifact
MailDocProp_Encode_Mechanism_EdiContent
ediSchemas. The following
options have been added. These properties are set/get using the
Option method of the object
OptSchemas_NoSchemas
OptSchemas_UseBuiltInCtrlSegs
ediTransports. The following
options have been added.
