14.0 Release 3 (v14.0.7449)

Connexion.14.0.7449.exe
Connexion.Integrator.14.0.7449.exe

CNXN-2390

Server/Database management - Should show the "Used Size" of the sql server database in the database info screen

This feature ties into 2389/2385/2383. Since we are now periodically checking the database health, we are simply displaying this information in the UI. This is displaying an additional property already part of the database diagnostics.

[When Connexion uses Express or LocalDb, there is no way to determine how much cap space remains]

CNXN-2389

Systems using Express and LocalDb should log an error when Database reaches 90% of maximum size allowed

Connexion systems which use size-limited databases (Express editions and LocalDb) will stop working if the maximum database size is reached. When this happens, it is difficult to get the system operational again - it requires SQL Management Studio and the manual deletion of data. Irrespective of any warnings or dialogs displayed about this database size limit, it will happen. Instead of Connexion just failing out of the blue, it should start logging warnings and errors as space runs out.

This is analogous to the physical disk freespace check to prevent Connexion from failing due to lack of space (which has happened even on monitored systems). This is a low impact feature (single additional query).

SQL Express & LocalDb only

[When Connexion uses Express or LocalDb, it will fail without warning once the database limit is hit]

CNXN-2385

Create a feature to allow space reclamation for SQL Express and LocalDb.

Per above, if a system runs out of physical free space or hits the database size limit. SQL Manager must be installed and non-critical data pruned - not a trivial process. A routine was added which will prune non-critical data and remove the oldest 10% of messages. Once this is complete, normal database maintenance operations can succeed. This feature is called automatically if the database is on the verge of running out of space (SQL Express and LocalDb).

For Sql Standard and above (no size limit), this feature must be triggered from the UI. This may be useful in the case where physical free space runs out.

SQL Express & LocalDb only

[When Connexion fails due to the database limit being reached, there is no way to recover]

CNXN-2383

Database Maintenance should include shrinking the log file

We have seen database log files grow significantly during some of the database maintenance routines. In some cases the log file exceeds the database size. In order to minimize the impact on physical disk space, the log file will be automatically shrunk under the following circumstances:

1) Log file is greater than 1GB
2) Database is in SIMPLE recovery model
3) A FULL back has occurred

[Certain database maintenance routines create extremely large log files which waste disk space]

CNXN-2376

System Level Stats should be available in the dashboard

In version 13 we used to display 'system'-level stats (ie, total message counts). Tony has requested that this be re-added in version 14. We already have all the data / infrastructure, so it was simply a case of displaying this data in the UI.

[There is no way to visualize a system's overall message count, or a channel's total message count, which makes it impossible to quickly establish if a Connexion system is configured incorrectly]

CNXN-2373

HL7 Outbound Device Debug Logging Link to log file

Chrome change only.

CNXN-2395

Flush the temp directory as part of the install wizard routine

The Connexion temp folder isn't currently being flushed and can get quite large. When Connexion is upgraded, it should be emptied.

[The Connexion temp folder grows indefinitely and wastes disk space]

CNXN-2397

Getting FileNotFoundException and "Error moving file" in File Reader device although file moves correctly

CNXN-2396

HL7 Tx v1/v2 have issues with large map tables

CNXN-2388

Fatal/FatalFormat errors do not make it into the EventHistory

CNXN-2386

Queue in/out preview display for xml documents is showing namespace prefix

CNXN-2384

Database Maintenance - Message data in the database is not being properly purged

CNXN-2382

Connexion Logging - Info, and warning messages no longer found in the EventHistory

CNXN-2381

Text viewer is blank when a single collapsed region should be displayed

CNXN-2380

Channel Backup doesn't seem to work

CNXN-2379

Queue device shouldn't fire 'message changed' when the selected column changes

CNXN-2368

Re-importing devices causes the 'old' device to remain hooked to the client message channel

CNXN-2377

Cannot import a channel when a matching channel has been deleted

CNXN-2195

Internal references (in the CCD) are not displayed / updated via the manage devices dialog.