Closed Issues in 6.0.0_HF-002 (This Release)
HL-346
The plug-in allowed you to customize timestamp format for the Parse Header
activity and the Generate ACK activity. You could set an option
ìtibco.env.HL7.MSH_ts_formatî in the tra file, such as the designer.tra file
and the bwengine.tra file (for TIBCO Administrator). The valid timestamp formats
were compatible with the formats on the http://www.w3.org/TR/NOTE-datetime website.
For example:
tibco.env.HL7.MSH_ts_format yyyyMMdd
tibco.env.HL7.MSH_ts_format yyyyMMddhhmmss
tibco.env.HL7.MSH_ts_format yyyy-MM/dd-hh:mm:ss
Implemented.
HL-345
The Translate HL7 activity supported the same input encoding that was supported
by the Foresight translator engine. The input_encoding field was added in the
Input tab. You should provide the correct encoding information for the
ìmsg_contentî input parameter (string).
Implemented.
Note:
Currently, the Foresight engine supports UTF-8, UTF-16, and ISO-8859-1 encodings
by default. If no input_encoding is provided, the Translate HL7 activity will use
the default JVM encoding to make the new project compatible with the old project.
The plug-in does not automatically detect the input encoding from the
"msg_content", therefore, you need to set the correct input encoding for
the translation.
HL-331
The translation performance of the plug-in was boosted from the previous version.
Implemented.
HL-329
The acknowledgements generated by the HL7 parseHeader activity were invalid.
There was a character "\r|" in the result which did not match the HL7 standard
format.
Defect has been fixed.