Common Issues - EDI 810 Processor - English - Foundation 22.1 - OnBase - Premier - Standard - external - Standard - Premier

EDI 810 Processor

Platform
OnBase
Product
EDI 810 Processor
Release
Foundation 22.1
License
Standard
Premier

Some XML documents are not being displayed correctly.

Beginning in Microsoft .NET Framework 2.0, the XslTransform class was deprecated and replaced with a new XSLT implementation, XslCompiledTransform. This change to the Microsoft .NET Framework enforced stricter standards for how style sheets must be created, and may cause display issues when viewing XML documents in OnBase with style sheets that do not conform to these stricter standards. For example, XML documents may be displayed as shifted down and to the right, or other unexpected behavior may occur when viewing documents with the affected style sheets.

Beginning with OnBase 9.0, this issue has been corrected for all custom and standard style sheets created by Hyland Software, including style sheets for the EDI processors. However, this issue may still affect style sheets created by Hyland Software prior to the release of OnBase 9.0, as well as any style sheets that users have developed on their own, depending on how they were created.

If you are upgrading from OnBase 8.2 or earlier, or if you believe that style sheets created for your OnBase solution are, or may be, affected, please contact Hyland Software's Technical Support for additional information and assistance in resolving this issue.

Segment Terminators in the EDI Data Stream

The EDI standard states that the segment terminator is the byte following the 105th byte. It is usually the tilde (~) character.

Per the EDI standard, a segment terminator is not a required field. OnBase can recognize a segment terminator, but if one does not exist then a valid suffix (i.e., CR, LF, or CR\LF) in the 106th byte can be used to correctly identify documents. Or, if this character is left blank, you can use a line feed to indicate a segment terminator.

In most files, when the segment terminator is explicitly defined, line feeds still appear but strictly for formatting/readability purposes.

Documents imported via the EDI processors are not being printed with the Print style sheet applied.

In order to print any OnBase XML document with the Print style sheet applied, the document must be printed using the OnBase print logic (i.e., from the OnBase Print dialog box). Depending on how the printing action was initiated, HTML/XML-based documents may display the Internet Explorer Print dialog box instead of the OnBase Print dialog box.

For information steps you can take to ensure the OnBase Print dialog box is displayed when initiating most printing actions from HTML/XML-based documents, see Print Logic for HTML Documents in the System Administration documentation.

EDI field code values are being truncated when mapped to OnBase Keyword Types and imported as Keyword Values.

When the value represented by the EDI field code exceeds the maximum configured length of the OnBase Keyword Type it is mapped to, then the value is truncated so that the Keyword Value consists of the maximum number of characters allowable for the Keyword Type.

When a Keyword Value is truncated, a warning message is displayed in the Verification Report.