**CUAL UPDATES**

Improved error message logic for interference section to prevent premature alerts.

MV-EXPInter TSTS BG QNT | Interference Error Message Logic

Ensure error messages on the Interference section are only displayed when both relevant fields have been interacted with, preventing premature visual noise. Currently, the error message "An Interference must have an Interfering Substance and Allowable Error %" appears prematurely when a new interference row is added. The error message should only be triggered whenboth fields have been interacted with (touched) but left blank. Leaving the "Interfering Substance" field blank should not trigger an error. h2. *Implementation Details:* # Update the validation logic for the Interference section: #* The error message is only triggered when both fields are touched and left blank. # Ensure the form validates correctly on save, ensuring that: #* An error message appears if any of the 2 fields are left empty, regardless of either field's state. h2. *User Flow:* # The user adds a new interference row. # No error message is displayed initially, even if both fields are empty. # The error message only appears when either field is touched but left blank.

Fixed validation error preventing test saving despite correct Range Low and Range High values.

MV-EXP TSTS QNT | Range Low and Range High Errors During Test Editing

The application displays a validation error message, *“Range low must be less than range high”*, and prevents saving a test, even when the entered values satisfy the condition (i.e., _Range Low_ is indeed less than _Range High_). !2025-01-21_173047_Microsoft_Edge.png|thumbnail! h4. *Steps to Reproduce* # Open the test setup or experiment configuration page. # Enter a valid *Range Low* and *Range High* value where _Range Low_ is less than _Range High_ (e.g., Range Low = 2.4, Range High = 186.2). # Attempt to save the test.

Updated the "Save" button to enable only when changes are made in the Method Comparison settings.

MV-EXP MV-EXPMC SMQ | Save Button Enabled Only on Change

Ensure that the "Save" button is only enabled if there are changes made in the Method Comparison (MC) experiment settings modal. Currently, the "Save" button in the *MC Experiment Settings* modal remains enabled regardless of whether there have been changes to the input fields. To enhance the user experience and prevent unnecessary submissions, the "Save" button should only become enabled when changes are detected in any of the fields. h2. User Flow: # User opens the *MC Experiment Settings* modal. # By default, the *Save* button is disabled. # If the user edits any of the fields (e.g., *Min. Samples*), the *Save* button becomes enabled. # If the user reverts all fields to their original values, the *Save* button is disabled again. # On clicking the *Save* button, it will be disabled once changes are saved successfully.

Fixed the missing yellow check icon for incorrect daily run results in SMQ and Qualitative modes.

MV-EXPPrec BG QL SMQ | Yellow Check Icon Missing for Incorrect Daily Run Results in SMQ & Qualitative Modes

Ensure that the yellow check icon appears correctly when all run results in a day are incorrect for SMQ and Qualitative modes in the Precision Experiment. The Precision Experiment UI currently has a bug where the yellow check icon does not display when all run results in a day are incorrect in SMQ and Qualitative modes. Instead, the field remains blank. This behavior is inconsistent with Quantitative mode, where the icon functions correctly. !yellow check.png|width=745,height=580,alt="yellow check.png"! h2. Steps to Reproduce: # Open the Precision Experiment for SMQ or Qualitative mode. # Input incorrect run results for all runs in a single day. # Observe that the yellow check icon does not appear in the daily summary column.

Updated "Result" label to "Carryover (%)" and added tooltips for clarification in the MV Carryover Percent Mode.

MV-EXPCarry ADT | Update Label in MV Carryover SD Mode Experiment Results

In the MV Carryover Percent Mode, the label currently displays "Result" for the final value. To align with the display in Percent Mode, this label should be updated to "Carryover (%)." Additionally, tooltips should be added to provide further clarification on the terms "Low Diff." and "Carryover (%)." !Screenshot 2024-11-07 at 10.39.23 AM.png|width=1016,height=90,alt="Screenshot 2024-11-07 at 10.39.23 AM.png"! h2. Implementation Details: # Update the label "Result" to "Carryover (%)" in the MV Carryover Percent Mode display. # Add a tooltip for "Low Diff." with the text: "The subtracted difference between the average of High-Low and Low-Low results." # Add a tooltip for "Carryover (%)" with the text: "Measure of how much a high concentration sample influences the result of a subsequent low concentration sample." h2. User Flow: # The user navigates to the MV Carryover Percent Mode. # The user changes the experiment mode to Percent. # The user observes the updated label "Carryover (%)" in place of "Result." # When hovering over "Low Diff.," a tooltip appears with the text: "The subtracted difference between the average of High-Low and Low-Low results." # When hovering over "Carryover (%)," a tooltip appears with the text: "Measure of how much a high concentration sample influences the result of a subsequent low concentration sample."

Updated the percent status to reflect changes in real time for tests in QNT/QL.

MV-EXP BG | The percent (%) status under Select Test should be updated in real time

Test Condition: User is in QNT/QL Steps to Replicate: # Inside a test, update any data in the test # Click save button Result: Notice that the percent result is not being updated. Still need to hit refresh button for the percent to be updated Screen recording: [https://jam.dev/c/57758ca8-fd6b-4e12-8936-46a9852ef8ba|https://jam.dev/c/57758ca8-fd6b-4e12-8936-46a9852ef8ba|smart-link]

Fixed save option not triggering when switching to TEa mode and force passing a sample.

MV-EXPMC MV-EXPTrueness QNT QL BG | Switching Regression to TEa mode doesn't trigger save with Force Pass

When switching from MC Regression Mode to TEa Mode, Force Passing a sample does not trigger the Save option as expected. !2024-12-18_083442_Microsoft_Edge.gif|width=1040,height=1168,alt="2024-12-18_083442_Microsoft_Edge.gif"! h2. *Steps to Reproduce:* # Navigate to a Method Comparison or Trueness experiment. # Switch from Regression Mode to TEa Mode. # Force Pass a sample. # Observe the Save button. [https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|smart-link]

Removed the display of Test and Experiment values when their sections were already shown.

MV-EXP BG | Test and Experiment value should not be displayed if the Select Test and Select Experiment section is already displayed

(This is quite hard to replicate) Ref: [https://discord.com/channels/965551040890028062/1219085471557353652/1303573129146138717|https://discord.com/channels/965551040890028062/1219085471557353652/1303573129146138717|smart-link] !image-20241106-055428.png|width=1174,height=1102,alt="image-20241106-055428.png"!

Disabled saving if only spaces are entered in the Example Precision Experiment Summary.

MV-EXP SMQ BG | User should not be able to save the changes if the entered data is space only

Environment: Dev Test Condition: User is in Templates > Edit Example Precision Experiment Summary Steps to Replicate: # In Example Precision Experiment Summary, enter three space # Click Save button

Fixed incorrect label in Precision Report Summary from "Result 2" to "Result 1."

MV-EXPPrec BG SMQ | Incorrect Result label displayed in Precision Report Summary

In the *SMQ Precision* experiment report, the summary section incorrectly displays *"Result 2"* for all samples. The correct label should be *"Result 1"* as per the experiment setup. !1.png|width=1437,height=853,alt="1.png"! !2.png|width=1438,height=774,alt="2.png"! h2. *Steps to Reproduce:* # Navigate to a *SMQ Precision* experiment with multiple samples. # Generate the experiment report by clicking on *Export PDF*. # Check the summary section in the report.

Adjusted menu tooltip positioning upon window resizing to ensure visibility.

ORGS BG | If the window is resized and upon hover, the menu tooltip should be on the tap of the page content

Steps to replicate: # Resize the window # Hover on the menu Result: Menu label is not visible *Second scenario:* The tooltip is cropped !image-20241114-004522.png|width=1254,height=906,alt="image-20241114-004522.png"! !image-20241106-034445.png|width=1513,height=982,alt="image-20241106-034445.png"!

Fixed the progress indicator for SMQ tests to show accurate completion percentages.

MV-EXP BG SMQ | Progress Indicator Always Shows 0% for SMQ Tests

Fix the progress indicator for SMQ tests to accurately reflect the percentage of test completion. The progress indicator for SMQ tests always displays "0% complete," even when there is measurable progress on the test. This issue creates confusion for users tracking the status of their tests. !zero.png|width=583,height=395,alt="zero.png"! h2. Steps to Reproduce: # Open an SMQ test in the MV module. # Perform some test steps to make progress. # Observe that the progress indicator remains at "0% complete."

Updated the Carryover Percent calculation formula for MV Carryover Experiments to ensure accurate results.

MV-EXPCarry ADT | Correct Calculation Formula for Carryover Percent in MV Carryover Experiment

The current formula for Carryover Percent is incorrect. The calculation should follow the formula: Carryover Percent=[(LowDiff/(High-LowLow)]X100 See this Example: !Screenshot 2024-11-07 at 11.33.27 AM.png|width=399,height=229,alt="Screenshot 2024-11-07 at 11.33.27 AM.png"! where: * *Low Diff* is calculated as the difference between *High-Low*​(The Low Rep directly after the last High Rep) and *Low-Low*(Average of Low-Low results) Low Diff: 3.30 - 3  = 0.3 * *High, 23.5,* is the average of the high results (24, 23.5, 23). * *LowLow, 3,* is the average of the low results (3, 3). The calculation should be as follows: Carryover Percent = [0.3/(23.5-3)]100 = [0.3/(20.5)]100 =[0.01463415]100 =1.46% h2. Implementation Details: # Update the Carryover Percent calculation formula in the MV Carryover Experiment to use the corrected formula. # Ensure that the updated calculation is reflected accurately in all relevant sections where Carryover Percent is displayed. h2. User Flow: # The user conducts the MV Carryover Experiment in Percent Mode. # The user views the updated Carryover Percent, which now reflects the correct calculation.

Updated icons in the Results Banner for "Incomplete" and "Not Started" states to enhance clarity.

MV-EXPInter TSTS QNT | Update icons for Incomplete/Not Started states in Results Banner

To improve clarity in the Results Banner by replacing the current yellow checkmark icon for "Incomplete" and "Not Started" states with the three dots icon, ensuring consistency and better visual representation. Currently, the Results Banner uses a yellow checkmark icon for experiments marked as "Incomplete" or "Not Started," which may confuse users as the checkmark implies progress or completion. Updating these states to use the three dots icon will align them with user expectations and clearly indicate that the experiment is pending or incomplete. !image5.png|width=796,height=542,alt="image5.png"! !image4.png|width=351,height=65,alt="image4.png"!

Fixed inconsistency in undo/redo actions when using Force Pass in Method Comparison experiments.

MV-EXPMC MV-EXPTrueness QNT QL BG | Undo/Redo states inconsistent with Force Passing options

The undo/redo states behave inconsistently when using the Force Pass option in the Method Comparison experiment. * *Issue:* The "Undo All" option is available, but standard Undo and Redo actions are not functional when interacting with Force Passing. !2024-12-18_083124_Microsoft_Edge.gif|width=1040,height=728,alt="2024-12-18_083124_Microsoft_Edge.gif"! h2. *Steps to Reproduce:* # Navigate to a Method Comparison or Trueness experiment. # Force Pass a sample by double-clicking the icon. # Attempt to use the Undo/Redo buttons. [https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|https://discord.com/channels/965551040890028062/1112699023552421938/1318738675496128512|smart-link]

Removed unnecessary space appearing below the "Verification" and "Analyzer" buttons in the sidebar.

ORGS BG | When clicking the Verification and Analyzer in the sidebar, space below the "Verification" or "Analyzer" should not be displayed

*Test Condition:* User is in [https://staging.cualia.io/org/Tl2p0u9W/mvs|https://staging.cualia.io/org/Tl2p0u9W/mvs] *Steps to replicate:* # Click Dashboard # Click Verifications # Click Departments # Click Analyzers *Screen recording*: [https://jam.dev/c/37880f93-42be-4a47-951d-0b3c816db22a|https://jam.dev/c/37880f93-42be-4a47-951d-0b3c816db22a|smart-link] *Result*: Upon clicking Verifications and Analyzers button, a space will appear below the buttons

Fixed icon positioning; undo, redo, and reset icons remained stable after clicking redo button.

MV-EXP MV-EXPMC SMQ BG | The undo, redo and reset icons should not move upon clicking redo button

Environment: Staging Test condition: User is in [https://staging.cualia.io/org/Tl2p0u9W/mv/f1n5k0426x/tests/hh6uy6xr8xk/semiQuant/methodComparison|https://staging.cualia.io/org/Tl2p0u9W/mv/f1n5k0426x/tests/hh6uy6xr8xk/semiQuant/methodComparison] Steps to replicate: # Update the source of Label one, label two and label three # Click undo button # Click Redo button Result: Undo, redo and reset icons moved on the left side upon clicking Redo button

Made the "Run Order" column uneditable in MV Carryover experiments to ensure consistent sequencing.

MV-EXPCarry ADT | Make "Run Order" Column Non-Editable in MV Carryover Experiment

In the MV Carryover experiment, the "Run Order" column currently allows edits. This ticket proposes making the "Run Order" column hardcoded and non-editable to maintain consistent ordering across experiments. This will prevent accidental changes to the run sequence, ensuring clarity and uniformity. !Screenshot 2024-11-07 at 1.49.13 PM.png|width=1063,height=820,alt="Screenshot 2024-11-07 at 1.49.13 PM.png"! h2. Implementation Details: * The "Run Order" column should be hardcoded with predefined values (e.g., High Rep 1, High Rep 2, High Rep 3, Low Rep 1, Low Rep 2). * Disable editing permissions for this column for all user roles. * Ensure this change applies to both existing and new MV Carryover experiments. h2. User Flow: # User opens the MV Carryover experiment interface. # The "Run Order" column displays a fixed sequence without the ability to modify entries. # Users can view but not edit the sequence in the "Run Order" column.

Fixed issue where dropdown options appeared after adding a unique Analyte in the Quantitative Test modal.

ANZ BG | In analyzers, when adding a Analyte in Add Quantitative Test modal, If I entered the Analyte and I clicked the Add button, the dropdown options should not be displayed.

Test Condition: User is in [https://app.cualia.io/org/gnxnzhnh57j/analyzer/g19zft1ylf/tests/qual|https://app.cualia.io/org/gnxnzhnh57j/analyzer/g19zft1ylf/tests/qual] User is QA Owner Steps to replicate: # In Tests Quant, click Add a Test button # Input a unique or new Analyte Name e.g. TAN000000 # Click Add: [Name of Analyte] Result: Dropdown options were displayed Screen recording: [https://jam.dev/c/3b1a2cd5-8f25-4990-86a2-dfbc35f3d928|https://jam.dev/c/3b1a2cd5-8f25-4990-86a2-dfbc35f3d928|smart-link] Note: This is also applicable to QL

Fixed the status display in Experiment Result to show In Progress instead of Not Started.

MV-RPRT | Correct status should be displayed in Experiment Result

*Environment:* Dev *Test Condition:* int1: Failed int2: Incomplete int3: Not Started User is in: [https://dev.cualia.io/org/Tl2p0u9W/mv/syreqq5kxm/report/preview/experiments?testId=3yb4qnmspr5&expKey=interference|https://dev.cualia.io/org/Tl2p0u9W/mv/syreqq5kxm/report/preview/experiments?testId=3yb4qnmspr5&expKey=interference] In Experiment Result, status displayed is Not Started wherein it should be In Progress

Updated the label from "Result" to "Carryover SD" in MV Carryover Experiment results for clarity.

MV-EXPCarry ADT | Update Label in MV Carryover SD Mode Experiment Results

The current display of results in the MV Carryover (SD Mode) Experiment section shows "Result" as the label for the bottom results. To better align with the terminology used in this experiment, this label should be changed to "Carryover SD." !Screenshot 2024-11-07 at 10.19.58 AM.png|width=1123,height=87,alt="Screenshot 2024-11-07 at 10.19.58 AM.png"! h2. User Flow: # The user navigates to the MV Carryover Experiment. # The user changes the experiment mode to Standard Deviation (SD). # They observe the updated label "Carryover SD" where "Result" previously displayed.

Corrected table rows to remove status icons where data was missing, resolving confusion in experiment reports.

MV-RPRT QNT BG | Table Rows Without Data Display Icons and Sticky Results not Updating

In the experiment report, table rows without data are incorrectly displaying status icons (e.g., checkmarks or X marks). Rows with empty data should not display any icons, as this creates confusion and misrepresents the results. More issues found by developer(see comments). *Steps to Reproduce:* # Navigate to the *Method Verification Report* section. # Generate a report for a quantitative experiment. # Observe the *tables* in the report where some rows do not have data in the "Source" or "Actual" columns. # Notice that these rows still display icons in the status column. # Results greater than or equal to 3 will just show as a negative sign (-). # Results section doesn’t stick. # There are icons even if there is no data in the cells.

Fixed missing reference values in the SMQ Precision report PDF for samples.

MV-EXPPrec BG SMQ | Missing Reference Value in SMQ Precision Report PDF

In the *SMQ Precision* experiment report PDF, the *Reference Value* field is blank in the *Samples* section. This field should display the correct reference value associated with each sample as defined in the experiment setup. !3.png|width=692,height=612,alt="3.png"! h2. *Steps to Reproduce:* # Navigate to an *SMQ Precision* experiment. # Generate the experiment report by clicking on *Export PDF*. # Check the *Reference Value* column in the *Samples* section of the PDF.

Result Types: Qualitative and Quantitative MV Experiments: Method Comparison and Trueness A double click action on the green checkmark (eligible samples only) will set the result to pass regardless of the Error Index. This facilitates many tests where values in specific ranges do not follow the requirements around other ranges. The green ✅  checkmark will turn a lighter shade of green to indicate that it is force-passed without a strong negative aesthetic.

❗️MV-EXP ADT | Implement Force Passing of Results in MV-EXPMC QNT QL and MV-EXPTrueness QNT and QL

We will add forcepassing of results. This is because we’re doing a test where the allowable error is that actual and reference that are both below 100 are a pass. This makes using TEa’s awkward. As a user we want to allow the user to force pass a sample. Modify the existing column with the check (✅) and cross (❌) icons in the results table to support Force Pass functionality, allowing users to mark specific samples as "always pass" under defined conditions. [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-163421&t=fRFYuXpSzyddcMjH-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-163421&t=fRFYuXpSzyddcMjH-4|smart-embed] See the last column of row 3 in the Figma above. h2. *Implementation:* # *Update Existing Column*: #* Modify the existing check (✅) and cross (❌) icons in the last column of the results table to include Force Pass functionality. # *Edit Mode Behavior*: #* Feature is only accessible in *Edit Mode* (not in read-only mode). #* Mouse changes to a pointer cursor when hovering over the icons. #* Tooltip on hover in Edit Mode: #** Default state: _“Force Pass: double click the icon to set this sample to always pass.”_ #** When Force Passed: _“Sample is set to Force Pass when eligible. Double click to remove.”_ # *Non-Edit Mode Behavior*: #* Tooltip on hover: _“Sample has been set to Force Pass.”_ # *Double-Click Functionality*: #* *Force Pass Action*: #** On double-click of a ❌ or ✅: #*** Icon opacity changes to *65%*. #*** Sample is set to *always pass*, regardless of the error index (-1 to 1) or edits. #*** Force Pass persists even if the sample becomes ineligible but will reactivate if eligibility is restored. #* *Remove Force Pass*: #** On double-click of a Force Passed sample, the Force Pass state is removed, and the icon reverts to its original state. # *Eligibility Handling*: #* Force Passed samples are not included in calculations if they become inel

When in an MV, the Analyzer name in left side navigation now has a button to return to the analyzer.

MV-EXP | Add "Go to Analyzer" Icon Button

Add an icon button in the MV navigation that allows users to open the associated analyzer in a new window for quick access. !2024-12-05 140203 Microsoft Edge.png|width=530,height=690,alt="2024-12-05 140203 Microsoft Edge.png"! h2. *User Flow* # User navigates to the MV section. # The "Go to Analyzer" icon button is visible in the MV navigation bar. # User clicks the button. # The analyzer details page opens in a new browser window or tab.

Fixed a bug where a deleted tests would still show up in the analyzer for a few minutes.

TSTS ADT | Ghost of Deleted or Edited Test in Analyzer Test List

Fix the issue where deleted or edited tests briefly appear ("ghost") in the analyzer test list after deletion or editing. Ensure the redirect only occurs after the API call is successfully completed. When a test is deleted or edited, the user is redirected back to the analyzer test list. However, the deleted or edited test briefly appears in the list before the update is reflected, causing confusion. This occurs because the redirect happens before the API call completes. h2. *Steps to Reproduce* # Navigate to the analyzer test list. # Delete or edit a test. # Observe the brief presence ("ghost") of the deleted or edited test in the list after redirection.

In the MV Method Comparison and Trueness experiment table headers, the “Source” column header was renamed to “Comment”. This was to help provide flexibility to put whatever supplementary information is required such as source, date, operator or general commentary.

❗️MV-EXP ADT MV-EXPMC MV-EXPTrueness QL QNT | Update Column Header Text in Experiments and Exported Files

Update the column header text from “Source” to “Comment” across the following areas: # Method Comparison (MC) Experiments. # Exported XLSX, CSV, and PDF files. The column header labeled as “Source” needs to be changed to “Comment” for consistency and clarity. This change should apply to all relevant sections, including both the experiment UI and exported files. The updates will apply to both Quantitative (QNT) and Semi-Quantitative (QL) methods, specifically for Method Comparison (MC) and Trueness experiments. h2. *Implementation Details:* # *UI Changes:* #* Locate the “Source” column in the experiment table within the MC experiments. #* Update the header text to “Comment.” !Screenshot 2024-12-05 at 1.55.10 PM.png|width=1586,height=767,alt="Screenshot 2024-12-05 at 1.55.10 PM.png"! # *Export Changes:* #* Ensure the “Source” column in exported XLSX, CSV, and PDF files reflects the new header text “Comment.” #* Confirm this change applies to all relevant exportable formats. [^MCV_semiQuant.xlsx] # *Affected Experiments:* #* QL QNT Method Comparison (MC). #* QL QNT Trueness experiments.

Whenever you start a new MV without a template, the defaults will be set to the reports: Header Title: Analyzer Information Header Subtitle: Department Name Footer Line 1: Evaluator Footer Line 2: Date the MV Started

MV-RPRT ADT | Default Report Values on MV Creation

Set default values for report headers and footers upon MV creation. These values may be hardcoded to ensure consistency and ease of implementation. When a new MV is created, default values for the report headers and footers should automatically populate. This will save time and ensure uniformity across reports. The default values may be hardcoded but should pull dynamically from the relevant properties. !2024-12-05 134534 Microsoft Edge.png|width=1219,height=350,alt="2024-12-05 134534 Microsoft Edge.png"! h2. *Default Values* # *Header Title:* {{{analyzer.name} {analyzer.identifier} MV}} # *Header Subtitle:* {{{department.name}}} # *Footer Line 1:* {{Evaluated by: {mv.createName}}} # *Footer Line 2:* {{Date Started: {mv.createdDate in YYYY-MM-DD format}}} h2. *Implementation Details* # *Default Population Logic:* #* Populate the default values during MV creation. #* Values may be hardcoded and should dynamically map to the relevant fields. # *Formatting Requirements:* #* Ensure the date format is strictly {{YYYY-MM-DD}}. #* Use dynamic placeholders to pull values from the respective properties: #** {{{analyzer.name}}} and {{{analyzer.identifier}}} from the analyzer. #** {{{department.name}}} from the department associated with the MV. #** {{{mv.createName}}} from the creator's name. #** {{{mv.createdDate}}} from the creation timestamp. # *UI/UX Considerations:* #* Display these values in their respective fields on the report preview or editor. #* Allow users to manually edit these values if needed after creation.

Share and invitation emails will no longer be case sensitive. This was causing invitations to not be sent.

GLBL RLS DV | Case Sensitivity Bug in Emails for Shared Invites and Authentication

Fix the issue where email addresses in shared invites, invite emails, and authentication registration workflows are treated as case-sensitive, causing mismatches and access issues. !2024-12-05 115446 Microsoft Edge (1).png|width=600,height=632,alt="2024-12-05 115446 Microsoft Edge (1).png"! Emails currently require an *exact match*, including case sensitivity, when inviting, sharing, or authenticating. For example: * If an invite is sent to {{Calvin@cualia.io}}, users cannot access the shared resource with {{calvin@cualia.io}}. This behavior is inconsistent with standard email handling, where addresses are typically case-insensitive. h2. *Steps to Reproduce* # Send an invite to a user with an email address using uppercase letters (e.g., {{Calvin@cualia.io}}). # Attempt to log in or authenticate using the lowercase version of the email (e.g., {{calvin@cualia.io}}). # Observe that access is denied due to a mismatch. h2. *Implementation Details* # *Normalization Fix*: #* Normalize email addresses (convert to lowercase) before storing them in the database. # *Affected Workflows*: #* Shared invites #* Invite emails #* Authentication registration emails # *Database Update*: #* Normalize existing email records in the database, if feasible. # *Validation*: #* Apply input sanitization to remove unnecessary whitespaces.

In MV Previews, selecting the export to PDF button will download the PDF with a set naming convention to match what is being viewed on the PDF preview.

MV-RPRT ADT | Dynamic PDF Export Filename Based on Context

Ensure PDF exports are named dynamically based on the context of selected tests and experiments, providing meaningful and user-friendly filenames. The current export filenames do not reflect the specific content of the exported report. This task standardizes filenames for exports, improving clarity and usability by reflecting the selected analyzer, tests, and experiments. h2. *Filename Rules:* # *All Tests and Experiments:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - All Experiments}} # *One Test’s Experiments:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - {test.nameAbbrev}}} # *One Experiment from All Tests:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - {experiment.name}}} # *One Test and One Experiment:* #* *Filename:* {{MV {analyzer.nameAbbrev} {analyzer.identifier} - {test.nameAbbrev} {experiment.name}}} h2. *Implementation Details* # *Dynamic Filename Logic:* #* Implement a function to determine the appropriate filename format based on the selection context. #* Retrieve the necessary data from the selected analyzer, test, and experiment. # *Integration Points:* #* Update the export process to include the dynamic filename generation before saving the PDF. # *Validation and Fallbacks:* #* Ensure all variables ({{{analyzer.nameAbbrev}}}, {{{analyzer.identifier}}}, {{{test.nameAbbrev}}}, {{{experiment.name}}}) are properly populated. #* If any required data is missing, use a generic fallback filename, e.g., {{MV Export}}. # *Edge Cases:* #* Handle scenarios with incomplete selections or empty data gracefully, ensuring no errors in export functionality.

The test’s units were added to each header of the PDF exports as a reference for viewers.

MV-RPRT ADT | Add Units to All Experiment PDF Export Files

Ensure that units associated with a test are included in the exported PDF reports, enhancing clarity and alignment with experiment data. Currently, experiment exports in PDF format do not display the test units. This ticket aims to append the corresponding units (if they exist) to the right side of the *Experiment Design Title* for all exported PDF reports. !2024-12-05 130746 Microsoft Edge.png|width=867,height=204,alt="2024-12-05 130746 Microsoft Edge.png"! h2. *Implementation Details:* # *Condition:* #* Check if the test has units associated with it. #* If units exist, append them to the *Experiment Design Title*. #* If no units exist, the title remains unchanged. # *Placement:* #* The units should be appended on the right side of the *Experiment Design Title*, separated by a space or parentheses (e.g., "Experiment Design Title (mg/dL)"). # *PDF Export Update:* #* Update the PDF generation logic to dynamically include units in the title section of the exported report. #* Ensure proper formatting to maintain readability and consistency. h2. *User Flow:* # User initiates the export of an experiment in PDF format. # The system generates the PDF, dynamically appending units (if applicable) to the *Experiment Design Title*. # The exported PDF is downloaded or previewed, displaying the updated title with units.

When creating or editing a test, the analyte selection dropdown is now in alphabetical order.

TSTS ADT |  Analyte Dropdown Alphabetical Order on Test Creation

Ensure the Analyte dropdown in the Test Creation form is displayed in alphabetical order to improve usability and efficiency. Currently, the Analyte dropdown in the Test Creation form may not be sorted, making it difficult for users to locate specific analytes quickly. This task ensures that the list is presented in alphabetical order by default. !2024-12-05 140442 Microsoft Edge.png|width=523,height=434,alt="2024-12-05 140442 Microsoft Edge.png"!

Fixed an issue where the linearity chart was missing in PDF exports.

❗️MV-RPRT ADT BG | Export Missing the Graph

Fix the issue where the graph is missing from the exported files in the MV-EXPLin experiment results. Currently, when users export the results from the MV-EXPLin (Linear Regression) experiment, the graph section is not included in the export. This bug affects the ability to provide a complete report, as the graph is a critical part of the experiment's results. h2. *Steps to Reproduce* # Navigate to an MV-EXPLin experiment with results. # Ensure that the graph is displayed on the results page. # Click on the "Export" button. # Open the exported file (e.g., PDF or Excel). # Observe that the graph is missing from the export.

Add and Edit Department action buttons have been changed to “Add Department” and “Save.”

ORGS DEPS ADT | Update Department Edit CTA Buttons

Improve clarity and user experience by updating the CTA buttons in the Department section to reflect the action being performed (e.g., adding or editing a department). Currently, the CTA button for editing a department only displays "Edit," regardless of the action context. This ticket aims to update the button text to provide clear labels based on the user's current action: * *"Cancel"* and *"Add Department"* when adding a new department. * *"Save"* when editing an existing department. h2. *Implementation Details:* # *Adding a Department:* #* Display two buttons: #** *"Cancel"* - Cancels the action and reverts to the default Department page state. #** *"Add Department"* - Confirms the addition of a new department. # *Editing a Department:* #* Replace the current "Edit" button with a single *"Save"* button to save changes. # *General Behavior:* #* Ensure proper state management for the buttons to reflect the correct context (adding or editing). #* Provide visual feedback upon button click (e.g., loading indicator, state change). #* Retain accessibility features for all buttons. h2. *User Flow:* # User navigates to the Department section. # Clicks *"Add Department"* or selects a department to edit: #* If adding a department: #** *"Cancel"* and *"Add Department"* buttons are displayed. #* If editing a department: #** *"Save"* button is displayed. # User completes the action or cancels it, returning to the default Department page view.

A fix was made where the MV sharing mechanism for email input would stay within the text box even after submission.

MV-RPRT ADT BG | MV Sharing Email Should Disappear on Submit

Ensure that after the user submits an email address for sharing, the input field and any associated UI elements (e.g., email validation messages) disappear, providing clear feedback that the action was successful. Currently, when an email is submitted for sharing an MV, the input field remains visible, which could cause confusion about whether the email was sent successfully. !2024-12-05 114441 Microsoft Edge (1).gif|width=764,height=566,alt="2024-12-05 114441 Microsoft Edge (1).gif"! h2. *Steps to Replicate:* # User navigates to the *MV Sharing* page. # Enters an email address in the input field. # Clicks the *Submit* button. # Email still shown in email field. h2. *Implementation Details:* * After the "Submit" button is clicked and the email is successfully sent: ** Hide the email input field and associated elements. ** Display a success message confirming the email was sent. ** Ensure proper error handling if the submission fails (retain the input field in this case with an error message).

A return to MV button was added to the reports page to make it easier to return to the workspace.

MV-RPRT ADT | Go To MV Button in Report Section

Enable users to navigate back to the MV section from the Report section easily, ensuring seamless interaction for both standard and shared modes. Add a "Go To MV" button in the Report section. The button's behavior should adapt to the linking protocol based on whether the MV is in *Standard Mode* or *Shared Mode*. !Screenshot 2024-12-07 at 2.09.09 PM.png|width=253,height=461,alt="Screenshot 2024-12-07 at 2.09.09 PM.png"! h2. *Implementation Details* * *Button Placement*: Add the button to the header (or other prominent area) of the Report section for high visibility. * *Button Behavior*: ** *Standard Mode*: Link directly to the corresponding MV details page. ** *Shared Mode*: Follow the shared protocol to navigate to the appropriate shared MV details page. * *UI/UX Requirements*: ** The button text: "Go to MV". ** Design and style should align with existing navigation buttons. * *Additional Considerations*: ** Ensure the button is disabled if the navigation path cannot be determined. ** Display an appropriate error message if navigation fails. h2. *User Flow* # User is in the Report section. # User clicks on the "Go to MV" button. # Depending on the mode: #* *Standard Mode*: Redirect to the specific MV details page. #* *Shared Mode*: Redirect to the shared MV view, based on the shared protocol.

Result Types: Quantitative MV Experiments: Method Comparison In Quantitative Method Comparisons, an option to use R-Squared Linear Regression values as the acceptance criteria has been added. Use the Experiment Settings to switch to R-Squared regression as the acceptance criteria. You will be able to set a min. R-Squared value required to meet experiment requirements.

❗️MV-EXPMC ADT QNT | Linear Regression Acceptance Criteria

We are going to add a new acceptance criteria to Quantitative Method Comparison [https://www.notion.so/cualia/DV-TSK1203-2024-12-04-UIX-Sitdown-with-Marianne-1521b48e658180989f81f92b5eb000fe?pvs=4#1521b48e6581807490bdfb9d81cbb7b3|https://www.notion.so/cualia/DV-TSK1203-2024-12-04-UIX-Sitdown-with-Marianne-1521b48e658180989f81f92b5eb000fe?pvs=4#1521b48e6581807490bdfb9d81cbb7b3] h2. Important Note * Calculations are the same.The only difference is that we only base pass/fail on if the calculated R-Squared ≥ Acceptance Criteria R-Squared. This is already calculated in our math. * MC ONLY. NOT MV-EXPTRUENESS. h2. General Changes and Notes * *Line Chart*: Remove all TEa Lines. Only persist the linear regression line. ** Removed in PDF chart as well * *Remove Error Index Chart* ** Removed in PDF export as well * R-Squared results should have max 3 decimals h2. *Experiment Settings*: * New Regression Mode option * *Min. R-Squared field*: Same as the one on MV-EXPLin [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23603-206737&t=WxKwVPiPNrlJHhvz-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23603-206737&t=WxKwVPiPNrlJHhvz-4|smart-link] ** *Tooltip Adjustment on this field*: “R-Squared coefficient from calculating Linear Regression. Values above 9.95 are often deemed acceptable.” !2024-12-05 151706 Microsoft Edge.png|width=274,height=122,alt="2024-12-05 151706 Microsoft Edge.png"! h2. Results Table * Removed Bias and Error Index Column (there is no pass fail of individual results) [https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-150091&t=fRFYuXpSzyddcMjH-4|https://www.figma.com/design/4RAzhHq6SOf5hYY2aeGKi5/Cualia-Application-UI---main?node-id=23601-150091&t=fRFYuXpSzyddcMjH-4|smart-link] h2. Results Section * Results Section should match the [Figma|https://www.notion.so/DV-TSK1203-2024-12-04-UIX-Sitdown-with-Marianne-1521b48e658

In the analyzer’s list of quant, qual and semi-quantitative tests, the alignment of the name was fixed to be more readable.

MV EXP QL SMQ BG | The Name label should be properly aligned

Test condition: User is in [https://cualia-svelte-git-cmv-278-smq-cualia.vercel.app/org/Tl2p0u9W/analyzer/g4vibfj2n1/tests/qual|https://cualia-svelte-git-cmv-278-smq-cualia.vercel.app/org/Tl2p0u9W/analyzer/g4vibfj2n1/tests/qual] Test account: QA Owner Notes: Kindly properly align or align center the “Name” label Screen recording: [https://jam.dev/c/bf939ec5-e16d-4982-968a-a29e69179cf1|https://jam.dev/c/bf939ec5-e16d-4982-968a-a29e69179cf1|smart-link]

Added result options for SMQ tests created after the Method Validation.

ANZ TST SMQ BG | SMQ test added after MV is created should include Result Options

*To Replicate* # Use an analyzer to create an MV # In the organization's analyzer, add a SMQ test with result options # In the MV, load up the new SMQ test. Result options will not be available. !2024-12-03_083644_Microsoft_Edge.png|width=3406,height=1242,alt="2024-12-03_083644_Microsoft_Edge.png"! [https://discord.com/channels/965551040890028062/1313303425802440775/1313303431984709642|https://discord.com/channels/965551040890028062/1313303425802440775/1313303431984709642|smart-link]

Fixed search issue for verifications using File Name, Evaluator, and Analyzer ID.

MV BG | Unable to search for verification using File Name, Evaluator, and Analyzer ID

Steps to replicate: # Login to the app. # Navigate to Verifications. # Search for a Verification using the following: ## File Name ## Evaluator ## Analyzer ID !Searchbug.PNG|width=1179,height=491,alt="Searchbug.PNG"! [https://discord.com/channels/965551040890028062/1112699023552421938/1313315079646875699|https://discord.com/channels/965551040890028062/1112699023552421938/1313315079646875699|smart-link]

[Verifications] MV Experiment Printing

[Verifications] MV Experiment Printing

Place tooltips on each of the Performance Characteristics fields

Place tooltips on each of the Performance Characteristics fields

!Screenshot 2024-05-18 at 1.44.13 PM.png|width=1338,height=603,alt="Screenshot 2024-05-18 at 1.44.13 PM.png"!

MV - Update Verification Tables

MV - Update Verification Tables

Analyzer verifications - the last column doesn’t make sense. It should be last updated? Also is it consistent with !20240602-123858 - Microsoft Edge - Cualia.png|width=751,height=598,alt="20240602-123858 - Microsoft Edge - Cualia.png"!

LBS | Add, Edit, and Delete Laboratory

LBS | Add, Edit, and Delete Laboratory

This is the Epic for all tasks, bugs, and user stories related to the Adding, Editing, and Deleting of Laboratories.

20240516 Organization Audit Tickets p01

20240516 Organization Audit Tickets p01

These are the tickets associated with the 20240516 Organization Audit. Part 1 [http://app.noota.io/share-transcribe/N5kY4FFUsdTMMJmewZzUtoWZ1QFSEFD0TLdDOuo3aq5kMBRkT|http://app.noota.io/share-transcribe/N5kY4FFUsdTMMJmewZzUtoWZ1QFSEFD0TLdDOuo3aq5kMBRkT|smart-link] Part 2 [http://app.noota.io/share-transcribe/np1a0k2RIRjWzdmVLBXdwU1TzEzcZFU0NJJUbuMzaq5kMBRkT|http://app.noota.io/share-transcribe/np1a0k2RIRjWzdmVLBXdwU1TzEzcZFU0NJJUbuMzaq5kMBRkT|smart-link]

ORG - Organization Plan Features

ORG - Organization Plan Features

MV | Implementation of Sharing Functionality

MV | Implementation of Sharing Functionality

This is an epic that will handle all items and bugs related to the MV sharing capabilities of the app.

[Verifications] Test Experiment Summaries

[Verifications] Test Experiment Summaries

This is an epic that handles features and bugs related to Experiment Summaries.

ADT | 202407 Dev UX Audit

ADT | 202407 Dev UX Audit

h1. Context Calvin performed an audit of the app in preparation for launch in July 31. This Epic includes all the required changes prior to going live on July 31. Priorities are all that has the {{❗️}} mark. The audit is composed of 3 parts. They are all documented in this [notion page|https://www.notion.so/cualia/2024-07-DV-UX-Audit-0baa84b241ec498fa5bc198d37582cf4] together with the recording. All the parts of the audit are added in this single epic, to differentiate which ticket belongs to which part, a label has been added to each ticket. ||*Part*||*Label*|| |Part 1 Auth Org SomeMVSettings|{{202407-app-audit-p1}}| |Part 2 Quant MV Experiments|{{202407-app-audit-p2}}| |Part 3 Qual MV Experiments Reports Printing Sharing|{{202407-app-audit-p3}}|

Update deprecated sass import to sass use

Update deprecated sass import to sass use