A maintenance release contains fixes for issues affecting customer Vaults in production environments. Maintenance releases can occasionally include enhancements, for example, a time-sensitive regulatory requirement. This page covers maintenance releases deployed to General Release Vaults only. We communicate 24 hours prior to a maintenance release. There may be a short service disruption during deployment.
This list only covers fixes for issues that impact 24R1 General Release versions of Safety Vaults. The list of fixed issues is subject to change until the release occurs. When we identify issues to fix in a maintenance release, we attempt to get them into the earliest release possible. Sometimes, we target a specific release but are not able to deliver a fix early enough for full testing. In situations like this, we postpone the fix for a later release and strike out the description in this list.
We number maintenance releases for Safety by appending the number of the Safety-specific maintenance release to the General Release number. The most recent Vault General Release is 24R1.0, so our maintenance releases for this version are 24R1.0.2, 24R1.0.3, and so on.
Vault frequently delivers Platform maintenance releases. Safety deploys these Platform maintenance releases at a later date, along with any required fixes to Safety. For details on Platform fixes in these maintenance releases, see 24R1 Maintenance Releases.
Last Updated: May 16, 2024
May 15, 2024
Release Number: 24R1.0.4 | Build Number: 226
| Description | Issue No. |
|---|---|
| Vault cannot generate or validate custom E2B Transmission formats that use SDK. | SAF-58847 |
May 14, 2024
Release Number: 24R1.0.3 | Build Number: 223
| Description | Issue No. |
|---|---|
| For Study Cases with non-Study Products, when the Case enters the Revision state, Vault clears the value in the Case Blinded field of the Details section. | SAF-55749 |
| When generating FDA MedWatch 3500A forms, if the Rank 1 Case Product is a Device and the Product Registration field of the highest ranked non-Device Product is blank, Vault does not populate the NDA # field in Section G of the form. | SAF-56220 |
| When creating a Follow-up Case for a Study Case that was kept blinded through the Case workflow, Vault sets the Case Blinded field to No on the Follow-up Case. | SAF-56783 |
| If Smart MedDRA Coding is enabled, in some instances importing a high volume of Inbox Items causes the Number of Requests in Current Month counter on the MedDRA Coding Settings record to lock and E2B import fails. The Number of Requests in Current Month counter has been turned off and will be fixed in a future release. | SAF-56801 |
| When Automated Case Promotion is configured with the Override merge method, if an Inbox Item has a matching MRN with a Case, but the Worldwide UID does not match, Vault creates a new Case and changes the Worldwide UID on the original Case. | SAF-56018, SAF-57164 |
| Vault does not run Validation Criteria with a Rule Formula Format of Case Data or Case Data - Expression when the Agency field is blank. | SAF-57779 |
May 7, 2024
Release Number: 24R1.0.2 | Build Number: 212
| Description | Issue No. |
|---|---|
| When the Safety-EDC Vault Connection is enabled, after creating a serious adverse event (SAE) that includes multiple adverse events (AEs) in a CDMS Vault, when Vault generates an Inbox Item in the connected Safety Vault, Vault does not assign Rank 1 to the primary AE. | SAF-54230 |
| When the Safety-EDC Vault Connection is enabled, if a user in a CDMS Vault deletes SAE subject data that was previously linked on an Inbox Item in a Safety Vault, Vault maps the deleted subject data when creating an Inbox Item for a Follow-up. | SAF-55733 |