Resolution:
Description:
============
When using the BusinessConnect (BC) EDI protocol to process an inbound EDI-TEXT document the parsed document fails to appear in the output of the Receive Request task. The task only presents the TextRawRequest field rather than the parsed document.

Environment:
==========
BusinessConnect EDI Protocol 5.3.0 and above.

Resolution:
=========
The DFF guideline generates an .xsd file with the root element of format "Message-&ltxxx>".  The schema can be imported into a BusinessWorks project from BC into BW.  However, the BC palette can not read it because the root element does not contain "Transaction-&ltxxx>" which is required by the palette. There is also no way to rename the root element. Consequently, the "Parse XML" option can not be used in the BC Receive Request process starter.

The payload is still received through the TextRawRequest field with the "Parse XML" feature disabled.  Set up a Parse XML task to parse the payload, referencing the stored schema in the Parse XML task.  This will accomplish the same function.