Discngine assay Cloud Analytics, version 6.4.0
- Release Date: 17/04/2024
General
Improvements
-
11372 - Move plate layout in Reference Data
- In order to unify the experience in all applications, all plate layout definitions, no matter their types (Control, Dilution, Dose, ...) have been moved to Reference Data as a central place. They remain accessible and usable in all relevant applications, as they were.
- In the scope of this feature, some components of the Discngine assay platform have been deprecated. They are listed in the Deprecation Note. It is highly recommended that people working on integrations consult this document to be informed of required updates.
-
11408 - Upgrade Apex to version 23.2
- The application's visual framework has been updated to the latest version (23.2). The applications have been adapted accordingly.
Sample
Known bugs
- The following endpoints are not functional :
layouts/dose_layouts
layouts/plate_layouts
Assay
Improvements
- 10061 - Add and run oml cutoffs
- Automatic analysis/invalidation/selection is now possible using R or Python scripts.
- 10986 - See annotations in the Spotfire visualisations
- Annotations are now available through information links in Spotfire. You can add them to your templates.
- 11521 - Make PP readers compatible with multiple reader
The use of multiple readers in a single run has been extended to include Pipeline Pilot readers.
Bugs resolved
- 9174 - Unnecessary null values in aggregated_data and aggregated_data_text Spotfire Information Links
- In Spotfire, the aggregated data information links used to retrieve some results with no business value. These results are now discarded.
- 9108 - Assay : Load barcode management - Plate mapping step
- During the plate mapping, in some specific circumstances, clicking on the previous button would redirect you to the wrong page. The redirection is now fixed.
- 11555 - Multiple reader bug after run copy
When copying a run that uses the multiple reader feature, files could get mixed up between parent and child runs. When this happened, a file removed from one would also be removed from the other. This behavior has been fixed and the files are now properly separated.
Warehouse
Bugs resolved
-
11130 - Experiment not deleted after run depublication
When a run is unpublished in Assay, the corresponding experiments in Warehouse are deleted. -
11354 - Technical debt - Relaunch aggregation from the protocol page should not delete experimental data.
Experimental data is no longer deleted when the aggregations are restarted.

