This section lists known issues for iWay E-Business Adapters in iWay Version 7.0.7.

• Tidy Print may cause false validation errors on outbound documents. It is recommended that you do not reformat the XML with any non-iWay software before processing through preemitters.
• Metadata is cached for performance in channels. After changing the Ebix associated with a channel (add or remove), the server must be restarted to clear the old information from the cache.
• Standard document processing always creates an acknowledgement. Currently there is no standard methodology to create acknowledgements by trading partner or turn off all acknowledgements. This will be addressed in a future release.
• Adding new elements using the Dictionary Builder in iWay Integration Tools (iIT) does not validate the attributes of the segment (IIT-3550).
• EDIFACT Version 4 does not respect an escaped asterisk when the default delimiter is also present in the data. This will be addressed in a future release. As a workaround, manually correct the document to remove the offending character(s) and reprocess (SEV-1075).
• Saving multiple Ebix when closing iIT presents ambiguous dialog boxes (IIT-3973).
• HIPAA Ebix for Version 4010A1 and 5010 187, 214,215, 217 may not load into iIT correctly. You may continue to use your existing Ebix in production environments and the transformations will continue to be correct. Contact customer support if you need to use iIT to modify the metadata.
• Schemas in custom Ebix created by iIT may have different styles and validation content. They are functionally the same as those released with the product. This will be addressed in a future release (SEV-962).
• EDIHL7 UAC authentication is not currently supported (SEV-1133).
• iWay Integration Tools (iIT) may run out of heap memory when exporting a large HL7 Ebix. You can increase the maximum memory available to iIT by changing the -Xmx parameter of the iit.ini file, which is located in the root folder of your iIT installation.
• SWIFT_to_XML output in iIT only works when run against a running server (IIT 3603).
• SWIFT MT3xx 15 tags do not validate order of fields that follow under certain circumstances (SEV-1643).
• SWIFT 2016 MT362 changes Sequence B 37L to 37G, resulting in two indistinguishable 37G tags in Sequence B (SEV-1681). This will be addressed in a future release.
• SWIFT trace outputs qualifier list for 22H but not 22F (SEV-1912). This will be addressed in a future release.