4.2.0 Upgrade Notes

Removed the Remove All Events Button

We removed the Remove All Events button in the Events screen to comply with Cures certification security requirements. If developers need to remove all events, they can use the Prune Events in the Data Pruner tab of the Settings screen. This is the preferred method to remove or prune events.

Changed the patient_id Query Parameter Naming Scheme for the Remove Message API Request

For the DELETE /channels/{channelId}/messages/{messageId} (Remove Message) API request, the patient_id query parameter is changed to patientId.

Renamed the User Authorization Extension to Role-Based Access Control

The User Authorization extension is changed to the more standard name, Role-Based Access Control. All references to "User Authorization" in the user and extension guides, application user interface elements, and the GitHub Wiki, are changed to "Role-Based Access Control". Going forward, the User Authorization extension will be referred to as the Role-Based Access Control extension.

Moving Java Home Preference Checks

The JAVA_HOME environment variable is now higher in the list when launching the server.

If you only have one version of Java installed on your system, then this doesn't matter. But if you have multiple versions installed, you may want to check to see that the Mirth® Connect server is using the version of Java that you expect. You'll be able to see what version is being used in the server logs at startup.