Note Beginning with 23R3 content and for all subsequent releases, Vault Release Notes is the official site for Vault Safety release notes.
A maintenance release contains fixes for issues affecting customer Vaults. Maintenance releases can occasionally include enhancements, for example, a time-sensitive regulatory requirement.
We communicate 24 hours prior to a maintenance release when there will be a short service disruption during deployment. The Veeva Trust Site provides the most up to date information on Vault's service status. Check this site to view the current status of Vault PODs and upcoming scheduled system maintenance.
The contents is subject to change until the release occurs. When we identify items for 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 an update early enough for full testing. In situations like this, we postpone the update for a later release and strike out the description in this list.
Veeva frequently delivers maintenance releases for the Vault Platform. Vault Safety deploys these Vault Platform maintenance releases at a later date. For details on the Vault Platform fixes in these maintenance releases, see Vault 20R3 Maintenance Releases.
Note This page covers maintenance releases deployed to General Release vaults only.
March 2021
March 25, 2021
Release Number: 20.3.0.10 | Build Number: 736
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Transmissions: E2B Validation | Fixed an issue where regulatory conformance rules would not validate a Case with the country code XI for Northern Ireland. | SAF-16031 |
| Transmissions: E2B Validation | Fixed an issue where the regulatory conformance of a follow-up Case could not be evaluated, resulting in an error. | SAF-16023 |
| Transmissions: E2B Validation | Fixed an issue where a unique name was not generated for the Validation Result Record after generating a Validation Summary Result record for a case. The unique name will be formatted as "ABCD-1234." For example, "VEEV-1254 (v2.0) Validation Results Summary." | SAF-16028 |
| Vault Safety.AI | ||
| Intake: Data Extraction | Fixed an issue where the Inbox Item creation was unsuccessful when no document was attached. | SAF-14328 |
| Intake: Data Extraction | Fixed an issue where an exception would occur when creating an Inbox Item with an attached form. | SAF-13259 |
March 18, 2021
Release Number: 20.3.0.9 | Build Number: 723
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety and Safety.AI | ||
| Case Processing: Data Entry | Fixed an issue where the maximum length for certain fields was too small. The case_contact_v.additional_information_v field character limit has been increased from 200 to 1,500 characters. The case_contact_v.email_address_v field character limit has been increased from 50 to 100 characters. Lastly, the case_version_v.reason_received_late_v field character limit has been increased from 200 to 1,500 characters. | SAF-16190 |
| Vault Safety.AI | ||
| Intake: Case Promotion | Fixed an issue where the Receipt Date is not applied to the New Info Date on the Inbox Item upon Case Promotion. | SAF-15278 |
February 2021
February 25, 2021
Release Number: 20.3.0.8 | Build Number: 662
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety.AI | ||
| Intake: Verification | Fixed an issue where edits to the Receipt Date and Report Type fields did not save if the page was refreshed after editing these fields for the first time. | SAF-15418 |
| Intake: Verification | Fixed an issue where, if a Safety.AI vault received an Inbox Item from the API with a time specified in the Receipt Date structured data (JSON), users could not verify the Details section on the Inbox Item. | SAF-15082 |
| Intake: Data Extraction | Fixed an issue where the maximum length for any Inbox Item or Case pass-through fields was 1,000 characters. Now, text fields can store up to 1,500 characters and long text fields can store up to 32,000 characters. Validation rules enforce field-specific maximum length. | SAF-14604,
SAF-14660 |
February 11, 2021
Release Number: 20.3.0.7 | Build Number: 627
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Transmissions: E2B Validation | Fixed an issue where the E2B ACK Accepted message would not be displayed when performing an EMA Submission with an attached XML file. | SAF-14651 |
February 3, 2021
Release Number: 20.3.0.6 | Build Number: 598
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Transmissions: Reporting Rules | Fixed an issue where an error appeared when evaluating reporting obligations for a Case with registrations to an inactive agency without submission rules configured. | SAF-14396 |
| Vault Safety.AI | ||
| Intake: Verification | Fixed an issue where Case Contact subheadlines were not updated to Reporter after selecting the "Contact is also Reporter" checkbox. | SAF-14402 |
| Intake: Data Extraction | Fixed an issue during automated intake where an Inbox Item was not created if Case Contact information was extracted from unstructured data. | SAF-14365 |
January 2021
January 21, 2021
Release Number: 20.3.0.5 | Build Number: 559
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Report Generation: E2B Export | Fixed an issue with E2B (R3) exports where a blank autopsy section (D.9.3) was included when there was no death, causing submissions to the EMA Gateway to be rejected. | SAF-14235 |
| Transmissions: Transmission Generation | Fixed an issue where an error prevented automatic generation of Health Canada Submissions through the rules engine. | SAF-13075 |
| Vault Safety.AI | ||
| Intake: Verification | Fixed an issue where the Source Data panel was showing the API name for Case Contact type. | SAF-14383 |
| Intake: Verification | Fixed an issue where date validation errors appeared on different sections after removing the Date of Death. | SAF-13482 |
| Intake: Verification | Fixed an issue where multiple Drug History records were created for a single Combination Product once an Inbox Item was promoted to a Case. | SAF-13294 |
January 14, 2021
Release Number: 20.3.0.4 | Build Number: 509
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Case Processing: Follow-Ups | Fixed an issue where users were unable to create a follow-up from a Case when blinded study arms were enabled and the Download Dosage to Case option was turned on. | SAF-13601 |
| Case Processing: Follow-Ups | Fixed an issue where duplicate dosages were created when a follow-up was created from a Case with Blinded Study Arms. | SAF-13600 |
January 8, 2021
Release Number: 20.3.0.3 | Build Number: 474
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Case Processing: Data Entry | Fixed an issue where a system error appeared when attempting to create an External Case Product. | SAF-13675 |
| Case Processing: Data Entry | Fixed an issue with Combination Products comprising of multiple vaccines and a single device product, where the Device Case Product record was being nested under each Vaccine Case Product record instead of only the primary (PMOA) record. | SAF-13302 |
| Case Processing: Medical Review | Fixed an issue where the medical review timeline was not loading. | SAF-13507 |
| Case Processing: Watchlists | Fixed an issue where the Case Watchlist tag was updated with a constituent product’s watchlist tag when the constituent product had an associated Watchlist, but the Combination Product did not. | SAF-13295 |
| Coding: MedDRA | Fixed an issue where the MedDRA browser version was using the active version in Business Admin instead of using the Case MedDRA Version for Case Drug History and Case Diagnoses records. | SAF-13462 |
| Report Generation: CIOMS I | Fixed an issue where Case Assessment Results listed on overflow pages showed event names as AE-{####} instead of the coded term. This fix temporarily disables the Assessment Results section from appearing on the CIOMS I overflow pages. | SAF-13429 |
| Transmissions: E2B Validation | Fixed a date validation issue where, if the start date was not entered, the end date validation logic did not evaluate correctly. | SAF-13572 |
| Transmissions: E2B Validation | Fixed an issue where the ICH.F.r.4/5 E2B validation rule did not allow decimal numbers. | SAF-13435 |
| Transmissions: E2B Validation | Fixed an issue where the ICH.D.4 E2B validation rule did not show warnings if the Height was a decimal number. To fix this issue, the ICH.D.4 criteria has been removed. | SAF-13431 |
| Transmissions: E2B Validation | Fixed an issue with E2B validation where the Validation Result Summary did not list IDs for records evaluated with the ICH.G.k.4.r.1a validation rule. | SAF-13424 |
| Transmissions: E2B Validation | Fixed an issue with E2B validation where the Validation Result Summary did not list vault fields evaluated with the ICH.D.10.3-3 and ICH.D.10.8.r.5-3 validation rules. | SAF-13421 |
| Transmissions: E2B Validation | Fixed an issue where certain patient-related ICH.D E2B validation rules failed for device malfunction-only Cases with no patient. | SAF-13378 |
| Transmissions: E2B Validation | Fixed an issue where certain ICH validation criteria was not provisioned. The following E2B validation rules are now provisioned: ICH.D.2.3, ICH.C.2.r.3-3, ICH.D.8.r.1-3, ICH.D.10.3-3, ICH.D.10.7.1.r.2-3, ICH.D.10.7.1.r.4-3, ICH.D.10.8.r.4-3, ICH.D.10.8.r.5-3, ICH.F.r.4, ICH.F.r.5, ICH.E.i.1.1b, ICH.E.i.6a, ICH.E.i.6b, ICH.G.k.2.3.r.3a-1, ICH.G.k.4.r.1a, ICH.G.k.4.r.1b | SAF-13206 |
| Transmissions: Gateway Transmissions | Fixed an issue where gateway transmissions with validation errors became stuck in the Sending ICSR state. | SAF-13432 |
December 2020
December 16, 2020
Release Number: 20.3.0.2 | Build Number: 358
| Category | Issue Description | Issue No. |
|---|---|---|
| Vault Safety | ||
| Transmissions: E2B Validation | Fixed an issue where the ICH.D.2.1-2 E2B validation rule failed for Date of Birth referring to a future date when the Case Date of Birth field was not set to a future date. | SAF-13463 |
| Transmissions: E2B Validation | Fixed an issue where the ICH.E.i.5-2 E2B validation rule failed for a valid Case Adverse Event Cessation Date. | SAF-13478 |
