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: October 7, 2025
October 7, 2025
Release Number: 25R2.0.17 | Build Number: 300 | Platform: 10706
| Description | Issue No. |
|---|---|
|
For E2B-imported Inbox Items with a source file that includes multiple instances of the same A.1.11.2 Case Identifier value, Vault imports only one instance of the Case Identifier, regardless of whether the A.1.11.1 Source value is the same. Admins can now configure their Vault to import all Case Identifier and Source pairs, regardless of uniqueness. Enablement: Support |
SAF-86454 |
| When Inbox Items generated by the Safety-EDC Connection are multi-event cases, Vault now generates Case Identifiers for each subsequently merged Inbox Item to ensure that any future follow-up information is matched. In addition, Vault now adds and deletes Case Identifiers following the creation or deletion of Case Adverse Events. | SAF-87339 |
| When promoting Inbox Items received from the Intake Vault API, for coded Combination Products with IMDRF codes, Vault now generates Case Product Device Code records for each device constituent. In addition, Vault displays the IMDRF codes for each device on the Inbox Item to Case Compare page. | SAF-87348 |
| When generating FDA E2B(R3) files, if the associated Transmission Profile is not CDER IND Exempt, Vault now populates E2B codes in the FDA.G.k.10a data element based on the Compounding Type field on Case Products. When the Compounding Type field is blank, Vault now includes the OID when exporting nullFlavor NA. | SAF-87394 |
| When coding Case Products in the Product Browser, Vault now improves the order of the returned search results. | SAF-87406 |
| Vault displays an error during E2B import if the country on the source file matches multiple two-letter codes in Vault. | SAF-85430 |
| When generating FDA E2B(R3) files, Vault incorrectly uses the OIDs from the FDA VAERS(R3) format for the FDA.G.k.12.r.8, FDA.G.k.12.r.10, and FDA.G.k.12.r.11.r data elements and misplaces the FDA.G.k.12.r.9 and FDA.G.k.12.r.10 data elements within the XML structure. | SAF-86712 |
| In Vaults configured to automatically classify the significance of Inbox Items generated by the Safety-EDC Connection, following Inbox Item promotion through the Inbox Item to Case Compare page, Vault does not create the matching Link values on the Case to identify follow-up Cases. | SAF-86926 |
| When a user moves a PSMF document with multiple versions to an Obsolete state type, Vault displays an error message. | SAF-87001 |
| Rule expressions for post-closure Case Checklist Creation Rules do not support multiple paths with related object fields. | SAF-87351 |
| When generating FDA E2B(R3) files for postmarket Cases that are cross reportable as premarket Investigational New Drug (IND) to the FDA, Vault does not populate the G.k.9.i.2.r section for Case Assessment Results with Sponsor as the Source Type. | SAF-87638 |
Release Number: 25R2.0.16 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
October 2, 2025
Release Number: 25R2.0.15 | Build Number: 286 | Platform: 10699
This release contains no customer-facing fixes.
October 1, 2025
Release Number: 25R2.0.14 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
September 30, 2025 (Postponed) October 1, 2025
Release Number: 25R2.0.13 | Build Number: 285 | Platform: 10695
| Description | Issue No. |
|---|---|
| To improve filtering on the Signal Monthly Calculate and Create Data job, Vault now maps the start and end dates of the reporting period to additional date-based view columns. | SAF-84016 |
| When transferring data through the Safety-EDC Connection, Vault now maps custom Reason Omitted fields from EDC Vaults to the Case-level, as well as CDMS Subject Information records, in Safety Vaults. | SAF-84679 |
| Rules Based Narrative generation now supports the list and LIST operators in the VS_Repeat function for any Case child object. Vault does not support these operators for grandchild objects or nested VS_Repeat functions. | SAF-86363 |
| Rules Based Narrative generation now supports Case Relationship objects (case_relationships_case_vr and case_relationships_related_case_vr) in the VS_Repeat function. | SAF-86366 |
| When filtering on Datasheets and MedDRA Criteria in Datasheets in scheduled Signal Calculations, Vault now ensures that active start dates are before Reporting Period End Dates and active end dates are after Reporting Period End Dates. | SAF-86856 |
| In some instances, FDA MedWatch 3500A form generation fails for Cases with a high volume of Case Products. | SAF-86014 |
| When generating a domestic follow-up for an imported Case without a linked localized narrative, Vault generates a blank narrative document instead of using the local narrative template. | SAF-86017 |
| The MedDRA version on a Case does not always match the version on the related Parent Information Case. | SAF-87341 |
| When a Combination Product includes more than one device constituent, Vault doesn't map Product Codes and Trade Names from Product Registrations to Case Product records. | SAF-87345 |
September 30, 2025
Release Number: 25R2.0.12 | Build Number: N/A | Platform: N/A
This release affects only internal infrastructure and contains no customer-facing fixes.
September 23, 2025
Release Number: 25R2.0.11 | Build Number: 272 | Platform: 10647
| Description | Issue No. |
|---|---|
| This update optimizes code for Workbench reporting. This will be available for configuration in a future release. | SAF-86669 |
| Expanding the Case Assessment, Case Assessment Results, and Case Assessment Expectedness sections does not refresh the data. | SAF-83797 |
| In Vaults configured to isolate blinded clinical trial information and to use rules-based narratives, after running the Generate Narrative from Outline action on a follow-up blinded study Case with an unblinded Study Product, the follow-up summary on the narrative document includes information for the unblinded Case Product and Case Assessment Result. | SAF-86582 |
Release Number: 25R2.0.10 | Build Number: N/A | Platform: N/A
| Description | Issue No. |
|---|---|
| To address an Excel limitation, Safety Workbench now wraps text in merged cells to support long text fields such as Case Comments. | SAF-85847 |
September 16, 2025
Release Number: 25R2.0.9 | Build Number: 267 | Platform: 10612
| Description | Issue No. |
|---|---|
| Vault now supports configuring the Investigational to Investigational (same agency) option on the Reporting Scenario reporting rule parameter. | SAF-84275 |
| When editing a Workbench Dashboard component, the View options now include only Workbench Views with a matching Criteria VQL reference constraint. | SAF-85761 |
September 11, 2025
Release Number: 25R2.0.8 | Build Number: 262 | Platform: 10589
| Description | Issue No. |
|---|---|
| In some Vaults, the Product Coding Browser displays substances as "VV-####" instead of the substance name. | SAF-58730 |
| In some cases, Vault encounters an error when attempting to access a Case Adverse Event with a superseded MedDRA term after updating the MedDRA Version value on the parent Case. | SAF-83821 |
| When the Case Receipt Date includes a time and timezone, this sometimes results in invalid C.1.4 and C.1.5 data element formats on submissions to regulatory agencies, leading to rejections. | SAF-85007 |
| The Registration Holder/Applicant and Product (Coded) localized fields on domestic Case Products appear editable but the values do not save upon selecting the Save button. | SAF-85016 |
| Due to a caching issue, rule sets may incorrectly evaluate Safety Data Expression Building Blocks by using the results of another rule evaluation. | SAF-85665 |
| This update optimizes code for downloading Workbench Dashboard Components as CSV files. This will be available for configuration in a future release. | SAF-85965 |
September 3, 2025
Release Number: 25R2.0.7 | Build Number: 247 | Platform: 10582
| 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.