Note Beginning with 23R3 content and for all subsequent releases, Vault Release Notes is the official site for Vault Safety release notes.
You may encounter the following known issues or limitations in certain environments or configurations. Where possible, workaround instructions are provided to solve the issue.
We actively investigate all known issues and will be providing fixes and updated information in future releases.
For details about known issues in the Vault Platform in 22R3, see the Vault Release Notes.
Intake
Indication Name (Reported) is Mapped to the Localized Field on Import When Localization Type is Local
SAF-35958
If the Auto-select Inbox Item Localization by Reporter Country feature is enabled and if the Localization Type is Local, the system maps the Name (Reported) field to the localized field instead of the global field (English) on the Inbox item.
Workaround
Copy the value over to the global field (English) for each Case Product with an Indication Name (Reported).
Case Processing
Locking Error Occurs When Routing Case to Approved State
SAF-34566
The Strict Case Locking feature may prevent users from changing case state. This is due to the Assign Due Date action being configured as an entry action and being in the Strict Case Locking criteria.
Workaround
Switch off the Strict Case Locking feature in your Vault. For details, see Enable Strict Case Locking.
Follow-up Questionnaire Not Sent for Inbox Item or Case if Product Not Specified
SAF-35889
If a Follow-up Questionnaire is created for an Inbox Item that does not have a specified company Product, the generic product template is not selected for the questionnaire and the questionnaire is not sent.
Blinded Name (Placeholder) Not Populated When Matching Study Blinded Name Exists
SAF-35176
The Blinded Name (Placeholder) field on the Case Product record is not populated as expected even though the reported name is an exact match of the Blinded name.
E2B Importing to Inbox Item or Case Fails if Record is Inactive
SAF-35116
When importing to an Inbox Item or an Imported Case, if the imported value is inactive in Vault Safety (the Study or the Product for example), then the import fails with an error.
Incorrect Localized Case Link on Transmission Record Generated During Case Voiding
SAF-36554
When voiding a Follow-Up Case, the linked Localized Case is incorrectly pointing to a previous version.
Workaround
Manually update the Localized Case field to point to the correct version.