Compatibility Issues for Version 5.6

Framework EDI version 5.6 (and later) has changed which may affect existing code using previous versions of FREDI:

• Error Descriptions Have Changed
• New Error Codes Assigned to Existing Errors for Situational Conditions
• UN/EDIFACT Creates 2 CONTRL Messages
• AS2 ISAPI is no longer included

DETAILS:

• Error Descriptions Have Changed.  Quotes may have been applied to some word(s) in an error description.  This applies only to error descriptions created by Edidev and not to error descriptions generated by Windows and/or client applications, which are outside our control.  Client source code(s) that watch for error description(s) to control the flow of logic of the program may be affected.
  
  For example, the error description
  
      No data in mandatory data element '92' in Data Segment 'BEG'
  
  has been changed to
  
      No data in mandatory data element '92' in 'Data Segment' 'BEG'
  
  Note that the words Data Segment has been enclosed in quotes.
  
  This change was made as part of a new feature in FREDI to allow users to change error description.  For more, see ediWarnings.OverrideErrorDescription.
  
• New Error Codes Assigned to Existing Errors for Situational Conditions.  The following error codes that use to occur for situational (i.e. errors generated as a result of a semantic rule violation) and non-situational conditions, now only get thrown for non-situational conditions.  Now, new error codes have been created for the same errors occurring for situational conditions only.
  

  Standard Error Code	Situational Error Code	Error Description
  6016	14118	No data in mandatory data element.
  6011	14119	Missing mandatory segment in EDI file.
  13831	14115	Data segment in loop is encountered but has been specified as 'Not Used'.
  13832	14117	Data element designated 'Not Used' contain data in segment/composite.
  13833	14116	Composite element designated 'Not Used' contain data in segment.
  13887	14113	No values in the list matched the value '%s' for data element.
  13888	14114	The value does not follow any of the regular expression in the list for data element.
  14037	14120	Mandatory Loop is missing.

  
  For example, normally the error code 6016 is thrown if a 'mandatory' data element contain no data.  In an alternate scenario, error code 6016 is not thrown if an 'optional' data element contain no data, but if the same data element is changed to 'mandatory' (because of a semantic rule) then error code 14118 is thrown instead because it contains no data.

  This change affects client source code that map error codes to acknowledgment errors, or those that use error codes to control the flow of logic of the program.

   

• UN/EDIFACT Creates 2 CONTRL Messages.  An interchange receipt and an interchange response can be generated as an acknowledgment to a subject interchange.  To generate an interchange receipt, the EnableInterchangeAcknowledgment option is enabled; and to generate an interchange response, the EnableFunctionalAcknowledgment is enabled.  When both options are enabled, previous versions created only a single CONTRL message; this version now creates 2 CONTRL messages: one for the interchange receipt and the other for the interchange response.  For more, see Reporting Syntactical Errors for UN/EDIFACT.

• AS2 ISAPI components are no longer included.  The AS2 ISAPI server (frediAs2Isapi.dll) and console (frediIsapiConsole.exe) are no longer included in installer packages.  Originally, the AS2 ISAPI components were installed on servers as part of an AS2 solution for processing AS2/AS3 files received from clients.  This is no longer recommended as it does not provide enough flexibility and security in AS2/AS3 implementations.  Instead improved features in client development tools have allowed better implementation of AS2/AS3 using FREDI on servers, and the flexibility provides organization to adapt to changes in the future.

   

See Also

Backward Compatibility