Content Comparison

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

ImprovementNew 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:

Image Added