The issues listed below may impact Vault functionality for some users. We are actively investigating all known issues and will be providing fixes and updated information in future Vault releases.
| Description |
Issue No. |
|
When Override Payee is enabled, Vault overrides the Override section and allows users to save Fees even if there is a mismatch between the Total Fee Amount and the sum of the override payees.
Issue published in error
|
DEV-530563 |
|
In some cases, running the Save Object Record, Delete VOF Record, Update Study Person Record, or Delete Study Person Record action against the Study Person object takes longer than expected.
|
DEV-542639 |
|
Transfer failure records are not created for the Study Site when the the Study Country does not transfer successfully.
|
DEV-552235 |
|
Transfer failure records are not created when referencing a country__v record that only exists in the source Vault but not the target Vault.
|
DEV-552650 |
|
In some cases, the CDMS to Clinical Operations connection job takes longer than expected to run, resulting in failure of related jobs.
|
DEV-555900 |
|
In some cases, when Payable Items generated for a single Fee with a Holdback are modified and the Generate Payable Items action is re-run, Vault fails to correctly update the Payable Items and their Related Holdback Items.
|
DEV-560951 |
|
In some cases, when users update the Study Hierarchy Fields on a document with tasks and navigate back to the document's tasks, the filters for Study Hierarchy are not updated accordingly.
|
DEV-561150 |
|
In Vaults using the Study Training to Clinical Operations connection, target CrossLinks in the Study Training Vault may be up-versioned unintentionally if a Study Training Connection Event was re-processed.
|
DEV-563091 |
|
Under certain circumstances, Vault incorrectly allows multiple Study Organization records to be set as the primary payee for a Study Site when there are no existing Study Organizations for the site.
|
DEV-567840 |
|
The Study Training to Clinical Operations connection CrossLink sync may fail during create draft or state change operations when attempting to sync large sets of CrossLinks.
|
DEV-568855 |
|
Vault does not display the expected error message when a user attempts to create a new draft and the product linked to the document's study is no longer valid.
|
DEV-570869 |
|
When users import documents using Vault Loader, and have EDL items with milestones that match those documents, Vault does not automatically update the milestones on the imported document.
|
DEV-571206 |
|
Under certain circumstances, site users may experience server errors after selecting a Study from the Tasks widget on the Site User homepage.
|
DEV-573882 |
|
Vault incorrectly displays the envelope icon in the Notifications section of the Home tab.
|
DEV-574813 |
| Description |
Issue No. |
|
In some cases, after Vault creates a document from an email, users see a "Document not found" error when attempting to open the file from their Document Inbox.
|
DEV-556144 |
|
In some cases, using the Google Drive integration results in server errors if the Vault's name includes special characters.
|
DEV-560171 |
|
In some cases, Vault fails to display certain document relationship types in the Entry Criteria dropdown menu during Document Lifecycle State configuration.
|
DEV-562022 |
|
Under certain circumstances, Vault fails to render XLSX files.
|
DEV-565272 |
|
In rare cases, Vault fails to apply overlays to all applicable pages in a document.
|
DEV-570298 |
|
Under certain circumstances, Vault fails to render large Adobe InDesign Packages
|
DEV-572878 |
|
In some cases, Vault does not display binders created from a Submission Content Plan in Library search results.
|
DEV-574089 |
|
When the "Restore placemarks on brought forward annotations" setting is disabled, Vault may fail to persist references to Claims in Claim Link annotations, and may not update the Where Used view.
|
DEV-575385 |
|
After users sign a document and it moves into the Steady State in which they do not have the View Document permission, Vault intermittently generates the eSignature page while updating the audit trail with the message "Signature page failed to generate." Vault will generate the eSignature Page the next time a user with the appropriate access views it.
|
DEV-576222 |
|
After users sign a document via workflow and it moves into the Steady State, Vault may not automatically generate the eSignature page. Vault will generate the eSignature Page upon the next request.
|
DEV-576718 |
| Description |
Issue No. |
|
In some cases, the email log does not show translated exception details.
|
DEV-528825 |
|
If an email to Vault has two attachments with the same name but different contents, Vault may upload only one version of the attachment.
|
DEV-537288 |
|
If a custom record action is only available for certain states, Vault only blocks the page briefly as it executes the action and interrupts any subsequent user activity when the action completes.
|
DEV-540597 |
|
When a rich text field on an object enables Contains Protected Health Information (PHI) or Personally Identifiable Information (PII), users are unable to create new records with a value in the rich text field.
|
DEV-545732 |
|
When a high volume object has a related object section for another high volume object, Criteria VQL filters are not applied to the corresponding dynamic tab.
|
DEV-551179 |
|
Users cannot delete EDL records with 100 or more outbound fields.
|
DEV-554975 |
|
If a user creates a record through the Copy Record action, the inline error message "This email already exists" does not show unless the user clicks on the Email field.
|
DEV-558543 |
|
When records exist for a deleted User Task object, Vault displays a server error on the My Tasks and All Tasks pages.
|
DEV-570036 |
|
Vault may send emails to addresses on the Email Suppression List if the addresses are entered in a different case.
|
DEV-571250 |
| Description |
Issue No. |
|
When users filter on lookup fields in custom tabs, Vault fails to display matching records.
|
DEV-532221 |
|
Under certain conditions, Query Field on an Integration Rule do not display properly.
|
DEV-535988 |
|
In some cases, emails with non-Latin characters sent to Vault have incorrect content in the email body.
|
DEV-539608 |
|
Deployment of migration packages may fail to create lifecycles for high volume objects that exist in the target Vault.
|
DEV-555009 |
|
Users are able to input more than the maximum 750 characters into the search bar when adding object references.
|
DEV-556180 |
|
Audit trails may not accurately display delegate actions performed within multi-record workflows.
|
DEV-559983 |
|
Users using Firefox as their browser may not receive the "Some filters are no longer available" warning.
|
DEV-559985 |
|
Certain components present in the target Vault may be displayed as missing when deploying migration packages, resulting in blocked steps.
|
DEV-564567 |
|
On the My Vaults page, if the list of Vaults is on page 2 or greater and a user applies a filter resulting in only one page, Vault shows "No items found."
|
DEV-565083 |
|
Vault may fail to remove a user task from the task view upon completion.
|
DEV-570016 |
|
In some cases, users receive a network issue message when attempting to inline edit a field in the grid view.
|
DEV-573166 |
|
The Business Admin > Picklists drop-down menu does not include a tooltip with the picklist name (e.g., activity_type__c).
|
DEV-574393 |
|
Vault fails to resolve numeric field tokens in notification templates.
|
DEV-576070 |
| Description |
Issue No. |
|
In certain circumstances in Validation Management, Vault may not display an error message when a user attempts to save a step in the Test Authoring interface without all required fields populated.
|
DEV-534696 |
|
Vault may display an error when a user attempts to create a Duplicated Record Check with an Inactive status and defined object match criteria.
|
DEV-544291 |
|
Vault may display a blank page when attempting to remove a user from a Quality Team role membership with the backspace key in the "Manage Invalid Team Members" dialog.
|
DEV-550767 |
|
In Vault LIMS, inputs may incorrectly be cleared when adding a sample to a test.
|
DEV-556479 |
|
Some state types may incorrectly be duplicated or share the same label.
|
DEV-556664 |
|
In some cases, the Application Role or Security Profile field may incorrectly display as required but incomplete when attempting to save a QMS User Template.
|
DEV-557037 |
|
In Vaults using the QMS-RIM connection, in some cases, the system may create duplicate Impacted Country records after performing the Update QMS Details action.
|
DEV-557601 |
|
In the Risk Builder, an input box may incorrectly remain after switching to View mode.
|
DEV-560698 |
|
In some cases, the Risk Builder may incorrectly display no steps when using the "All" steps view option.
|
DEV-560805 |
|
When using the QRM Risk Builder, Vault may incorrectly display an error when a user without Admin permissions attempts to copy or save a Risk.
|
DEV-561968 |
|
The Related Root Cause Analysis Item field may incorrectly be editable on manually-created Root Cause records.
|
DEV-564495 |
|
Vault may incorrectly display errors when a user without permissions to update the Risk Matrix field attempts to make changes in the RIsk Builder.
|
DEV-564662 |
|
In cases where a Learner has failed a class, then been added to a new class, the Learner Homepage may fail to display properly.
|
DEV-566744 |
|
In Validation Management, Vault may display an error when a user types "All" or "Not Challenged" into the Filter Requirements dialog.
|
DEV-570708 |
|
In Vaults using the QMS to RIM connection, transactions may be marked with an incorrect status when certain combinations of failures and successes are processed together.
|
DEV-570715 |
|
In some cases, Vault may display an error when attempting to create FMEA Risk Events.
|
DEV-572631 |
|
On the Training Dashboard, Vault displays a Page Not Found error when a user attempts to view tabs which have been inactivated.
|
DEV-573121 |
|
Under certain configurations on custom Risk object types, Vault may incorrectly display an error when a user populates the Severity, Occurrence, and Detectability values.
|
DEV-576377 |
|
In some cases, the “Resubmit Spark Trigger” User Exception Item may not function correctly for the QMS - RIM Connection.
|
DEV-579370 |
| Description |
Issue No. |
|
In some cases, the notifications for the Update Content Plan and Update Global Content Plan actions do not specify the constraints excluded during the update.
|
DEV-538745 |
|
When users drag and drop Active Dossier records into the viewer and do not populate the Product field with the Inactive Ingredient field, Vault does not display the created records in the viewer.
|
DEV-544331 |
|
In some cases, Vault does not execute Rule 5200 on incoming links during continuous publishing.
|
DEV-550919 |
|
The Quality to RIM Vault Connection does not create Event records in RIM when the QMS-RIM Integration and associated integration points are inactive.
|
DEV-551858 |
|
When a matched source document includes Vault annotations to permalinks to multiple targets, on-demand publishing does not up-version source documents and resolve the link if a target document is updated.
|
DEV-552009 |
|
When managing registered details, users receive a network issue error on the Summary page when attempting to submit updates to ~17K Registered object records.
|
DEV-553502 |
|
If the Submissions Archive application is disabled and re-enabled by Veeva in a RIM Vault, the Submissions Archive Application Settings are disabled but not re-enabled.
|
DEV-554437 |
|
When users apply a saved view in the Active Dossier viewer, Vault does not populate the Product Family filter, and the Product Family picklist is blank.
|
DEV-555308 |
|
When users expand a section in the new Submissions Archive Viewer, Vault does not display the loading icon.
|
DEV-556946 |
|
When splitting Activities, Vault does not Regulatory Objective Product Characteristic and Regulatory Objective Packaging Characteristic records if the Enable Application Relationships and Exclude Submission Lifecycle States application settings are enabled.
|
DEV-564870 |
|
When pulling Regulatory Objective data to a Submission, Vault does not create Product Characteristic join records.
|
DEV-566421 |
|
Within the M5 STF section, running On-Demand Publishing can result in binder leafs in a different order than the Content Plan Items are displayed.
|
DEV-566749 |
|
Users without read access to the Submission Metadata object are unable to apply filters in the new Submissions Archive Viewer, and the viewer displays but does not allow users to select Submission related objects in the Submission filter.
|
DEV-567129 |
|
Users without read permission to the Submission Metadata object receive an error when attempting to view document and leaf hovercards in the new Submissions Archive Viewer.
|
DEV-567266 |
|
When viewing documents in the new Submissions Archive Viewer in Safari or Firefox, users intermittently receive a server error if the viewer does not have any applied filters.
|
DEV-567458 |
|
Vault displays lists of related objects to users without Read permission on the object.
|
DEV-568273 |
|
Users cannot drag and drop to match documents from a document tab within a Tab Collection into the Content Plan Hierarchy Viewer.
|
DEV-568477 |
|
When creating Submission records in bulk from an Event, Vault does not create records if there are Constraints configured for the selected Submission Type.
|
DEV-568536 |
|
When cell text is truncated in the new Submissions Archive Viewer, Vault does not display the ellipsis icon.
|
DEV-568779 |
|
Users cannot drag and drop documents from a document tab within a Tab Collection into the Active Dossier Editor.
|
DEV-569039 |
|
Users cannot generate IDMP elements when the Application on the Lead Registration is specified as a Centralised Procedure (via the Application Procedure Type field) and the Lead Registration’s Country field is blank.
|
DEV-569416 |
|
The Generate UDI Submission job confirmation CSV file incorrectly counts the number of UDI Submission DI records Vault created during the job run.
|
DEV-569544 |
|
Users cannot navigate the UDI Submission Viewer using the Next button.
|
DEV-572142 |
|
Users receive a Page Not Found error when attempting to view FHIR messages in the IDMP Viewer if the XML does not include an <id value="mpid"/> tag under <MedicinalProductDefinition>.
|
DEV-572872 |
|
For AU submissions with a blank ARTG Number, Vault generates the ARTG Number in the XML.
|
DEV-573588 |
|
Users without Edit permission to a matched document’s Content Plan Item record are able to view the record’s empty Actions Menu.
|
DEV-574037 |
|
When the Set Bookmarks & Hyperlinks to Page & Coordinates - RLCP setting is enabled, the bookmark page destinations for merged documents within Report Level Content Plans are not updated.
|
DEV-574416 |
|
The Submission Wizard is unable to load the Application Relationship page when there is at least one relationship with a populated number field.
|
DEV-574489 |
|
When dragging and dropping documents to the Active Dossier Editor, the Add to Active Dossier dialog’s Save button is disabled if the user selects a different Section from the drop-down.
|
DEV-575350 |
|
When dragging and dropping a document with a Source Reference to the Active Dossier Editor, Vault does not populate it as the Submissions Archive Document in the resulting Active Dossier Item and Active Dossier Item Detail records.
|
DEV-575993 |
|
When users bulk update STF Content Plan Item file tags and continuous publishing is enabled, Vault intermittently does not maintain their ordering in the Submissions Archive Viewer.
|
DEV-576363 |
|
Users without access to the Submissions Archive Viewer tab are able to access the viewer via URL.
|
DEV-577801 |
| Description |
Issue No. |
If the Default Localization field on a User Profile is blank or set to "Global", users will encounter a server error when opening a Case adverse event.
Workaround: Set the Default Localization field on the User Profile to a specific language.
|
SAF-36860 |
Users may encounter a server error when adding or editing an adverse event on a Case.
Workaround: To edit an adverse event, make changes directly on the Case page instead of selecting the adverse event to open it separately.
|
SAF-36873 |
|
When the Complete state of a Localized Case is changed in the Intake Translation Settings, the corresponding Inbox Item remains in the Translation Requested state.
|
SAF-37509 |
When browsing for a MedDRA term on an adverse event, the MedDRA Browser appears in English even if the user's language is set to Japanese.
Workaround: Switch the MedDRA browser's language from English to Japanese.
|
SAF-37696 |
|
If an inbox item is opened while it is still in the Importing state when it is being created from an E2B file, several fields are prevented from being imported to the inbox item.
|
SAF-39092 |
|
When Follow-Up Cases are created from blinded studies with open-label or unblinded Standard of Care products, the Blinded field on Case Products is incorrectly set to "Yes".
|
SAF-39149 |
|
Transmissions may not be prevented from submission if the gateway connection is inactive.
|
SAF-39238 |
|
If a gateway transmission fails, the error notification email does not include a reason for the error.
|
SAF-39280 |
When creating an AER from an E2B file, document import will fail if the "Always: Set new major version" entry action is added to the Imported state for AERs.
Workaround: Delete the "Always: Set new major version" entry action from the Imported state for AERs.
|
SAF-39796 |
|
When conducting deep duplicate detection on inbox items, the Potential Matches page may display some Japanese characters even if the user's language is set to English.
|
SAF-39845 |
|
The value entered in the Origin field in the Case information section is not imported to inbox items if the inbox items are created from multiple E2B files.
|
SAF-40033 |
|
Users encounter a server error if an inbox item is opened while it is still in the Importing state when it is being created from an E2B file.
|
SAF-40118 |
|
Users encounter a server error if the creation of an inbox item from an E2B file fails and the inbox item is in the Import Error state.
|
SAF-40138 |
|
For general reporting and I–> X cross reporting, reporting rules generate transmissions for Non-Study Case Products instead of just for Study Case Products with Suspect or Interacting drug roles in Clinical Trial Study Cases.
|
SAF-40180 |
|
When conducting deep duplicate detection on inbox items that have custom lifecycle states, the Potential Matches page does not display the lifecycle states of the matching inbox items.
|
SAF-40594 |
|
When the user's language is set to French, the Event Reported field on Cases and Case adverse events displays the French translation of the LLT code.
|
SAF-40656 |
When Localization-based Mapping on Import is enabled for Domestic Cases, populating the English text values for the Patient RoA and Dose Form fields will cause the local text values for these fields to disappear.
Workaround: When the local text values disappear, populate them once again before populating the English text values.
|
SAF-40710 |
|
Users with the Case Processing security profile receive a job error notification when they perform actions such as "Create New Case" or "Promote to Follow-Up" on the Case Compare page.
|
SAF-40827 |
|
When conducting deep duplicate detection on inbox items, the Potential Matches page does not display matching Patient MRNs.
|
SAF-40846 |
|
When conducting deep duplicate detection, some cases with matching Gender and Country fields are ranked higher, while some with matching Patient Initials are ranked lower than others on the Potential Matches page.
|
SAF-40847 |
Custom fields are not imported to inbox items if the inbox item is created from a JSON file.
Workaround: Import custom fields at least five (5) hours after creating them to allow for a cache refresh.
|
SAF-40936 |
|
When a suspected and unexpected assessment is added to a Case created from a Clinical Trial study, the Assessment Tag does not change from SAE to SUSAR.
|
SAF-41079 |
The value entered in the Medical History Text field on Parent Information is not imported to inbox items if the inbox item is created from an E2B file.
Workaround: In Safety General Settings, clear the Enable Localization-based Mapping on Import checkbox for Domestic Cases.
|
SAF-41209 |
|
When conducting deep duplicate detection, Study and Study Number matching is completed within Reporter matching and is also assigned the same priority as Reporter matching.
|
SAF-41329 |
|
Users encounter an error when creating Follow-Up Cases from Japan Localized Cases that are imported from PMDA E2B files with Case Product Registrations, Local Reporting Details, and Local Reporting Details records or Product Join records included.
|
SAF-41371 |
|
Users encounter an error when creating Follow-Up Cases from the Case Compare page for Japan Localized Cases with Primary Case Product Registration records and Local Reporting Details included.
|
SAF-41372 |
|
The information entered in the Parent Medical History Text field is incorrectly mapped to the Patient Medical History Text field on Cases imported from E2B files with the Localization Type set to "Local".
|
SAF-41540 |
|
For Japan Localized Cases with Multilingual MedDRA enabled, English translations are not updated when Indications, adverse events, or Medical History information is updated, and translations and codes are missing when a new Indication is added.
|
SAF-41603 |
|
The Coding Method fields for Indication and Event are populated on inbox items even when the Enable Smart MedDRA Autocoding and Enable Smart MedDRA Coding Predictions settings are disabled.
|
SAF-41674 |
| Description |
Issue No. |
|
Precision highlighting does not work when rich or long text columns appear in an object data grid.
|
DEV-535225 |
|
In some cases, some Person records that should appear in the Learner field for Curriculum Completion objects are not visible.
|
DEV-549461 |
|
In some cases, users may see unavailable filters included in pill text, sidebars, and export search criteria.
|
DEV-558941 |
|
Users may receive a server error when changing a Saved View Task Type filter from Document to All, when a sort on document field is saved and Envelope tasks are included.
|
DEV-561400 |
|
In some cases, users are able to create saved views that include outdated study field names.
|
DEV-562239 |
|
In some cases, document placeholder tasks are included in filtered results and result counts when they should not be.
|
DEV-566219 |
|
After navigating to a saved view from a saved or bookmarked URL, users are unable to update or remove Study filters from the view.
|
DEV-566229 |
|
Users may experience performance issues when many users are searching concurrently.
|
DEV-567392 |
|
In cases where Study Hierarchies are broken, saved views with multiple studies applied as filters may incorrectly appear blank.
|
DEV-569147 |
|
After editing columns or changing the layout of a saved view, users are unable to alter filters on Study fields.
|
DEV-570354 |
|
When filtering tasks on some document fields, the facet counts may not be displayed on unselected filter values.
|
DEV-570856 |
|
Vault displays unexpected characters in the long and rich text fields of objects which are part of an expanded search collection.
|
DEV-574332 |
|
When clicking "Show in Tab" on a related list for a High Volume Object, some filter types will remove all results until the filters are cleared on the Tab.
|
DEV-576387 |