| Description |
Issue No. |
|
Under certain conditions, Admins cannot download or delete overlay overrides.
|
DEV-370027 |
|
Formatted output reports fail to generate when the template includes a document relationship that references an object.
|
DEV-373447 |
|
When Internet Explorer 11 users generate a Vault Comparison or Vault Configuration report, Vault does not apply proper bullet formatting to the resulting notifications.
|
DEV-376768* |
|
After performing the Make a Copy action, Vault displays a “rendering” status for the copy on the Rendition Status page.
|
DEV-377633* |
|
When a document fails to render due to an issue with endnotes, Vault displays an unhelpful error message.
|
DEV-378099* |
|
Under certain conditions, expanding a section on the page layout of the Product-Tokens record results in a server error.
|
DEV-378400* |
|
When a user loads an invalid mapping file to Vault Loader, Vault displays an Uploading File pop-up with a continuously looping progress bar instead of an error message.
|
DEV-378542* |
|
Users are unable to deploy Inbound Packages containing Object type Tab or Subtab components with multiple Object Type values.
|
DEV-380048 |
|
In some cases, when a user clicks Restore Defaults in the Column Selector on the Vault Loader Extract page, Vault does not reset the columns.
|
DEV-381770* |
|
Users are unable to upload files to the File Staging Server via FTP.
|
DEV-382259 |
| Description |
Issue No. |
|
If users try to execute the archive job for a study that includes documents with missing required fields or other invalid metadata, the archival job fails.
|
DEV-351171 |
|
Documents transferred from SiteVault via Veeva Site Connect do not include Product values.
|
DEV-369261* |
|
Error messages on Distribution Tasks do not match the error message on the corresponding CDX Issue records.
|
DEV-374798 |
|
Vault does not allow users to save Studies for Study object types that are not associated with the CDX ID field
|
DEV-376639 |
|
When EDLs are configured with custom lifecycles, sending the records to sites via Veeva Site Connect results in an unexpected error.
|
DEV-377159 |
|
On CrossLink documents, Vault changes the lifecycle state prior to updating the document fields.
|
DEV-378236* |
|
Vault creates only a single CTN Data Change Log when the Name on an IP Name record is modified, even if there are multiple CTN Site IPs that reference the same IP Name.
|
DEV-378276* |
|
The Assigned To picklist on the Quality Issue object includes the value Java SDK Service Account.
|
DEV-378380* |
|
Vault does not display an error message if a user attempts to create a duplicate Organization record with the same USN value.
|
DEV-378677* |
|
In some cases, users get a server error when creating Safety Distributions from a document.
|
DEV-378939 |
|
In some cases, scheduling multiple Change Milestones to Complete jobs may result in performance issues and delays in job execution.
|
DEV-379165 |
|
In vaults with Issue Management Enhancements enabled, users are sometimes directed to a Page Not Found page after clearing filters on the Protocol Deviations and Other Issues widget on the CRA Homepage.
|
DEV-379225* |
|
After accepting and approving a study Agreement, distribution tasks and document IDs are not logged correctly.
|
DEV-379364 |
|
In vaults that contain TMF Documents with Source Artifacts that are not mapped to Type Defaults, non-TMF Documents may appear in the incorrect classifications in the Vault Clinical Docs view model of the TMF Viewer.
|
DEV-379562* |
|
In certain scenarios, the Create Milestone from Template job fails with the error message “As an Owner of this job, this notification is to inform you that the job was unable to complete its execution (ID: 107024), and ended with a status of: Errors Encountered.”
|
DEV-379584 |
|
Vault does not create Study Sites via Vault Loader if they reference an organization with an invalid USN.
|
DEV-379828* |
|
Users can edit the Name field on Organization records that have valid USNs.
|
DEV-379968* |
|
In some cases, selecting “TMF RM 2.0” from the drop-down menu in the TMF Viewer results in a network issue error message.
|
DEV-380013 |
|
When users add new research sites to a document in a source vault, Veeva Site Connect creates duplicate profile documents rather than upversioning existing documents in the target vault.
|
DEV-380432 |
|
In some cases, the Postal Code field on USN records displays underlying tokens.
|
DEV-380808 |
|
In some cases, the Update Metrics job fails when a study’s Metric Calculation value is Date Based and Subjects have a Screen Failed Date without a Screen Date or a Withdrawn Date without an Enrolled Date.
|
DEV-380826 |
|
The Create Metrics Over Time job fails if there are more than 500 planned rollups for metrics over time.
|
DEV-381427 |
|
The Formula field is editable for the Connected field on the Organization and Study Site objects.
|
DEV-381913* |
|
In some cases, TMF Transfer does not transfer placeholder documents.
|
DEV-382001 |
|
In some cases, sending an Agreement to a target vault results in multiple server errors.
|
DEV-382002 |
|
In some scenarios, users receive a “server having problems” error when trying to send a document through Veeva Site Connect.
|
DEV-382391 |
|
“MyVeeva Integration User” is included in the Assigned To picklist on Quality Issue records.
|
DEV-382464* |
| Description |
Issue No. |
|
In some cases, large Microsoft Excel™ files fail to render.
|
DEV-299889 |
|
In some cases, Microsoft Word™ documents fail to render.
|
DEV-341002 |
|
In some scenarios, merge fields resolve as blank (tokens do not resolve).
|
DEV-346729 |
|
In some cases, after rendering a Microsoft Excel™ document, Vault displays text in empty table cells.
|
DEV-362037 |
|
The second time a user brings forward an annotation and selects “Do not bring forward page-level annotations”, Vault does not bring forward the replies.
|
DEV-362953* |
|
When using a CSV file to create a document with the API or Vault Loader, passing in a null value for a required field fails to enforce the constraint.
|
DEV-364959 |
|
Empty Microsoft Excel™ worksheets fail to render.
|
DEV-373986 |
|
In some cases, fields do not populate with default values during document classification if DAC is configured on the document.
|
DEV-374453 |
|
In some cases, Vault does not render Microsoft Word™ documents with tracked changes enabled as expected.
|
DEV-374785 |
|
In a Document Inbox in Tabular View, the Select All checkbox does not reflect changes made by filters.
|
DEV-375097* |
|
In some cases, the Where Used view displays the incorrect document count and pagination when the document is associated with archived documents.
|
DEV-376623 |
|
Users may see a previously deleted rendition in the document viewer if the user uploaded renditions manually and the rendition is a protected PDF.
|
DEV-376631 |
|
Bookmarks in Microsoft Word™ documents navigate to the wrong place after rendering.
|
DEV-377366 |
|
Vault fails to merge Microsoft Excel™ worksheets containing merge fields and WHERE clauses and does not display a warning.
|
DEV-377987* |
|
When a user without the correct permissions attempts to re-render an annotated document and does not select “Preserve my annotations”, Vault displays an error but deletes the relationships.
|
DEV-378017* |
|
Checking documents in or out may result in performance issues.
|
DEV-378474 |
|
On Internet Explorer, the status icon for document upload does not accurately reflect upload progress.
|
DEV-379109* |
|
In some cases, users cannot delete relationships from the Linked Documents section.
|
DEV-379147* |
|
In some cases, Vault does not carry forward the linked document relationships from permalink annotations when the source document is versioned.
|
DEV-379397* |
|
When users bring forward annotations, the document’s annotations do not fit within the mini-browser.
|
DEV-379446* |
|
In a Document Inbox with more than 25 documents, the Complete button is inactive when the user clicks Select All, uploads a new file using drag-and-drop, and then switches view.
|
DEV-379650* |
|
Relationships of different types to the same target document are displayed as duplicates in the Linked Documents section.
|
DEV-379764* |
|
In some cases, Vault does not display images in renditions when images are embedded in Microsoft Word™ documents.
|
DEV-379849 |
|
When an Admin configures Linked Document relationships to target a specific document type, the Select targets dialog does not apply this filter by default.
|
DEV-379888* |
|
Microsoft™ Outlook™ Mail Message (MSG) files are not accepted for document creation when a user drags and drops them into a Document Inbox.
|
DEV-380126* |
|
The filename extension of PDF documents is case sensitive, which prevents PDF files from being displayed in the document viewer if the extension is not exactly “.pdf”.
|
DEV-380224 |
|
When a user navigates to document using a URL containing a version number that does not exist, Vault generates a duplicate “View document” event in the audit trail.
|
DEV-380249 |
|
Microsoft Excel™ worksheets without a header or footer are incorrectly rendered.
|
DEV-380716* |
|
In some cases, the annotation filter defaults to document view instead of note view.
|
DEV-381050 |
|
After a sandbox is refreshed, Vault fails to generate viewable renditions and does not display document thumbnails in the Library.
|
DEV-381201 |
|
In some cases, there is a delay when adding a new section to very large binders.
|
DEV-381412 |
|
When creating a document, a Yes/No field dependency without a value acts as though No is selected.
|
DEV-382064 |
|
When a user attempts to open a Linked Documents section that contains over 1000 document relationships, a network issue occurs.
|
DEV-382240 |
|
Vault displays an incorrect message when merge field objects are not found.
|
DEV-382308* |
|
In some cases, the “File doesn’t exist in remote but exists in local” error dialog shows the file paths of the file involved.
|
DEV-383214* |
| Description |
Issue No. |
|
In certain cases, the participant selection dialog box may not allow the user to continue when there are ineligible participants selected.
|
DEV-362565 |
|
In object lifecycle configuration, the functions Includes and Text for multi-picklist data types may incorrectly return a null value.
|
DEV-363303* |
|
In certain cases, the timeline view may not display the most recent effective version of a document if there was a state change by the Change State of Related Documents entry action, or triggered due to removal of documents in a multi-document workflow.
|
DEV-366073 |
|
In some cases, a user may see multiple instances of the same active workflow.
|
DEV-371943 |
|
If permissions are updated between adding a document to the Cart and starting a multi-document workflow, a user may potentially start a multi-document workflow for documents they cannot view.
|
DEV-375208* |
|
Vault may incorrectly allow selection of system-owned users in workflow user selection drop-downs.
|
DEV-376268* |
|
Vault may display a server error when a record state change triggers a related document state change with failing entry criteria.
|
DEV-378708* |
|
In certain cases, participants added to a workflow with the Add Participants function may not properly receive the workflow task.
|
DEV-380069 |
|
Certain verdict configurations in multi-document workflows may result in unexpected verdicts.
|
DEV-380491 |
|
Vault may display an error when attempting to start a multi-document workflow from a tab view.
|
DEV-380768* |
|
In some cases, a network issue occurs when Admins modify existing User Actions that have a long list of conditions.
|
DEV-380835 |
| Description |
Issue No. |
|
In Vault Product Surveillance vaults, notification emails after sending a Transmission to an electronic gateway may not be fully translated to non-English languages.
|
DEV-368478* |
|
Improper text formatting in hovering help text for the Issue Training Assignments entry action.
|
DEV-370744* |
|
Improper spacing for fields in the Issue Training Assignments action configuration.
|
DEV-372302* |
|
Users are unable to open Facilitated Training Request records if they contain formula icon fields
|
DEV-374990 |
|
In certain cases, Vault may not correctly close a Document Change Control when it enters a state with the Check and Close Multi-Document Change Control entry action configured. This primarily occurs when a document is added to the Documents to be Made Obsolete section of a Document Change Control and a new version of a document is created and then deleted prior to the entry action executing.
|
DEV-375591 |
|
Page navigation may not function as expected in Visual Hierarchy detail pages after applying filters.
|
DEV-378239* |
|
In Vaults using the Preview E-Learning Content user action, Vault comparisons may report an unexpected discrepancy due to XML values which differ between individual vaults.
|
DEV-378874 |
|
After adding a prerequisite training rule via Vault Loader or MDL, Vault may display an error upon attempting to save the rule after editing.
|
DEV-379043* |
|
Some SCORM 2004 e-learning content does not play as expected with the Preview E-Learning Content action.
|
DEV-379257 |
|
In some configurations, Vault does not correctly copy a null date value from a Training Requirement Impact Assessment to an impacted Training Requirement.
|
DEV-379382* |
|
In some cases, Vault may incorrectly apply prerequisite training rules to Training Requirements for Curriculums in which they do not have prerequisites.
|
DEV-379532* |
|
Some prerequisite requirement configurations may result in the Update Training Assignments job failing to properly link a dependent requirement to its prerequisite.
|
DEV-379859* |
|
In Vault Training, E-learning videos do not play on iOS (iPad, iPhone).
|
DEV-381236 |
|
In Vault Product Surveillance vaults, the Include in XML? field is incorrectly available to all VPS document types instead of the Attachment document type only.
|
DEV-381316* |
| Description |
Issue No. |
|
During the Create Content Plan, Update Content Plan, Split Content Plan, and Update Token actions, Vault fails to replace some periods with hyphens.
|
DEV-339782* |
|
When Vault saves import results in a CSV file attachment on the Submission record, Chinese or Japanese characters and apostrophes in the CSV file are replaced with random characters.
|
DEV-360186* |
|
Vault does not populate Archive Sections correctly when concurrent submission imports occur.
|
DEV-365740 |
|
When a non-primary submission is added to a Grouped Submission, Vault does not update the Submission Contains Files field to No.
|
DEV-366349* |
|
Vault does not populate submission metadata for a reference leaf that targets a document in a submission with a different lead market.
|
DEV-368902* |
|
In some cases, when running On-Demand Validation, Rule A01 fails for Canadian submissions and Rule 15.10 fails for Swiss submissions.
|
DEV-368914* |
|
The audit trail does not include an entry for the user who initiates a submission import via Vault File Manager.
|
DEV-374784* |
|
In the Manage Registered Details wizard, when updating an unbound document field, Vault incorrectly displays a clickable link. When updating a bound document field, Vault displays an error when users clear the Version field.
|
DEV-375300* |
|
After an Admin disables the Show Correspondence in Viewer setting, correspondence folders still appear in the Submissions Archive Viewer and when users export the submission.
|
DEV-375418 |
|
After publishing a content plan that contains a TOC Content Plan Item, users who are not Vault Owners cannot see the generated Table of Contents because the Owner role is granted to System.
|
DEV-376372* |
|
Vault populates the checksum in the XML for a reference leaf with different lead market.
|
DEV-376409* |
|
Vault does not publish documents for Japanese submissions when the Published Output Location is a relative path.
|
DEV-376681* |
|
During continuous publishing, Vault does not create a placeholder document after a matched document is deleted.
|
DEV-377037* |
|
During publishing, Vault does not create the STF reference leaf correctly when the target and source site attributes are the same on both the imported submission and the referenced submission.
|
DEV-377059* |
|
Continuous publishing does not up-version published documents to remove links to documents matched to inactive Content Plan Items.
|
DEV-377396* |
|
After a user makes a Content Plan Item record active, continuous publishing does not up-version documents that contain links to the newly-active Content Plan Item’s matched documents.
|
DEV-377483* |
|
Copy from Content Plan has decreased performance.
|
DEV-377882* |
|
When a matched document contains a link targeting another matched document, continuous publishing does not up-version the source document when the document containing the link target moves from inactive to active.
|
DEV-377931* |
|
If a Submission record is created with the Sequence ID automatically populated, when a user attempts to remove the value in the field, Vault increments the ID number instead of removing it.
|
DEV-378173* |
|
On CrossLink documents, Vault changes the lifecycle state prior to updating the document fields.
|
DEV-378220* |
|
An extra Actions menu appears on the right side of the screen when users hover over module sections in the Submissions Archive Viewer.
|
DEV-378258 |
|
If the last created Submission record is Inactive, Vault does not automatically populate the Sequence ID on the next submission the application.
|
DEV-378387* |
|
If a user deletes a generated TOC document after initial publishing completes, republishing the submission does not regenerate the TOC document.
|
DEV-378528* |
|
During continuous publishing, Vault does not generate a Table of Contents when the TOC Content Plan Item changes from Inactive to Active.
|
DEV-378596* |
|
When a content plan contains a root TOC Content Plan Item and a TOC Content Plan Item under module, continuous publishing does not up-version the published TOC after a user deletes another Content Plan Item in the same module.
|
DEV-378606* |
|
When a user republishes a submission, the publishing job fails and the Viewer does not display the latest published TOC version.
|
DEV-378630* |
|
In some cases, publishing jobs take longer than expected to complete.
|
DEV-379033 |
|
When a submission containing a TOC Content Plan Item has not been published and the Dossier Status is Empty, making any updates to the content plan causes continuous publishing to run, and Vault generates the TOC.
|
DEV-379301* |
|
When a submission contains a TOC Content Plan Item, the Publishing Status icon doesn’t update immediately after initial publishing completes.
|
DEV-379353* |
|
In some cases, users see unexpected leaf node warnings in the submission import notification, and some documents don’t appear correctly in the Submissions Archive Viewer.
|
DEV-379716 |
|
The EMA rejects XEVMPD messages that contain the GB country code due to Brexit.
|
DEV-379815 |
|
Enabling the Enable Submission based Viewer Filters setting on the Application Settings page does not remove values from the object reference fields used for submission metadata mapping.
|
DEV-379975 |
|
Errors occur on submission imports when an Admin enables the Show Correspondence in Viewer setting but doesn’t select a Document Type.
|
DEV-380364* |
|
When the XML Operation is set to Delete on a link target document, Vault publishes the target document as a placeholder but does not remove the link on the source document.
|
DEV-380746* |
|
The Registration Wizard Job In Progress notification template is missing from some vaults.
|
DEV-381039 |
|
In some cases, the Merge PDF action fails, and Vault publishes all files separately rather than creating a single merged PDF.
|
DEV-381115 |
|
Transmission to the Health Authority gateway fails for a submission that includes a content plan.
|
DEV-382413* |
|
Users cannot see submissions in the Submissions Archive Viewer when the Dossier Status or Dossier Details fields are blank or not available on the Submission object type.
|
DEV-382786 |
The Safety release, including all Platform fixed issues, is targeted for tentative availability on March 12, 2021.
| Description |
Issue No. |
|
Fixed an issue where some Turkish and Korean translations were missing.
|
DEV-380572 |
|
Fixed an issue where an error would occur when creating an AER from an imported E2B file.
|
SAF-12826 |
|
Fixed an issue where a duplicate CIOMS document was created when the Generate CIOMS Preview action was performed.
|
SAF-13016 |
|
Fixed an issue where Optimistic Lock errors were included on the Customer Email Statistics log.
|
SAF-13719 |
|
Fixed an issue where a literature document would not attach to an E2B R3 file.
|
SAF-13793 |
|
Fixed an issue where the Medical History, Race, and Ethnicity fields on a case were not exported to a submitted report with Vaccine information included.
|
SAF-13909 |
|
Fixed an issue where a Case may be rejected by VAERS when the Case contained a Malfunction without an Adverse Event, or Patient Info, and the Drug Role was set to "Drug Not Administered."
|
SAF-13931 |
|
Fixed an issue where the Invalid Email in Reporter Notification was unexpectedly included in the Customer Error Log.
|
SAF-14001 |
|
Fixed an issue where a Duplicate Key error could occur when promoting an AER to a Case.
|
SAF-14225 |
|
Fixed an issue where the E2B Import would not proceed and would not display an error message.
|
SAF-14306 |
|
Fixed an issue where a system error would occur when adding an External Product to a Case while in the Medical Review lifecycle state.
|
SAF-14337 |
|
Fixed an issue where the E2B ACK warning is unexpectedly displayed when an EMA submission is submitted to gateway.
|
SAF-14651 |
|
Fixed an issue where literature types from post market flags were not being mapped to CIOM and FDA3500A report type Literature.
|
SAF-14682 |
|
Fixed an issue where an SDK error could occur when validating a Case with the Evaluate Regulatory Conformance action.
|
SAF-14703 |
|
Fixed an issue where users were unable to save Datasheet Expected Adverse Events when a MedDRA term was included.
|
SAF-14758 |
|
Fixed an issue where, if a Safety.AI vault received an Inbox Item from the API with a time specified in the Receipt Date structured data (JSON), users could not verify the Details section on the Inbox Item.
|
SAF-15082 |
|
Fixed an issue where the Gestation value would appear as "Null" on a potential match when the Gestation field has no value.
|
SAF-15143 |
|
Fixed an issue where the "Unit" placeholder text was missing on certain unit measure fields.
|
SAF-15151 |
|
Fixed an issue where users could not save information entered in the Details section of the Inbox Item.
|
SAF-15277 |
|
Fixed an issue where the Receipt Date is not applied to the New Info Date on the Inbox Item upon Case Promotion.
|
SAF-15278 |
|
Fixed an issue where users could not create an Inbox Item if the user did not have the Document Download Permission enabled.
|
SAF-15453 |
|
Fixed an issue where the field labels on the potential matches page would not translate to other languages when the user selected a Vault language other than English.
|
SAF-154935 |
|
Fixed an issue where PADER reports would not generate for Vaults that did not have the new report templates cofigured.
|
SAF-15531 |
|
Fixed an issue where the system would be unable to process an EMA R3 date during validation.
|
SAF-15570 |
|
Fixed an issue where a Duplicate Key error would occur when a Case contains two Combination Products have the same Product.
|
SAF-15664 |
The Veeva Claims release, including all Platform fixed issues, is targeted for tentative availability on March 16, 2021.