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. |
|
Vault incorrectly displays a “success” status and message on the Rendition Status page when attempting to render a password protected file.
|
DEV-367684 |
|
When configuring integration field rules, users receive a server error when configuring a type__v, subtype__v, or classification__v on a field rule for a document.
|
DEV-370973 |
|
Configuration Migration packages generated by Vault Compare sometimes order steps in a way that causes deployment to fail.
|
DEV-371080 |
|
While rendering a video, Vault displays a “Queue” status and does not display a rendering time on the Rendition Status page.
|
DEV-376390 |
|
After exporting the Rendition Status page to a .CSV file, the file does not contain a log item for the export process.
|
DEV-376942 |
|
In some cases, Vault displays an incorrect error message on the Rendition Status page.
|
DEV-376955 |
|
“Rendering Time” and “Queue Time” values on the Rendition Status page are missing after the document is approved.
|
DEV-376962 |
|
Vault does not display “token not found” errors for documents on the Rendition Status page.
|
DEV-383276 |
|
Users who do not have Read permission on the Users and Groups objects are unable to open the Vault Loader Extract page.
|
DEV-384172 |
|
When extracting data with Vault Loader, users are able to see and select fields on objects for which they do not have read permission. Vault does not include data for these fields in the resulting extract.
|
DEV-384685 |
|
Users experience an error and the load fails when using Vault Loader to upsert object records containing blank values for object reference fields.
|
DEV-385701 |
|
In rare cases, certain components are missing from exported VPKs even after refreshing the component directory.
|
DEV-387978 |
|
When a lifecycle state contains the same user action more than once, the state’s Atomic Security page may not load properly.
|
DEV-390756 |
| Description |
Issue No. |
|
Under certain circumstances, when users attempt to save a document with an unmet field dependency, Vault displays an alert instead of the expected error dialog.
|
DEV-362445 |
|
Attempts to render files fail with an “unsupported file type” error message when Vault is in Document Migration mode.
|
DEV-370685 |
|
In some cases, users are unable to select text in Microsoft PowerPoint™ renditions.
|
DEV-375156 |
|
When a user attempts to switch vaults or log in as a delegate user while an unclassified file upload is in progress, the browser displays a “Leave site?” warning. If the user then clicks Cancel, Vault displays a blank page instead of continuing the upload.
|
DEV-377117 |
|
After editing a Microsoft Excel™ worksheet and uploading the new version to Vault, users are unable to view the rendition or download the file.
|
DEV-381041 |
|
After editing and checking in a Microsoft Word™ template document, headers are missing from the source document and viewable rendition.
|
DEV-381262 |
|
In some cases, tokens in merge fields documents are resolved incorrectly and result in rendering errors.
|
DEV-383279 |
|
When a user attempts to edit the fields of an image file that has embedded metadata, Vault displays a “Server having problems” error.
|
DEV-384036 |
|
After an .RTF file fails to render, Vault displays an “unsupported file type” error message and does not allow the user to re-render.
|
DEV-384095 |
|
In some cases, when Vault auto-links an Adobe® Illustrator® file from an Adobe InDesign® package document, the icon and File Info section incorrectly indicate that the file is a PDF.
|
DEV-384580 |
|
Users are unable to upload a viewable rendition of password-protected PDF documents.
|
DEV-384582 |
|
When uploading a rendition, the Upload Rendition progress dialog is missing the header.
|
DEV-384621 |
|
When a user moves an annotation, the annotation becomes unselected and remains unselected when the user clicks it.
|
DEV-385362 |
|
Users are unable to upload a video file that is 3 GB or larger using the drag-and-drop action.
|
DEV-386820 |
|
In the Select Targets dialog, if a user unselects certain nested targets using the mini-browser, the list under the target document will render incorrectly.
|
DEV-389731 |
|
The Select Targets dialog incorrectly displays long document names that do not contain whitespace.
|
DEV-390312 |
| Description |
Issue No. |
|
When a user attempts to perform an inline update of an object reference field that already contains a value and the object has over 100 records, only the first 100 records are available for selection.
|
DEV-356948 |
|
In some cases, Vault fails to populate values for object reference fields with dynamic reference constraints when the referenced field value is null.
|
DEV-361299 |
|
After changing an object’s Data Store to High Volume, removing a field’s uniqueness requirement may not affect its search indexing as expected.
|
DEV-373906 |
|
If an existing standard volume object is edited to become a high volume object, users experience a server error when viewing records for other objects containing fields which reference text fields on the high volume object.
|
DEV-381428 |
|
Users may require Read access on object fields in order to edit user profile fields that are configured as editable in the profile layout configuration.
|
DEV-384333 |
|
Vault may display duplicate error messages when attempting to delete an object with multiple layouts using Related Document filters.
|
DEV-384624 |
|
Under certain circumstances, after renaming a field while in Record Migration Mode, queries of the renamed field’s values may fail if performed in the same MDL action.
|
DEV-384906 |
|
Under certain circumstances, Vault fails to import multiple Adverse Event Report records that reference MedDRA dictionary records.
|
DEV-389002 |
|
If the first field a user edits on their user profile is a text field, long-text field, or rich-text field, the Save button does not become enabled until the edited field loses focus.
|
DEV-389037 |
|
When a user attempts to edit a controlled object reference field in bulk, it remains disabled even if the user edits all controlling fields.
|
DEV-389100 |
| Description |
Issue No. |
|
In some cases, when attempting to access the page layout configuration for an object, Vault displays a “Server having problems” error.
|
DEV-359320 |
|
Under certain circumstances, binder exports take a long time to complete.
|
DEV-360887 |
|
Searching in the Document Number Format field in Document Type configuration may take longer than expected with non-English locale settings.
|
DEV-370443 |
|
In some cases, certain tabbed pages in Vault do not load in Internet Explorer 11.
|
DEV-372386 |
|
Vault may take longer than expected to start and cancel workflows for large numbers of users at the same time.
|
DEV-378290 |
|
When used in notification templates, Rich Text field values display as plaintext, including HTML tags. In 21R1.0, Rich Text fields will still display as plaintext, but without any HTML markup.
|
DEV-378613 |
|
In rare cases, Vault fails to load the Create menu when a user clicks the Create button from their Home tab.
|
DEV-382473 |
|
In some scenarios, Long Text fields do not display hovercards.
|
DEV-386598 |
|
Fonts and icons are larger in size on some Admin pages.
|
DEV-387099 |
|
On the user details page, section help icons (?) are mispositioned.
|
DEV-389231 |
| Description |
Issue No. |
|
In some cases, Vault doesn’t publish links correctly when the Planned Submission Date is set to a future date and the Published Output Location changes on the link’s source and target documents.
|
DEV-367505 |
|
In some cases, after publishing a grouped submission, Vault doesn’t include non-primary submissions in the “Where Used In Archive” section of the primary submission’s regional XML.
|
DEV-369260 |
|
Vault link annotations that were added to matched documents in quick succession do not appear in the published documents after continuous publishing runs.
|
DEV-371868 |
|
During continuous publishing, Vault does not publish links to published target documents correctly.
|
DEV-372269 |
|
Links are not published when continuous publishing is running at the same time as on-demand publishing.
|
DEV-373292 |
|
Vault does not publish a reference leaf when the letter case in the Published Output Location field doesn’t match the letter case of the document.
|
DEV-375076 |
|
In vaults with the “Automatic creation of Application Country records” setting enabled, Vault does not update the Country Decision Detail records related to the Application’s Regulatory Objective when the Application’s Lead Market changes.
|
DEV-375491 |
|
In the Content Plan Hierarchy Viewer, Vault does not scroll users back to their previous location in a content plan after users collapse a large hierarchy section when filters are applied.
|
DEV-375731 |
|
In the Content Plan Hierarchy Viewer, Vault does not scroll users back to their previous location in a content plan after users add new columns to the grid or resize columns.
|
DEV-375732 |
|
After importing a submission and the Dossier Status is Import Successful, Vault displays an orange icon in the Publishing Status field rather than a green icon.
|
DEV-376713 |
|
When a user updates a reference leaf so that the Published Output Location is within the current submission, continuous publishing does not create a placeholder for the reference leaf, and the submission metadata fields are not populated.
|
DEV-376830 |
|
The Published output order is not updated after reordering the Content Plan.
|
DEV-378650 |
|
When a published TOC document is unmatched from a Content Plan, Vault does not update it to a placeholder.
|
DEV-378690 |
|
Published TOC documents with TOC Content Plan Items are not up-versioned when the state is changed to Approved.
|
DEV-378733 |
|
Published content plans with matched documents do not include links that loop to one another.
|
DEV-380140 |
|
Users cannot download Publishing Progress details for Content Plans with a failed publishing status.
|
DEV-380519 |
|
Vault reports validation rules 11.10, 11.9, and 13.4 incorrectly for Swiss submissions.
|
DEV-381466 |
|
After users first publish a non-eCTD submission, the Validation Result Status on Submission Validation Results is Not Executed rather than Pass or Fail.
|
DEV-381524 |
|
During continuous publishing, Vault does not report Rule US5200 correctly.
|
DEV-381961 |
|
In some cases when multiple publishing jobs are triggered and one of the jobs fails, Vault does not generate XML renditions.
|
DEV-382463 |
|
Vault sometimes updates the icon in the Publishing Status field to green before all continuous publishing finishes.
|
DEV-382601 |
|
In some cases, when multiple continuous publishing jobs are triggered on non-eCTD submissions in a short period of time, Vault doesn’t display the latest versions of published documents in the Submissions Archive Viewer.
|
DEV-382883 |
|
In some cases, when multiple continuous publishing jobs are triggered in a short period of time, Vault does not publish the latest document versions during continuous publishing.
|
DEV-383285 |
|
In some cases, continuous publishing does not publish matched documents and links for non-eCTD submissions.
|
DEV-383297 |
|
When multiple continuous publishing jobs are triggered in a short period of time, Vault does not publish links on a document that was just unlocked.
|
DEV-383352 |
|
Vault publishes a Module 1 reference leaf when the Published Output Location contains “./” instead of publishing a placeholder.
|
DEV-383531 |
|
In some cases, when on-demand publishing is running for multiple Content Plans or Content Plan Items, Vault creates Submission Validation Result records with no values in the Content Plan or Content Plan Item fields.
|
DEV-383586 |
|
After selecting a large number of Regulatory Objectives in the bundling wizard, the Define Regulatory Objectives page is unresponsive.
|
DEV-384017 |
|
In some cases, Vault incorrectly reports Rules 2002 and 2012 as Fail.
|
DEV-384248 |
|
In some cases, documents are not published during continuous publishing when the XML Operation is updated from New to Delete and then quickly changed back to New.
|
DEV-384257 |
|
The Truncate Cell Text and Wrap Cell Text options do not work correctly in the Content Plan Hierarchy Viewer.
|
DEV-385166 |
|
During continuous publishing, Vault does not report Rule INFO_104 correctly.
|
DEV-385264 |
|
The “RMS Integration and Synchronization” job title does not appear on the Job Definitions page.
|
DEV-385467 |
|
Users cannot filter on the Notes field on the Content Plan or Content Plan Item objects in the Content Plan Hierarchy Viewer.
|
DEV-385476 |
|
On the Add New Details page in the Manage Registered Details wizard, the grid pane sometimes disappears when users select a Registration record or click Select All.
|
DEV-386981 |
|
On the Admin > Settings > Application Settings page, there is an unnecessary checkbox below the RIM Settings section.
|
DEV-388360 |
|
The Manage Registered Details wizard does not launch the registration verification workflow or capture changes in the Unverified Data object if document fields are required on the registration details or registered details.
|
DEV-390890 |
|
Under certain circumstances, when a user attempts to create two reference leafs to the same document published from a content plan, only one reference leaf is created.
|
DEV-390254 |
|
The user running a Configurable Impact Assessment Report is added to the report copy as a Viewer instead of as an Editor.
|
DEV-391403 |