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. |
|
The Safety Document field value is applied to subsequent document versions in Vaults with Site Connect enabled.
|
DEV-338748 |
|
In some cases, CTN Data Change Log records do not contain Study, Study Country, or Study Site values.
|
DEV-349227 |
|
In some cases, new documents transferred from a Clinical Operations Vault result in a new version of a document previously transferred to a SiteVault Vault.
|
DEV-350361 |
|
In some cases, Vault may not transfer all documents in Site Packages that contain large volumes of data.
|
DEV-351168 |
|
Activating an Agreement may cause performance issues.
|
DEV-353675 |
|
In some configurations, the Create Draft user action sets the Quality Issue metrics on a document to null.
|
DEV-354125 |
|
Resolving Quality Issues on archived documents results in a server error.
|
DEV-354441 |
|
Vault does not prevent Quality Issues from being reassigned to Application Owner & Clinical Network users.
|
DEV-354874 |
|
In some cases, the Send Agreement Invitation user action results in a server error in Vaults with Site Connect.
|
DEV-356378 |
|
Inactive values are included in the Milestone Category picklist on Homepages.
|
DEV-357207 |
| Description |
Issue No. |
|
When selecting facets for a search in the Portal Library, the screen refreshes on each click and users are unable to select additional facets.
|
DEV-342331 |
|
In some cases, Vault does not display values for document URL tokens in notifications.
|
DEV-345297 |
|
Users are able to add multiple instances of the same portal to the Related Portals widget.
|
DEV-347189 |
|
In some cases, regenerating a compliance package does not update the 2253 form.
|
DEV-352639 |
|
Vault incorrectly changes the state of a regenerated compliance package.
|
DEV-353780 |
|
Vault does not display all related portals in the Related Portals widget.
|
DEV-353818 |
|
When a user attempts to add a document on which they don't have the Edit Fields permission to a Portal widget, Vault displays a “server having problems” error instead of a more helpful message.
|
DEV-354077 |
|
When regenerating a Pre Clearance Compliance Package with field Center set to CDER – OPDP, Vault incorrectly generates the 2253 and Supplementary forms.
|
DEV-355812 |
| Description |
Issue No. |
|
In some cases, PDF renditions with embedded fonts include an extra character.
|
DEV-345193 |
|
If Vault defaults a field value into a controlling field during Make a Copy, field dependency rules do not take those default values into account.
|
DEV-346111 |
|
In some cases, a page with a list of font names is added to rendered documents.
|
DEV-346939 |
|
When attempting to render a file that does not have a file extension, Vault displays an incorrect error message.
|
DEV-348053 |
|
In certain cases, Vault may fail to render Word documents containing eSignatures.
|
DEV-349489 |
|
In Vaults with Auto Claims Linking enabled, Vault ignores wildcards in Match Text and Match Text Variations when {curly brackets}, asterisks(*), or both are included in excluded characters.
|
DEV-351292 |
|
If a user opens the Select Anchors dialog for the same Claim record in multiple separate browser tabs, Vault does not prevent the user from creating multiple references to the same Link Target.
|
DEV-352625 |
|
If Vault defaults a field value into a controlling field during Make a Copy, field dependency rules do not take those default values into account.
|
DEV-353326 |
|
Users are able to see the “Get Link Annotation Data” action by performing Bulk Actions from the Cart view.
|
DEV-354750 |
|
In some cases, users cannot re-render documents created before June 2019.
|
DEV-355024 |
|
Vault does not prevent the creation of duplicate references to a Claim
|
DEV-355537 |
|
In some cases, the Document Version field in the References section of a Claim is blank.
|
DEV-358070 |
|
Documents crosslinked to a Steady State version in a source Vault that is in migration mode may have the wrong Bound Source Version.
|
DEV-359246 |
| Description |
Issue No. |
|
Adding a long-text field to a high-volume object may fail due to improper indexing.
|
DEV-346203 |
|
When trying to delete a record with inbound references, the error messages only tells the user what object has the blocking records. Instead, this error message should provide the list of blocking records.
|
DEV-350962 |
|
Vault configuration migration packages may fail to deploy in a destination Vault if a custom index for a high volume object was added to the source Vault.
|
DEV-353311 |
|
In some scenarios, performing a “Deep Copy” or “Hierarchical Copy” does not copy related section records when custom sharing rules are enabled on the child object.
|
DEV-353419 |
|
When setting an object type-specific field default, Vault sets the default field value for inactive fields.
|
DEV-353908 |
|
In some cases, Vault allows single-value picklists to be converted to multi-value picklists even when they are used in the defaulting rule of another picklist field.
|
DEV-353938 |
|
If a high volume object which contains an auto-indexed field is added to a destination Vault using a configuration migration package, and the auto-indexed field is removed from the source Vault, subsequent configuration migration packages containing the high volume object may fail to deploy in the destination Vault.
|
DEV-354400 |
|
In scenarios where unique values do not make sense, selecting the “Values must be unique” option on an HVO object's document reference field causes a server error. Instead, the error should tell the user why this option does not make sense.
|
DEV-357102 |
| Description |
Issue No. |
|
Certain configurations including Quality Teams and Formatted Outputs may cause errors when creating configuration migration packages.
|
DEV-346264 |
|
Viewing Quality Events has decreased performance.
|
DEV-353645 |
|
In some cases, submissions to the electronic submissions gateway may be missing information.
|
DEV-354631 |
|
In certain cases, the FDA ESG rejects XML submissions sent via Vault Product Surveillance.
|
DEV-355386 |
|
The electronic submissions gateway may not return a failure message after it receives a submission with an incorrect Health Authority ID value.
|
DEV-355835 |
|
Setting an inactive field as required on the Proposed Audit and Audit Program Planning objects may result in an error when creating Audit Records.
|
DEV-356611 |
|
Vaults that do not have the Vault Product Surveillance application may incorrectly see its associated document types in their document type list.
|
DEV-356965 |
|
In some cases, actions utilizing QMS User Templates may result in an error if special characters are used in names on the targeted Person record.
|
DEV-357624 |
| Description |
Issue No. |
|
Vault doesn't up-version published documents after they are locked or unlocked.
|
DEV-329475 |
|
In the Manage Registered Details wizard, no filter values appear when users attempt to apply a filter on Object fields that reference complex join objects.
|
DEV-339379 |
|
After initial submission publishing, links in published source documents don't always navigate users to the correct published target documents in the current submission.
|
DEV-339612 |
|
After continuous publishing, when a source document is matched across multiple submissions, some source documents are missing from submission exports or the XML, and link navigation doesn't always work.
|
DEV-340560 |
|
During continuous publishing, Vault does not convert target documents to placeholder documents when users unmatch the source document in the current submission but the target exists in another application or submission.
|
DEV-340610 |
|
Vault does not publish some Vault links when users match source documents to content plan items that are initially publishing the submission.
|
DEV-341238 |
|
In the View Manager within the Content Plan Hierarchy Viewer, Vault does not show a warning dialog to users when they attempt to open a view that they cannot access.
|
DEV-346027 |
|
Continuous publishing does not publish all links after a matched target document is unlocked.
|
DEV-346519 |
|
Vault does not resolve permalinks in published target documents within the current submission if the link target URL is locked to an earlier document version.
|
DEV-347276 |
|
In some cases, when users copy from an existing content plan, the results notification does not accurately reflect records that Vault failed to create.
|
DEV-347457 |
|
Performance is slower than usual when users delete a content plan containing over 100,000 records.
|
DEV-347463 |
|
If a source document is matched in separate submission content plans for different regions, continuous publishing does not always publish links if the link target exists is only one of the submissions.
|
DEV-348656 |
|
Vault performance is slow when creating or updating many records from the Manage Registered Details wizard.
|
DEV-350357 |
|
When publishing Japanese submissions, Vault does not resolve links to the submission with the latest Actual Submission Date.
|
DEV-350498 |
|
After users unlock a previously locked matched document, continuous publishing does not publish links in the latest document version.
|
DEV-350527 |
|
Vault includes the incorrect source file paths for grouped submissions in the XML when dossier formats are applied.
|
DEV-350913 |
|
On the Submission Administrative Information page for Japanese Submissions, Vault does not set the Application Date field to the current date as the default value, and the field is blank.
|
DEV-351553 |
|
When working with Japanese submissions, users can select the same Additional Submission Type value multiple times in the Submission Administrative Information viewer, and Vault includes duplicate values in the XML.
|
DEV-351557 |
|
Vault does not create node extensions correctly in the cumulative submission XML.
|
DEV-351727 |
|
After applying an advanced filter in the Submissions Archive Viewer, when users open a document, Vault navigates them to the Notifications page.
|
DEV-351995 |
|
Vault incorrectly reports CA validation rules B35 and B37 for broken hyperlinks/bookmarks across applications instead of rules B06 and B17.
|
DEV-352938 |
|
In Vaults with Configurable Impact Assessment Reports enabled and configured, the Create Related Records action is sometimes available from an Impact Assessment Report when it shouldn't be.
|
DEV-353104 |
|
Continuous publishing does not update relative link paths after a user updates the source document's Published Output Location if the target is a cross-application document.
|
DEV-353305 |
|
Applying column filters for some field types in the Content Plan Hierarchy Viewer results in a Vault error.
|
DEV-353561 |
|
Vault includes the incorrect source file paths for grouped submissions in the XML.
|
DEV-353612 |
|
In the Content Plan Hierarchy Viewer, when users attempt to share a saved view with a group and expand the group in the dialog before clicking OK, Vault displays an error.
|
DEV-354401 |
|
During continuous publishing, Vault removes link anchors if the link target document's Published Output Location changes.
|
DEV-354407 |
|
Vault performance is slow when publishing a report level content plan that includes Vault annotations.
|
DEV-354514 |
|
After publishing and merging a report level content plan that contains placeholders matched to content plan items, Vault fails to republish the placeholders when users attempt to publish again.
|
DEV-355046 |
|
Vault performance is slow when users import large submissions using Vault File Manager.
|
DEV-355830 |
|
In some cases, deleting sections from a Content Plan results in no available actions in the Actions menu for the Content Plan.
|
DEV-359268 |