QBench August 3, 2026 Product Release Notes

This release gives you finer control over who hears from QBench and who can move your work forward: per-role email settings in the Customer Portal, API-only status transitions for your integrations, and exact-ID search for Batch building, plus a significant speedup on Dynamic Worksheet saves.

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!)

• Email Permissions by Customer Portal Role: Choose exactly which emails each Customer Portal role receives. See details below.
• API-Only Status Transitions: Reserve a Status Workflow transition for your integrations without opening it to every user. See details below.
• Exact-ID Search When Adding Tests to a Batch: Search Tests by exact ID so scanners and ID lookups return only the Test you meant. See details below.

Customer Portal

• Email Permissions by Customer Portal Role: Decide which notifications each Customer Portal role receives instead of choosing between all Order emails or none.
  • Configure emails per role in Settings > Customer Portal > Roles & Permissions, covering Order Published, Report Published, Order Request Converted, Sample Received, Quotation Sent, Invoice Sent, and Invoice Paid.
  • Email options follow the role's Access Policy, so a role can only receive emails for Records it has Read access to.
  • Your Portal users keep their own Email Preferences, so they can still opt out of anything their role enables.
  • Existing roles carry over automatically from their current "Assign Portal User's Email to All Orders" setting, so nothing changes until you adjust it.

Status Workflows (Beta)

• API-Only Status Transitions: Restrict a transition so only your integration can run it. "Transition allowed by" now offers an API-only option alongside specific Users, Teams, and Anyone.
  • Previously, letting an integration drive a transition meant opening it to Anyone, which also exposed it to every user in your instance. The API-only option closes that gap.
  • Only an authenticated API client with Test update scope can execute the transition. It is unavailable to users in the Test Details dropdown or in bulk actions. A LIMS admin can still override from the UI when needed.
  • Every API-driven transition is recorded in history and attributed to the API client that made it, so your audit trail stays complete.
  • This unlocks fully automated post-publication corrections: your integration can unlock a set of Tests, update fields, attach a regenerated Report, and re-lock them, with the lock and unlock transitions never exposed to users.

🧪 Status Workflows is in beta. Contact your Account Manager to turn it on in your instance.

Batches

• Exact-ID Search When Adding Tests to a Batch: Turn on "Search by exact IDs only" when adding Tests to a Batch to match on Test ID alone, mirroring the option already available on the Samples tab. The setting is off by default and the preference is saved per user, so it stays on for you once selected.

‍

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

What did the thermometer say to the graduated cylinder?‍

You may have graduated, but I have many degrees.

‍

v2.112