Connexion v15.1 R4 (15.1.751)

Released On

May 5, 2021 Aug 8, 2022 - v15.1.757 - Added fix for: FLUC-9954: UCSD: Error in Connexion v15: Function 'coalesce' not found

Release Type

Release

Connexion

.NET 4.8 may need to be manually installed if your systems don't have internet access.

Internal Connexion libraries now target .NET 4.8. If you are referencing any Connexion assemblies other than Connexion.Core, you will need to target .NET 4.8 in your projects. Please note that all non-core libraries are internal and subject to change.

Breaking Change - Connexion Unit Test API

The Connexion Unit Test API has been expanded/changed. If you are using this feature please contact Conevity for further details.

  File Modified

File Connexion.15.1.751.exe

May 05, 2021 by Jonathan Reis

File Connexion.15.1.757.exe

Aug 08, 2022 by Jonathan Reis

Integrator

  File Modified

File Connexion.Gateway.15.1.751.exe

May 05, 2021 by Jonathan Reis

File Connexion.Integrator.15.1.751.exe

May 05, 2021 by Jonathan Reis

File Gateway.ManagementUI.15.1.751.msi

May 05, 2021 by Jonathan Reis

File Integrator.RemoteAgent.15.1.751.msi

May 05, 2021 by Jonathan Reis

File Integrator.UpdaterA.15.1.751.msi

May 05, 2021 by Jonathan Reis

File Integrator.UpdaterB.15.1.751.msi

May 05, 2021 by Jonathan Reis

Ticket

Type

Summary

Ticket

Type

Summary

FLUC-9954

Defect

UCSD: Error in Connexion v15: Function 'coalesce' not found

CNXN-4129

Defect

Connexion client not remembering last selected channel if it was navigated to via search results

CNXN-4128

Suggestion

FileWriterDevice - Add option to copy file without copying with .tmp extension and renaming

CNXN-4127

Defect

Connexion ConfigWizard - Exception if the database password contains a single quote character

CNXN-4126

Defect

Install fails if the __cxne_user__ doesn't exist (and the user chooses this)

CNXN-4124

Suggestion

Update Incompatible version number

CNXN-4123

Defect

Add auto-format button on the text viewer for json text types

CNXN-4122

Suggestion

Connexion Server Listing Exporting and Importing Connections

CNXN-4120

Defect

Queue preview is incorrectly displaying JSON ISO 8601 date/time stamps with adjusted hour and TZO

CNXN-4119

Defect

Plugins not showing in Connexion

CNXN-4118

Defect

Batch messages marked as processed after an exception is thrown 

CNXN-4117

Defect

Log Management - System.IO.IOException: 'The process cannot access the file 'C:\ProgramData\ConnexionV14\Audit\Connexion.Audit.txt' because it is being used by another process.'

CNXN-4115

Task

Update 15.1 branch to have same batch methods as 15.5.

CNXN-4114

Suggestion

Database Polling Device: Add support for JSON to Output Format on Options tab

CNXN-4112

Defect

Connexion - Moving a channel that has global settings to another Group, or Tab causes errors in the database cleanup routine

CNXN-4111

Defect

Failure upgrading from Connexion v15.1 R1 to v15.1 R3

CNXN-4109

Task

Add Setting to Remote Agent Queue to Disable Caching

CNXN-4108

Defect

DateTimeOffset is not defaulting to the local DateTimeOffset when parsing HL7DateTime in V15

CNXN-4105

Defect

ChannelService.UpdateChannelGroupAsync - Audit log is dumping all tabs and channels into a serialized blob

CNXN-4104

Defect

SafeObservable<T>: [InvalidOperationException] Collection was modified; enumeration operation may not execute. 

CNXN-4102

Defect

Bug Report Destination File Name should auto update to match the currently selected server

CNXN-4101

Task

The database polling device doesn't work in the remote agent

CNXN-4100

Suggestion

No messages were found in the file.  Make sure framing settings are correct.

CNXN-4099

Suggestion

Add Column to Connected User displaying their Authorization Role(s) comma delimited

CNXN-4098

Suggestion

 "Disallow Logins" setting with a list of specific user accounts that are denied access even though they have an account in AD

CNXN-4095

Suggestion

Support for writing to S3 in Channel Backup

CNXN-4086

Task

Add option to File Reader Device to Delete Zero Byte files if older than 6 Hours

CNXN-4084

Defect

Unexpected exception getting statistics for the monitoring process

R4 Change Log

CNXN-4128: FileWriterDevice - Add option to copy file without copying with .tmp extension and renaming

We have encountered a case where an sftp server will allow file creation but not rename. This new setting lets you upload the file with the final filename directly (as opposed to uploading as a temp file followed by a rename to the final filename). We recommend this only for sftp, as this protocol has a specific ‘file close’ command missing from many other protocols (like ftps, or file system).

 

CNXN-4119: Plugins not showing in Connexion (defect)

15.1 R3 and 15.1R4 have been partially optimized to require less data during the initial load, as well as more efficient use of data over the network. This should help these builds be faster when used over slow network connections (15.5 has been further optimized to be even faster). This introduced this defect which causes unused versions of plugins to not be displayed in the UI. This has been fixed in R4.

CNXN-4109: Add Setting to Remote Agent Sender to Disable Caching

The remote agent batch logic was updated in the 15.1 branch to allow messages to build up within the remote agent for up to 20 seconds. In some cases, this may be too long. In order to decrease this batching period, or, completely disable batching, a ‘Max Batch Latency’ setting was added to the remote agent sender device. Setting this to zero will disable batching altogether. Updating the remote agent sender device (or channel) with a <R4 client will most likely reset the batching latency back to the default (of 20 seconds).

 

CNXN-4101: The database polling device doesn't work in the remote agent

The services required to make the database polling device work on the remote agent were not implemented prior to this build. The database polling device will now has the same capabilities whether running in Connexion or a remote agent. Note that working with a database polling device in the gateway UI will be slower since calls must be forwarded to the remote agent.

CNXN-4100: No messages were found in the file. Make sure framing settings are correct.

Issue: When a corrupted file (typically HL7) is encountered by the file reader, the file is not ingested and an error is posted to the device (no message is posted on the queue). This corrupted file is never picked up and remains in the directory indefinitely (and an error is logged on each directory read).

Solution: When the file reader has [Message Framing] enabled and a file is encountered containing zero valid messages, the contents of the file are read into a message and placed on the error queue. An error is logged to the device, and then source file is then deleted. If the file is large (Configurable via the UI), then it is added as an attachment to the message.

For example, the following file is not valid HL7 as it is missing the MSH segment. Prior to R4, this file would not be ingested and an error logged on each read of the source directory.

PID|||100001||CIERS^HANH^CHANTAY|^^CIERS|19340901|F||U|6834 RIO ESTRADA WAY^^SLC^UT^60561^USA^^SALT LAKE||(408)-131-3279|(408)-389-4489||||872-39-1819|872-39-1819|||||||||| PV1||O|NEPH^^|||^^|2190^TESTA^GIULIANO^^^|308447^ABBO^PAUL^R^^||TRP||||||||||BLUE CROSS||||||||||||||||||||||||201101111454| IN1|1|BC-PPO^|BLUE CROSS OF ILLINOIS||||(408)-374-7817|941-53-6056||||||||KORTHAUER^MISHA^GIHANHA|||953 BENBROOK LANE^^BURBANK^CA^^USA^^LOS ANGELES

In R4, this file is read into a message and placed onto the error queue.

CNXN-4099: Add Column to Connected User displaying their Authorization Role(s) comma delimited

New Feature: The ability to easily view which Authorization Role(s) a currently logged on user is mapped to. This applies to both Connexion and Gateway.

CNXN-4098: "Disallow Logins" setting with a list of specific user accounts that are denied access even though they have an account in AD

New Feature: The ability to reject users from logging into Connexion / Gateway without disabling their active directory / windows account.

Normal procedure for disallowing access to Connexion / Gateway is to remove the user from the relevant active directory (or Windows) user groups. There may be cases where a user account cannot be disabled or removed from the relevant user groups without breaking access to other software. In this case, the AppSettings.config file can be changed to exclude specific users:

<?xml version="1.0" encoding="utf-8"?> <appSettings> <add key="LohCompactionFrequencyInMinutes" value="60"/> <add key="wcf:disableOperationContextAsyncFlow" value="false"/> <add key="MaximumAuditFileAgeInSeconds" value="120"/><!--Sets the maximum age (in seconds) of an audit file before it is processed--> <!--<add key="AuditWriterFormat" value="protobuf"/>--><!--protobuf, json--> <!--<add key="AuditWriterLogToNLogOnly" value="false"/>--><!--This will disable the Custom Code Handling of audit records and write them directly to a log file instead--> <!--<add key="EnableGatewayApi" value="false"/>--> <add key="UserBlackList" value="Domain\User, Domain\User"/><!--This will reject specific users from logging into Connexion. Comma-delimited list of Domain\User--> </appSettings>

Update the [UserBlackList] setting to include a comma-delimited list of user accounts (in the form of Domain\User) followed by a service restart. Rejected users will see the following message upon connecting to Connexion / Gateway:

CNXN-4095: Support for writing to S3 in Channel Backup

Improvement: The ability to send channel backup files to AWS S3 (or Azure blob storage)

The channel backup UI has been updated to reflect the file writer’s ability to send to AWS/Azure. Store your channel backup files in the cloud. The recommended approach is to test sending files via a file writer device (in a normal channel). Once successful, copy the settings into the channel backup UI.

Channel backups are never automatically deleted - you must periodically purge old channel backup files.

CNXN-4086: Add option to File Reader Device to Delete Zero Byte files if older than 6 Hours

New Feature: File reader can automatically (old) delete zero-byte files.

Occasionally, zero-byte files are deposited into a directory being monitored by a file reader device. Zero-byte filenames are remembered, and after 6 hours the files are deleted (assuming they are still zero-byte). A log is written when this happens.