Resolution:
Description:
============
When sending an outbound EDI-X12 document to a trading partner using the BusinessConnect EDI Protocol ,  BusinessConnect does not convert certain ISO-8859-1 or UTF-8 characters correctly from XML to EDI.  The non-standard characters get translated to something that is not recognizable.  This occurs when outbound validation is disabled.

Environment:
==========
BuinessConnect EDI Protocol 5.3 and above.
 
Symptoms:
=========
User sends an XML document encoded in UTF-8 with some Japanese characters in it.  The resulting segment in the EDI output has these Japanese characters garbled.
 
Cause:
=====
BusinessConnect is not converting the UTF-8 or ISO-8859-1 character correctly.
 
Resolution:
=========

To correct the issue, use the BusinessWorks project that is generating the UTF-8 XML document for BC.  Convert the UTF-8 payload to UTF-16 by:

1).  Use a "Parse XML" task using the transaction schema to generate the outbound document transaction.

2). Feed this transaction to a "Render XML" task with a encoding option of "UTF-16".  This will generated a UTF-16 XML string.

3).  Send this string to BusinessConnect using a Send Request task with the "Parse XML" option disabled.  This will set the input map to accept a string rather than a Transaction schema.

BusinessConnect (BC)is not converting ISO-8859-1 or UTF-8 characters correctly from XML to EDI using EDI-X12.