> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/clarity-lims/clarity-lims/clarity-and-lablink/other-release-notes/release-notes-clarity-lims-v5.4.0.md). # Clarity LIMS v5.4 Published: 2021 Latest Release: v5.4.0 These Release Notes describe the key changes made to software components for BaseSpace Clarity LIMS since version 5.3. This is an optional software update for customers interested in the new features available with this release. If you are upgrading from a version prior to v5.3, review the release notes for v5.3 for a list of features and bug fixes introduced in that version. ### New Features * **Genealogy View** — Provides an interactive and hierarchical view of the history of an experiment processed through BaseSpace Clarity LIMS. Genealogy view shows the relationship between submitted samples, derived samples, and related outputs. Information is presented in a hierarchy, starting with the submitted sample and progressing through all steps performed on derived samples. Genealogy view can also be used for troubleshooting and to help those upgrading from Clarity LIMS v4.x to the latest version of v5.x in the cloud. * **Email notifications for LabLink notes** — LabLink will send an email notification when a new Project Note or Sample Note is created on the Project Overview or Sample tab. This feature is not active by default. * **LDAP support for LabLink users** — LabLink now supports LDAP authentication. Customers with LDAP authentication enabled for Clarity LIMS are now able to sign in to LabLink. * **Security improvements** — When upgrading to v5.4, for password management, users must now provide an email address and reset the password. ### Bug and Security Vulnerability Fixes * Move to Next Step when uploading a measurement file to Standard QC step artifact. * Remove from Workflow assigned by Script is not recognized when used on a Pooling Step. * Running Automations on Step Entry with AutoPlacement and different destination container type no longer results in a 500 error message. * The Show History feature correctly displays the QC step values. * The Custom Fields screen can now be accessed by LabLink when Numeric Range fields only have a lower limit. ### Known Issues * You may experience a decrease in performance when handling large pools of samples (approximately 4000) from the Clarity LIMS interface in pool creation or the creation of output container. * When using the Processes REST API endpoint with a `projectname` filter on projects with more than 500 samples, the query returns an incomplete set of data. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.bioinsight.illumina.com/clarity-lims/clarity-lims/clarity-and-lablink/other-release-notes/release-notes-clarity-lims-v5.4.0.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.