Description |
Issue No. |
Hover text may not appear as expected in some Admin areas.
|
DEV-320143 |
Audit filters for timestamps in Admin logs and individual audit trails may incorrectly disappear upon clicking outside the selection drop-down.
|
DEV-317457* |
User license limit error messages may inappropriately appear in a sandbox environment.
|
DEV-319933* |
Clicking the User must always enter a value (required) checkbox does not save for Shared Fields that are assigned to a document type.
|
DEV-320733 |
The package comparison report shows differences for workflows configured prior to 20R1.0, even when the workflows have not been modified.
|
DEV-317392 |
When creating a new object field with the Text field type, Vault does not allow users to set the Maximum Length above 255, although the limit should be 1,500.
|
DEV-319715 |
Some users experience a failure when generating Vault Configuration Reports that include Document components.
|
DEV-314724 |
VPK deployment is blocked when a target component's label contains a comma.
|
DEV-322593* |
When a user imports a migration package with a custom Objecttype component and a Checklistype component that depends on the object's base type, the Checklistype step is blocked.
|
DEV-320362* |
When a job's conditions reference an inactive component, for example, an inactive lifecycle, users see a server error when viewing the job criteria.
|
DEV-299215* |
Under certain conditions, custom role permissions may not be properly evaluated for the “No DAC/Yes RRO” case.
|
DEV-314551* |
On the Users & Groups > Groups tab, the groups list drop-down menu filtering may not function properly.
|
DEV-318428* |
Under certain conditions, a user can access a Vault as an Application Owner by getting delegate access to the Application Owner user.
|
DEV-312399* |
When adding or removing a user to a record's sharing settings, the grid may not render properly upon completion.
|
DEV-310906* |
Users may receive a server error when attempting to view EDC Jobs from Admin > Operations.
|
DEV-320197* |
When the principal user's Vault is disabled or deleted, delegated users may still appear in the UI even after the delegation has been removed or the user has been inactivated.
|
DEV-320113 |
A server error may occur when editing a user account activation job.
|
DEV-320499* |
Description |
Issue No. |
From a site-level EDL item, executing the user action “View Related Expected Documents” instead executes the Clinical Operations-specific user action “Update Related Expected Documents.”
|
DEV-304736 |
In some scenarios, milestone rollups do not correctly populate the finish date in the related milestone dependency records.
|
DEV-318919 |
Bulk document transfer for Clinical Network is experiencing some performance issues.
|
DEV-286770* |
In some Vaults, the Study Person object is missing the external_id__v field.
|
DEV-319568* |
In some scenarios, CRF Import is vulnerable to Cross-Site Scripting (XSS).
|
DEV-309255* |
The Bulk Loader job fails when the batch size exceeds 200 sites.
|
DEV-320163* |
Bulk document creation is experiencing some performance issues.
|
DEV-317899* |
Documents transferred from SiteVault result in new document creation rather than creating a new version.
|
DEV-319576* |
Editing a CTN Site IP/ 治験施設治験薬情報 record results in an internal error.
|
DEV-318361* |
The Recalculate Enrollment Metrics user action does not delete Metrics Over Time records as expected.
|
DEV-311914* |
The Recalculate Enrollment Metrics user action does not delete Metrics Over Time records as expected after changing milestone dates.
|
DEV-316889* |
CTN document does not include the CTN IP Name.
|
DEV-315849* |
Users without the Read permission for Queues are unable to save files after upload.
|
DEV-321350* |
Vault allows multiple ad hoc asynchronous jobs to run concurrently, creating duplicate EDL Items for milestones.
|
DEV-313970* |
The “Back to Monitoring Events” breadcrumb takes users back to the record creation page, instead of the Monitoring Event record.
|
DEV-320302* |
Description |
Issue No. |
Documents using many matching sharing rules may result in reduced performance.
|
DEV-302161* |
Users are unable to create or update field dependencies when using Vault in the latest version of Chrome.
|
DEV-321662 |
When archiving staged documents, Vault displays “success” to users even though the documents are not archived, as staged documents cannot be archived.
|
DEV-300163* |
In some cases, users see a message like “Successfully created 49 of 49 document(s)” when uploading a single document via EDL.
|
DEV-309561* |
In some scenarios, Vault displays an error message after clicking on a link in an email notification.
|
DEV-318304* |
In some scenarios, Vault does not display all Link Annotations.
|
DEV-321612* |
In Veeva Claims Vaults, Vault is unable to add a CrossLink document to an object record.
|
DEV-300817* |
CrossLink documents require a page refresh to display content after updating the Source Binding Rule from Latest Steady State Version to Latest Version.
|
DEV-315741* |
In some scenarios, Vault does not replace the major version of a document after executing the Delete Minor Versions action.
|
DEV-322444* |
In some cases, users see a server error when attempting to update a document that has an invalid Currency/Cost combination.
|
DEV-316030* |
The document audit trail window displays an incorrect number of events.
|
DEV-317409 |
In some cases, users see an error when attempting to select a related object record from a document field on the Doc Info page.
|
DEV-321513* |
In some scenarios, automatic document tagging does not tag all of the required documents.
|
DEV-318664 |
Vault attaches Large Size Asset rendition files to staged documents rather than the intended documents when users upload via FTP Inbox.
|
DEV-319954 |
When migration mode is on, users receive a notification that a bulk action to update fields was successful.
|
DEV-316779* |
In some cases, users cannot create a binder through bulk action.
|
DEV-307283 |
In some cases, timestamps on renditions are incorrect.
|
DEV-313949* |
Copying a document with an inactive or deleted relationship type results in an error.
|
DEV-314407* |
In some cases, document checkout headers are not displayed when editing a checked out document in a different browser.
|
DEV-321369* |
When viewing the Documents Using page, users are told they do not have access to the documents they are shown.
|
DEV-317480* |
In some cases, creating a shared document field results in an error.
|
DEV-317134 |
In some cases, fonts appear squished or collapsed after applying an advanced overlay.
|
DEV-321822 |
In some cases, documents utilizing the “Add links to Endnotes and Footnotes” option may fail to render.
|
DEV-319052* |
Links in viewable renditions do not work after applying an advanced overlay.
|
DEV-316976* |
In some cases, Table of Contents heading numbers are blurry.
|
DEV-314971 |
Kaiti fonts are replaced by default fonts.
|
DEV-301351* |
Hidden text in headers and footers which contains hyperlinks may incorrectly display as unhidden in MS Word renditions.
|
DEV-317397 |
Description |
Issue No. |
In some view configurations, tasks in custom task views may not be clickable as expected.
|
DEV-313292 |
In some cases, the Unsaved Changes warning prompt does not appear upon leaving an edited record page.
|
DEV-319537 |
The dashboard Refresh button may incorrectly appear to be disabled.
|
DEV-318322 |
The Advanced Search dialog may not correctly appear when clicking the binoculars icon while performing a bulk edit action.
|
DEV-320944* |
The left and right arrow keys do not correctly scroll horizontally in the updated record picker dialog.
|
DEV-315008* |
In certain situations, the “Name” field is missing from the related object records grid and users cannot access the Actions menu.
|
DEV-317559 |
Users see a blank screen after uploading a related document from an object record.
|
DEV-315654 |
The Welcome to Veeva Vault email contains a broken link when accessed in Safari.
|
DEV-321693* |
Users are unable to attach documents in a checklist response when Documents Required is set to either Single Document or Multiple Documents.
|
DEV-318066* |
For some users, editing object records inline requires clicking a field multiple times.
|
DEV-314523 |
In some cases, when a user clicks the Vault Selector but navigates away without selecting a Vault from the drop-down, Vault displays a white text box instead of the current Vault name.
|
DEV-321489 |
In some cases, clicking on the link to an attachment from the document viewer takes the user to their Home tab instead of to the attachment.
|
DEV-320344* |
For some users, the Product Announcements and Service Availability notification options may inadvertently change when saving their profile.
|
DEV-317355* |
Under certain conditions, some users are unable to login after creating large Vaults from an export package.
|
DEV-313693 |
The `ls` command fails to list files and hangs for some FTP client directories.
|
DEV-303671 |
Generating formatted output and exporting binders may take an inordinate amount of time.
|
DEV-314835 |
Creating a binder from a template may take longer than expected.
|
DEV-317128 |
Extracting documents with advanced overlays takes longer than expected.
|
DEV-314005* |
Exporting a large report to an Excel template takes longer than expected.
|
DEV-319811* |
In some cases, flash reports take longer than expected.
|
DEV-316078 |
Description |
Issue No. |
Submissions-specific change related active object lifecycle state configuration does not work with Conditions on Related Records, resulting in Vault displaying a server error.
|
DEV-318377* |
In some scenarios, Vault does not display documents after clicking on a bookmark in the Submissions Archive Viewer.
|
DEV-314076 |
In some cases, Vault does not update the Regulatory Objective field when a user performs the Manage Registered details action.
|
DEV-319303* |
In some cases, device-specific fields that are hidden from users prevent users from creating Registered Packaging records through the Manage Registered Details wizard.
|
DEV-315984* |
Users experience an error when importing submissions if the XML contains a reference preceded by “./”.
|
DEV-318607* |
In some scenarios, a published STF may appear duplicated in the published output.
|
DEV-318982 |
When users create object lifecycle state entry actions, Vault incorrectly includes the “Resubmit spark message” option in the list of available actions.
|
DEV-314251* |
Sometimes, Vault does not create the expected number of sections when copying a content plan.
|
DEV-222148* |
Vault does not mark lifecycle entry criteria fields as mandatory in the Update Fields dialog within the Manage Registered Details wizard.
|
DEV-315086* |
In the new Content Plan Hierarchy Viewer, users experience slow performance when expanding content plan sections with many children.
|
DEV-299753 |
When using object types in the QMS to Registrations Spark Connection, Vault fails to create an Event record if a field exists on one object type but not others.
|
DEV-315628 |
When Dynamic Access Control is configured, Vault includes records on which users lack the Read permission in the Add: Registered Details dialog within the Manage Registered Details wizard.
|
DEV-319603 |
Vault does not support multi-value picklist fields in the Create Registrations wizard.
|
DEV-318455 |
Sometimes, when working in the Manage Registered Details wizard, if a user selects a Country-level checkbox to select all records on an Update Registered Details page, deselects several individual records, and then selects the Country-level checkbox again, the grid disappears.
|
DEV-317585 |
In some RIM Vaults, the Workflow Timeline section is missing from some Regulatory Objective object type page layouts.
|
DEV-317066* |
In some cases, users see an error when attempting to inline edit on the grid panes within the Manage Registered Details wizard.
|
DEV-317115* |
When copying a content plan for an EU submission from a content plan for a US submission, the content plan structure is incorrect.
|
DEV-243072* |
The Start Multi-document Workflow action is available when inactive Content Plan Items are displayed in the grid, and users can send documents matched to inactive records on the workflow.
|
DEV-316784* |
Admins can't enable submission-based view filters on Vaults with existing saved views.
|
DEV-316778* |
Managing Submission Administrative Information fails when users save multiple identical values on common and country-specific pages.
|
DEV-312529, DEV-310835* |
Vault sometimes creates the same leaf twice in a submission rather than replacing the file.
|
DEV-307422* |
When users filter in the Submissions Archive Search dialog in list view, navigate to a folder, and then attempt to search again, the search dialog appears twice and users can't select a value.
|
DEV-315078* |
When users launch a multi-document workflow from the Hierarchy Viewer, Vault doesn't send the documents on the workflow in the correct order.
|
DEV-314979* |
The Enable Submission based Viewer Filters checkbox does not appear on the Admin > Settings > Application Settings page.
|
DEV-315925 |
Vault changes the capitalization of the Leaf ID in the stf.xml file after a submission is published.
|
DEV-312993* |
After users select a document in the Dossier Review Panel, Vault navigates them back to the top of the panel.
|
DEV-314661* |
In some cases, publishing fails when there is a bookmark or link to an invalid named destination across the application.
|
DEV-314657* |
The action to manage Submission Administrative Information appears in the Actions menu for inactive Submission Country records.
|
DEV-314656* |
When users open the Submissions Archive Search dialog and click the Binoculars icon to select a related record, they cannot type in the search bar.
|
DEV-313769* |
In the Content Plan Hierarchy Viewer, when users filter by Type to only see Matched Documents and then start a multi-document workflow, Vault sends specific, bound document versions on the workflow rather than the latest version.
|
DEV-318436 |
Some imported submissions don't display in the Submissions Archive Viewer.
|
DEV-318382* |
Vault doesn't send a notification or email when users export submissions in bulk.
|
DEV-319604* |
Newly-imported submissions don't appear in saved views within the Submissions Archive Viewer.
|
DEV-319222* |
In the Submission Administrative Information viewer, Vault treats blank values in the Tracking Number, INN, or Invented Name fields as overrides for some countries.
|
DEV-312580* |
In Vaults with both the Submissions Archive and the Publishing applications, if a Submission record has a mandatory custom field that is blank, the values in the Dossier Status field and the Submissions Archive Status field don't match.
|
DEV-310675 |
When users add a new row in the Submission Administrative Information viewer, Vault does not create the new row in Edit mode.
|
DEV-312071* |
Vault doesn't display the correct number of records in the grid on the Update Registration pages within the Manage Registered Details wizard.
|
DEV-317592* |
In the Dossier Panel, Vault automatically expands sections that were recently collapsed when users select a document in a different section.
|
DEV-313951* |
Adding the Application lookup field to Submission join records, for example, Submission Regulatory Objective, reset the Relate Multiple Records checkbox on these objects.
|
DEV-318612* |
The Manufacturer attribute doesn't appear in the Viewer for published submissions.
|
DEV-241316 |
When users apply an “is blank” or “is not blank” filter on the Hierarchy Level field in the Content Plan Hierarchy Viewer, they can't remove the individual filter from the applied Filters section.
|
DEV-322637* |
Users cannot include or exclude values on the Procedure Tracking Number field in the Submission Administrative Information viewer.
|
DEV-318950* |
Users see an error and the page appears blank when a user working in the Content Plan Hierarchy Viewer attempts to drag and drop to match a document when cascading state changes are not configured.
|
DEV-317117* |
Validation rule EU 15.BP3 reports as Pass incorrectly for certain filenames.
|
DEV-320919* |
In the Submissions Archive Viewer, when users apply filters and then select All in that filter, Vault doesn't return to the root level and instead displays the section that was open previously.
|
DEV-318158* |
In some cases, users receive an error when attempting to import a dossier to a Submission record.
|
DEV-321570* |
Vault creates documents but doesn't render the “toctarget” Table of Contents token if the token doesn't contain an object.field parameter, for example, edl_item_v.xml_xlinkhref_v.
|
DEV-316737 |
The Safety release, including all Platform fixed issues, is targeted for tentative availability on June 11, 2020.
Description |
Issue No. |
Fixed an issue where the Age at Onset field was not being recalculated correctly on Cases imported from an E2B file with multiple Case Adverse Event records.
|
SAF-5632 |
Fixed an issue where a descriptive error message did not appear below the MedDRA field when a non-primary MedDRA term was selected for a Case Adverse Event.
|
SAF-5735* |
Fixed an issue where the AESI Watchlist Tag was unable to be added on Study cases.
|
SAF-5741* |
Fixed an issue where, when three keywords were inputted in the MedDRA search bar, no results were shown.
|
SAF-5827* |
Fixed an issue where the selected MedDRA term was not shown in results upon exiting and re-entering the browser.
|
SAF-5828* |
Fixed an issue where the coded value of the MedDRA term was not shown in results upon exiting and re-entering the browser.
|
SAF-5850* |
Fixed an issue where, when a MedDRA term was coded to a non-primary SOC, the term was not shown in results upon exiting and re-entering the browser.
|
SAF-5854* |
Fixed an issue where users were unable to open links to documents or Cases from vault notifications.
|
SAF-5874 |
Fixed an issue where, when Adverse Events on Study and Literature Cases did not have a Case Assessment, they were not counted on the PSUR Summary Tabulation.
|
SAF-5875* |
Fixed an issue where the Binoculars icon next to the Event (Reported) field was missing on MedDRA control.
|
SAF-5893* |
Fixed an issue where, when the Case Product registration was updated, the system set the Expedited flag to NO instead of leaving the Expedited flag as-is.
|
SAF-5904* |
Fixed an issue where a server error appeared when a user assigned the Lock Manager role tried to create an AER.
|
SAF-5907* |
Fixed an issue where Null appeared on CIOMS II listings when Event MedDRA was not provided on the case.
|
SAF-5921* |
Fixed an issue where PSUR reports failed to generate when a non-serious case has the Expectedness field left blank.
|
SAF-5933* |
Fixed an issue where the Adverse Event was exported with Event MedDRA instead of in format Event Reported (Event MedDRA) when generating PSUR Summary Tabulations.
|
SAF-5950* |
Fixed an issue where a Study Case Product on Open case went to Unblinded lifecycle state instead of Open lifecycle state.
|
SAF-5968* |
Fixed an issue where the user was unable to change the state of the case to Approved once the user locks the case.
|
SAF-5985* |
Fixed an issue where, when evaluating reporting obligations, the Case Adverse Event was not being filtered based on agency country.
|
SAF-6003* |
Fixed an issue where the selected MedDRA term was not displayed on the first page after re-opening the browser.
|
SAF-6038* |
Fixed an issue where ROA values with nullflavors and blank values were not being exported in HC E2B (R2) files with value 065.
|
SAF-6040 |
Fixed an issue where the Case page could not load when the Medical Review Timeline section control was added to the Case page layout.
|
SAF-6049* |
Fixed an issue where “highcharts.com” was displayed at the bottom right corner of the Medical Review Timeline section.
|
SAF-6075* |
Fixed an issue where the Medical Review Timeline Header was not displayed correctly when the Case Adverse Event contained a start and end date.
|
SAF-6079* |
Fixed an issue where, when the Case Adverse Event had the same start and end date, the Medical Review Timeline bar was empty instead of displaying a Milestone Marker.
|
SAF-6080* |
Fixed an issue where the Date Range field for the Medical Review Timeline was misplaced on the screen when the user tried to edit it.
|
SAF-6094* |
Fixed an issue where the Medical Review Timeline hovercard only displayed the year value when the Onset date of the Case Adverse Event was the first day of any month.
|
SAF-6095* |
Fixed an issue where the Expected (expectedness) fields on Follow-Up Cases did not match the field values from the initial Case.
|
SAF-6096 |
Fixed an issue where the End date was calculated incorrectly when the Case Adverse Event contains an Onset date and Outcome is Unknown or left blank.
|
SAF-6103* |
Fixed an issue where the Date values in the Medical Review Timeline hovercard were displayed incorrectly when the Case AE contains an Onset or Cessation date and Duration < 1 day.
|
SAF-6116* |
Fixed an issue where, when the Case Adverse Event had Onset Date and Outcome: “recovered/resolved” or “recovered/resolved with sequelae”, the Timeline bar is empty instead of displaying the Milestone Marker.
|
SAF-6119* |
Fixed an issue where after you manually changed the auto-calculated Expected field to set the value to Yes (Overriden), the system updated the Expedited field to No instead of leaving the Expedited field as-is.
|
SAF-6123 |
Fixed an issue where a server error appeared when a Case Product Dosage did not have a Frequency Value and a First Admin Date.
|
SAF-6124* |
Fixed an issue where the Dosage Details on the Medical Review Timeline contained extra decimals compared to the Dosage Details of the Case Product.
|
SAF-6125* |
Fixed an issue where the Assessment Result of the Adverse Event Report did not copy over when a user opened a new Study Case.
|
SAF-6144* |
Fixed an issue where you could not create a Follow-Up Case from a Case containing multiple Case Product or Case Adverse Event records with identical names.
|
SAF-6157 |
Fixed an issue where a server error appeared when multiple dosages are updated or created on Case Product and result in auto-calculation.
|
SAF-6168* |
Fixed an issue where a system error appeared when trying to create a follow up Adverse Event Report from potential matches with a different Adverse Event MedDRA.
|
SAF-6179* |
Fixed an issue where the Title field for Case Narratives was not being populated correctly.
|
SAF-6223* |
Fixed an issue where a SOC product in a blinded study case was getting created as Blinded instead of Open.
|
SAF-6255* |
Fixed an issue where a duplicate Case Adverse Event record was created on the follow-up case when the auto-calculated Expected value was updated on the original case.
|
SAF-6257* |
Fixed an issue where the audit log recorded that the system created Follow-Up Cases instead of the user who triggered the action.
|
SAF-6344 |
Fixed an issue where the system was not automatically calculating the Latency field on Case Assessment records after a Case was created from an imported E2B file.
|
SAF-6374 |
Fixed an issue where Case Relatedness was not properly set to Not Related when Case Assessment Result(s) referenced custom Controlled Vocabulary records for the company source using E2B values 2 or 4.
|
SAF-6447 |
Fixed an issue where a descriptive error message did not appear when Follow-Up Case creation failed due to a Case field referencing an inactive Controlled Vocabulary record.
|
SAF-6449 |
Fixed an issue where, when importing EMA E2B (R3) files, EU Assessment Result values were not being mapped to Default E2B Values.
|
SAF-6528 |
Fixed an issue where cumulative case calculations were not considering the correct start date when generating aggregate reports.
|
SAF-6605 |
Fixed an issue where the interval column did not include the latest New Info Date in range for PBRER Number of Product Reactions by Term for Postmarketing Sources table.
|
SAF-6648 |
Fixed an issue where EVWEB XSD validation failed after selecting “Cyclical”, “As Necessary”, or “Total” for Frequency instead of a value.
|
SAF-6806 |
Fixed an issue where a server error appeared when a user without permissions to read User security tried to create records on Safety objects with an api_name field.
|
SAF-6828 |
Fixed an issue where a server error appeared when a user tried to view Case Product page from VMC > View Configuration.
|
SAF-6832 & SAF-6158 |