Release Notes 6.6.0

Discngine assay, version 6.6.0

Release Date: 29/07/2025

General

Deprecated features

REST API authentication

The current REST API authentication method will be changed in one of the next releases (target: 7.0.0). It will be replaced with OAuth 2.0 as it is the industry standard for securing APIs. If you plan on building integrations or applications that rely on our REST API, we encourage you to start preparing for this change. Note that we do not plan on changing the endpoints themselves for the time being.

Reference Data

Improvements

#13247 - Display a warning when modifying a vocabulary item

When modifying a vocabulary item, a warning is now displayed to inform the user that this may not reflect everywhere in the application, as some data may have already been created using the former value of this item.

Bugs resolved

#12405 - Audit field is incorrect for well types

On the Well Type page, after creating a new type, the field "Last Updated By" now contains the username instead of an internal name.

#12412 - Parent is not correctly displayed for vocabulary and sites, in read only mode

When displaying a site or a vocabulary, the parent location is now correctly displayed in every case.

#12111 - Vocabulary's names and codes can not have the same value

It's now possible to have exactly the same name and short name for a vocabulary item.

#12407 - Automatically generated code for site is too long and prevents the site's creation

It's now possible to create sites with codes up to 100 characters without any error.

#12977 - When creating a new site, all parents are not displayed

When creating a new site, all parents are now displayed in the list, allowing you to select the correct parent site.

Sample

New Features

#12353 - Make Sample compatible to Mixture management

Previously, only one batch could be added to a sample. Now, we handle mixtures: multiple substances in one sample.

• The plate details page has been modified. Before, the plate viewer showed the batch names in each well, now we have information on whether it's a mixture or a single constituent.
  The plate content has been modified to include information on all the constituents and solvents contained in the plate.
• Sample administrators can now define a liquid or solid display unit according to container type. Quantities are then displayed in the selected unit according to type.
• All the workflows are working as intended but cannot be used with plates containing mixtures yet.
• The REST API currently does not support mixtures.

#12228 - Mixture preparation Workflow

A new Workflow Plate Creation from Batch Combination has been created to prepare plates containing mixtures in Sample, based on batch and dose definitions, while specifying the number of replicates and the well type for each mixture. This workflow is currently the only way to create mixtures in Sample.
Below are the main steps of the workflow:

🔧 Requesting

This is the entry point of the mixture generation workflow. At this stage, the user defines some parameters of the request like the Maximum number of constituents per mixture, the Target usage, and optionally a Control layout.

🧪 Task Requesting

In this step, the user defines the actual mixtures to be created. For each mixture, the user specifies:

• The list of constituents to be combined
• The list of doses to apply to each constituent
• The solvent to use for the dilution

Once all mixtures are defined, the user can:

• Adjust the number of replicates for each mixture
• Assign a well type to each mixture, if a control layout was previously defined during the Requesting step.

🔍 Sourcing

In the Sourcing step, the user selects the sourcing method.
Once the method has been run, a list of sourced containers is generated. For each mixture, the list shows:

• The source plate and well that will be used as a source
• The batch name that will be used for the mixture
• Other information such as the concentration, solvent, quantity, location...

If a single source does not cover all the replicates of a constituent, the system may select multiple sources to ensure there is enough material for all replicates.

🎯 Target Requesting

In this step, the system assigns the previously identified sources to specific wells on the target plate(s).

• Each item is placed according to its defined well type, if a control layout was selected in the request.
• The placement follows the filling layout chosen by the user (e.g., row-wise or column-wise).

This mapping takes into account:

• The number of replicates for each mixture or constituent
• The available space on the destination plates
• Any constraints introduced by control zones or reserved wells

This step translates the logical content into a concrete plate layout, preparing it for the processing phase.

🔧 Processing

In the Processing step, the goal is to generate the worklist for the robot to perform its tasks.

The robot then uses the logfile retrieved from the robot to carry out the necessary actions, and the system ensures that all relevant data is properly reflected in the database to maintain consistency and accuracy.

Bugs resolved

#11869 - Invalid wells block transformation (replication, compression, decompression) when quantity is insufficient

Previously, the process was blocked when invalid source wells were not usable (e.g., due to insufficient quantity).
Now, invalid wells are completely ignored during processing: no volume is taken from them or added to a destination well.
Invalid wells are also not available as sources at the sourcing step.

Assay

New Features

#12895 Handle mixtures in your Assay runs

You can now retrieve mixtures (several samples for each well) and use them in your Assay runs. You can use the Retrieve information from Sample functionality to import the information and display the values on the Experimental Conditions page. You can then use them in your aggregations and analyses at the Sample Analysis Settings step.

In order to visualize mixtures in Spotfire, a new template MixtureAnalysisDefaultTemplate has been created. Additionally, a new information link, validated_data_v2 has been added. The previous version, validated_data, does not support mixtures or multiple aggregations, but it will remain available and will not be deleted.

The information link aggregated_data has been updated to display the aggregation to which each group belongs.

#12924 Multiple Reference and Sample aggregations

Several aggregations can now be created in your run, allowing you to have several specific groups and add analyses to each of them. More information on how to create multiple aggregations and add analyses can be found on the Assay documentation Reference Analysis.

Improvements

#12990 - Be able to save and delete parameters when publishing in Design mode

Following the improvement of the publication process in the last release, it is now possible to save and delete parameters in design mode, without publishing the data. It's also possible to delete a publisher from the "Select Publisher" page.

#12965 - Move the buttons validate/invalidate in Assay

The buttons validate and invalidate are now accessible on the top bar, and visible even when the left panel is hidden.

#13104 - Dose rounding when retrieving concentration from Sample in Assay

When importing the concentration from Sample, you can now specify a number of significant digits to import, in case you have insignificant variations between several wells.

Bugs resolved

#11628 - Errors when clicking "Revalidate All"

At the Sample Analysis step, sometimes, the "Revalidate All" button led to an error. This is now resolved.

#11757 - Unable to see all associated runs to a Spotfire template

Previously, it was impossible to see the associated runs of a template associated with more than 10 runs.
Now, you can see the list of all associated runs even if there are more than 10.

#12996 - Sample mapping page is not refreshed after a revert when the run is reopened

When reopening a run, after a revert, the Sample Mapping page is now correctly refreshed to show the latest changes made to the run.

#13073 - Incorrect "At least one sample" count in control layout at Plate Mapping step

In the Plate Mapping step, a warning appeared, when applying a layout, without any valid reason. The warning is now displayed only if there are no samples in the control layouts added, even if the sample has a well_type other than 'SAM'/'Sample'.

#13035 - Experimental Conditions - Error when delete All

• Previously, when you attempted to delete all Experimental Conditions values on an execution run before the Sample Analysis Settings step, Experimental Conditions involved in aggregation were not deleted. Now, all unused Experimental Conditions at this step are removed when clicking Clear all values.
• On the Experimental Conditions page, plates could be considered complete even without any Experimental Conditions values. This has been corrected.

#13034 - Normalization parameter mismatch on copied run when using Experimental Conditions as parameters

When copying a run, the Experimental Conditions values used as normalization parameters were referencing the original run instead of the copied run. This has been corrected, and the normalization parameters now properly reference the Experimental Conditions of the copied run.

#13174 - Dose response with multiple dose units

The R script 'Dose Response' has been improved to throw an error when the dose units are not homogeneous. A proper error message is displayed to ask for unit homogenization.

Deprecated features

The information link sample_information is deprecated. It only queries the experimental conditions of text type, while well_information returns all experimental conditions.

Warehouse

Improvements

#13025 - Add a call to a custom procedure at the end of the Warehouse protocol copy

It is now possible to call a custom procedure at the end of a Warehouse protocol copy.

Known bugs

General

#12720 Lists of values break some functionalities when the source vocabulary is too big. → Annotations (Assay), Assay Templates (Assay Catalog)

Reference Data

#13080 Making a copy of an Experimental Condition layout results in a new empty layout

Sample

#13252 "Dispense Vial" Workflow has checks and display issues

#13249 "Move & Dispose" Workflow - Invalid items are not ignored in the job

#12707 Impossible to cancel Edit Sourcing page when the selection is empty

#12582 Numbers are not displayed in dose layouts at the requesting step of the Plate Serial Dilution workflow

#12525 Inconsistent behavior of the batch list and the refresh icons in the Plate Creation workflow

#12416 A large amount of vocabulary items (~500+) can break the annotation edition at the task requesting step of the workflow "Container - Bulk Update Annotations Values"

#12360 During a reformatting job, if you select "Source" dilution with multiple copies, the dilution is listed multiple times in the generated worklist

Assay

#12703 Endpoint final_results doesn't work when too many lines are returned

#12536 Wrong redirection to the homepage when a reader runs into an error

Assay Catalog

#12877 Assay descriptions cannot contain more than 4000 characters

#12502 The task title is not updated when the assay name is changed after requesting publication