Release Date: November 16 & November 30, 2018
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.
Last Updated: November 16, 2018
Admin
Description | Issue No. |
---|---|
When migrating Docfielddependencies via Migration Packages (VPKs) that have multiple dependency rules using a single Docfield (picklist type), the import can fail. | DEV-219754 |
Cascade delete on a lifecycle does not delete Vault Java SDK document actions configured for that lifecycle. | DEV-211632 |
Vault Configuration Migration packages allow users to add the “com.veeva.vault.system.DeleteRecordAndRelatedSignatures” object action, which should be hidden as a system action. | DEV-216812 |
When Admins attempt to import a VPK, Vault displays a “System Role [distribution_contacts__v] cannot be deleted” error even when that role does not display for the given lifecycle in the source or target vaults. | DEV-216048 |
EDL Matching job fails when matching on 20 fields. | DEV-216146 |
Vault allows Admins to change a user’s application license to External User without validating that their email address has a different domain than the customer domain. | DEV-220678 |
Renaming a required object reference field on an object with a custom object type can sometimes cause server errors on the vault. | DEV-220945 |
Brand & Medical Portal
Description | Issue No. |
---|---|
Brand and Medical Portals do not properly show the defined “Primary Color.” | DEV-216184, DEV-218221 |
Clinical
Description | Issue No. |
---|---|
Some users encounter a server error when attempting to extract Payable Items with Vault Loader. | DEV-211510 |
Developer Features
Description | Issue No. |
---|---|
For API versions below v18.3, the Retrieve Job Results endpoint returns a non-working artifact link for extensible controlled copy jobs. | DEV-215437 |
API calls made within the same millisecond may not count towards allowed API Limits. | DEV-207474 |
Vault displays a server error when users initiate the same Java SDK Document Action from the Actions menu if the action is configured on more than one lifecycle state. | DEV-216685 |
Vault doesn’t return correct results when users search for synonyms using VQL with parentheses. | DEV-216263 |
When adding a user to a second Vault that has custom required field on the user object via the API, Vault still completes the update even though the response returns a failure. | DEV-206298 |
When updating a user with a custom required field on the user object via the API, Vault still completes the update even though the response returns a failure. | DEV-206301 |
When users attempt to bulk create attachments via the API, Vault returns a failure but returns a success after users wait and try again. | DEV-214129 |
Documents
Description | Issue No. |
---|---|
Bookmark links in the Bookmarks panel have incorrect names. | DEV-217799 |
In rare cases, Vault fails to report Rule 5102 when a document matched to an EDL Item has a bookmark that is linked to a page or Destination that does not exist in RIM Submissions Publishing vaults. | DEV-213531 |
The “Render Native-Resolution Images for Raster & Vector Images in Word Files” feature does not process vector images inside text boxes. | DEV-214631 |
Vault does not recognize anchor annotations when re-rendering a document with Word rendition settings. | DEV-211279 |
Vault removes bookmarks pointing to Destinations that doesn’t exist when generating viewable renditions. | DEV-213949 |
When the column is narrow enough, the Check Out icon overlaps the Favorite icon in Library Tabular View. | DEV-212568 |
When uploading a document, Vault does not properly render WMF images. | DEV-210819 |
When viewing annotations in PDF with Annotation, the “Revise Text” has no placemark. | DEV-208782 |
Users are unable to use Enhanced Checkout. | DEV-220295 |
The Disable Vault Overlays setting is ignored for renditions with signature pages. This issue only affects basic overlays, not advanced overlays. | DEV-220301 |
Users with External User license type cannot access the Check Out to Vault File Manager action. | DEV-217373 |
In vaults with Dynamic Linking enabled, users cannot delete a document containing a permalink. | DEV-222337 |
The My Cart view does not show document version numbers. | DEV-222169 |
Lifecycle & Workflow
Description | Issue No. |
---|---|
From the multi-document workflow document viewer, users are not able to use the Check Out action on a document. | DEV-216784 |
If an Admin deletes the workflow configuration, users cannot complete the assigned multi-document workflow. Users see a server error. | DEV-214872 |
Some workflows experience slow performance. | DEV-222273 |
In some cases, failed VPK migration causes server errors. | DEV-222066 |
Localization
Description | Issue No. |
---|---|
Vault does not include German, Italian, Japanese, and Polish translations for Vault Loader entries in System Audit History. | DEV-214696 |
Multichannel
Description | Issue No. |
---|---|
Users cannot delete a document that is referenced by a Channel Usage object record. | DEV-219291 |
Objects
Description | Issue No. |
---|---|
Vault allows Admins to use Corporate Currency fields when defining default expressions of associated Currency fields. | DEV-218292 |
In some cases, Vault removes field labels from existing objects after changing Vault’s base language. | DEV-204647 |
Indian Rupees (INR) do not display correctly in Currency type object fields. | DEV-218768 |
Vault does not mask user names on hover cards when Dynamic Access Control is configured on the User object. | DEV-217514 |
When adding related documents from an object record, a green plus (+) icon appears in the Search dialog for users who don’t have appropriate permissions. | DEV-217868 |
Vault inactivates the legacy user when a user object with a custom, required field is made inactive with the “Make User Inactive” action. | DEV-206302 |
When a user profile is in the GMT+14:00 time zone, Vault returns a server error when saving an object record with date and time fields populated. | DEV-221160 |
The Workflow Timeline section is not always displayed in object page layouts. | DEV-218419 |
Performance & UI
Description | Issue No. |
---|---|
Documents with Merge Field WHERE clauses take a very long time to render. | DEV-205012 |
Object record list pages display “Loading…” message even after all records are loaded. | DEV-213194 |
Users navigating to Destinations in the document viewer experience slow performance when documents contain many Destinations. | DEV-214004 |
Vault home loads slowly. | DEV-203115 |
When over 80,000 users exist in a vault, batch user creation slows down. | DEV-207087 |
Mac users can see the “Check Out to File Manager” action while in the library tabular view. | DEV-206462 |
When adding related documents from an object record details page, the dialog shows “Search: undefined”. | DEV-219420 |
In some cases, the Doc Info page is slow to load. | DEV-222180 |
When creating a custom text field on an object, saving takes longer than expected. | DEV-219063 |
Quality
Description | Issue No. |
---|---|
When users start a checklist and then load that checklist from a Quality Event details page, they sometimes see a 404 error because the checklist has not finished processing. | DEV-213164 |
Documents’ Version History does not include a clickable link to the related Document Change Control (DCC). | DEV-206187 |
In some cases, when completing an action on a change control workflow, Vault gives a server error if the next action in the workflow is a system action. | DEV-211825 |
Reference constraints on various Checklist-related objects sometimes prevent users from creating checklists. | DEV-213052 |
Users cannot approve a Quality Event Checklist if the Weight% field value is Zero (0). | DEV-205103 |
Vault gives a server error when creating a checklist using the Create button on a Quality Event object record. To avoid this error, create checklists by selecting the Start Checklist option in the Actions menu. | DEV-233300 |
Reporting
Description | Issue No. |
---|---|
Reports with the Document Relationship report type do not show up in the list of Recently Viewed reports. | DEV-219524, DEV-220638 |
Reports that use a today() formula with a “user” parameter don’t return consistent results. | DEV-214214 |
The Task Queue Group filter does not filter multi-document workflow data. | DEV-212531 |
In some cases, chart legends on dashboards are illegible. | DEV-209488 |
In some cases, Vault returns inconsistent results when users run a Binder with Document report on a binder with sections. | DEV-222248 |
When users export reports as PDF files, the column widths are not the same as those in the saved reports. | DEV-221878 |
RIM
Description | Issue No. |
---|---|
When creating a Content Plan from a Content Plan Template, content plan creation fails if the initiating user doesn’t have Read permission to a field on the Content Plan, even if the field is not on the Content Plan object type. | DEV-219334 |
After the initial publishing of a submission, if users set Enable Continuous Publishing to “No”, add new Content Plans (EDLs) and Content Plan Items (EDL Items), and run on-demand publishing from the parent Content Plan, Vault publishes the new Content Plan but not the new Content Plan Items. | DEV-214694 |
After completing the Run On-Demand Publishing action on a parent Content Plan record of a form Content Plan Item record, other forms no longer appear in viewer. | DEV-218678 |
After enabling the bundling wizard feature, bulk creating registrations no longer populates the regulatory objective. | DEV-214654 |
After publishing a submission, Vault doesn’t display a list of available actions when users click the Actions menu while in binder List View. | DEV-218307 |
After the primary submission is published, sometimes the forms for non-primary submissions appear incorrectly in the US Regional XML. | DEV-214483 |
Content Plan Items that have never been published and have Continuous Publishing set to No will appear in the published index and regional XML files. | DEV-214336 |
Help Content for Gateway Profile fields is not correct or unavailable. | DEV-213083 |
If a lifecycle has been applied to the Product Report object, outdated Product Report records will not be set to inactive as part of the Create Product Report lifecycle action. | DEV-214818 |
If Medicinal Product or Medicinal Product Full Name records don’t exist in Vault, users cannot create Product Report or Product Report Item records of the Presentation object type. | DEV-209700 |
In exports of non-primary submissions, the index-md5 is not named correctly and is not located in the right place within the submission. | DEV-213001 |
In some cases when splitting regulatory objectives, if a user attempts to search for a record, Vault returns the user the first page of the wizard. | DEV-218150 |
In some cases, links on published documents of non-primary submissions lead to a Document Not Found error. | DEV-210187 |
In some cases, the US Regional XML does not contain correct content for subsequent grouped submissions. | DEV-217783 |
In some cases, users encounter a file not found error when attempting to download validation results from an attached EDL item on a published report level content plan. | DEV-211164 |
In the RIM Registration App, users receive an error when trying to edit the rim_product_report_view__v notification template. | DEV-211087 |
Matching/unmatching a document to/from an EDL Item for a non-primary submission does not trigger Continuous Publishing. | DEV-213162 |
On an attachment document, Vault sets the Operation Type on the Product Item Report to the Operation Type value set on the Product Data Submission record. | DEV-218524 |
Previous EV Codes of lengths greater than 128 characters will not create a Previous EV Code Product Report Item (PRI) record. | DEV-214641 |
Product Report Items (PRIs) with a lifecycle applied will not be set to Inactive on subsequent generation of the Product Report. | DEV-218943 |
Product Report record creation fails if there is no associated Medicinal Product Registration record. | DEV-212476 |
Records filtered by objects on a product report do not appear when Vault exports the report to CSV or Excel. | DEV-205474 |
Running on-demand publishing does not update the regional or index XMLs. | DEV-210921 |
The Create Related Records Wizard fails when using Controlled Vocabulary fields that are constrained. | DEV-213461 |
The Published document field on EDL Item is not cleared when users remove a content plan from the Submission record. | DEV-212846 |
The published source document of a report level content plan with a named destination pointing to either a bookmark or other named destination does not have the correct zoom settings. | DEV-212767 |
The Submission Archive viewer shows the download button when the user does not have download permission. | DEV-205327 |
The Submission object page layout does not include the Workflow Timeline section by default. | DEV-212588 |
Users without permission to access the Product Report Item object cannot view Product Report records in Viewer. | DEV-209298 |
Vault does not create a Product Report Item if the requesting user does not have view permission for the document. | DEV-211090 |
Vault doesn’t create a document via the Create from Document user action when multiple values are selected in a picklist field on the Content Plan Item record but only a single value is allowed on the document field. | DEV-205725 |
Vault fails to publish certain Report Level Content Plans and show “Error when bulkPublishDocuments: This relationship already exists.” | DEV-214267 |
Vault fails to publish subsequent grouped submissions after an initial grouped submission has been published. | DEV-217552 |
Vault gives a job failure notification after users copy a Product Report. | DEV-205446 |
Vault should ignore the Continuous Publishing setting when users initiate on-demand publishing and validation for an EDL Item. | DEV-211425 |
When a permalink in a report level content plant points to a valid Destination, Vault incorrectly reports RLCP103 in publishing validation results. | DEV-212626 |
When a user attempts to view the Product Report object without the proper permission, Vault returns a server error. | DEV-209117 |
When copying related data from a regulatory objective to a submission, Vault does not check for duplicates and you may see duplicate records on the submission joins. | DEV-208473 |
When creating a document from a template, Vault matches the document to a Content Plan Item as “System” and not as the user who performed the action. | DEV-217694 |
When creating a Product Report record, Vault does not use the label from the Presentation object type to populate the Product Report name field. | DEV-209780, DEV-217531 |
When creating multiple Medicinal Product Name Part records, Vault does not populate the Medicinal Product Name Part field on the Product Report Item record with the correct value. | DEV-209864 |
When generating an xEVMPD product view for a complex drug product, Vault creates the Product Report section for a Pharmaceutical Product even when the correct related data is not present. | DEV-212787 |
When generating an xEVMPD product view for a product with a concentration type that is not a range, Vault populates the strength values with concentration strengths rather than presentation strengths. | DEV-212860 |
When re-creating an xEVMPD product report, the Validity Declaration field resets from “1” to null. Users will need to set this back to “1” prior to XML generation. | DEV-214722 |
When re-generating the xEVMPD Product Report, any Product Report Item records that are re-used are not correctly set to the Active status and are left in an Inactive state. | DEV-214472 |
When using Firefox, the first time a user navigates to the Viewer tab, the tab is empty. | DEV-217319 |
If bundling is enabled, the Create Related Records wizard does not populate the Submission – Regulatory Objective join when creating Submissions and Regulatory Objectives. | DEV-216447 |
Vault cannot generate a TOC when processing large Report Level Content Plans with a TOC Content Plan Item. | DEV-216439 |
When creating a content plan from a template, Vault populates the table of contents with the picklist value name instead of the label. | DEV-209944 |
Vault populates the binder for invalid, subsequent submissions. | DEV-208894 |
Vault does not report validation rule 3036 when the XML application number is not 6 digits. | DEV-208498 |
Vault erroneously reports validation criteria 5005, 5020, and 3102 on published submissions. | DEV-206868 |
When an invalid grouped submission is configured, the forms for the invalid submission in the group are still published and displayed in the published Submissions Archive Binder and XMLs. | DEV-212132 |
Vault is not correctly rendering 2253 form in RIM Submissions. | DEV-219000 |
In some cases, when a single document matches to a different Content Plan Item within one Content Plan, Vault exports the document twice in the published binder. | DEV-222293 |
In some RIM vaults, field information is incorrect on the Controlled Vocabulary object. | DEV-222255 |
Bulk Create Registrations does not recognize GB and GR country codes for the United Kingdom and Greece respectively. | DEV-222214 |
Some users are unable to proceed through the bundling or splitting wizards if there are required Yes/No fields configured on regulatory objective object records. | DEV-222050 |
In some cases, the form for the non-primary submission within a Grouped Submission is incorrectly associated with the primary submission. | DEV-223023 |
Search & Filter
Description | Issue No. |
---|---|
In some cases, search modifiers do not work on picklist fields for certain document types. | DEV-218504 |
In some cases, the Perform Bulk Actions option does not show in the library after enabling the feature. | DEV-212086 |
Some “All of these words” Advanced Searches return results with partial matches. | DEV-202726 |
The new “Search with Filters” feature is not working for standard views, for example, My Documents and Recent Documents. | DEV-220823 |
Security
Description | Issue No. |
---|---|
When editing a permission set, Admins are not able to remove permissions for locked tabs. | DEV-216019 |