QBench August 31, 2026 Product Release Notes

This release takes the friction out of multi-Assay Orders. Filter the Tests table on the Order Details page to a single Assay and the columns snap to exactly the fields that Assay needs, so your team enters the right data the first time. Rich text template libraries are now fully searchable, and v2 API writes support idempotency keys so your integrations can retry with confidence.

Are you a QBench customer with ideas for new features? We’d love to hear them. Use the "Submit Feedback" link in the Help menu to submit your ideas and vote on feature requests. The requests with the most votes get considered first in our roadmap planning.

‍

Customer Requests (You asked, we delivered!)

• Enhanced Sample Search in the Customer Portal: Search by the Sample fields your Customers actually use and get back matching Samples. See details below.
• Assay Field Screens on the Order Details Page: Filter an Order's Tests to one Assay and enter data against that Assay's fields. See details below.
• Searchable Rich Text Template Picker: Find a template by name instead of scrolling. See details below.

Order Details

Assay Field Screens on the Order Details Page: If you run several Assay types on one Order, you can now enter data against the right fields for each. Filter the Tests table to a single Assay and the columns switch to that Assay's field screen, falling back to your Customer field screen or default configuration. Required fields are enforced on save, and Tests added while filtered pick up that Assay's default values. Switching Assays with unsaved edits prompts you to save or discard. The unfiltered view is unchanged.

🧪 Contact your account manager to have this enabled for your lab.

Rich Text Fields

Searchable Rich Text Template Picker: Rich text fields now open a searchable picker instead of a scrolling list. Type part of a template's name to filter, preview it, and insert it exactly as before.

API v2

Idempotency Keys on v2 Writes: v2 writes now accept an Idempotency-Key header. If a request times out and your integration retries it with the same key, QBench replays the original response instead of applying the change twice, so retries can't create duplicate Records. Keys are scoped to your lab and API client and expire after 24 hours. Reusing a key with a different body is rejected. Requests without the header behave exactly as they do today.

🧪 Contact your account manager to have this enabled for your lab.

‍

A special treat for those who read all the way here:

What do you call a tooth in a glass of water?
‍A one molar solution.

‍

v2.114