# DesignStudio Array v2.2.0 Release Notes #### Release date May 2024 #### RELEASE V.2.2.0 HIGHLIGHTS * Ability to design EX-24 and EX-48 iSelect BeadChips. #### NEW FEATURES IN DETAIL * Options within Select Assays to design EX-24 iSelect and EX-48 iSelect BeadChips. * Updates to Compare Assays table to show new BeadChip types and specifications. * Out-of-date rsIDs submitted are automatically updated to the revised merged rsID per dbSNP. * Identity error file lists submitted rsID alongside revised merged rsID. * Score file automatically includes revised merged rsID. * rsIDs submitted with capital letters are automatically lowercased for consistent formatting. * Designs that use the automated strategy to convert from multi-allelic to bi-allelic are more clearly indicated in Review and Order Design page and output files. * Score file name updated from 'Failure\_Codes' to 'Warning\_Codes' to more accurately reflect the purpose. #### KNOWN ISSUES * Non-specific failures occur when: * Loci names include two dashes ("--") in the input file. * A M or MT chromosome designation is used for equine as species. * Submitting sequence files with certain formatting errors. The workflow terminates without allowing access to the error file. * When using an existing design file, a dropdown exists but the stand type cannot be changed. * Rare, specific Infinium II indels designing as Infinium I with a 3' ambiguity error message. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://help.connected.illumina.com/design-studio-array/reference/release-notes/designstudio-array-v2.2.0-release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.