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 default field labels display the ID value instead of the Name value on the Field Rule Detail page.
|
DEV-343872 |
|
Some text boxes and columns are not displayed as expected in Safari, Firefox, and Internet Explorer.
|
DEV-347759 |
|
Vault does not display a default value for the Rendition Status dropdown menu.
|
DEV-347865 |
|
In some cases, clicking the Select All button on the Review and Select Steps page when deploying a configuration migration package may not correctly select all items.
|
DEV-362030 |
|
In some scenarios, jobs stay in “Running” status and do not succeed or fail.
|
DEV-362366 |
|
In some cases, clicking on a Web Action record results in a server error.
|
DEV-364404 |
|
If a job condition references a deleted record, the job and associated audit trail may not update properly.
|
DEV-366315 |
|
In some cases, editing and then saving a scheduled job instance changes the scheduled Time from PM to AM.
|
DEV-366436 |
|
In some cases, the Filter Tab field on custom tabs does not display the filter value, though the filters are applied as expected.
|
DEV-365468 |
| 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, the Payment Level picklist does not display all expected values.
|
DEV-350737 |
|
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 |
|
Updating or resolving Quality Issues on recently archived documents results in a server error.
|
DEV-354441 |
|
Inactive values are included in the Milestone Category picklist on Homepages.
|
DEV-357207 |
|
Saving Study Product or Study Person records without a value in the Study Role field results in a server error if EDL creation is triggered on that record
|
DEV-363832 |
|
The SDV Requiredness field does not update as expected via the EDC/CTMS Spark Connection.
|
DEV-364931 |
|
The SDV Requiredness value does not always transfer correctly from CDMS via the EDC/CTMS Spark Connection.
|
DEV-365043 |
|
In some cases, Vault does not create CDX Issues when Configuration Mapping records have invalid field mappings.
|
DEV-365388 |
|
In some Vaults, attempting to open the Selected Study Organization Role Detail Page Layout results in an error.
|
DEV-366211 |
|
In some cases, users see a Page Not Found message after sending a document package to a study site.
|
DEV-366638 |
| 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 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 |
|
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 |
|
Removing the Document Version value from a Claim Reference results in an error.
|
DEV-362668 |
|
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 |
|
In some cases, Vault generates zero byte files when downloading a PDF with annotations.
|
DEV-367323 |
| 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 |
|
When setting an object type-specific field default, Vault sets the default field value for inactive fields.
|
DEV-353908 |
|
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 |
|
In some cases, attempting to create a Deep Copy of a secured parent object record causes an unexpected error.
|
DEV-364684 |
| Description |
Issue No. |
|
Expanding or collapsing a related object section has decreased performance.
|
DEV-347552 |
|
Under certain conditions initiating a user action may fail.
|
DEV-351439 |
|
Under certain conditions, users are unable to start a workflow action.
|
DEV-351813 |
|
Some Vaults may experience slowness or data errors for PDF and InDesign renditions due to a configuration error.
|
DEV-353348 |
|
Pressing the Page Down key on the document viewer may cause the page to continuously scroll up and down.
|
DEV-356399 |
|
When a user receives the error “Another record has the same value” when editing a picklist, the error message is displayed twice.
|
DEV-360296 |
|
In some cases, inline editing a cell on an object record page may freeze the page, making other actions impossible
|
DEV-360594 |
|
Attempting to activate custom jobs related to Study Person object records fails and results in performance problems.
|
DEV-366633 |
| Description |
Issue No. |
|
Vault doesn't up-version published documents after they are locked or unlocked.
|
DEV-329475 |
|
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 |
|
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 |
|
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 performance is slow when publishing a report level content plan that includes Vault annotations.
|
DEV-354514 |
|
In some cases, Vault cannot render or re-rend the Index XML file properly.
|
DEV-355621 |
|
Vault performance is slow when users import large submissions using Vault File Manager.
|
DEV-355830 |
|
After users delete a Content Plan section or Content Plan Item and continuous publishing runs, Vault fails to delete the related Submission Validation Result records.
|
DEV-359731 |
|
Validation rule CA F09 fails for some sequence descriptions.
|
DEV-362498 |
|
When the next version of a matched document contains a permalink pointing to the original version, Vault doesn’t resolve links properly during publishing or update the Published Document field to reflect the latest published version.
|
DEV-364466 |
|
During report level publishing, Vault updates the source file path incorrectly on published documents.
|
DEV-365262 |
|
When updating registration fields in the Manage Registered Details wizard, users cannot update custom document reference fields.
|
DEV-366119 |
|
In some cases, Sequence IDs with hyphens causes continuous publishing to fail.
|
DEV-367255 |
| Description |
Issue No. |
|
In Vault Safety 20R3, there is an issue where a warning notification does not appear when exporting an E2B R2 file from a Case with invalid data entered on the Case Product Dosage section.
|
SAF-12491 |
|
In Vault Safety 20R3, there is an issue with duplicate detection where Cases are not listed as potential matches when the only matching fields are ID fields (Worldwide UID, UID, External System UID).
|
SAF-12616 |
|
In Vault Safety.AI 20R3, there is an issue where the Transmission Record remains in the Active state instead of moving to the Error state when the Intake API is unsuccessful.
|
SAF-12725 |
|
In Vault Safety.AI 20R3, there is an issue where the Transmission Record remains in the Active state instead of moving to the Error state when the Intake API is unsuccessful.
|
SAF-12725 |
|
In Vault Safety.AI 20R3, there is an issue where users are unable to generate a transmission document on a Promoted Transmission record. However, when an AER is promoted to a Case, the transmission documents can be generated.
|
SAF-13232 |
In Vault Safety 20R3, there is an issue where an .rtf formatted file uploaded to a Case is considered invalid during EMA E2B R3 file generation.
Workaround: Convert the file to .docx format and retransmit with that file format.
|
SAF-13234 |
|
In Vault Safety.AI 20R3, there is an issue where an Inbox item cannot be created when a JSON document or form is attached to it.
|
SAF-13259 |
|
In Vault Safety 20R3, there is an issue where the Case Watchlist tag is updated with a contituent product’s watchlist tag when the constituent product has an associated Watchlist, but the Combination Product does not.
|
SAF-13295 |
In Vault Safety 20R3, there is an issue where gateway transmissions with validation errors become stuck in the Sending ICSR state. When the Submit to Gateway action is run, Vault Safety regenerates the .xml file and validates the E2B xml. If there are any validation errors, the record state changes to Validation Error before the file is submitted to the gateway. Since submissions can only happen from the Ready for Submission, Ready, and Pending states, the record becomes stuck in the Sending ICSR state with the file never submitted.
Workaround: - Fix all validation errors.
- Retry the gateway transmission.
If the transmission does not send, you can download the file and complete the submission through EVWeb.
|
SAF-13432 |
In Vault Safety.AI 20R3, there is an issue where a server error message is displayed when users attempt to save a product after performing a delete product action and then performing an undelete product action immediately afterwards.
Workaround: Refresh the page to clear the server error message.
|
SAF-15929 |
| Description |
Issue No. |
|
In some cases, documents transferred from SiteVault do not include Product metadata.
|
DEV-349153 |
|
In Vaults with digital delegation log enabled, the Assigned Responsibilities section of User records is missing.
|
DEV-350249 |
|
Changing a Study Person's delegations creates a DOA log document that is the same as the previous version.
|
DEV-351133 |
|
In some cases, Vault creates duplicate Distribution Tasks when the Send Document via Clinical Network action is taken.
|
DEV-353537 |
|
In some cases, the Send Document via Clinical Network action creates duplicate distribution tasks.
|
DEV-354697 |
|
In some cases, users cannot create multiple Research Organization records.
|
DEV-358405 |
|
In some cases, saving a new Study record results in an unexpected error.
|
DEV-367141 |