14.0 Release 7 (v14.0.9129)
Released On | Feb 11, 2016 |
Release Type | Production Release |
Release Location |
Notes
This is mainly a maintenance release, however; one fairly major feature was added to enable Custom Code Devices (CCDs) to have their references automatically updated during Plugin upgrades.
In the specific case where the CCD is referencing a Plugin, or a sub-reference of a Plugin in the same channel, the CCD's references will be automatically upgraded each time the Plugin is updated. This prevents the issue where the assembly used by the CCD has a different version than the plugin (after an upgrade) and the channel fails to operate properly.
The same auto-upgrade referencing mechanism also works for the HL7 Transform Device V1/V2, as well as other devices that allow dll referencing.
To make use of this new feature the references in the CCD need to be reset and reconfigured with references selected from the "Current Channel" references tab.
New Features
Resolved | Description |
|---|---|
Connexion Installer Log files should be captured to the log folder for trouble-shooting | |
Develop a mechanism to automatically update dll references contained in the CCD | |
Database Connexion Control should provide the ability to specify a failover partner | |
Add a command-line flag to remove old, unused devices. |
Bug Fixes
Resolved | Description |
|---|---|
Connexion Command-Line - An invalid parameter passed to Connexion.exe should error and return -1 | |
Command-Line - plugins saved as nuget packages cannot be installed from the command-line | |
Updating a channel via import does not update CCD references/resources | |
HL7 Branch Device - Evaluation of LIKE query incorrect | |
Configuration Wizards have incorrect validation account on the database config screen | |
License validation failure can cause Connexion in a clustered enviroment to not start | |
Importing a channel which gets renamed automatically caused the device refs/attachments to not be imported. | |
Template device razor template editor doesn't support multiple different @model types (in different templates) |