Release Notes

Release v2.1.0, available on November 19, 2019

What’s New

Locks:

• Admins can now set up automated locks for Orders and Tests based on any filter criteria
• Users are now able to lock a Log
• Users are now able to lock a Batch

Custom IDs:

• Users can now configure Custom IDs for Batches
• Introduced new Custom ID options for Samples:
  • Sample Custom IDs can now format date by the week of the year
  • Sample Custom IDs can now include only the last digit of the year
  • Sample Custom IDs can now have their number start at 1 and reset each week (Strongly discouraged. Read more...)
  • Sample Custom IDs can now have their number start at 1 prefixed by their Order ID (Strongly discouraged. Read more...)
• Introduced new Custom IDs option for Orders:
  • Order Custom IDs can now have Customer specific information prefixed

Email Alerts:

• Admins are now able to configure email alerts for Tests
• The alerts can be triggered when they meet a specific filter criteria
• The email will be sent to the specified recipients on the Order

General Emailing:

• Users are now able to see the status of emails that have been sent out by QBench
  • This provides improved visibility for when an email is sent, bounced, blocked, etc.

Customer Portal:

• Admins are now able to configure Required Fields and Default Values for Customer Portal users
• New or Unread Orders are now bolded in the Order List Page
• Now enforcing Customer Portal users to not use their previous passwords

QoL / Bug Fixes

• Fixed UI bug on Test List Page where the Order Status doesn’t properly update when it changes
• Fixed UI bug in the Batch History tab where it was improperly trying to show a status
• Fixed UI bug where Entity ID tiles would break to a new line on smaller screens
• Fixed permission issue where a user with read-only Sample access could upload attachments
• Fixed bug where updating Field and Data Type Settings did not persist when making rapid changes
• Fixed bug where users were not able to load a QMS Issue Detail Page when it is in the “CLOSED” state
• Users are now able to filter Assays by Team
• Introduced a setting where you can set a “default” timezone that gets used when utilizing Custom IDs and a timezone is not present (e.g. making calls to the API)
• Expanding on accessible fields of the “Entity Relation” additional field type in Template Configurations