Corolar Release 6.12.0302.1 October 2012 Hotfix1

Description

Corolar Hotfixes are a collection of hotfixes for issues that have been identified within the Dapasoft Corolar product. Corolar Hotfixes are cumulative, however each hotfix describes only the fixes added since the previous Corolar Hotfix. Thus, prior Hotfix release notes should be reviewed for information regarding earlier published fixes.

Affected Components

The affected components section describes the Corolar components for which this particular hotfix applies.

Dapasoft Corolar Pipeline Components

The hotfix addresses several issues identified within the Dapasoft Corolar Pipeline Components.

Fixes

Any pipeline that uses the “Dapasoft Corolar Monitor Tracking Message Pipeline Component”.

Symptoms:

If the HL7 message or HL7 ACK that is sent back from the downstream system does not have any value in MSH-9.2, the pipeline will throw an error when and there will be an entry in the Event Log that shows there was an error with index out of bound. The ACK would not be logged in the Database, but messages would still flow and won’t cause any suspended messages.

Cause:

The tracking pipeline component made an assumption that MSH-9.2 is always populated. Therefore, if MSH-9.2 is not available, it does not behave properly.

Solution:

Apply this hotfix to resolve the issue. If using unsolicited response in a static one-way send port, the receive pipeline for the ACK shall have the preprocessor set to Enabled = false and postprocessor set to Enabled = false

“ALL” appearing in MSH-9.2 even though in the map it is mapped to something else

Symptoms:

When a map is created that maps between different domains (e.g. ADT to ORM) or different namespace but the same domain, the output message will show “ALL” in MSH-9.2. (for example ADT^ALL or ORM^ALL in MSH-9.2)

Cause:

This has to do with the internal working of HL7 Accelerator on how it is promoting and reading the “MessageType” from the context.

Solution:

Apply this hotfix to resolve the issue.

When migrating pipelines to Corolar Q3 R2 release, the “FailLogPath” and “FailLogPrefix” in the Receive PostProcessor have wrong labels.

Symptoms:

“LogPath” and “LogPrefix” are displayed instead of “FailLogPath” and “FailLogPrefix”, making it confusing.

Cause:

The labels in the pipeline component were not correctly named.

Solution:

Apply this hotfix to resolve the issue.