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 24R2 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 24R2.0, so our maintenance releases for this version are 24R2.0.2, 24R2.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 24R2 Maintenance Releases.
Last Updated: September 6, 2024
September 10, 2024
Release Number: 24R2.0.5 | Build Number: 197
| Description | Issue No. |
|---|---|
| After receiving an ACK response to a gateway submission, Vault does not populate the ACK.B.r.2 Local Report Number in the Destination Case ID field of the associated Transmission record. | SAF-60483 |
| This update optimizes code for syncing global and localized follow-up cases. This will be available for configuration in a future release. | SAF-61855 |
| This update optimizes code for syncing global and localized case narratives. This will be available for configuration in a future release. | SAF-61873 |
| Transmission Output Templates do not generate multiple submissions to the same agency or multiple distributions to the same partner. If the due date is not less than the rule's Due Date, Vault ignores the applicable Transmission Profile. | SAF-62361 |
| This update optimizes the Vault Safety reporting rule engine in preparation for case reportability classifications. This will be available for configuration in a future release. | SAF-62662 |
August 27, 2024
Release Number: 24R2.0.4 | Build Number: 186
| Description | Issue No. |
|---|---|
| In some cases, users receive an error when merging to an in-flight Case if the Inbox Items were created using the Safety-EDC Vault Connection. | SAF-62113 |
| In Vaults with the Clinical Trials: Isolate Blinded Product Information enabled, some entry actions may not execute on Study Cases and Vault displays a system error message. | SAF-63012 |
August 18, 2024
Release Number: 24R2.0.3 | Build Number: 181
| Description | Issue No. |
|---|---|
| In some situations, when a PMDA localized case does not yet exist on the global case but validations are run, customers may experience an unexpected validation criteria failure for PMDA submittable cases. | SAF-63392 |
August 16, 2024
Release Number: 24R2.0.2 | Build Number: 179
| Description | Issue No. |
|---|---|
| Following reporting rule evaluation on Follow-up Cases with multiple PMDA cross reporting obligations, Vault displays an error message and prevents some actions, such as generating Transmissions or calculating due dates. | SAF-63127 |