Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 3 Next »

Released On

April 7, 2021

Release Type

Beta

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

Integrator

Breaking Change! - Certificate Rotation

15.0 R6 introduced Certificate Rotation which forces the Integrator to create a self-signed certificate on a rotating basis. If an Integrator is unable to communicate with the Gateway because of a downgrade to 15.0 R5 then you will need to use the "Break Glass" feature to re-establish the communications link.

See Certificate Rotation

Installer Descriptions
Gateway and Gateway Management Application: Connexion.Gateway.15.x.xxx.exe
Gateway Management Application Only: Gateway.ManagementUI.15.x.xxx.msi
Remote Integrator: Connexion.Integrator.15.x.xxx.exe
Remote Agent Push Update: Integrator.RemoteAgent.15.x.xxx.msi
Remote Updater A Push Update: Integrator.UpdaterA.15.x.xxx.msi
Remote Updater B Push Update: Integrator.UpdaterB.15.x.xxx.msi

  File Modified

Ticket

Type

Summary

R4 Change Log

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 writer, 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

Improvement: The ability to easily view which Authorization Role(s) a currently logged on user is mapped to.

  • No labels