Corolar On-Prem Documentation

 

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.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