Currently, in Analyses ListingView a new column is created for each interim field. When an analysis requires multiple interim fields, the table expands horizontally to the point where it becomes very difficult to view and manage the data.
Additionally, there is currently no native way to specify if an interim field should capture an uncertainty value alongside its main result.
I propose:
-
UI/Layout Refactor src/bika/lims/browser/analyses/view.py
Instead of creating a dedicated column for each interim field, the interim fields should be nested or displayed directly below the main Result column for that specific analysis.
-
Add allow_uncertainty to Interim Fields
src/bika/lims/browser/fields/interimfieldsfield.py . If allow_uncertainty is checked/true for a specific interim field, the system should render an interim uncertainty input field directly below the main +- (uncertainty) column.
Currently, in Analyses ListingView a new column is created for each interim field. When an analysis requires multiple interim fields, the table expands horizontally to the point where it becomes very difficult to view and manage the data.
Additionally, there is currently no native way to specify if an interim field should capture an uncertainty value alongside its main result.
I propose:
UI/Layout Refactor src/bika/lims/browser/analyses/view.py
Instead of creating a dedicated column for each interim field, the interim fields should be nested or displayed directly below the main Result column for that specific analysis.
Add
allow_uncertaintyto Interim Fieldssrc/bika/lims/browser/fields/interimfieldsfield.py . If
allow_uncertaintyis checked/true for a specific interim field, the system should render an interim uncertainty input field directly below the main +- (uncertainty) column.