Description |
Issue No. |
In some cases, users do not receive email notifications that should have been sent while the auth server was temporarily unavailable.
|
DEV-468996* |
In some cases, users receive a connection error when attempting to update a custom s3 bucket for Scheduled Data Exports.
|
DEV-478817 |
In some cases, Admins are unable to save changes made on the Versioning Settings page.
|
DEV-480307* |
In some cases, permission sets do not appear in the dropdown list for adding to a VPK.
|
DEV-483993 |
Extracting documents with Vault Loader may contain duplicates.
|
DEV-484026 |
In some cases, Distribution Task Recipient records become stuck in the Pending Distribution and Sending email status.
|
DEV-484349* |
In some cases, Scheduled Data Exports with the full data export option fail to export some records.
|
DEV-486842 |
In some cases, Tracked Emails sent to Gmail addresses may be incorrectly reported as opened.
|
DEV-487299* |
In some cases, the System Audit UI displays the incorrect User Name for Email Burst Threshold and Outbound Email Domain entries.
|
DEV-488882 |
Description |
Issue No. |
Vault does not generate a notification after the Recalculate Enrollment Metrics job completes.
|
DEV-332643* |
After successfully retrying a TMF Transfer with over 200 Transfer Failure records, Vault fails to delete more than 200 Transfer Failure records.
|
DEV-479621* |
In cases where a Study Person record does not have an underlying User record, updates to the Study Person record fail.
|
DEV-479953* |
In some cases, Vault creates multiple Transfer Failure records after the user has taken the retry action.
|
DEV-480130* |
Users receive a server error when attempting to deactivate an agreement that does not exist in the associated Vault.
|
DEV-480674 |
In some cases, distribution tasks fail to update the Sent Date, which causes the task to fail or be stuck in the Sending state longer than expected.
|
DEV-480897* |
When Site Connect is disabled, Vault displays "Server having problems" when loading a page layout containing the Site Document Exchange section.
|
DEV-482002* |
Checklist creation may fail if triggered indirectly via a different workflow.
|
DEV-483736* |
Users are unable to mark documents rescinded in cases where the site lifecycle stage is null and the documents have been sent to multiple sites.
|
DEV-484362 |
In some cases, documents are incorrectly marked as in bulk queue when they are not being processed.
|
DEV-485030* |
In some cases, users are able to create crosslink documents without the required Study field
|
DEV-486201 |
The Received from Sponsor/CRO state incorrectly appears in the Study Connect lifecycle.
|
DEV-486486* |
In some cases, users experience performance degradation when performing certain VQL queries on CDMS Vaults.
|
DEV-487985* |
In some cases, the EDL Matching job incorrectly updates EDLs that are Inactive.
|
DEV-488153* |
Users may receive "Server having problems" errors when completing tasks with entry actions that modify Study Hierarchy values.
|
DEV-488967 |
Description |
Issue No. |
Vault fails to display viewable renditions for documents created using the Make a Copy action.
|
DEV-467924 |
Vault incorrectly allows users to delete references on read-only Approved Claim records.
|
DEV-474173 |
After checking in a document edited in Google Drive, the document in Vault does not display the edits.
|
DEV-475943* |
In some cases, asset renditions are not copied over to the file system for newly approved versions.
|
DEV-476010* |
Under certain conditions, users are unable to update Major Version Number document field using a VPK.
|
DEV-482151 |
Find in Document fails to return results if the first word in the search is a single character.
|
DEV-482344 |
In some cases, Vault removes source document relationships.
|
DEV-482854 |
Under certain conditions, attempts to reclassify documents result in a server error.
|
DEV-484203* |
If users use a doc field containing '#' as an auto name, the '#' is replaced with @veevaEscapeCharacter.
|
DEV-484207 |
In some cases, document updates take much longer than they should, especially in Vaults with a high number of document annotations.
|
DEV-485027 |
In some cases, users are unable to update document fields, receiving an Unexpected Error.
|
DEV-485302 |
After regenerating a trip report, the status for Prior Version may be incorrect in the report and other places where the value is used.
|
DEV-485548 |
When a Delete Minor Version Entry Action fails, users may observe unexpected errors or documents with an incorrect version.
|
DEV-485863* |
In some cases, users receive a "Server having problems" error when attempting to view a document within a nested binder.
|
DEV-485930 |
When classifying or reclassifying documents, lookup fields may not populate.
|
DEV-486772 |
When indexing a document, Vault may index the Website field incorrectly.
|
DEV-486882 |
After updating a document with previously populated inactive fields, Vault sets the fields to blank.
|
DEV-487193* |
After bulk updating document fields, Vault incorrectly attributes the update to a user rather than the system on the audit trail.
|
DEV-488373 |
Description |
Issue No. |
Vault displays certain time zone abbreviations inconsistently in different parts of the UI.
|
DEV-472066* |
The Review Summary section link scrolls to and expands the incorrect section when one of the sections in a given page layout is hidden due to not having any fields associated with it.
|
DEV-473763 |
When a user enters an invalid value when inline editing a date field in a related objects section of an object record, Vault incorrectly displays the date picker over the error message.
|
DEV-476017* |
When inline editing in a Complex Join section, Vault refreshes the entire section rather than only refreshing the edited grid box.
|
DEV-476751* |
In some cases, Vault displays a blank page when a user tries to inline edit a picklist field from the object record list page.
|
DEV-479000* |
On the report Sharing Settings page, the breadcrumb trail does not display correctly and only shows a link back to the main Reports list.
|
DEV-479067* |
After running the Copy Record or Edit action on a record from a Related Object section, the breadcrumb link back to the record detail page does not appear.
|
DEV-481230* |
After inline editing formatted text in a Rich Text field from a Related Object section, HTML tags appear until the user refreshes the page.
|
DEV-481840* |
When searching a Related Object section, results do not include matching fields if they are hidden in the section.
|
DEV-483313* |
Description |
Issue No. |
In some cases in Training Vaults using the Assign Effective Training or Initial Due Date features, users may incorrectly receive additional assignments.
|
DEV-475368* |
Vault does not disable the "Complete Training" button after a user clicks it and the dialog appears.
|
DEV-478907 |
Vault may display a server error when attempting to select an empty picklist value on a Quality Record Check component.
|
DEV-480802* |
In Vaults using the External Notifications feature, deleting a distribution group may incorrectly result in Vault displaying an error.
|
DEV-481395* |
Attempting to use MDL to RECREATE or delete External Notification configuration components when the component is referenced in a notification template may result in an error.
|
DEV-481423* |
The results banner in Vault Training quizzes may incorrectly contain a dotted line.
|
DEV-482632* |
Vault may display an error when a user attempts to change the Quality Relationship Automation field value in a Quality Record Check configuration.
|
DEV-483488* |
In some cases in Vaults using the Quality Record Check feature, the system may incorrectly create a match record when no matches are present.
|
DEV-483498* |
Users are unable to successfully run the Generate Merged PDF action when the Final Report doctype is associated with any lifecycle other than APQR Lifecycle.
|
DEV-484013 |
In Vaults using the External Notifications feature, the Add Distribution Groups dialog does not correctly display the Name of the distribution group.
|
DEV-484110* |
Under certain APQR configurations, the Generate Merged PDF action may not complete successfully.
|
DEV-485309* |
Users may see a new document type that should be inactive, APQR, and two new document subtypes available for selection when creating a new document.
|
DEV-486143 |
In rare circumstances, a Quality Team role assignment may be duplicated on an object record.
|
DEV-487631 |
In some cases, training fails to load for users due to a stale cookie.
|
DEV-489498 |
Description |
Issue No. |
When a user inputs duplicate values into Content Plan fields with the “Values must be unique” configuration, the Content Plan hierarchy viewer does not display an error message.
|
DEV-380580* |
In some cases, Vault does not remove open validation results after a Content Plan section is inactivated.
|
DEV-430359 |
Vault fails to report Rule 1306 when a Content Plan Item's Published Output Location contains multiple consecutive forward slashes ("/").
|
DEV-442686 |
In some cases, on-demand publishing of a single Content Plan Item in a given study triggers Vault to re-publish unchanged Content Plan Items in the same study.
|
DEV-472380* |
After users update a Report Level Content Plan, created records do not inherit join field values from parent records.
|
DEV-477591* |
In some cases, Submissions Publishing is rejected due to XML being generated with lower case HA tags.
|
DEV-478429 |
After a user clicks Cancel on the Regulatory Objective change warning dialog, Vault incorrectly clears selections on records.
|
DEV-478847* |
When a user selects ‘Commit’ in the IDMP Viewer, the resulting dialog reads “click Commit to save changes” instead of “click Continue to save changes”.
|
DEV-479460 |
There is a minor typo in the IDMP record generation results: “The confidentiality indicator field must be populated on the registered rite [site] role record."
|
DEV-479467 |
When generating a UDI submission, Vault falsely reports a validation error and omits the element tag from the XML if the Certificate Type contains the value “ex_4-6”.
|
DEV-480192* |
In some cases, Vault fails to populate the UDI Submission Type and Generated By fields when generating a UDI submission.
|
DEV-480902* |
Users in Vaults without a configured Content Plan or Content Plan Item object lifecycle encounter a server error when applying a Type filter in the Content Plan hierarchy viewer.
|
DEV-481343* |
The RIM harmonization job does not correct the placeholders created for some grouped Submissions.
|
DEV-481499* |
In some cases, Vault does not render any XML files when the Submission index.xml references non-existing XML leaf nodes.
|
DEV-482158* |
The Extract Application Relationships job fails if the user who initiates the action does not have permission to Read matching Submission relationship object fields.
|
DEV-482506* |
Vault does not meet system performance expectations when initializing the Submission Wizard.
|
DEV-483198* |
When Active Dossiers are populated from a Submission Content Plan, sections may be duplicated or missing.
|
DEV-484399 |
Japan submissions fail PMDA validation if the xlink:href field is blank.
|
DEV-486057 |
When a target document for a link is updated and Continuous Publishing is set to No, the source document is not up-versioned and the link is broken.
|
DEV-486202* |
Users are unable to modify notification templates that include the ${gatewayFailure} token.
|
DEV-486223 |
Users are unable to make changes to unverified Registration join record lifecycle states.
|
DEV-486229 |
When pre-selecting Application relationship records in the Submission Wizard, Vault displays only 1,000 records (instead of 2,000).
|
DEV-487018* |
Vault does not include the Application folder within the zip file for AS2 transmissions to Health Canada.
|
DEV-487680 |
In some cases, Edit Table of Contents page goes blank when a user scrolls to the bottom of the page.
|
DEV-487837* |
In some cases, the Manage Registered Details wizard displays a generic error message in the validation results file.
|
DEV-488881* |
The Manage Registered Details wizard omits Registered Packaged Medicinal Product records from scope definition.
|
DEV-490585* |
The RegulatoryOne release, including all Platform fixed issues, is targeted for tentative availability on June 14, 2022.
The Safety release, including all Platform fixed issues, is targeted for tentative availability on June 9, 2022.
Description |
Issue No. |
Fixed an issue where Inbox Item fields did not appear in the language set on the Default Localization field of the user profile.
|
SAF-24972 & SAF-28387* |
Fixed an issue with Date Received by Manufacturer (Section G4) field mapping when generating FDA MedWatch 3500A forms. Now, the Case New Info Date field (if populated) will be used for the Date Received by Manufacturer on the form for both Initial and Follow-Up Cases. If the New Info Date field is blank, the field on the form will be populated as follows:- For Initial Cases, the Initial Receipt Date field will be used.
- For Follow-Up Cases, the date will be left blank.
|
SAF-26026 |
Fixed an issue with global Case processing where, when trying to update the rank of a Product with a Substance to a Product without a Substance, an error appeared if the Product with a Substance was on a linked Localized Case.
|
SAF-27681 |
Fixed an issue where, when Cases were imported using migration user, the Imported Cases were not automatically indexed for duplicate case detection.
|
SAF-27780 |
Fixed an issue where, when an Adverse Event Report was created from a non-E2B source file with a date in the Receipt Date field, the date was not applied to the New Info Date field on the Inbox Item.
|
SAF-27863 |
Fixed an issue where, when promoting E2B-imported Inbox Items, incorrect values appeared in the Source Type field on Case Assessment Results.
|
SAF-27871 |
Fixed an issue where, when the Evaluate Reporting Obligations action was run on a Case with a product registered in multiple countries, the exported E2B files incorrectly included the country-specific registration details entered on the Case Product for all countries instead of just the registration in the target jurisdiction.
|
SAF-27877 |
Fixed an issue where, when importing an E2B(R2) file that included multiple Adverse Events with the same MedDRA code, the Case Assessment records were not imported correctly.
|
SAF-27954 |
Fixed an issue with generating E2B(R3) files where the system was missing the following field validations:- C.2.r.2.1 Reporter’s Organisation field may not exceed 60 characters
- C.5.1.r.1 Study Registration Number must be populated, and must conform to the format YYYY-######-##, for example 2022-123456-78
|
SAF-28032 & SAF-28218 |
Fixed an issue where, when promoting an Inbox Item to a Case, the "D'ag'U" Dose Unit incorrectly appeared as "D\'ag'\U".
|
SAF-28184* |
Fixed an issue where, when a Case was locked, the system prevented SDK jobs from updating the Case and its child records.
|
SAF-28203 |
Fixed an issue where a term in the Vault Safety Designated Medical Events (DME) Watchlist did not match the EMA DME. The term Immune thrombocytopenia (10083842)* was added.
|
SAF-28217 |
Fixed an issue where, when using EMA E2B(R3) as the base document type for a custom E2B format, the Patient RoA TermID Version and Parent RoA TermID Version E2B data elements were set to version 2.2, instead of 2.1.
|
SAF-28256 |
Fixed an issue where, when a Case Test Result (Text) field had more than 18 characters, all subsequent field characters were replaced with zeroes on CIOMS I and FDA 3500A forms.
|
SAF-28354 |
Fixed an issue where the Age and Weight fields were not populated on the CIOMS I form after report generation if the following setup was present on the Case:- Age (normalized) was blank
- Weight (normalized) was blank
Now, if the Age (normalized) or Weight (normalized) fields are blank, the Age or Weight value and unit (if present) are exported and set on the CIOMS I form.
|
SAF-28482 |
Fixed an issue where, when the “AE in Jurisdiction” rule parameter on a rule set was set to No, Vault Safety did not apply the Agency Rule.
|
SAF-28534 |
Fixed an issue where, when editing a manually created Inbox Item to add a Product record, the system displayed an error.
|
SAF-28535* |
Fixed an issue where, on the NMPA Report Source Controlled Vocabulary type, editing the Name field was prevented by the system.
|
SAF-28619 |
Fixed an issue where the Weight field was not populated on FDA MedWatch 3500A forms after report generation if only Weight (normalized) was present. Now, if the Weight value and unit are blank on the Case, the Weight (normalized) field (if present) will be exported and set as the Weight on the FDA 3500A form.
|
SAF-28687 |
Fixed an issue where, when creating an Inbox Item, if a mixture of precise dates (for example, YYYY/MM/DD) and partial dates (for example, YYYY) was used for specific field combinations, and those dates included the same year, the system prevented Inbox Item creation.
|
SAF-28723 |
Fixed an issue where, when importing an E2B(R3) file, if the Date of Birth was a partial date (for example, YYYY), the Date of Birth field was blank on the Inbox Item.
|
SAF-28779 |
Fixed an issue with migrated Cases where the country was not populated on CIOMS I or FDA 3500A forms after report generation. Now, the fields will be populated as follows:- CIOMS I: The 1a. Country field is mapped from one of the following Case fields, ordered by priority: primary Adverse Event Country, primary Reporter Country, non-primary Reporter Country.
- FDA 3500A: The E.1. Name and Address > Country field is mapped from the Case primary Reporter Country.
|
SAF-28781 |
Fixed an issue with migrated Cases where if either the Normal Low Value or Normal High Value fields were blank, the normal range for the test was not populated on CIOMS I or FDA 3500A forms after report generation. Now, if one field is blank, the missing part of the range is populated as "Unknown". If neither the Normal Low Value nor the Normal High Value is populated on the Case, the normal range for the test is not included on generated reports.
|
SAF-28782 |
Fixed an issue where expectedness was not evaluated correctly when cross reporting to a study for the same product.
|
SAF-28890 |
Fixed an issue where, when a Case was missing a UID, the List of Subjects Who Died During the Reporting Period was not generated, preventing DSUR report creation.
|
SAF-29033 |
Fixed an issue where, when a Case Test Result value and unit were blank, the system prepended a zero to Case Test Result (Text) fields on CIOMS I and FDA 3500A forms.
|
SAF-29165 |
Fixed an issue where, after importing an Inbox Item from a non-E2B source document, if you manually changed the New Info Date on the Inbox Item, the Receipt Date was being populated incorrectly upon Case promotion.
|
SAF-29301 |
The Veeva Claims release, including all Platform fixed issues, is targeted for tentative availability on June 14, 2022.