Release Notes Clarity LIMS v6.3.1

Published: Nov 04, 2024

Last Update: Nov 04, 2024

Latest Release: v6.3.1

These Release Notes describe the key changes made to software components for Clarity LIMS v6.3.1. The Clarity LIMS v6.3.1 patch release supersedes v6.3.0. It is intended for customers on or migrating to Clarity LIMS v6.3.0.

This release resolves customer-reported issues related to the following functions:

• OpenAPI endpoint (POST /artifacts/batch/update) failure

• Change in Basic search functionality

• SSH access cannot be requested for username with period.

New Features

There are no new features added with this release.

Bug Fixes

• Fix a bug where openAPI endpoint (POST /artifacts/batch/update) returns error when user attempts to submit a batch update request that includes at least 50 artifacts of one type and 1 artifact of another type , example, 50 artifacts (Derived Sample) and 1 artifact (Measurement).

• Fix a bug that prevents File placeholder from displaying the full text value in Step Setup screen.

• Fix a bug where SSH request made through System Settings, do not allow period (.) as part of the provided username.

• Basic search is now case-insensitive for limids and workflow.

• Fix a bug where Automation Worker becomes unresponsive after cancelling an ongoing automation job in a step multiple times.

• Fix a bug where auditeventlog has incomplete event message "Creating new file attached to" when attempting to upload a file attached to a measurement (ResultFile). The event message now displays "Creating new file attached to ResultFile".

• Fix a bug where config slicer tool takes longer time (~8 times) to import a config slice into Clarity LIMS v6.2 and v6.3 when compared to earlier versions (v6.1 and below).

Known Issues

• In Add Label screen, the label will starts at the well position at which user drops in when transferring the equivalent number of labels to samples in the output container at the first instance.

• If the client and server are in different time zones, there can be additional or missing search results when using Date Received of a sample as one of the search criteria in Advanced Search.

• Multiple accounts that share an email address only receive a reset password email for one of the accounts when a reset password request is made using Email information.

• The step milestone screen will becomes unresponsive when the request header/URL size is larger than the defaults capacity limit configured in either Apache HTTPD or Tomcat application server.

• If there are changes made to the existing LDAP integration settings, restarting of Tomcat service will be required to provide the user access.

• Clarity page will need to be refresh after applying browser zoom in/out for proper display. This is mainly due to a limitation on ExtJS in which, the width that components take are only set when the page is refreshed.

• If Complete and Repeat routing action is added to the sample before the execution of the Step Automation upon step exit, the sample is considered Completed and Repeated. The message "Repeated step and advanced" appears in the Next Step even though the step had failed at the EPP upon the step exit. This results in an incorrect description of the next step.

Additional Notes

• Font used for some of the UI components has been changed from DINWeb to Inter v4.0.

• Dependancy version upgrade:

  • upgraded to Apache Standard Taglibs v1.2.5

  • upgraded to Lodash v4.17.21

  • upgraded to apache-poi v5.3.0

  • upgraded to jackson-core v2.17.2

• For on-premise in-place upgrade from Clarity LIMS v6.2.x to v6.3.1, user is required to reinstall Sequencer API RPM if BaseSpaceLIMS-sequencer-api RPM is installed on the server. On Premise to On Premise In-place Upgrade Procedures has been updated to include this step.

• Security vulnerabilities in PostgreSQL 15.x have been addressed. PostgreSQL 15.6-15.8 is at a low risk of security vulnerabilities for customers on Clarity LIMS v6.3.1.

• The following API endpoints relating to processes have been deprecated in Clarity LIMS v6.3.0 and will be removed in the next major release:

  • POST /api/{version}/processes/

  • GET /api/{version}/processes/

  • GET /api/{version}/processes/{processId}

  • PUT /api/{version}/processes/{processId}

• The following API endpoints relating to UDT will be deprecated and removed in the next major release:

  • PUT /{version}/configuration/udts/{udtid}

  • GET /{version}/configuration/udts

  • GET /{version}/configuration/udts/{udtid}

  • POST /{version}/configuration/udts