Prior to version 1.6, LoadXml and SaveXml activities did not accept the special encodings that control the byte ordering ('-nobom' etc.)        

Since the version 1.6, when specifying which character encoding to use in the LoadXml and SaveXml activities it is possible to use the special versions of the encodings that control the byte ordering and the generation of the initial byte order mark (BOM) - e.g. utf-8-nobom, utf-16le etc. (see http://forum.teradp.com/topic.asp?whichpage=1&TOPIC_ID=253#2797).

For a complete list of the Tera specific activities, see:

http://tech.teradp.com/tech/html/gn4/docs/VSdoc/frlrfTeraDPGN4WorkflowActivity.html