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. |
|
For some users, Pull CRM Inquiries updates all cases and case requests.
|
DEV-276791 |
|
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 |
|
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 sandbox, Vault sends welcome emails to inactive Domain Admin users.
|
DEV-277749 |
|
Migrating Vault Membership lifecycle through Configuration Migration is no longer supported.
|
DEV-272796 |
|
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 |
|
When creating a new object action, the object does not contain the appropriate Typeaction MDL attribute if you select an existing record action to use as the new object action.
|
DEV-285473 |
|
In some cases, users receive a Page Not Found error when changing the type of a person record.
|
DEV-285334 |
|
When editing the dataset of an outbound package for record migration, the “User User Name” and “User Federated ID” fields are not in the correct columns.
|
DEV-286264 |
|
Creating a document from a template uploaded with Merge Tokens, some data may not be rendered upon initial creation.
|
DEV-283619 |
| Description |
Issue No. |
|
A server error may appear when completing a Monitoring Event requiring no changes.
|
DEV-278049 |
|
The “Promote Person to User” action creates a new person record rather than linking back to the user, creating duplicate records.
|
DEV-283036 |
|
In some vaults, attempting to create a Site record results in a server error.
|
DEV-271305 |
|
When using Veeva Clinical Network, Vault encounters an error when a study is transferred without a CDX ID value.
|
DEV-282379 |
|
When using Veeva Clinical Network, the global ID and link fields are causing document transfer to fail.
|
DEV-277616 |
|
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 |
|
Some users are unable to edit monitored subject when study metric calculation is date-based.
|
DEV-284500 |
|
Vault drops Kanji characters when generating trip reports in Japanese.
|
DEV-279709 |
|
Some users are unable to create trip reports as part of completing a task in an object workflow.
|
DEV-278301 |
|
In rare cases, Vault encounters an error when running the Create Metrics Over Time job.
|
DEV-275374 |
|
The “Tasks Requiring Attention” widget on the SSU home page loads twice when toggling from a numeric count to a list view.
|
DEV-284226 |
|
In some situations, eTMF does not populate milestones on a document upon upload.
|
DEV-280914 |
|
When classifying a previously unclassified document, a previously removed Study may be added back to the document.
|
DEV-284882 |
|
In some cases, the Product field on documents does not obey field dependencies.
|
QA-47852 |
|
Vault does not update the Completeness and % Complete fields for milestones.
|
DEV-284827 |
|
Some users see an error when they attempt to create more than 500 payable events using Batch Payment Requests.
|
DEV-284603 |
|
When some users bulk update the study values on documents, the product values are not automatically defaulted as expected.
|
DEV-285826 |
|
For some users, the Function field disappears from the page layout for the Study Person object after Person Migration is enabled on their vault.
|
DEV-285822 |
| Description |
Issue No. |
|
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 |
|
After disabling the rendition setting ‘Generate bookmarks for Title Style’, Destinations for title styles are not displayed in the viewable rendition
|
DEV-265464 |
|
For some users, checking out a large file with Collaborative Authoring takes over a minute.
|
DEV-274367 |
|
In some cases, Vault does not generate suggested links for MSG files when there is a match in the text.
|
DEV-275562 |
|
Some users are able to API batch create new versions of documents that have been checked out with Collaborative Authoring.
|
DEV-276124 |
|
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 |
|
On Microsoft Edge browsers, when users open a document that is already checked out, Vault wraps the text in the banner message.
|
DEV-279262 |
|
With Auto-Linking enabled, users can create duplicate references for a Claim record if the Target Document Type is disabled and re-enabled between creating references.
|
DEV-273124 |
|
In certain situations with canceled checkouts to Collaborative Authoring, there are file conflicts.
|
DEV-280388 |
|
While ultimately uneditable, the Edit button is displayed for the “Check out type” document field
|
DEV-271295 |
|
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-276672 |
|
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 |
|
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 |
|
In rare cases, documents utilizing Merge Fields may not correctly merge upon initial rendering and may require a field update to correct the rendition.
|
DEV-271258 |
|
For some users, PDFs with one or more invalid bookmark are not displaying in the Document Viewer.
|
DEV-285896 |
|
Some users are unable to edit and save a document when the document type has a required field dependency on a hidden or read-only field.
|
DEV-285541 |
|
Documents fields delineated as “hidden” are uneditable even when the field is required via a field dependancy.
|
DEV-285354 |
|
Sometimes, Vault displays the encrypted form of a file as the viewable rendition when uploading encrypted source files via API.
|
DEV-287788 |
|
In some cases, Vault does not generate renditions for audio or video files.
|
DEV-287795 |
| Description |
Issue No. |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
Vault intermittently schedules the RIM Publishing Validation Monitor job twice.
|
DEV-257565 |
|
Vault sometimes does not render XML documents from imported submissions.
|
DEV-255920 |
|
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 |
|
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 |
|
When a user selects a different application in the Submissions Archive Viewer, the link to the application record in the Viewer header directs the user to the record detail page for the previous application.
|
DEV-282537 |
|
Users experience slower than usual performance after selecting the Excel Tree with All Descendants export option from the Hierarchy Viewer.
|
DEV-280455 |
|
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 fails to report PDF validation rules after a user makes a Content Plan Item record inactive and the continuous publishing job runs.
|
DEV-279029 |
|
When a document template includes a TOC bookmark token without words – bookmark() – Vault doesn’t generate the TOC with bookmarks.
|
DEV-278435 |
|
Users experience slow performance when publishing report level content plans containing links.
|
DEV-278176 |
|
Vault fails to apply a defined dossier format to eCTDs imported via the FTP.
|
DEV-277662 |
|
Users are unable to open the dossier review panel in Safari.
|
DEV-276587 |
|
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 |
|
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 |
|
Users experience slow performance in the Submissions Archive Viewer when expanding a section that contains 10,000 documents.
|
DEV-275284 |
|
Vault doesn’t update the binder structure correctly when a user sets an STF XML Content Plan Item record to Inactive.
|
DEV-275240 |
|
In some cases, when publishing submissions for Canadian validation, bookmarks and hyperlinks targeted to unknown destinations are reported with incorrect validation results.
|
DEV-274693 |
|
In the Submission Administrative Information viewer, Vault should display excluded values at the bottom of the screen.
|
DEV-274059 |
|
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 |
|
Users sometimes experience slow performance when publishing large content plans.
|
DEV-272908 |
|
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 |
|
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 |
|
After a user uploads a submission with an invalid index.xml to the FTP, attempts to import it, and then uploads a valid index.xml, the import still fails.
|
DEV-277585 |
|
When creating investigational registrations through the Create Registrations wizard, if a user removes a Clinical Study record through the search dialog rather than clicking the X icon directly on the value in the field, the user will not be able to proceed to the next step.
|
DEV-280483 |
|
Some users see unfiltered values of opposite parent objects when relating multiple complex join records through a dialog.
|
DEV-284800 |
| Description |
Issue No. |
|
Users experience slow performance when running reports configured with multiple columns containing web links.
|
DEV-266956 |
|
Selecting Document State Type as a column in some Multi-Pass report types results in a server error.
|
DEV-268805 |
|
When running a Multi-Pass report on a workflow view after removing the Workflow Name column, users experience an error.
|
DEV-271975 |
|
In certain cases, users experience server errors when running reports configured with summary calculations on document formula fields that return dates.
|
DEV-277367 |
|
In rare cases, users experience a discrepancy between the data displayed in dashboards and their reports.
|
DEV-278776 |
|
When grouping on Task Instructions in a Workflow with Documents report, the total count on “None” is inaccurate.
|
DEV-282289 |
|
Object Reference field to Object Reference fields joins do not create a useful Multi-Pass Reports and can create server issues. Vault should prevent users from creating these reports.
|
DEV-284632 |
|
In some vaults, the bands on gauge charts are not displayed correctly.
|
DEV-277428 |
|
When some users run an upgrade task to replace one field with another field, one corrupted report can cause the whole upgrade to fail.
|
DEV-285673 |
|
Reports and VQL queries time out when returning large numbers of documents with unbounded relationships.
|
DEV-282439 |
| Description |
Issue No. |
|
Vault Safety does not currently support user access control for Expected Adverse Event records configured on a Product Datasheet. Any user can view the Expected Adverse Event records for any organization in their vault. Vault Safety does not currently support blind protection for the Expected field on Case Assessments.
|
SAF-1987 |
|
When adding or updating a Case Product Indication, Vault Safety does not recalculate the Case expectedness. This issue affects environments where a suspect Product Datasheet lists the reported adverse event as expected, qualified by the same medical condition reported on the Case Product Indication. In this scenario, the system determines that the adverse event is unexpected instead of expected.
|
SAF-1996 |
If you try to assign an External-type Case Product a rank of 1, an unclear error message similar to the following appears:
Primary Field: Field [external__v] is not valid for Object Type [{1}].
If you see this error message, note that the rank of 1 is reserved for primary Case Products. External Case Products cannot be assigned the primary role.
|
SAF-2233 |
|
When you create a Follow-Up Case, the Language (ISO) field on the Follow-Up Case translation document may be updated to English. This issue occurs when the Language (ISO) field on the initial case narrative translation document is blank, due to an E2B import with an invalid language code.
|
SAF-2372 |
If a Case meets the following conditions, it is included in both 15-day and Non-15 day alert PADER tables:- The Case criteria is set to Serious and Unexpected.
- The Case Assessment Result > Result field is to No Reasonable Possibility.
|
SAF-2498 |
|
For Reporting Families set up to use the FDA reporting ruleset, the system still generates Transmission record(s) when a Case Product or Study Registration is set to a non-USA country.
|
SAF-2905 |
|
When you merge a PDF from a binder containing a high number of documents, if any documents do not have a viewable rendition, the vault warning notification and email are truncated after a certain limit (approximately 35 documents) and do not contain the full list of documents.
|
SAF-3237 |
|
In the Parental Case field, if you link to a case with the object type as Case (case__v) instead of Parental Case (parental_case__v), you will not be able to generate a valid E2B file. If you generate an E2B file, the file will contain multiple primary records, such as Case Product, Case Adverse Event, and Case Reporter.
|
SAF-3341 |