Corolar Release 7.6.0

Description

The 7.6.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

Prerequisite

Corolar v7.5.0 or above must be installed

Installation

Before installing, please stop any application using Corolar assemblies, otherwise Corolar installer will not upgrade
those assemblies in GAC
Stop Resubmission Service
Stop BizTalk Management Service

Uninstallation

Before uninstalling, please stop any application using the Corolar assemblies, otherwise Corolar uninstaller will not downgrade those assemblies in GAC
Stop Resubmission Service
Stop BizTalk Management Service

Affected Components

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

-Corolar Monitor

Fixed security/permission issue for uploading Excel sheets under Codeset Management

-Other Corolar components

Includes all updates from Corolar 7.5 to corolar 7.5.8

Corolar Release 9.0.1

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.

Note: This Hotfix requires Corolar 9.0.0 installed

AFFECTED COMPONENTS

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

COROLAR DATABASE

Stored procedure for tracking/logging message is optimized

COROLAR MONITOR

New feature added: User now can "download" a message under message management. This is especially
useful when the message is too big to be displayed, or to test the message that is causing issues.
This is currently disabled by default. To enable it, modify the web.config as below:
Add new app setting parameter: "EnableDownloadMessage"
1 - Enable message download feature when viewing or editing a message
0 - Disable message download feature
Default value is 0.

Fixed security/permission issue for uploading Excel sheets under Codeset Management
Added "Refresh" button under the Exception Management page to refresh the search result

COROLAR BIZTALK ARTIFACTS

Updated FHIR Property Schema, Pipeline Components and Library
FHIR Schema now available under SDK/FHIR/Schemas folder

COROLAR REPORT

Audit event for message download (see above) is included

Corolar Release 9.0.0

Corolar 9.0.0 is compatible with BizTalk 2020 running on
SQL 2019, SQL 2017, SQL 2016 SP2 CU7

The 9.0.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

To install 9.0.0, please uninstall all previous versions of Corolar before installing
v9.0.0. If you want to retain the original settings and data in the Corolar Database,
please bring the Corolar DB offline before uninstalling the previous versions, and then
bring the Corolar DB back online before installing Corolar 9.0.0.

AFFECTED COMPONENTS

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

COROLAR MONITOR

You can now configure Corolar to purge exceptions without "resolving" them
Exception Management will now show the name of the interface causing the exception, if the API
call includes the interface name in the parameter
You can now put a description for Code set tables
It is now possible to search for values in codeset table management via the UI, without having
to export to Excel sheet to do searching (you can still export to Excel)
When a codset lookup fails, instead of throwing an "ERROR" level exception that tends to clog
up the event log, it will now throw a "WARNING" instead
Resolved issues related to Corolar Monitor when users configured with "monitor" role
Resolved issues related to Codeset management giving 500 error when saving changes on code/value edit screen
Various performance improvements on UI refresh

COROLAR BIZTALK ARTIFACTS

FHIR API fixed for handling repeating nodes for FHIR extensions

VISUAL STUDIO SOLUTION TEMPLATE

Enchancement to the Visual Studio 2019 Corolar solution templates
New HL7 v2 schemas added for more HL7 domains

COROLAR DATABASE

Corolar now supports both SIMPLE and FULL recovery modes. A new SQL job is added to support
FULL recovery mode: Dapasoft_Corolar_Monitor_Transaction_Log_Backup

SDK

New FHIR SDK added

Corolar Release 8.2.1

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.

Note: This Hotfix requires Corolar 8.2.0 installed

AFFECTED COMPONENTS

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

COROLAR DATABASE

Stored procedure for tracking/logging message is optimized

COROLAR MONITOR

new feature added: User now can "download" a message under message management. This is especially
useful when the message is too big to be displayed, or to test the message that is causing issues.
This is currently disabled by default.
To enable it, modify the web.config as below:
Add new app setting parameter: "EnableDownloadMessage"
1 - Enable message download feature when viewing or editing a message
0 - Disable message download feature
Default value is 0.
Fixed security/permission issue for uploading Excel sheets under Codeset Management
Added "Refresh" button under the Exception Management page to refresh the search result

COROLAR BIZTALK ARTIFACTS

Updated FHIR Property Schema, Pipeline Components and Library
FHIR Schema now available under SDK/FHIR/Schemas folder

COROLAR REPORT

Audit event for message download (see above) is included

Corolar Release 8.2.0

The 8.2.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

AFFECTED COMPONENTS

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

COROLAR MONITOR

You can now configure Corolar to purge exceptions without "resolving" them
Exception Management will now show the name of the interface causing the exception, if the API
call includes the interface name in the parameter
You can now put a description for Code set tables
It is now possible to search for values in codeset table management via the UI, without having
to export to Excel sheet to do searching (you can still export to Excel)
When a codset lookup fails, instead of throwing an "ERROR" level exception that tends to clog
up the event log, it will now throw a "WARNING" instead
Resolved issues related to Corolar Monitor when the users configured with "monitor" role
Resolved issues related to Codeset management giving 500 error when saving changes on code/value edit screen
Resolved issues related to importing legacy table template with extra columns, using the OLEDB driver
Various performance improvements on UI refresh

COROLAR BIZTALK ARTIFACTS

FHIR API fixed for handling repeating nodes for FHIR extensions

COROLAR DATABASE

Corolar now supports both SIMPLE and FULL recovery modes. A new SQL job is added to support
FULL recovery mode: Dapasoft_Corolar_Monitor_Transaction_Log_Backup

Corolar Release 8.1.0

The 8.1.0 release of Corolar includes all features from previous releases and hotfixes, as well as a number of enhancements to core Corolar components.

AFFECTED COMPONENTS

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

COROLAR SDK

FHIR assembler and disassembler are now part of the Corolar. A full set of FHIR schema is also included as part of Corolar 8.1.0

COROLAR MONITOR

Viewing messages with the <tab> character will now be displayed properly and the formatting on the messages is now more user friendly
When resubmitting messages, the “Resubmit all” button will now resubmit properly all messages that fit the search criteria for the receive location, instead of the receive port
Queue size sorting (when clicking on column) now sorts properly
Exception Management Event ID now sorts properly
Fixed typo

COROLAR BIZTALK ARTIFACTS

Various fixes on CorolarNonHL7InputSendPipeline. There will no longer be any errors when trying to use this pipeline with various settings on IsSolicitResponse
When “UseDirectSynHL7Ack” is turned on under the MLLP adapter, and the Corolar Receive Pipeline property “TraceEnableDirectSynAck” is turned on, it will now generate a proper HL7 Acknowledgement message. Previously it was missing the MSA segment header.
Corolar HL7 Batch pipeline now support configurable HL7 versions.

COROLAR BIZTALK MANAGEMENT SERVICE

Fixed an issue where sometimes it throws an error “The source was not found, but some or all event logs could not be searched”, when such error should not be thrown

COROLAR VISUAL STUDIO ADD-IN

Fixed an issue with references to the HL7 Disassembler and Assembler. Users are no longer required to remove/re-add references to them.

Corolar Release 8.0.0

DESCRIPTION

Corolar 8.0.0 is compatible with BizTalk 2013, BizTalk 2013R2 and BizTalk 2016

The 8.0.0 release of Corolar includes all features from previous releases and hotfixes, as well as a number of enhancements to core Corolar components.

To install 8.0.0, please uninstall all previous versions of Corolar before installing v8.0.0. If you want to retain the original settings and data in the Corolar Database, please bring the Corolar DB offline before uninstalling the previous versions, and then bring the Corolar DB back online before installing Corolar 8.0.0.

AFFECTED COMPONENTS

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

COROLAR MONITOR

This release contains a number of new features for Corolar Monitor

Code Set Table Mapping (aka, Table Lookup) now supports multi-column tables. Previously, the table lookup was 1-to-1. Now it supports 1-to-many. Please export an Excel template for an example on how to achieve this. A new API guide is also available to assist you on how to take advantage of this new functionality through API
Corolar RBAC now support Active Directory user group. You can now assign an AD Group to Roles, Interface Profiles and Code Set Profiles instead of adding all users within a group individually
You can now safely cancel a message resubmission task through the Corolar Monitor. Go to Message Management -> Resubmission Progress -> Group, then click on “Cancel” on the task that you would like to cancel
It is now possible to start, stop (disable) and restart (recycle) a receive port / send port from the Corolar Monitor without having to go to the BizTalk Administration console

COROLAR TESTING TOOL

The testing tool now supports sending all messages in a folder by specifying the folder name in the config file instead of having to name individual files in the config.
Documentation is included within the same folder where the testing tool resides

COROLAR BIZTALK ARTIFACTS

Now, only one resubmission receive port is required for outbound resubmission instead of one per send port. Also, only one reusbmission receive port is required for inbound resubmission as long as the interface’s receive port does not contain any custom pipeline components. A new user defined code set table is required to achieve this.
In the Corolar receive pipeline, the property “TriggerReplacementValue” will now work with the property “TriggerEventsToBeExcluded” without Corolar defaulting back to the generic schema

COROLAR HL7 2.X SCHEMAS

Corolar now official supports multiple versions of HL7 2.x. By modifying the Receive Pipeline Component property “HL7VersionReplacementValue” you can now use any HL7 2.x schema with rootnode MSH_ADT_ALL_<xx>_GLO_DEF

Corolar Release 7.5.8

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar Monitor Tool

Fixed a bug causing message search result to not list messages in the correct sequence
when more than one message were received/sent within the same second

Corolar Release 7.5.7

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar FHIR component

Fixed a bug causing datatype "Decimal" to not handle numbers with decimal
Added a new property "EncodingCharset" to the FHIR assembler and disassembler pipeline component
Supported values are ",." (ASCII), ",1252" (Western European), and ",65001" (UTF-8)

Corolar Tracking Generic Message Component

Added a new property "EncodingCharset" so the generic logger. Supported values are ",." (ASCII),
",1252" (Western European), and ",65001" (UTF-8)

Corolar Release 7.5.6

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar SDK

FHIR assembler and disassembler are now part of the Corolar. A full set of FHIR schema
is also included as part of Corolar 7.5.6

Corolar Monitor - Message viewer

Viewing messages with the <tab> character will now be displayed properly and
the formatting on the messages is now more user friendly

Corolar BizTalk Artifacts

Various fixes on CorolarNonHL7InputSendPipeline. There will no longer be any errors
when trying to use this pipeline with various settings on IsSolicitResponse

Corolar Release 7.5.5

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar Database

The Corolar Databaes Backup and Purge job will no longer cause timeout issues on Corolar
message logging

Corolar Release 7.5.4

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar BizTalk Artifact

Corolar pipelines will no longer empty the message(payload) when the host instance runs
out of memory

Corolar Release 7.5.3

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar Monitor

Fixed some display issues with interface filters and exception column display on the dashboard
Enhanced Exception Management functionalities where the user will now be able to view invalid messages and its
corresponding NAK. This is done by bringing the user to the message management page with the corresponding
search criteria
Other enhancements on user experience

Corolar BizTalk Artifact

The Corolar HL7v2X Send PostProcessor now allow the user to opt for logging messages to files for every retry,
or only logs when the message is sent successfully to the destination system. There is now a new property,
LogOnEachRetry to turn the logging for each retry on or off

Corolar Release 7.5.2

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar BizTalk Management Service

Fixed an issue caused by this service when "auto resume" suspended messages is turned on, it would resume
the suspended messages even if the send port is stopped. It will now only resume messages when the send
port is "Started".

Corolar Release 7.5.1

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.

Note: This Hotfix requires Corolar 7.5.0 installed

Affected Components

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

Corolar BizTalk Artifacts

Batch Receive Pipeline now properly supports custom values in BatchTriggerEventReplacementValue and
TriggerReplacementValue. Previously it only supported ALLBATCh and ALL

Corolar Database

When an HL7 message is received without the field MSH-11, Corolar will now log the message as an
invalid message. Previously, it did not log the message
fixed a deadlock issue on the Corolar Database

Corolar Monitor

User Management under Security Settings will now work correctly if the default page size of
10 users per page is changed to a different value
Corolar Monitor Health Status / last activity should now be shown in the correct icon and colour.
Code Set tables are now case sensitive. Previously the input entry "Abc" is the same as "ABC".
Now "Abc" and "ABC" are distinct values
Audit Reports will now correctly shown the audit entry that states the user that had viewed a message
A warning will appear if a user is added to user management without interface/table profile
When importing Code Set Tables via Excel spreadsheets, Corolar will now trim leading and trailing spaces.
There is now a setting for frequency of sending alerts for message resubmission (default now 10mins).
This can be changed under the resubmission service config file

Corolar Release 7.5.0

Description

The 7.5.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

Affected Components

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

Corolar BizTalk Management Service

A new windows service is introduced for Corolar v7.5.0. This is to enhance the reliability of auto-resuming
BizTalk suspended instances. This service is listed in the installer as a separate item. Please make sure this
is checked when installing v7.5.0 on a BizTalk server.

Corolar Database

A deadlock issue is resolved when resubmitting a large amount of messages (100k+ messages).

Corolar Installer

Installer will pop up warning when user is trying to run the installer as someone that is not a sysadmin to the Corolar Database.
Resolved an issue when the Corolar Account password contains special characters.
Various enhancements on installer UI

Corolar Monitor

Message correlation is enhanced to include the destination interface name.
Various user interface enhancements.

Corolar Release 7.4.0

Description

The 7.4.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

Affected Components

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

Corolar Monitor

The timestamp of the messages and the timestamp of the acknowledgements are now separated.
Users can now see the time lags between time of messages and the time of the acknowledgements
The HL7 message parser will now only render the message into a tree view when the user clicks on
"Parse HL7 2.x message", instead of rendering the moment the user click on "View Message"
There is now a default date/time when the user search for messages so that it does not search the
full message archive if the user did not put in a date range
Importing code tables will now use OLEDB driver if available, greatly improvement performance
Exception Management handling had been enhanced and performance has been improved
Various bug fixes and enhancements

Corolar Release 7.3.1

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.

Note: This Hotfix requires Corolar 7.3.0 installed

Affected Components

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

Corolar Monitor

This releases fixes various bugs on the Corolar Monitor.

Importing tables while selecting 'delete existing tables' now work as expected
Page navigation under Code Table Mapping Management now works properly
Deleting rows under Code Table Mapping Management now works properly
Status dialog box informing the user of table update status now relay clearer information
Message content search under Message Management now have the highlights shown properly

Corolar Release 7.3.0

Description

The 7.3.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

Affected Components

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

-Corolar Monitor - HL7 message viewer/parser. This is a new feature that specifically built for
HL7 v2.x messages viewing. Whenever a user is trying to "view message" under message management or
Exception Management. If the message is an HL7 v2.x message, Corolar Monitor will attempt to parse
the message and display it in a tree view.

The standard names for each field/components are also included so a user can find information within
an HL7 message much easier.

The parser will parse an HL7 message as well as HL7 ACK/NAK.

Known Issues

Corolar Monitor:

Under User Management, the grid that shows details show both Interface Profiles and
Code Table Profiles in the same "Profile" column

Symptoms:

When an administrator gets an overview of the user management details, the "Profile" column
shows both Interface Profiles and Code Table Profiles.

Workaround:

Name Interface Profiles and Code Table Profiles with a naming convention like IP_xxxxx and
CTP_xxxxx to differentiate them.

Next release of Corolar will have the 2 different types of profiles shown in different columns

Corolar Release 7.2.0

Description

The 7.2.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

Affected Components

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

Corolar Monitor - Code Set Mapping

Code Set Maps now have tighter permission control. Previously, a user either has access to all
code set tables or has none. In Corolar 7.2.0, "Code Table Profiles" are introduced (similar
to "Interface Profiles"), where users can be assigned to Code Table Profiles, and they
will only have access to the tables belonging to that profile.
Administrators can go to Settings -> Security -> Code Table Profile to set up the profiles and
assign tables to the profiles.
To assign users into a Code Table Profiles, administrators can go to Settings -> Security ->
User Management -> Edit -> Manage Code Table Profiles.

Corolar BizTalk Artifacts

Code Set Mapping API - GetMappingValueWithDefault
> This API call no longer writes an "error" to the event log when the mapping value is not found.
It simply returns the default value and no events will be written to the Windows Event Log.

Known Issues

Corolar Monitor:

Under User Management, the grid that shows details show both Interface Profiles and
Code Table Profiles in the same "Profile" column.

Symptoms:

When an administrator gets an overview of the user management details, the "Profile" column
shows both Interface Profiles and Code Table Profiles.

Workaround:

Name Interface Profiles and Code Table Profiles with a naming convention like IP_xxxxx and
CTP_xxxxx to differentiate them.

Next release of Corolar will have the 2 different types of profiles shown in different columns

Corolar Release 7.1.1

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.

Note: This Hotfix requires Corolar 7.1.0 installed

Affected Components

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

Corolar Monitor - Code Set Table Mapping

This hotfix addresses a number of issues identified in the Corolar Monitor Tool

When a user tries to import a file for Code Set Table Mapping that contains an empty value,
the value becomes a space after import.

Symptoms:

When a user tries to import a file that contains an empty value (either input or output), after
the import, the value becomes a space instead of being empty.

Cause:

A bug in handling empty/space in the Code Set Table Mapping causes this issue

Solution:

Apply Corolar Release v7.1.1.

When a user adds a row with empty input and empty output value into an existing table through
Corolar Monitor, the row that was added contains a space in the input and output value.

Symptoms:

Under Corolar Monitor Code Set Table Mapping, when a user tries to add a row with empty input
and output value, after the row is added successfully, the input value and output value actually
contains a space instead of empty.

Cause:

A bug in handling empty/space in the Code Set Table Mapping causes this issue

Solution:

Apply Corolar Release v7.1.1.

While importing an Excel file that contains 2 tables or more (2 or more worksheets), the table names
of the first 2 tables are swapped.

Symptoms:

The imported tables have the first two tables with table names swapped. The name for the first table
has the name of the second table and vice versa. In other words, after importing original Table A
containing 3 rows and Table B containing 5 rows, becomes Table B containing 3 rows and Table A
containing 5 rows.

Cause:

A bug during the import process causes this issue.

Solution:

Apply Corolar Release v7.1.1.

Corolar BizTalk Artifacts

This hotfix addresses an issue identified in the Corolar BizTalk Artifacts

While applying a BizTalk Map on a send port that subscribes to a receive location that uses the
CorolarHL7v2XBatchReceivePipeline, the message gets suspended.

Symptoms:

While applying a BizTalk Map on a send port that subscribes to a receive location that uses the
CorolarHL7v2XBatchReceivePipeline, it causes an error in BizTalk and the message is suspended.
The error message looks like this:

The Messaging Engine failed when executing the outbound map for the message going to the
destination URL "xxxxxxxx" with the Message Type "yyyyyy". Details:"Root element is missing."

Cause:

A bug in the Corolar Batch Receive Post Processor causes this issue.

Solution:

Apply Corolar Release v7.1.1.

Known Issues

Corolar Monitor - Code Set Table Mapping

Unable to import tables, error reporting the file is not in .xlsx extension even though it is

Symptoms

When trying to import an Excel file from a path that contains a dot ".", or
the Excel filename contains a dot ".", Corolar Monitor throws an error saying the file
does not have the extension .xlsx

Cause

The import validation has an issue parsing a path/filename with a dot "." that is
the delimiter for the file extension

Workaround

Make sure the path and filename does not contain a dot "." before importing.

Corolar Release 7.1.0

Description

The 7.1.0 release of Corolar includes all features from previous releases and hotfixes,
as well as a number of enhancements to core Corolar components.

Affected Components

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

Corolar Monitor

This release contains a number of new features for Corolar Monitor

Corolar can now correlate messages and their corresponding response (ACKs) for any
type of messages. Previously, only HL7 v2.x was supported for message/ACKs correlation
Corolar can now correlate inbound messages with its corresponding outbound messages.
This feature can be turned on in "Interface Settings" by clicking "YES" on "Enable
Message Correlation" and accessed by going to Message Search and "View Correlated Messages"
Corolar Monitor "Settings" is now more granular, giving the user more control on
permission settings for different roles. All security settings will be preserved when
the user upgrades to 7.1.0

Corolar BizTalk Artifacts

Users can now reload messages that were stored in the file system, due to the Corolar DB
being unavailable, into the Corolar DB

Corolar SDK

Included a component to guide the user on how to integrate Exception Management with maps

Known Issues

Corolar Monitor:

Under Audit Reports, clicking on the dropdown list sometimes does not work

Symptoms:

When the user selects the filtering criteria for Audit reports, sometimes the dropdown
list for some criteria would not show up when the user clicks on the down arrow

Cause:

UI controls are not reset properly

Workaround:

Click on "View Report" to view a report, and the UI controls will be reset

2. Under Exception Management, the filtering sometimes show the same receive port name multiple times

Symptoms:

If the user has configured multiple Receive Locations (that are under the same Receive
Port) to be monitored in Corolar Monitor, under Exception Management Inbound Interface
Filtering, the Receive Port name will show up multiple times instead of the individual
Receive Location name

Cause:

As of v7.1.0, Exceptions are always recorded under the port name. Even in cases where
there are multiple receive locations for one receive port, and the receive locations are
configured to be monitored under Corolar Monitor (and not receive port), the exceptions
are still written at the receive port level. This potentially could cause the exception
management page inbound port filtering to show the same receive port name multiple times

Workaround:

This issue will be fixed in the next Corolar Cumulative Update