> 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/instruments-and-integrations/other-release-notes/ipp-v2.3.0-release-notes.md). # IPP v2.3.0 Release Date: March 2022 These Release Notes describe the key changes to the Illumina Preset Protocols (IPP) since version 2.2. This is an optional software update for customers interested in the new features available with this release. If upgrading from a version prior to version 2.2, review the release notes for v2.2 for a list of features and bug fixes introduced in that version. ## Compatibility * Clarity LIMS v5.1 and later * NGS Extensions Package v5.21 and later ## New Features * Support for Clarity LIMS v6.0. Clarity LIMS v4.x and v5.0 are not supported. * Updated NovaSeq v3 workflow to generate v2 sample sheet to support NovaSeq Control Software (NVCS) v1.8.0. * Fixes to address the following Apache log4j vulnerabilities: * CVE-2021-44228 * CVE-2021-45046 * CVE-2021-45105 * CVE-2021-44832 * Tech refresh to upgrade third party libraries. ## Defects Fixed * Fixed Oracle 4000 maximum character limit issue in the NovaSeq, MiSeq, and CovidSeq workflows. This fix was achieved by moving long automation scripts into a custom field. * Fixed MiSeq workflow by removing setUDF script from the MiSeq Set Next Step - Advance automation. ## Known Issues This release contains the following known issues in the NextSeq 1000/2000 v2.1 workflow: * Sample Name can only contain alphanumeric, dash, and underscore characters. For more information, refer to NextSeq 1000/2000 Integration v2.2 Validation and Troubleshooting in the Clarity LIMS Integrations & Tool Kits documentation. * Having two samples with the same name in the same sequencing run is not supported. --- # 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/instruments-and-integrations/other-release-notes/ipp-v2.3.0-release-notes.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.