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 25R2 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 Veeva Vault General Release is 25R2.0, so our maintenance releases for this version are 25R2.0.2, 25R2.0.3, and so on.
Veeva 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 25R2 Maintenance Releases.
Last Updated: August 31, 2025
September 3, 2025
Release Number: 25R2.0.7 | Build Number: TBD | Platform: TBD
| Description | Issue No. |
|---|---|
| In Vaults with the "Use Product Coded for HC E2B(R2)" Submission and Distribution Settings application setting enabled, when generating Health Canada E2B(R2) files and populating coded Product names in the B.4.k.2.1 data element, for values that include a substance name, Vault now excludes the substance name upon export. | SAF-84087 |
| After running the Sync Global Narrative to Local Narrative action, in addition to updating the local narrative document with the most-recent version from the related global or domestic Case, Vault now also updates the narrative language and narrative preview on the Localized Case. | SAF-85140 |
| Due to a known issue with the "Enable Advanced Product Coding Verification" Intake Settings application setting, Vault attempts to complete product coding on Study Products, which should not occur, and in some instances, this causes Case Product Registration generation to fail on Japan domestic Cases. | SAF-84509 |
| On Inbox Items generated through the Intake Inbox Item Vault API, when Vault cannot auto-code products, it does not import the related IMDRF codes. | SAF-84830 |
| In Vaults configured to base clinical trial study Case expectedness on the Onset date of Case Adverse Events or configured with the Recalculate Post-Market Expectedness on Follow-up application setting not enabled, when processing follow-up information where the Seriousness on an Adverse Event is blank on both the initial Case and the follow-up Inbox Item, Vault reevaluates expectedness although it should not. | SAF-85138 |
| After Admins run the Manage Sponsor Certificate action on an AS2 Connection, Vault displays an error and does not create and attach a new sponsor certificate. | SAF-85158 |
August 26, 2025
Release Number: 25R2.0.6 | Build Number: 236 | Platform: 10519
| Description | Issue No. |
|---|---|
| This update optimizes code for deleting Case Products and Case Adverse Events. This will be available for configuration in a future release. | SAF-82436 |
| After running the Update from MedDRA Queries action on a Datasheet or Watchlist, Vault now displays a clear error message when the MedDRA version on the Datasheet or Watchlist is different to the MedDRA version on any MedDRA Criteria within the MedDRA Query. If Vault finds the MedDRA version variance on a MedDRA Criteria within the MedDRA SMQ of a MedDRA Query, Vault completes the update. | SAF-82821 |
| When coding a Primary MedDRA Term on a Product-Event Combination, if the selected MedDRA term is at the Preferred Terms (PT) level and does not include other hierarchical levels, Vault duplicates the PT in the MedDRA Dictionary. | SAF-81141 |
| On Cases created through tabular data import, Cumulative Dose units from source files appear on Inbox Items but not on Cases after promotion. | SAF-83746 |
| In Vaults configured with custom entry actions that affect the Rank of Case Assessments, in some instances Vault sets more than one Case Assessment to Rank 1. | SAF-84809 |
| When generating MFDS E2B(R3) forms for domestic Cases, Vault populates the C.5.1.r.1 and C.5.1.r.2 data elements for foreign Study Registrations. | SAF-85039 |
| Vault does not generate validation warnings for non-current EDQM terms. | SAF-85216 |
| For post-closure QC checklists configured to run weekly, in some instances, completed Cases incorrectly do not pass Checklist Creation Rule Criteria, so Vault does not generate expected checklists. | SAF-85396 |
Release Number: 25R2.0.5 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
August 19, 2025
Release Number: 25R2.0.4 | Build Number: 222 | Platform: 10474
| Description | Issue No. |
|---|---|
| When a Case includes Transmission Document records for which document generation did not complete, custom E2B generation fails and Vault displays an unclear error message. | SAF-83680 |
| When generating MFDS E2B(R3) forms, Vault converts the MPID Version to date format when populating the G.k.2.1.KR.1a and G.k.2.3.r.1.KR.1a data elements. | SAF-84326 |
| When generating MFDS E2B(R3) files, Vault populates values in both the D.2.1 and D.2.2.1 data elements, though only one (1) should be populated on a report. | SAF-84457 |
August 12, 2025
Release Number: 25R2.0.3 | Build Number: 214 | Platform: 10436
| Description | Issue No. |
|---|---|
| In some cases in Vaults with the 'Enable Suggestions' MedDRA setting enabled, when creating Case Adverse Events on domestic Cases and auto-coding fields that support dual language intake, Vault encounters an error and does not save the Case Adverse Event. | SAF-83087 |
| When processing an Inbox Item for a Study with Study Arms, after adding a Study Product through the multi-product selector and then saving the Inbox Item, Vault maps Study library details to the Study Product resulting in incorrect or blank Rank, Drug Role, and Company Product values. | SAF-83264 |
| Case data expression rule parameters fail unexpectedly when Submission or Distribution rules include the Case Data - Expression reporting rule parameter configured with an expression that evaluates the top-level Case with the assigned keyword that does not validate the case using the VS_LET and does not contain a reference to this Case record through another object path. | SAF-83881 |
| When generating FDA E2B(R3) forms for clinical trial study Cases, Vault populates the G.k.4.r.10.2a data element. | SAF-84771 |
August 7, 2025
Release Number: 25R2.0.2 | Build Number: 207 | Platform: 10417
This release includes only Platform fixes.