Pre-Release Date: March 18, 2019 | Release Date: April 12 & April 19, 2019


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: March 18, 2019

Admin

Description Issue No.
When setting a default field value for a date field, Vault does not allow Admins to enter a 1-9 month or day value with a leading zero.   DEV-233428
Under certain conditions while using VPKs or MDL, Vault allows Admins to create more than one page layout for a single object type.   DEV-223084
When users attempt to delete an object field that is referenced in layout rules, the error message does not show all layout rules that use the field.   DEV-232303
In the Create Layout Rules dialog, Vault cuts off the referenced object name if it exceeds 21 characters.   DEV-232769
When setting a default value for a picklist field on an object, Vault does not properly represent the valid format: Picklist.field name.value name.   DEV-236784
When creating a document via Vault Loader and a failing Event Action follows a succeeding Event Action, Vault Loader still successfully creates the document.   DEV-225070
When using Vault Loader to extract a document with a large number of multi-value object reference fields, Loader does not extract all the values.   DEV-235562
When using Map Fields in Vault Loader, Vault displays role assignment fields as lookup fields when selecting the Document object type, but does not display them as lookup fields when selecting the Document Versions or Document, Versions, Roles object types.   DEV-235986
Admins cannot delete a custom security profile if it is used by an Auto Managed Group.   DEV-239387
Field dependencies based on document lifecycle are able to use the Unclassified and Staged lifecycles.   DEV-240757
When converting a DateTime value to Date in order to perform a function (dateDiff, for example), the system uses UTC for object lifecycle and workflow usages and Vault object usages, but Vault Time Zone for other usages. The fix for this issue will change all usages to use Vault Time Zone.   DEV-240326
Admins sometimes see errors applying layout rules when there are deleted object type page layouts that control the same fields.   DEV-240337

Clinical

Description Issue No.
For some users, hover cards do not appear when hovering over the Completeness Status of an expected document.   DEV-234927
Some users are not able to enable the Person & Organization Migration feature for their vaults.   DEV-229168
When viewing records from the Site Activation Progress tab, Vault incorrectly displays the filter “All EDL Item”.   DEV-234733
Vault encounters an error when attempting to update person records that have other person records that reference the same user.   DEV-228941

Commercial

Description Issue No.
Vault fails to generate Automated Image Renditions in some cases with large files or complex transformations.   DEV-230548
When uploading PDF, IMAGE or HTML documents to vaults with CLM enabled, Vault displays an error reading “A viewable rendition does not exist for this document. An Admin can re-render the document, or a user can upload a new viewable rendition” after the user clicks save, however, the document will display correctly after the user refreshes the page.   DEV-237174
In the Approved Email portal, users experience incorrect highlighted tabs and breadcrumbs in some cases.   DEV-218347

Developer Features: API

Description Issue No.
After creating document versions in bulk with the REST API, the Library sometimes shows multiple versions for the same document.   DEV-232238

Developer Features: SDK

Description Issue No.
If one of the vaults in a vault-to-vault connection is deleted, users receive a server error when trying to interact with the connection record.   DEV-236788
Previously, when you get documentVersion from DocumentActionContext, it only returns document ID. Now, getting documentVersion from DocumentActionContext retrieves all document fields. The Vault Java SDK does not have permission to set some fields, so existing SDK may break from this change.   DEV-238193
When troubleshooting message processing errors in a queue, users receive the Error Message “Exception occurred” instead of “Http Resp Code: 403”.   DEV-236954
Users can edit the Remote Vault ID on a Vault-to-Vault connection record.   DEV-237151
If a user uploads a Connection file from an established connection to a new vault, the error message indicates the connection failed rather than indicating the connection file is already in use.   DEV-237164
When creating a Vault-to-Vault Connection, you can set an invalid value as the Remote Vault ID. For example, “abc”.   DEV-237175
Users cannot delete a Connection record which was previously associated with a queue, even if the record no longer references the queue.   DEV-237283
When creating a Vault-to-Vault Connection, if you change the Remote Vault ID in the downloaded Connection file and attempt to connect to the new vault ID, the connection record in the source vault moves to the Active state even though the connection fails to establish.   DEV-237349
When a user in the target vault does not have the Workflow: Start permission, uploading a connection file produces an error message that states “Connection created failed unexpectedly” rather than an error message about permissions.   DEV-237358, DEV-237362
Deploying a package with the Vault Java SDK Deployment Option Delete All deploys with an exception stating “An unexpected error occurred” instead of informing the user there are Message Processors associated to inbound queues.   DEV-238196
Message Processors created as placeholders during Configuration Migration are available for selection when creating or editing inbound queues.   DEV-237891
When attempting to create a Content Plan Item which initiates an SDK trigger, users see an Out of Memory error.   DEV-238528

Developer Features: VQL

Description Issue No.
When using a nested VQL SELECT query to retrieve the count of large data sets, Vault returns incorrect results.   DEV-233809

Documents

Description Issue No.
Vault displays a server error when creating a child document type under document type Case > Source.   DEV-219069
In some cases, after re-rendering a document and changing rendition settings, the Rendition Profile field is set to blank rather than Custom.   DEV-237003
When navigating through documents in a binder, the count of documents incorrectly shows 1 of 1, 2 of 1, etc. when there are many documents.   DEV-219845
When creating a new document through a Supporting Documents relationship on an existing document, document creation fails with a server error if Vault triggers an event action on the new document.   DEV-237147
In situations where a document lifecycle has two or more document types with different fields, performing an action (creating or copying a document) that triggers an event action to update a document field can cause a server error when the field to update does not exist on the document type.   DEV-237284, DEV-240424
After classifying an unclassified document, it does not render with the correct rendition profile.   DEV-238678

Lifecycle & Workflow

Description Issue No.
The Change Related Object lifecycle state action does not work if the referenced document version is “Specific Version”.   DEV-237493
The dateDiff() formula sometimes returns incorrect output when used to set a field with a formula in an entry action.   DEV-238230

Objects

Description Issue No.
In an object record page, when users are creating a new record from a related object section, the navigation panel does not always update to highlight the right section.   DEV-236231
When viewing object records in a related object section, Vault allows users to modify values on the related object record.   DEV-216755
In an object record page, the navigation panel does not always update to highlight the right section when users are navigating by scrolling.   DEV-235760
In layout rule configurations where the rule expression uses a field that’s not included in any page layout, Vault does not hide fields correctly on the initial record creation page.   DEV-233901
In objects with record locking functionality, Vault sometimes allows one user to save a conflicting change and does not show an error.   DEV-237558
In objects with record locking functionality, Vault sometimes allows one user to save a conflicting change and does not show an error. This occurs when the record has never previously been edited.   DEV-238653
In certain configurations with dynamic reference constraints, the object record page shows a field enabled which should be disabled until the controlling field is populated.   DEV-236623
When a record details page loads, some sections with required fields do not automatically expand. When users try to expand these sections, they open and immediately close again. This only affects certain objects.   DEV-238729
In object record details pages, document reference links do not function in some situations.   DEV-240208

Performance & UI

Description Issue No.
When using the Checkout to Office Online™ feature in Internet Explorer™ 11, the tab icon does not change to the proper Office Online™ icon. When returning to Vault from Office Online™ in Firefox ® , the tab icon does not change to the proper Vault icon.   DEV-228280
Rendering documents with overlays make take additional time.   DEV-236720
In some Parent Object records, the DateTime field format is a single field instead of separate date and time fields.   DEV-215961
Admins are unable to save SAML profiles.   DEV-216461
When creating a custom currency field, users experience a server error if they enter a string as the value.   DEV-216779
Admins experience slow performance when configuring tabs.   DEV-217561
When viewing an object record detail page with no attachments, Read-Only users are unable to expand the attachments panel.   DEV-238307
In the object record detail page, record select dropdown fields incorrectly display a “no records available” message.   DEV-236440
Users are able to edit disabled controlled record select fields if they are configured to be in a different details section than the controlling field.   DEV-229667
When a user creates a child field, the parent object reference field is not auto populated.   DEV-229881
In the object record detail page, users are unable to tab to the lookup icon in the document reference field.   DEV-235826
Running a Workflow History Report with the Action column takes too long to load (4.5 seconds).   DEV-227863
Adding or removing fields in the Searchable Object Fields page has poor performance.   DEV-232143
The Document Inbox sometimes loads slowly.   DEV-232272
Notification emails show newline characters as “
” rather than rendering them as new lines.
 
DEV-239253
When authenticating on an iPad™ or iPhone™, the User Name and Password fields show spelling suggestions.   DEV-239204
After checking in a document from Office Online™, the Vault page does not render correctly and must be refreshed. This only affects Chrome, Safari, and Firefox browsers.   DEV-238637
Rarely, Actions menus open in the wrong place on the screen.   DEV-237022
Some users experience slow performance when using Chrome with the LastPass browser extension.   DEV-242660

Quality

Description Issue No.
In some cases, Vault displays a server error when adding or removing members on a Quality Team for a related record with a specified trigger, such as an Extension Request with a due date of the current date.   DEV-235385
Vault displays a server error when a non-Admin user without the Quality Teams security permission attempts to save a record with a Quality Team.   DEV-237141
In a Quality vault with Quality Teams enabled, Vault displays a server error when clicking on an object lifecycle state if the object lifecycle is not associated with an object.   DEV-237381
Formatted Output timestamp tokens appear in the incorrect format.   DEV-237340
A new matching field pair overwrites an existing matching field pair in a Checklist record if the only difference in the new matching pair label is an added space between words.   DEV-236816
Vault displays a server error when creating a Checklist Type targeting a Quality Event object.   DEV-237461
QualityOne displays a server error when a user that does not have Workflow > Participate permission starts a workflow that creates a task.   DEV-238210, DEV-231908
The following join objects in Quality QMS vaults should not include the External ID field: related_audit__qdm, related_quality_event__qdm, capaquality_event__qdm, product_quality_event__qdm, context_organization__qdm, contextquality_event__qdm.   DEV-238602
Vault Quality includes a new object type for Checklist Design. This object type should be inactive.   DEV-238979

Regulatory

Description Issue No.
After publishing a Report Level Content Plan, Vault does not remove bookmark links in documents matched to Content Plan Items, and clicking a bookmark link leads users to a Document Not Found page.   DEV-224795
When viewing a Product Report, users can’t see child Product Report records in the master hierarchy pane.   DEV-223225
After creating a content plan, users receive a success email and Vault notification, but the RIM Submission Plan Creation job still shows as Running (100%).   DEV-230154
Users cannot delete Controlled Vocabulary records that are updated or loaded with the Vault RIM UUID field populated.   DEV-236805
During the publishing process, Vault erroneously reports Rules 11.11, 15.1, and 15.BP3 on Content Plan Items with Continuous Publishing and Continuous Validation set to No.   DEV-237286
When the XML Modified File field on the Content Plan Item is incorrect on a published Submission and a user updates the field to the correct value, Vault continues to report the Rule 11.9/11.BP1 validation error.   DEV-237290
When attempting to submit a Submission through the EMA Gateway, the Submit to US FDA ESG action should fail if the binder export completes with errors.   DEV-219513
Adding overrides on the Common Administrative Information screen and then excluding a value on a Country-specific screen does not update the override count.   DEV-233492
When managing Submission Administrative Information, Vault does not populated common values on Country-specific screens if a Country is added to the Application and Submission after a user adds overrides on the Common Values screen.   DEV-233750
In some cases, Vault navigates the user back to the Vault login page after a user edits information and clicks Save when managing Submission Administrative Information.   DEV-232463
Vault does not trigger continuous publishing and update the EU Regional XML when a user deletes a Submission Drug Product record and the Dossier Status field on the related Submission is set to Publishing Active.   DEV-233061
In some cases, when a user double clicks on a field to add a value while managing Submission Administrative Information, Vault doesn’t display the inline edit text box and users can’t enter new values.   DEV-232393
If users add or remove links to a document after it has been published, Vault does not add or remove all links in the updated version of the published document.   DEV-237117
Vault erroneously reports validation Rule 14.BP3 when a user publishes an EU submission that contains specific countries but the XML Operation is set to Delete for those countries.   DEV-233811
The Submission viewer and Regional XML show different information when an EU submission contains two Content Plan Items in the same section with the same Country and Language but different XML Leaf Attributes.   DEV-234961
In some cases, when publishing a submission with a content plan containing multiple Content Plan Items, Vault only reports validation Rule 16.BP8 instead of both Rule 16.BP8 and Rule 16.BP9.   DEV-235239
For submissions that contain documents with hyperlinks, Vault reports validation Rules 16.BP2 and 16.BP3 without link details in the validation results.   DEV-235789
Rule 16.1 is not reported if a version 1.3 PDF is matched to a Content Plan Item and a user sets the Source of Published Document to the Source Document.   DEV-235968
Rule 16.BP4 is not reported when a document matched to a Content Plan Item contains a hyperlink and the PDF zoom level is not set to Inherit Zoom.   DEV-236356
Rule 11.BP2 is not reported if node-extensions are in the same content plan section but the XML Title is different.   DEV-236410
When a Content Plan Item is set to Inactive and a user runs the on-demand publishing job, Vault erroneously reports validation Rule 11.3 and updates the Last Modified date.   DEV-236431
Vault should not report validation Rule 16.BP2 if a hyperlink exists that targets a document matched to a Content Plan Item and the document is updated so the hyperlink points to a new target page.   DEV-236638
Vault doesn’t report Rule 9.4 on an EU Regional Content Plan Item when the XML Operation field is blank on the cover Content Plan Item.   DEV-237139
When users add overrides while managing Submission Administrative Information, Vault displays fields over the footer information in the browser window.   DEV-230566
When submissions contain Content Plan Items with matched documents in unsupported file formats, Rules 15.1 and 15.2 should only be reported for all unsupported file extensions.   DEV-237497
Vault fails to report Rule 11.9 on Content Plan Items outside of Module 1 for EU submissions.   DEV-236997
Vault only reports Rule 10.1 for Index Content Plan Items instead of both Index and EU Regional Content Plan Items.   DEV-237069
Vault does not report Rule 16.BP2 and 16.BP3 when a bookmark target doesn’t exist on a matched document.   DEV-235818
Vault does not report Rule 16.BP2 when a bookmark or link targets a non-existent named destination or document page, or when a bookmark or link is inactive.   DEV-235863
Vault erroneously reports Rule 9.4 on the Regional Content Plan Item.   DEV-231234
Vault fails to report Rule 15.8 when the Index XML Content Plan Item has Enable Continuous Publishing set to No for an EU submission.   DEV-232410
When the XML Operation field is set to delete, Vault erroneously reports Rules 10.1, 11.1, 11.5, and 11.6.   DEV-232665
Vault fails to report Rule 9.4 when there is no Submission Country record related to the Application and Submission.   DEV-232456
Vault returns inconsistent Rule VRSP013 validation results for continuous publishing, on demand publishing, and on demand validation when the Procedure Type is blank on a submission.   DEV-235763
For some users, Vault does not execute XML-level validation rules when using the “Run On-Demand Validation” action.   DEV-235728, DEV-235742
Vault fails to publish Report Level Content Plans if the source document contains an old named destination.   DEV-236000
When running the Split Content Plan Item action, Vault sometimes experiences a timeout and does not complete splitting content plans.   DEV-234002
Vault encounters an error when users execute the Split Content Plan Item action on a content plan that has a uniquely named EDL item and no associated template.   DEV-237376
Sometimes, Vault does not create the expected number of sections when copying a content plan.   DEV-222148
Vault sometimes fails to publish report level content plans if the source document contains permalinks and the “Source for Published Document” field is set to “source document”.   DEV-233969
When splitting content plans, the “Values must be unique” setting does not append a unique identifier correctly.   DEV-230661
Vault does not convert embedded links that point to named destinations to page number and coordinates.   DEV-222223
After running a harmonization job, Vault displays the historical lifecycle of an imported submission in multiple groupings.   DEV-225483
Some users are experiencing slowed performance when bulk-uploading submissions.   DEV-233174
When bulk creating registrations, the “Next” button is sometimes greyed out.   DEV-237897
Users sometimes see a “Server Having Problems” error when importing submission archives.   DEV-237554
Vault doesn’t populate the Archive Section and Submissions Archive Document Section document fields on Module 1 Country-specific published documents matched to Content Plan Items.   DEV-238531
Vault includes Inactive Content Plan sections in the index.xml file when Continuous Publishing is enabled.   DEV-239324

Reporting

Description Issue No.
Users experience an error on the Dashboard when attempting to view reports with a large number of groupings.   DEV-230263
Some users experience misaligned rows in the Flash Report email.   DEV-216355
Users running certain report types experience an error message.   DEV-237389
When creating a conditional field, a user clicking save multiple times creates multiple conditional fields.   DEV-233680
On Multi-Document Workflows, running the Workflow History Report generates no results.   DEV-233673
In some cases, users cannot unschedule a previously scheduled flash report.   DEV-236175
Document relationship matrix reports show incorrect data after editing the report.   DEV-233419
Running a Content Plan report with a prompt for [report_level_plan_clinical_study__v] or [report_level_plan_nonclinical_study__v] causes server error.   DEV-218639
Users see a server error when attempting to run a report that uses the Workflow with Object report type.   DEV-236295

Search & Filter

Description Issue No.
Applying a document type filter from advanced search sometimes causes a server error.   DEV-236708

Vault File Manager

Description Issue No.
Vault File Manager users who click Take me to my vault from the client are taken to the All Documents library view instead of to the Recent Documents view.   DEV-233937