The following applications may have different release dates: Safety, RegulatoryOne, and Veeva Claims.
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.
| Description |
Issue No. |
|
When creating a Content Plan from a Content Plan Template, content plan creation fails if the initiating user doesn’t have Read permission to a field on the Content Plan, even if the field is not on the Content Plan object type.
|
DEV-219334 |
|
After the initial publishing of a submission, if users set Enable Continuous Publishing to “No”, add new Content Plans (EDLs) and Content Plan Items (EDL Items), and run on-demand publishing from the parent Content Plan, Vault publishes the new Content Plan but not the new Content Plan Items.
|
DEV-214694 |
|
After completing the Run On-Demand Publishing action on a parent Content Plan record of a form Content Plan Item record, other forms no longer appear in viewer.
|
DEV-218678 |
|
After enabling the bundling wizard feature, bulk creating registrations no longer populates the regulatory objective.
|
DEV-214654 |
|
After publishing a submission, Vault doesn’t display a list of available actions when users click the Actions menu while in binder List View.
|
DEV-218307 |
|
After the primary submission is published, sometimes the forms for non-primary submissions appear incorrectly in the US Regional XML.
|
DEV-214483 |
|
Content Plan Items that have never been published and have Continuous Publishing set to No will appear in the published index and regional XML files.
|
DEV-214336 |
|
Help Content for Gateway Profile fields is not correct or unavailable.
|
DEV-213083 |
|
If a lifecycle has been applied to the Product Report object, outdated Product Report records will not be set to inactive as part of the Create Product Report lifecycle action.
|
DEV-214818 |
|
If Medicinal Product or Medicinal Product Full Name records don’t exist in Vault, users cannot create Product Report or Product Report Item records of the Presentation object type.
|
DEV-209700 |
|
In exports of non-primary submissions, the index-md5 is not named correctly and is not located in the right place within the submission.
|
DEV-213001 |
|
In some cases when splitting regulatory objectives, if a user attempts to search for a record, Vault returns the user the first page of the wizard.
|
DEV-218150 |
|
In some cases, links on published documents of non-primary submissions lead to a Document Not Found error.
|
DEV-210187 |
|
In some cases, the US Regional XML does not contain correct content for subsequent grouped submissions.
|
DEV-217783 |
|
In some cases, users encounter a file not found error when attempting to download validation results from an attached EDL item on a published report level content plan.
|
DEV-211164 |
|
In the RIM Registration App, users receive an error when trying to edit the rim_product_report_view__v notification template.
|
DEV-211087 |
|
Matching/unmatching a document to/from an EDL Item for a non-primary submission does not trigger Continuous Publishing.
|
DEV-213162 |
|
On an attachment document, Vault sets the Operation Type on the Product Item Report to the Operation Type value set on the Product Data Submission record.
|
DEV-218524 |
|
Previous EV Codes of lengths greater than 128 characters will not create a Previous EV Code Product Report Item (PRI) record.
|
DEV-214641 |
|
Product Report Items (PRIs) with a lifecycle applied will not be set to Inactive on subsequent generation of the Product Report.
|
DEV-218943 |
|
Product Report record creation fails if there is no associated Medicinal Product Registration record.
|
DEV-212476 |
|
Records filtered by objects on a product report do not appear when Vault exports the report to CSV or Excel.
|
DEV-205474 |
|
Running on-demand publishing does not update the regional or index XMLs.
|
DEV-210921 |
|
The Create Related Records Wizard fails when using Controlled Vocabulary fields that are constrained.
|
DEV-213461 |
|
The Published document field on EDL Item is not cleared when users remove a content plan from the Submission record.
|
DEV-212846 |
|
The published source document of a report level content plan with a named destination pointing to either a bookmark or other named destination does not have the correct zoom settings.
|
DEV-212767 |
|
The Submission Archive viewer shows the download button when the user does not have download permission.
|
DEV-205327 |
|
The Submission object page layout does not include the Workflow Timeline section by default.
|
DEV-212588 |
|
Users without permission to access the Product Report Item object cannot view Product Report records in Viewer.
|
DEV-209298 |
|
Vault does not create a Product Report Item if the requesting user does not have view permission for the document.
|
DEV-211090 |
|
Vault doesn’t create a document via the Create from Document user action when multiple values are selected in a picklist field on the Content Plan Item record but only a single value is allowed on the document field.
|
DEV-205725 |
|
Vault fails to publish certain Report Level Content Plans and show “Error when bulkPublishDocuments: This relationship already exists.”
|
DEV-214267 |
|
Vault fails to publish subsequent grouped submissions after an initial grouped submission has been published.
|
DEV-217552 |
|
Vault gives a job failure notification after users copy a Product Report.
|
DEV-205446 |
|
Vault should ignore the Continuous Publishing setting when users initiate on-demand publishing and validation for an EDL Item.
|
DEV-211425 |
|
When a permalink in a report level content plant points to a valid Destination, Vault incorrectly reports RLCP103 in publishing validation results.
|
DEV-212626 |
|
When a user attempts to view the Product Report object without the proper permission, Vault returns a server error.
|
DEV-209117 |
|
When copying related data from a regulatory objective to a submission, Vault does not check for duplicates and you may see duplicate records on the submission joins.
|
DEV-208473 |
|
When creating a document from a template, Vault matches the document to a Content Plan Item as “System” and not as the user who performed the action.
|
DEV-217694 |
|
When creating a Product Report record, Vault does not use the label from the Presentation object type to populate the Product Report name field.
|
DEV-209780, DEV-217531 |
|
When creating multiple Medicinal Product Name Part records, Vault does not populate the Medicinal Product Name Part field on the Product Report Item record with the correct value.
|
DEV-209864 |
|
When generating an xEVMPD product view for a complex drug product, Vault creates the Product Report section for a Pharmaceutical Product even when the correct related data is not present.
|
DEV-212787 |
|
When generating an xEVMPD product view for a product with a concentration type that is not a range, Vault populates the strength values with concentration strengths rather than presentation strengths.
|
DEV-212860 |
|
When re-creating an xEVMPD product report, the Validity Declaration field resets from “1” to null. Users will need to set this back to “1” prior to XML generation.
|
DEV-214722 |
|
When re-generating the xEVMPD Product Report, any Product Report Item records that are re-used are not correctly set to the Active status and are left in an Inactive state.
|
DEV-214472 |
|
When using Firefox, the first time a user navigates to the Viewer tab, the tab is empty.
|
DEV-217319 |
|
If bundling is enabled, the Create Related Records wizard does not populate the Submission – Regulatory Objective join when creating Submissions and Regulatory Objectives.
|
DEV-216447 |
|
Vault cannot generate a TOC when processing large Report Level Content Plans with a TOC Content Plan Item.
|
DEV-216439 |
|
When creating a content plan from a template, Vault populates the table of contents with the picklist value name instead of the label.
|
DEV-209944 |
|
Vault populates the binder for invalid, subsequent submissions.
|
DEV-208894 |
|
Vault does not report validation rule 3036 when the XML application number is not 6 digits.
|
DEV-208498 |
|
Vault erroneously reports validation criteria 5005, 5020, and 3102 on published submissions.
|
DEV-206868 |
|
When an invalid grouped submission is configured, the forms for the invalid submission in the group are still published and displayed in the published Submissions Archive Binder and XMLs.
|
DEV-212132 |
|
Vault is not correctly rendering 2253 form in RIM Submissions.
|
DEV-219000 |
|
In some cases, when a single document matches to a different Content Plan Item within one Content Plan, Vault exports the document twice in the published binder.
|
DEV-222293 |
|
In some RIM vaults, field information is incorrect on the Controlled Vocabulary object.
|
DEV-222255 |
|
Bulk Create Registrations does not recognize GB and GR country codes for the United Kingdom and Greece respectively.
|
DEV-222214 |
|
Some users are unable to proceed through the bundling or splitting wizards if there are required Yes/No fields configured on regulatory objective object records.
|
DEV-222050 |
|
In some cases, the form for the non-primary submission within a Grouped Submission is incorrectly associated with the primary submission.
|
DEV-223023 |