| Description |
Issue No. |
|
In cases where EDL templates are configured to match on owning milestone, but the template record does not have an owning milestone type specified, Vault creates EDL items without an owning milestone specified.
|
DEV-409033* |
|
In some cases, users encounter an error when attempting to transfer documents from RIM to Clinical.
|
DEV-442938 |
|
In some cases, users are unable to create eTMF binders in bulk.
|
DEV-483411 |
|
In some cases, the system incorrectly populates the Previous Monitoring Event field to the incorrect monitoring event.
|
DEV-483860 |
|
Users receive an unexpected error when trying to create a checklist when the associated contact record includes an email address that is formatted incorrectly.
|
DEV-492414* |
|
Line breaks and spacing are not correctly displayed in the Review mode (read-only) of the Response and Comment fields on a Trip Report Question.
|
DEV-493898 |
|
The Distribution Task does not update the eReg document version to the Study Connect document version.
|
DEV-494195* |
|
Users experience slow transfer times for documents sent from SiteVault to their sandbox Vault.
|
DEV-495339* |
|
When users reject a Study Agreement, Vault displays an error.
|
DEV-495946* |
|
In some cases, users attempting to transfer documents from RIM to eTMF receive an error stating that the study__v object does not exist in the target Vault even though there are valid study records in the target Vault.
|
DEV-498529 |
|
Certain documents are unable to be transferred successfully.
|
DEV-499465 |
|
In certain cases, documents fail to update during a CDX document update.
|
DEV-500431 |
|
If CDX encounters an issue upon attempting to transfer documents, it reattempts the transfer but does not correctly identify the documents to send, leaving the documents from the first attempt untransferred.
|
DEV-500772 |
|
The number of User Exception Messages and Failed Message Items do not match for the Clinical to RIM Connection.
|
DEV-502646 |
|
Vault disallows study archival due to associated documents being under legal hold, despite the fact that the legal hold has been removed.
|
DEV-502810 |
|
In some cases, searching for a USN number when creating an Organization record causes server problems and is unsuccessful.
|
DEV-505118 |
|
In rare circumstances, when the "Match EDL Items to Doucment" job runs, it updates the metadata of inactive Expected Document Lists.
|
DEV-508717 |
|
In some cases, Baseline and Planned Study Milestone Dates do not roll up consistently.
|
DEV-509611* |
| Description |
Issue No. |
|
Vault fails to render Microsoft Word files stuck in Draft view.
|
DEV-457277 |
|
After document creation, OCR may incorrectly update the Last Modified By field in the document info section.
|
DEV-465062 |
|
In some cases, Vault fails to render documents with bookmarks while the Auto generate bookmarks for captions setting is enabled.
|
DEV-465124 |
|
In some cases, Excel source files with merge fields are corrupted after rendering.
|
DEV-470802 |
|
Users with names more than 100 characters are unable to save pending annotations on documents.
|
DEV-475106* |
|
Source files with merge fields are corrupted and display a different file size after rendering.
|
DEV-479705 |
|
In some cases, DAC roles are not applied for some document classifications.
|
DEV-480973* |
|
Vault may fail to render Microsoft Word files with multiple INCLUDEPICTURE fields.
|
DEV-484455 |
|
Under certain circumstances, Vault fails to render documents with page section breaks.
|
DEV-492205 |
|
In certain cases, when applying a legal hold on a document and deleting multiple versions through the API, some versions are successfully deleted and others are stopped due to the legal hold.
|
DEV-493897* |
|
Vault fails to render .XML files when the file path contains special characters.
|
DEV-494925 |
|
Vault fails to escape special characters within Binder section names.
|
DEV-494956* |
|
In some cases, generated Signature Pages may display numeric characters instead of step names and verdicts.
|
DEV-496464 |
|
In some cases, when uploading a document to Vault through the Google Drive Integration, the document is shown as a zipped file.
|
DEV-496501 |
|
Under certain circumstances, Vault fails to render .XML files in .ZIP files.
|
DEV-496668* |
|
In some cases, Vault fails to publish a merged PDF from a Report Level Content Plan.
|
DEV-498183 |
|
Within a multi-document workflow, the page number does not reset upon choosing a new document to view.
|
DEV-500650 |
|
When exporting archived documents in bulk, document fields fail to be exported.
|
DEV-502817 |
|
After re-rendering a document, the annotation count is incorrect while annotations are preserved.
|
DEV-507263* |
| Description |
Issue No. |
|
Canceling a legacy workflow from the timeline view may result in the browser's dev console displaying an error.
|
DEV-478430* |
|
An object workflow step that is configured to update a text field may replace the string "Object" with the object's name field value.
|
DEV-491985* |
|
Users may experience performance lag or be unable to select certain users if using legacy workflows with roles whose allowed groups include a group with over 10,000 users.
|
DEV-492900 |
|
After workflow task reassignment, the original task owner receives a notification but the new task owner does not.
|
DEV-496508 |
|
MDL RECREATE and inbound package deployment fail for document lifecycles with Send a notification entry actions that reference inactive users.
|
DEV-497201* |
|
When a user starts the next workflow upon workflow completion, the new tasks and states do not display until they manually refresh the page.
|
DEV-498757 |
|
When the user language is German, the workflow Completion Status incorrectly uses the word "öffnen" as a translation for "open".
|
DEV-499252 |
|
Users are unable to start a document workflow when only System-owned users are assigned to a role configured in the Participants control.
|
DEV-504142* |
|
In some cases, the order of verdicts in the workflow task dialog is different from the order in the workflow configuration.
|
DEV-504298 |
| Description |
Issue No. |
|
When deploying a migration package that contains a layout rule that hides a control, Vault does not validate that the control exists on the page layout in the target Vault.
|
DEV-476252* |
|
In some cases, object reference fields do not update as expected during Vault pre-release.
|
DEV-483169 |
|
Vault clears object reference field default values from object record pages when a user enters edit mode.
|
DEV-490214 |
|
When a user adds a formula field that references a high volume object picklist to the columns on an object record list page, Vault fails to display object records.
|
DEV-495854* |
|
Object records with a field pointing to the latest version of a document may show an incorrect value if the latest version of that document is deleted.
|
DEV-498095* |
|
Vault displays a confusing error message when a user attempts to cascade delete 1000 or more object records.
|
DEV-499274 |
|
After migrating a child object to HVO, the object record list may take a long time to load or may time out.
|
DEV-501226* |
|
After a user's name is updated in their User record, Vault displays the old name in the Last Modified By and Created By fields of object records.
|
DEV-505140 |
| Description |
Issue No. |
|
In some configurations, changes to Training Requirements marked as substitute training requirements, which also do not have any Training Rules defined, may fail to trigger a Training Requirement Impact assessment.
|
DEV-481491* |
|
In some cases, Vault fails to translate the Process Navigator dropdown into the proper language when viewing documents.
|
DEV-484389* |
|
In some cases, Vault restricts users without Objects: Lab Test Set: Edit permission from adding Lab Tests to a Test Set.
|
DEV-488450* |
|
While attempting to execute a test in Vault LIMS, Vault fails to prevent user from editing test results.
|
DEV-488725* |
|
When attempting to save a Related Record Configuration, certain Outbound Reference Field and Field Value Mapping combinations may cause Vault to display an error.
|
DEV-494031 |
|
In rare cases, Vault fails to evaluate test results on behalf of users without a Vault Owner security profile.
|
DEV-496141* |
| Description |
Issue No. |
|
When an external user fails to upload a COA file by email intake, the error message received is partially translated according to the user's non-English profile language.
|
DEV-495828* |
|
When users attempt to view a 5 Whys diagram in Vaults with Supplier Portal enabled, Vault displays a blank page.
|
DEV-501231* |
|
When closing out the Hazard Create dialog with the ESC key, the page is no longer accessible and displays error messages.
|
DEV-503915* |
|
When adding a Why item to a 5 Whys diagram, the "Why" text color is not displayed as expected.
|
DEV-504808* |
|
In some cases after deleting a Why item from a 5 Whys diagram, users cannot click into any other items in the digram.
|
DEV-504987* |
|
When Admins add a Question Help Text to a Question in an Audit Checklist, it is visible during preview but does not display after saving.
|
DEV-505580 |
| Description |
Issue No. |
|
In some cases, Vault incorrectly reports Rule 1154 when validating grouped submissions.
|
DEV-461472* |
|
Vault incorrectly reports Rules 2002 and 2012 as Not Executed for some grouped submissions.
|
DEV-469448* |
|
Vault incorrectly reports Rule 1901 as failed when there is Site Tagging File section published under m5-3-6.
|
DEV-474955* |
|
In some cases, publishing job progress percentages appear to drop while the job is running.
|
DEV-479841* |
|
In some cases, Submissions Archive users are unable to access the Submission Archive Viewer.
|
DEV-482334* |
|
In some cases, Vault incorrectly reports Rule 5215 as failed when a target document is published and locked to a different version.
|
DEV-483773* |
|
Vault incorrectly reports Rule 2025 as passed for some submissions.
|
DEV-485946 |
|
In some cases, Vault incorrectly reports Rule 1789 as failed when the Continuous Validation field on a Content Plan Item is set to “No”.
|
DEV-486451 |
|
Continuous publishing tasks fail when Vault attempts to add annotation links to a target document while it is locked to a lower version.
|
DEV-490647* |
|
Validation fails with a nonspecific error if duplicate Leaf IDs are detected during validation.
|
DEV-492027* |
|
Vault annotations to permalinks are not published when there are five or more matched documents in a content plan.
|
DEV-493122* |
|
In some cases, Vault incorrectly populates Product Data Message Level 1 and Level 2 Acknowledgement receipt dates.
|
DEV-494627 |
|
In some cases, Vault incorrectly passes rules 5030 and 5 when blank and unedited PDF forms are matched to a Content Plan Item.
|
DEV-495006 |
|
In some cases, users cannot download Submission exports from the Notifications menu when the Submissions Archive Viewer tab is open.
|
DEV-495818 |
|
Vault publishes stylesheet references in GCC Submission regional.xml in single (instead of double) quotes.
|
DEV-495920 |
|
In some cases, users cannot complete a Submissions Archive Bulk Export.
Internal fix published in error
|
DEV-496352 |
|
In some cases, Vault builds CN Submission binders incorrectly.
|
DEV-496423* |
|
In some cases, Vault incorrectly reports CN Rules 4.2.6 and 4.2.10 as failed.
|
DEV-496431* |
|
On-demand publishing fails when Vault re-generates a merged Submission Content Plan’s updated Table of Contents.
|
DEV-500900* |
|
Under certain circumstances, Vault fails to publish submissions documents while Continuous Publishing is enabled.
|
DEV-501117 |
|
The compliance_package_v and compliance_package_documents_v integration rules do not support query object relationships.
|
DEV-501286* |
|
In some cases, Vault shows an incorrect breadcrumb trail when viewing Submission Binders.
|
DEV-501699 |
|
In rare cases, submission imports result in an internal system error.
|
DEV-502526 |
|
When submitting via the gateway to the EMA, if publishing has not yet completed, the system does not prevent the transmission.
|
DEV-504020 |
|
After clicking Edit in the Action menu, users are unable to edit job fields.
|
DEV-504784 |
|
Vault incorrectly reports Rule 5117 as failed when validating some matched PDF documents.
|
DEV-505295 |
|
Under certain circumstances, split regulatory objectives display warnings and fail to specify fields for some records with multiple matching records.
|
DEV-505439* |
|
When editing some standard notification templates, users receive invalid token warnings for pre-configured tokens.
|
DEV-505459 |
|
Vault fails to publish Study Tagging Files during Continuous Publishing while EDL is active.
|
DEV-505565* |
|
The Content Plan Viewer indicator is not updated with asynchronous state changes in Vaults where the Copy Into Content Plan feature is not enabled.
|
DEV-505898 |
|
Users are unable to generate Registration History Reports.
|
DEV-507739 |
The RegulatoryOne release, including all Platform fixed issues, is targeted for tentative availability on August 30, 2022.
The Safety release, including all Platform fixed issues, is targeted for tentative availability on August 25, 2022.
| Description |
Issue No. |
|
Fixed an issue where all Reasons Omitted (NullFlavors) were available in the Case Medical History Text field, enabling invalid data to be included on E2B reports. A new Medical History Text app control filters the Reasons Omitted picklist to only valid values.
|
SAF-28803 |
|
Fixed an issue where the Transmission Lifecycle reverted to the "Ready" state after the "MDN Received" state.
|
SAF-30144 |
|
Fixed an issue where, when an Inbox Item was promoted to a Case, if the Case Lifecycle included a custom state and the User Profile was set to a non-English value, the system displayed an error message.
|
SAF-30152 |
|
Fixed an issue where, when validation criteria rule evaluation generated only one warning, the Case Validation Status was set to Fail.
|
SAF-30657 |
|
Fixed an issue where, when importing an E2B(R2) file with multiple < drug > sections with different dosages for the same < medicinalproduct > and < drugindication >, the system created multiple Product Indication records instead of consolidating the information into a single Product Indication record.
|
SAF-30748 |
|
Fixed an issue where, when the Re-evaluate Reporting Obligations action was run on a Case with multiple Transmission Profiles for the same Origin and Destination, a second Transmission was generated using a different Transmission Profile to the first-created Transmission.
|
SAF-31086 |
|
Fixed an issue where, when generating FDA MedWatch 3500A forms, the Date of Event field (B.3) was populated with the Date of Onset on the primary Case Adverse Event record. Now, by default the Date of Event field is populated with the earliest Onset Date for any Case Adverse Event associated with the Case version. To continue populating the Date of Onset on the primary Case Adverse Event record, contact Veeva Support.
|
SAF-31128 |
|
Fixed an issue where, when an Inbox Item contained Case Identifiers with leading or trailing spaces (for example, “NN-ABCD-123 ”), during promotion to a Follow-Up Case, on the Case Compare page the system did not match the Case Identifier to the record on the original Case. When Create Follow-Up was selected, an error message appeared and the system prevented Follow-Up Case creation.
|
SAF-31206 |
|
Fixed an issue where, after running Evaluate Regulatory Conformance for a Case without reporting obligations, the system set the Validation Status to blank and then prevented moving the Case to the Approved state.
|
SAF-31207 |
|
Fixed an issue where, for an imported Inbox Item for a Study Case, on the Case Compare page, the system prevented the creation of a Follow-Up Case if the original Case did not include a Study Product.
|
SAF-31398 |
|
Fixed an issue where, when there was a non-English Localization specified on the Inbox Item, after Case promotion, on Adverse Events, the Event (Reported) Language field defaulted to English. This issue impacted Vaults with the “Enable auto-set Inbox Item Localization by Reporter Country” setting enabled and the Localization field hidden on the Inbox Item layout.
|
SAF-31844 |
|
Fixed an issue where, when a Vault had a large number of Studies, Inbox Items loaded slowly.
|
SAF-31972 |
|
Fixed an issue with system performance when loading a Domestic Case with localized dual-entry fields.
|
SAF-31987 |
|
Fixed an issue with the Case Product Indication (Reported) field on Domestic Cases where the MedDRA browser appeared in English, instead of the Localized language on the Case.
|
SAF-31990 |
|
Fixed an issue where, when typing Case data into an app control field, there was a lag before the value appeared in the field.
|
SAF-32089 |
|
Fixed an issue where, after promoting a Localized Inbox Item, the value in the localized Case Product (Reported) field was not populated on the Case.
|
SAF-32317 |
| Description |
Issue No. |
|
When validating uniqueness of the name field for a new HVO object, users may receive an error.
|
DEV-454531* |
|
Non-mandatory savedview component records are not in the component directory and cannot be migrated with VPKs.
|
DEV-473760* |
|
In some cases, documents that have had a checkout undone can appear to be checked out from the library page, but not the document information page.
|
DEV-479736 |
|
The Suggest Links document action creates suggested links for single words rather than correctly matching the entire sentence.
|
DEV-489215* |
|
After performing a bulk action on a document section on the expanded search page, the user is redirected to the 'All' view instead of back to the expanded search results.
|
DEV-490734* |
|
In rare cases, users may receive a "Server having problems" error when attempting to open any tabs in a Vault.
|
DEV-496254 |
|
In some cases, users are unable to edit some fields in-line on the Expanded Search Page.
|
DEV-497960 |
|
If a user doesn't have read permission on an object in a search collection, attempting to navigate to the expanded search page results in a "Page not found" server error.
|
DEV-498921* |
|
When a user clicks through views too quickly in the tabular layout, Vault switches back and forth between views indefinitely rather than eventually stopping on the last clicked view.
|
DEV-500251* |
|
Vault fails to export document metadata while in grid view.
|
DEV-509417 |