25R3 Safety Maintenance Releases

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 25R3 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 25R3.0, so our maintenance releases for this version are 25R3.0.2, 25R3.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 25R3 Maintenance Releases.

Last Updated: February 17, 2026

February 17, 2026

Release Number: 25R3.0.20 | Build Number: 286 | Platform: 10624

Description	Issue No.
When populating the C.1.CN.2 data element on NMPA E2B(R3) files, Vault now exports a value based on the NMPA Report Classification on the Localized Case. If that is blank, Vault populates a value based on the NMPA Center on the Transmission Profile.	SAF-91563
When configuring Rules Based Narratives, Admins can now configure an optional input for the VS_ExistCheck function to specify a "text2" field value to render if the "PrimaryField" is blank.	SAF-92742
In Vaults using the "Exclude External Products when Generating Assessments" setting, Admins can now configure the new "Continue generating assessments for Clinical Trial cases" sub-setting so that Vault suppresses assessments for External Products on postmarket Cases but continues to generate them for clinical trial Cases.	SAF-93135
When generating EU MIR files, for field 1.2b Vault now populates a date range for when the onset of the event could have occurred based on the Onset date of the primary Case Adverse Event, and for field 1.2g Vault adds more logic based on Case Adverse Event Seriousness and Case Assessment Expectedness.	SAF-95207
For the Transmission Reason reporting rule parameter, to determine whether a Case being reported to the FDA is a follow-up, Vault now considers only premarket or postmarket Transmission Profiles based on the Transmission being evaluated.	SAF-95210
On unblinded Case Assessments generated by running the Generate Assessments action on blinded study Cases, Vault copies the Expected and Expected (Status) values instead of evaluating them.	SAF-73005

February 12, 2026

Release Number: 25R3.0.19 | Build Number: 279 | Platform: 10614

This release includes only Platform fixes.

February 10, 2026

Release Number: 25R3.0.18 | Build Number: 278 | Platform: 10603

Description	Issue No.
For customers using the Safety-EDC Connection, when adding subject data to a Case through the Add Relevant Subject Information dialog, Vault now displays an error message and prevents users without Create permissions for an object from adding related records.	SAF-88692
When creating a follow-up for a previous Case version without a link to a narrative document, Vault searches for an existing document on the previous Case version or, if none exists, generates a new narrative document, and then populates a link in the Case Narrative field.	SAF-91296, SAF-91300
When generating FDA E2B(R3) files for Cases with no First Admin Date in the Dosages section for a combination product, Vault does not populate the FDA.G.k.10.1 FDA Specialized Product Category data element.	SAF-91624
On FDA E2B(R3) files, when the associated Transmission Profile is not CDER, CBER, or CDER IND Exempt and there are Case Assessment Results with Sponsor as the Source Type, Vault does not populate "FDA" in the G.k.9.i.2.r.2 Method of Assessment data element.	SAF-93062
When generating Transmission documents, if a Transmission has an XSD schema error, Vault moves the document to the Validation Error state.	SAF-94010
After a non-EDC Inbox Item with a Link value is promoted to a follow-up Case or merged to an in-flight Case, Vault populates "Veeva EDC" as the Case Identifier type.	SAF-94243
In Vaults with the Mask Reporter For PM Non-Literature Case application setting enabled, when generating the FDA MedWatch 3500A form (August 2024 version) for postmarket non-literature Cases, Reporter Qualification and Reporter Country values are masked.	SAF-95217

February 3, 2026

Release Number: 25R3.0.17 | Build Number: 266 | Platform: 10574

Description	Issue No.
For customers using the Safety-EDC Connection, when a user changes the primary Case Adverse Event in their Safety Vault, Vault now applies an Add decision to all child records, ensuring all records are correctly populated in the new SAE casebook.	SAF-93188
To support compliant FDA E2B(R3) generation, Vault adds the following Reasons Omitted field values: "Not applicable" for Patient Initials and "Asked But Unknown" and "Not Asked" for Last Menstrual. For all other E2B(R3) formats, when the Patient Initials Reason Omitted is "Not applicable", Vault populates "UNK" in the D.1 data element; when the Last Menstrual Reason Omitted is "Asked But Unknown" and "Not Asked", Vault does not populate the D.6 and D.10.3 data elements.	SAF-93197, SAF-93199
In Vaults configured for strict Case locking, Vault now updates the Narrative Preview value when any user checks in a new version of the narrative document on a locked Case, regardless of which user locked the Case.	SAF-94676
When generating MFDS E2B(R3) files, Vault does not export a code to the G.k.9.i.2.r.3.KR.1 WHO-UMC Result of Assessment data element if the Assessment Result on the Case Assessment Result is Reasonable Possibility.	SAF-93063
After running the Generate Document Collection action on an E2B R3 Document Collection, Vault does not attach E2B(R3) files with warnings to the associated binder.	SAF-93267
For Inbox Items generated through the Safety-EDC Connection, when merging an Inbox Item to an in-flight Case, Vault does not reflect a change to the primary Case Adverse Event on the updated Case.	SAF-93425
In Vaults configured to assign a Significance value to Inbox Items generated through the Safety-EDC Connection, when a follow-up Inbox Item for a Safety Case with multiple adverse events is transferred to a Safety Vault and promoted through the Inbox Item to Case Compare page, Vault does not ignore missing records and recalculates Significance incorrectly.	SAF-93739
After clearing the "Contact is also reporter" checkbox on a Case Contact on an Inbox Item, during duplicate detection Vault continues to evaluate the contact as a reporter.	SAF-94035
A user can run the Create Follow Up Case action on a Case that is locked to another user.	SAF-94187
When generating MFDS E2B(R3) and NMPA E2B(R3) files for a Localized Case with a Localized Parent Information Case, in some instances Vault attempts to populate the H.5.r block with data from the Localized Parent Information Case instead of the Localized Case, resulting in an error.	SAF-94381
In Vaults configured to isolate blinded clinical trial information, during bulk unblinding Vault does not map Substance Names from the Product library to Case Products.	SAF-95254

January 27, 2026

Release Number: 25R3.0.16 | Build Number: 254 | Platform: 10547

Description	Issue No.
When using the Document Intake Highlighter, after running the Extract Company Products action, products added to the panel based on matching Study Name include non-product annotations.	SAF-90771
In Vaults configured for Case Access Group Security, when promoting an Inbox Item to a follow-up Case or merging to an in-flight Case, if the Case Assignment Team of the existing Case conflicts with an update to the Access Group, Vault displays an error and prevents promotion or merge.	SAF-92780
When users run the Generate Assessments action to regenerate previously deleted Case Assessment Results on a global Case, Vault does not regenerate Localized Case Assessment Results on the related Localized Case, and then during the one-time sync from the global Case to the Localized Case after follow-up Transmission generation, Vault displays an error and prevents Case approval.	SAF-93002
When transferring data through the Safety-EDC Connection, values in custom fields do not map to the Safety Case.	SAF-94192
When generating FDA E2B(R3) files, Vault does not consider the Report Type of a Case or the Study Type of a Case Study to determine when to populate the 7-day E2B code (6) in the FDA.C.1.7.1 data element, resulting in rejections when cross reporting spontaneous foreign Cases to the FDA.	SAF-94486

January 20, 2026 (Postponed) January 21, 2026

Release Number: 25R3.0.15 | Build Number: N/A | Platform: N/A

This release affects only internal infrastructure and contains no customer-facing fixes.

Release Number: 25R3.0.14 | Build Number: 238 | Platform: 10497

Description	Issue No.
This update optimizes code to support Case Product Type changes on the Inbox Item to Case Compare page for records from the Safety-EDC Connection.	SAF-89894
After running the Evaluate Reporting Obligation action, for some Cases where the Agency is missing Submission Rules, Vault does not display an error message and can still generate Transmissions.	SAF-92175
After running the Evaluate Regulatory Conformance action, in some Cases with Transmissions of the same Document Type but different agencies, validation passes for EMA.F.r.3.3 Test Result (unit) when a failure is expected.	SAF-93066
When a user creates a second Case Contact with Patient qualification on an Inbox Item, a validation error correctly occurs, however, Vault still takes the second Patient Case Contact into consideration during duplicate detection.	SAF-93183

January 14, 2026

Release Number: 25R3.0.13 | Build Number: 230 | Platform: 10462

Description	Issue No.
Admins can now create View Columns with a "Reporting Period ID" API Name and the "Object" Column Type, so that Vault populates the ID of the Reporting Period record when users run Signal Calculations.	SAF-92446
To populate the G.k.9.i.CN.1 data element on NMPA E2B(R3) files, Vault now exports a code based on the Expected value on Localized Case Assessments. If blank and the related Case Assessment is for a Case Product being exported in the G.k Drug(s) Information section, Vault exports a code based on the Expected value on the Case Assessment Expectedness record generated for a core Datasheet for China or a core Datasheet.	SAF-93068
When mapping a Literature Reference value that contains over 500 characters from an EVDAS Line Listing record to the C.4.r.1 Literature Reference(s) data element in an E2B file, Signal maps only the first 500 characters.	SAF-91757
When Vault generates a narrative from an outline for a Case with an existing narrative, if a Case Product has been deleted, the summary on the upversioned narrative includes a statement indicating that the deleted product's drug role changed.	SAF-92774
When a user creates a follow-up Case, if they don't have permissions for the Localization on a related Localized Case, Vault does not generate that localized narrative and leaves the Case Narrative field blank on the Localized Case.	SAF-92775
Signal displays an error when running the Create Statistical Data action and signal alert rule engine for the same Product Family.	SAF-92819
When generating a CIOMS I (Chinese) form, Vault does not map the complete narrative from the Localized Case or the MedDRA Preferred Term (PT) Chinese name into the CIOMS I (Chinese) field 7 + 13 Describe Reaction(s) or the CIOMS I (Chinese) field 23 Other Relevant History.	SAF-93067

January 9, 2026

Release Number: 25R3.0.12 | Build Number: N/A | Platform: N/A

This release contains no customer-facing fixes.

December 22, 2025

Release Number: 25R3.0.11 | Build Number: 216 | Platform: 10395

This release includes only Platform fixes.

December 19, 2025 (Postponed) December 22, 2025

Release Number: 25R3.0.10 | Build Number: 219 | Platform: 10426

Description	Issue No.
For cases with a high volume of data, users experience performance issues when promoting Inbox Items to Cases through the Inbox Item to Case Compare page.	SAF-93006

December 16, 2025

Release Number: 25R3.0.9 | Build Number: 212 | Platform: 10393

Description	Issue No.
When generating MFDS E2B(R3) files, Vault detects an error for the C.5.4.KR.1 data element and moves Submissions into the Validation Error state, instead of the Ready state.	SAF-92893
When generating E2B(R3) files, Vault does not convert the TermID Version to YYYYMMDD format when populating the G.k.2.3.r.2a data element, resulting in NACKs. This issue does not impact MFDS E2B(R3) files.	SAF-92983
~~When generating and updating Case Assessments, users may experience performance issues if an assessment has a blank Case Product.~~ If a Case Assessment is created without a Case Product or a user manually clears a Case Product on a Case Assessment, users may experience performance issues.	SAF-93318

December 12, 2025

Release Number: 25R3.0.8 | Build Number: 204 | Platform: 10386

Description	Issue No.
In some instances, during promotion of an Inbox Item with a high number of Products, an error occurs during duplicate detection, which prevents case processing.	SAF-91274
In Vaults with the "Related Case Identifier source (On Edit)" application setting enabled, users may experience performance issues following changes to the Related Case on a Case Relationship record.	SAF-93138

December 10, 2025

Release Number: 25R3.0.7 | Build Number: 202 | Platform: 10372

Description	Issue No.
During approval of a global follow-up Case with a related foreign follow-up Localized Case for the NMPA, users experience performance issues while Vault performs the one-time data sync from the global to the Localized Case.	SAF-93050

December 8, 2025

Release Number: 25R3.0.6 | Build Number: 199 | Platform: 10368

Description	Issue No.
When processing a Case that includes some, but not all, constituents of a Combination Product, users experience significant performance issues when Vault maps and creates Case Product records for the remaining constituents.	SAF-92838
When Vault performs the one-time data sync from a global follow-up Case to a foreign follow-up Localized Case for the NMPA, users experience significant performance issues when Vault syncs Case Assessment Results.	SAF-92862

December 4, 2025

Release Number: 25R3.0.4 | Build Number: 193 | Platform: 10359

Description	Issue No.
In some cases when coding an External Product using the WHODrug Search browser, Safety does not populate the TermID Version field on the generated Substance records, triggering a validation error.	SAF-90116
In some cases upon removing a Yes/No filter from a Workbench Dashboard, Workbench encounters an error and displays a blank dashboard.	SAF-90836
In Vaults without the Enable Isolation of Blinded Product Information setting enabled, after populating the Combination Product field on an unblinded Study Product within a Case that already contains one or more of the Study Product constituents as Case Products, Vault creates duplicative Case Products for those constituents.	SAF-91437
In some cases when accessing a Case with failed Validation Results, Vault displays a record count of 0 for Validation Results (Failures & Warnings) in the sidebar.	SAF-92139
When generating a Transmission to the NMPA for a foreign follow-up Localized Case for China, if multiple Case Assessment Results have the same Relatedness value, an error occurs during the one-time sync from the global Case to the Localized Case, and Vault prevents additional Case processing.	SAF-92319