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 migrating a custom tab via VPK, Vault cannot handle labels greater than 40 characters.
|
DEV-256342 |
|
In some cases, Vault Loader fails when extracting object records.
|
DEV-273901 |
|
When creating a sandbox, Vault sends welcome emails to inactive Domain Admin users.
|
DEV-277749 |
|
When an Admin updates a Pending state user’s security profile from the legacy user page, the Pending state user moves into the Inactive state.
|
DEV-273233 |
|
When an Admin changes the domain status on a Pending state user to Inactive, the user account is not moving to the Inactive state on the vault where it’s currently Pending.
|
DEV-278024 |
|
Some users are unable to push case records to CRM when the records are in the closed state or updated.
|
DEV-277381 |
|
For some users, Pull CRM Inquiries updates all cases and case requests.
|
DEV-276791 |
|
The Delete button is visible when attempting to delete a Type Field for a standard object, which cannot be deleted in the UI. Attempting to use the button results in an error.
|
DEV-272901 |
|
A server error may occur when creating a Session on a Class Schedule record.
|
DEV-271156 |
|
Migrating Vault Membership lifecycle through Configuration Migration is no longer supported.
|
DEV-272796 |
|
Admins see a server error when attempting to delete an object field that’s used in a workflow. They should see an error that explains what has happened.
|
DEV-279652 |
|
Admins are able to assign Vault Owner and System Admin security profiles to user records in Pending state. This should be blocked.
|
DEV-279869 |
|
When creating a new User record by selecting an existing domain user, Vault populates the user details but the Domain User field shows as blank.
|
DEV-275167 |
| Description |
Issue No. |
|
On the Enrollment Status Graph, Vault does not display an aggregate number for date-based metrics that are calculating for metrics over time.
|
DEV-277705 |
|
When Person Organization & Migration is enabled, Vault updates the Monitoring Visit Participant field on all Study Team Roles to “Included”. Additionally, Vault updates the Monitoring Visit Participation field on the Principal Investigator and Site Monitor Study Team Roles to “Included & Invited.”
|
DEV-275788 |
|
In some cases, Vault cannot create placeholders in bulk.
|
DEV-271101 |
|
In some vaults, attempting to create a Site record results in a server error.
|
DEV-271305 |
|
When transferring data using Veeva Clinical Network, Vault sometimes ends agreement processing if there is a failure in the document transfer process.
|
DEV-277210 |
|
Users are unable to select the “Study Does Not Already Exist” option if the study record in their vault has a required field that is either not required or blank in the initiator vault.
|
DEV-278882 |
|
In some cases, the CDX Pending Scope Variable Value object is visible in vaults without Veeva Clinical Network enabled.
|
DEV-279074 |
|
When the Clinical Network Connection is initially inactive, users are able to create and send agreements without an error message, however, Vault will not transfer object records or documents.
|
DEV-277385 |
|
For some users, Vault reports the error: “Unable to create pending record due to configuration issues. Please create a temporary record and map it to the incoming record.” when attempting to complete an agreement workflow even though there is no configuration error.
|
DEV-277414 |
|
In some cases, Vault encounters a server error when attempting to resolve a CDX mapping issue.
|
DEV-274292 |
|
Vault encounters an error if a user runs the Update Metrics Job and the Arm Based Metric? field is null.
|
DEV-277977 |
|
In rare cases, Vault encounters an error when running the Create Metrics Over Time job.
|
DEV-275374 |
|
Some users are unable to create trip reports as part of completing a task in an object workflow.
|
DEV-278301 |
|
Some users are unable to add a new trip report section to a Monitoring Event page layout.
|
DEV-279357 |
|
Vault drops Kanji characters when generating trip reports in Japanese.
|
DEV-279709 |
|
A server error may appear when completing a Monitoring Event requiring no changes.
|
DEV-278049 |
|
In some situations, eTMF does not populate milestones on a document upon upload.
|
DEV-280914 |
| Description |
Issue No. |
|
After disabling the rendition setting ‘Generate bookmarks for Title Style’, Destinations for title styles are not displayed in the viewable rendition
|
DEV-265464 |
|
In some cases, a bookmark may lead to an incorrect document location if its associated Word fields are out of date.
|
DEV-268664 |
|
In vaults with the Rendition setting ‘Set link text to blue’ enabled, some Arabic text in close proximity to link text may incorrectly render in blue.
|
DEV-267718 |
|
For some users, checking out a large file with Collaborative Authoring takes over a minute.
|
DEV-274367 |
|
Some users are able to API batch create new versions of documents that have been checked out with Collaborative Authoring.
|
DEV-276124 |
|
Some users see a “file not found” error message when they attempt to download uploaded renditions from FTP inbox.
|
DEV-277357 |
|
Some users see an “Error transcoding video” message when they attempt to make a copy of a video file.
|
DEV-277380 |
|
When some users configure a document type with a global ID set to “regenerate name on save,” the global ID field does not populate.
|
DEV-274266 |
|
For some users, the Edit button for Collaborative Authoring appears on Planned documents and displays a server error when clicked.
|
DEV-277638 |
|
Some users see a server error when attempting to edit some documents with Collaborative Authoring.
|
DEV-277066 |
|
While the action ultimately fails, the Compare Version action menu item appears in the Version History dialog even if a user does not have the View Content permission on both versions.
|
DEV-276636, DEV-276672 |
|
Vault does not generate suggested links for the Claims object when the object has picklist and field values while the document does not have equivalent fields.
|
DEV-277671 |
|
In some cases, Vault does not generate suggested links for MSG files when there is a match in the text.
|
DEV-275562 |
|
Vault does not generate suggested links if the matching text contains certain special characters, such as <, >, ≥, or ≤, without a space character to separate them from other characters.
|
DEV-276466 |
|
If you create a draft of a checked-out document with API >v19.3, the checkout is canceled, but Collaborative Authoring with Microsoft Office still shows the document as checked out.
|
DEV-276279 |
|
While ultimately uneditable, the Edit button is displayed for the “Check out type” document field.
|
DEV-271295 |
|
On Microsoft Edge browsers, when users open a document that is already checked out, Vault wraps the text in the banner message.
|
DEV-280388 |
|
In certain situations with canceled checkouts to Collaborative Authoring, there are file conflicts.
|
DEV-279753 |
|
When using Find in Document, Auto Claims Linking, or certain annotations, Vault cannot find documents by searching on words that use combining characters (ä, ü, etc.).
|
DEV-274469 |
| Description |
Issue No. |
|
When a user views a sub-folder in the viewer, Vault does not display the Back to previous page link.
|
DEV-265175 |
|
Vault is unable to create viewable renditions of XML files for some SPL imports.
|
DEV-262088 |
|
For Canadian submissions, when a user overwrites the initial submission description within the Submission Administrative Information with a blank value, the initial value is published instead of the blank value.
|
DEV-268774 |
|
Users are unable to open the dossier review panel in Safari.
|
DEV-276587 |
|
Users are not notified when they select inactive submissions records for inclusion in a bulk import.
|
DEV-276260 |
|
In some cases, users experience a “Page not Found” error when clicking links in the Application Selector menu in the Submissions Archive viewer.
|
DEV-273378 |
|
In some cases, document fields for merged document PDFs in submission ready binders are not populated when publishing report level content plans.
|
DEV-277699 |
|
In some cases, when publishing submissions for Canadian validation, bookmarks and hyperlinks targeted to unknown destinations are reported with incorrect validation results.
|
DEV-274693 |
|
Users are unable to change the status of document fields when multi-select is enabled.
|
DEV-278052 |
|
Users experience slow performance when publishing report level content plans containing links.
|
DEV-278176 |
|
Vault doesn’t include a published document in a merged PDF if the Owner role on the Submission Ready document lifecycle does not include the Edit Document permission on the Published state.
|
DEV-277898 |
|
Users can’t open the Manage Submission Administrative Information page from a content plan that was copied from another content plan and that contains two join records for the same country.
|
DEV-278319 |
|
Vault fails to report Rule 5205 when an EDL Item record is changed from active to inactive, when Continuous Publishing is set from No to Yes, or when the Published Output Location is changed.
|
DEV-272329 |
|
In some cases, users experience slow performance when publishing a document containing 2,000 or more pages.
|
DEV-274112 |
|
Vault intermittently schedules the RIM Publishing Validation Monitor job twice.
|
DEV-257565 |
|
Vault fails to apply a defined dossier format to eCTDs imported via the FTP.
|
DEV-277662 |
|
Target link page numbers are incorrect in validation error details when a user creates a permalink to a specific document page.
|
DEV-266981 |
|
In some cases, users in RIM Submissions vaults experience slow performance creating a binder from a content plan when the binder contains 500 or more documents.
|
DEV-266695 |
|
After publishing a submission, if a user updates the Continuous Publishing field to No on a Content Plan Item record matched to a link target document and then runs on-demand publishing from the root Content Plan record, Vault removes the permalink from the source document and doesn’t republish the target document.
|
DEV-266213 |
|
Vault sometimes fails to delete Submission Validation Result records after the Validation Results Archival job runs and attaches the ZIP file to the Content Plan record.
|
DEV-265907 |
|
Users experience slow performance in the Submissions Archive Viewer when expanding a section that contains 10,000 documents.
|
DEV-275284 |
|
When an Admin configures a Gateway Profile and uploads a certificate that is in an incorrect format, the Admin sees a server error instead of an error message.
|
DEV-275972 |
|
Vault displays values in the wrong columns for Rule 5200 in the Detailed Publishing Results section on the Submission Validation Result record, and the continuous validation job clears the values in the table and leaves the columns blank.
|
DEV-261140 |
|
The report level publishing job fails and Vault unmatches a matched document when a user upversions a version-locked document and republishes the report level content plan.
|
DEV-276225 |
|
Vault doesn’t update the binder structure correctly when a user sets an STF XML Content Plan Item record to Inactive.
|
DEV-275240 |
|
In the Submission Administrative Information viewer, Vault should display excluded values at the bottom of the screen.
|
DEV-274059 |
|
When a document template includes a TOC bookmark token without words — bookmark() — Vault doesn’t generate the TOC with bookmarks.
|
DEV-278435 |
|
In the Submissions Archive Viewer, when a user selects the Historical Lifecycle for the document and clicks the document link, Vault should open the Doc Info page with the Dossier Review Panel displayed.
|
DEV-276513 |
|
When the RIM Submission Publishing job runs on a submission with over 20,000 content plan items, Vault creates the binder and users can access the published documents, but the Job Status shows “Running (95%)”.
|
DEV-268732 |
|
After the continuous publishing job runs, Vault fails to remove Rule 1425 when the source document has been included on the source Content Plan Item record.
|
DEV-272057 |
|
When a user adds a Submission Country join record on a published submission where overrides have already been added in the Submission Administrative Viewer, Vault fails to highlight the overrides in bold and use them as the default value for the new country.
|
DEV-269718 |
|
Vault fails to remove Rules 1323 and 1425 when a document is matched to a source Content Plan Item record and published as part of the continuous publishing job.
|
DEV-272234 |
|
Users sometimes experience slow performance when publishing large content plans.
|
DEV-272908 |
|
A network error message may occur when opening a placeholder document from the submission archive list view.
|
DEV-277227 |
|
Merging a PDF may fail if Published Document field is null or empty.
|
DEV-276989 |
|
Under certain conditions, permalinks may not update properly when uploading a new version of the target document after approval.
|
DEV-277202 |
|
Vault sometimes can’t resolve the Table of Contents in a newly-created document after a user selects the Document from Template action from a Content Plan Item record.
|
DEV-280377 |
|
Users experience slower than usual performance after selecting the Excel Tree with All Descendants export option from the Hierarchy Viewer.
|
DEV-280455 |
|
Vault fails to report PDF validation rules after a user makes a Content Plan Item record inactive and the continuous publishing job runs.
|
DEV-279029 |
|
Vault truncates unresolved tokens during publishing.
|
DEV-280376 |
|
Vault fails to up-version the source document when a user approves the source document and target document at the same time after publishing.
|
DEV-280239 |
|
Vault creates an incorrect number of Registrations records when the Product Variant field is populated on a Submission Product join record and the referenced product is complex.
|
DEV-280071 |