The issues listed below are fixed in the 21R2 release.
| Description |
Issue No. |
|
Some non-Vault Owner users may be able to see a Vault in configuration mode on their My Vault page, and are redirected to the Login page when selecting such a Vault.
|
DEV-235474 |
|
Components may be missing from Outbound Packages if duplicate records are created when a job is altered.
|
DEV-356839 |
|
When exporting an object and the OFFSET exceeds the total record number of the object, Vault Loader extract records from OFFSET 0 rather thanreturning an empty result file.
|
DEV-365233 |
|
In some cases, Quality Team components are not included in auto-generated VPKs.
|
DEV-373540 |
|
In rare scenarios when creating a user through the UI, the newly created user may appear with a different First and Last name than specified during user creation.
|
DEV-381195 |
|
For sandbox vaults with linked file staging servers, users are unable to refresh the sandbox even after deleting all other vaults sharing the same linked file staging server.
|
DEV-383778 |
|
When Vault updates the last_login_date field on a user, Vault also sets the last_modified_by and last_modified_date fields for the user.
|
DEV-383812 |
|
Admins cannot update object picklist fields to be multi-select when a picklist field on another object uses a dynamic default expression that references the original picklist field.
|
DEV-383830 |
|
Users experience an error and the load fails when using Vault Loader to upsert object records containing blank values for object reference fields.
|
DEV-385701 |
|
In some scenarios, Vault updates the Edit Localized Labels field to blank.
|
DEV-386902 |
|
Users with the Business Administrator security profile are unable to view a User object's Email Preferences fields.
|
DEV-387355 |
|
In rare cases, certain components are missing from exported VPKs even after refreshing the component directory.
|
DEV-387978 |
|
When delegating user accounts through a user detail page (Admin > Users & Groups > Vault Users), users receive different options for start dates than when delegating through Admin > Users & Groups > Active Delegations.
|
DEV-389084 |
|
In rare scenarios, valid VPKs fail to deploy.
|
DEV-394533 |
|
In IE11, when adding a reference lookup to an existing integration rule, the labels for required fields are truncated and therefore difficult to read.
|
DEV-395801 |
|
Criteria VQL with reference criteria referencing Lifecycle State (state__v) in a subquery fails.
|
DEV-397477 |
|
A Vault Owner using Vault Loader to update user account records may be able to inadvertently deactivate their own account.
|
DEV-397732 |
|
In certain scenarios, users receive an authentication error with correct credentials when attempting to access the file staging server.
|
DEV-399199 |
|
Admins who are active in one vault and inactive in another vault on the same domain experience a server error instead of a permission error when editing vault membership of another user in the vault where the Admin is inactive.
|
DEV-400104 |
|
When a Security Policy's Authentication Type is changed from Password to Single Sign-on, Vault Compare and Configuration Reports omit eSignatureProfile settings and display values for Minimum Password Length and Password History Reuse associated with the Password Authentication Type configuration.
|
DEV-402293 |
|
In some cases, users are unable to edit Matching Sharing Rules when creating a new document lifecycle role with Dynamic Access Control enabled.
|
DEV-405526 |
|
When executing a Multi-File Extract Job, filenames that contain commas may not extract properly.
|
DEV-408678 |
|
Users cannot edit the label for Spark and Job Queues when using the Edit action from the Actions menu in the List View.
|
DEV-412175 |
|
In certain scenarios, sandbox vaults fail to refresh.
|
DEV-416656, DEV-413153 |
|
In vaults where Enable User Mentions in annotations is disabled, users experience a server error when loading the Notifications page.
|
DEV-423046 |
| Description |
Issue No. |
|
Vault fails to create a CDX Issue record when a study site cannot be created due to the license limit being reached.
|
DEV-345476 |
|
In some cases after switching views in the TMF Viewer, Vault does not display all content in the viewer.
|
DEV-366557 |
|
CTN Data Change Logs are created when Study Person records with CRA roles are created and the Include in CTN / 届出書記載 field is set to Yes.
|
DEV-379168 |
|
In some cases, Vault fails to roll up a planned date from a Milestone record into the related Country or Study records.
|
DEV-379844 |
|
In some cases, users may see Studies listed in TMF Viewer that they no longer have access to.
|
DEV-382250 |
|
In some cases, the TMF Viewer includes documents that are classified as document types that an Admin has set as Display in TMF Viewer to No.
|
DEV-382374 |
|
In some scenarios, Vault displays the ${choose_file} token in the File Upload Task dialog when users hover over the Choose button.
|
DEV-382621 |
|
In some cases, changes to the Name field on the CTN IP Name object are not included in the CTN Data Change Logs.
|
DEV-382717 |
|
The paragraph alignment in the CTN Microsoft Word™ document attachment is incorrect.
|
DEV-382724 |
|
In certain scenarios, the Send Safety Distribution Emails job fails.
|
DEV-384488 |
|
In some cases, updating a Study in Candidate state to Planning state causes the creation of erroneous Milestones.
|
DEV-385776 |
|
CTN Site IPs are not listed in the correct order number on generated CTN documents.
|
DEV-387525 |
|
In some cases, Vault deletes necessary User Role Setup records.
|
DEV-391383 |
|
In some cases, Vault does not create CTN Data / 治験届関連情報 records when an Organization with the CTN Organization for Japan enabled is modified.
|
DEV-392028 |
|
In some cases, clicking on the Create Monitoring Follow Up Letter action a second time on a Monitoring Event record results in an error, and the document version is not updated.
|
DEV-393031 |
|
If a user filters the documents in the TMF Viewer to display documents in Approved and In QC Review statuses, Vault only displays documents in Approved status.
|
DEV-393865 |
|
Incoming archived Study records transferred via TMF Transfer display the wrong Lifecycle State.
|
DEV-395274 |
|
In some cases, components related to the Veeva Site Connect and Vault Payments remain visible in a vault after they have been disabled.
|
DEV-395934 |
|
In some cases, Vault fails to apply DAC rules to previously unclassified documents once they are classified.
|
DEV-396315 |
|
In some cases after reclassifying a document, it is not included in the correct binder classification structure when it is configured to automatically file into a binder.
|
DEV-397204 |
|
TMF Transfer fails to send documents when the Reference Model matches the Document Type.
|
DEV-397664 |
|
In certain scenarios, Vault adds an Entry Action without a selection in the perform actions dropdown menu, which causes some lifecycle state change actions to fail and a server error.
|
DEV-398065 |
|
In some cases, when the creation of Study Person records fails due to a validation rule, Vault erroneously creates and deletes associated User Role Setup records.
|
DEV-398086 |
|
In some cases, Vault does not create CDX Issue records when the vault's FTP service is unavailable.
|
DEV-398250 |
|
Vault populates the Study, Study Country, and Study Site fields on CrossLink documents transferred via the Clinical Operations & RIM Vault Connection.
|
DEV-398911 |
|
In some cases, Vault does not show the document field attribute "Do not copy this field during Make a Copy".
|
DEV-401904 |
|
In some cases, documents mapped to the TMF TM v3.0 reference model cause an error when transferred via TMF Transfer.
|
DEV-402663 |
|
The Universal Site Number field is not read-only for users that do not have permission to edit the field.
|
DEV-402695 |
|
Vault only allows one document per Document Type to be sent in a Site Package.
|
DEV-404140 |
|
TMF Transfer does not support the transfer of more than 80000 documents at once.
|
DEV-405644 |
|
Vault displays a Network Issue error when clicking on an Issue record from the CRA Homepage.
|
DEV-407186 |
|
When objects in an EDL have inactive parents, Vault fails to create some automated items.
|
DEV-408684 |
|
Vault displays an unhelpful error message when some matching fields have a mismatched data type.
|
DEV-409177 |
|
In some cases, Vault displays an error when attempting to Complete a Vault to Vault connection between two eTMF vaults.
|
DEV-409411 |
|
In some cases, TMF Transfers fail when they contain very large quantities of documents.
|
DEV-409775 |
|
The Recalculate Enrollment Metrics user action, when run by some users without permissions to all related records, results in incorrect Enrollment Metrics.
|
DEV-410644 |
|
In some cases, archiving a Study fails due to a database timeout.
|
DEV-411001 |
|
Vault fails to show tooltips for some Clinical Operations fields.
|
DEV-413079 |
|
TMF Transfer fails to send documents between Vaults when Study-related lifecycles are not enabled on those Vaults.
|
DEV-413630 |
|
Vault only allows one document per Document Type to be sent in a Site Package.
|
DEV-414842 |
|
Vault fails to send surveys to external respondents unless the Vault Owner initiates the process.
|
DEV-414871 |
|
In some cases, Vault fails to display the correct user-specified Labels for fields.
|
DEV-414902 |
|
In some cases, Vault prevents the reuse of Study documents by users with limited permissions.
|
DEV-415040 |
|
Vault fails to complete Document Reconciliation when over 500 records are being checked.
|
DEV-415042 |
|
During very large transfers, TMF Transfer may fail to create some documents.
|
DEV-415425 |
|
In some cases, the Create Site Budget Records action incorrectly creates Budget Items multiple times.
|
DEV-415920 |
|
In some cases, TMF Transfer Agreement records can be modified when in states that shouldn't allow changes.
User accounts that are not a Clinical Network user, System user, or Application Owner account, or that contain an email address that doesn't end in "@veeva.com" cannot modify the following records: cdx_document_lifecycle_state_mapping_v, cdx_rulev, cdx_rule_setv, and cdx_scope_variable_v
|
DEV-416155 |
|
When an Update Metrics, Update Monitored Metrics or Enrollment Status Log Job fails due to a duplicate record, Vault does not log information about which record is duplicated.
|
DEV-416665 |
|
Vault fails to correctly populate the CTN Submission Date on the CTN Cover Letter.
|
DEV-417149 |
|
In some cases, Vault includes CTN remarks that are set to not be included.
|
DEV-417259 |
|
The Create Subsequent CTN action fails to copy the correct value for "Include in CTN" in the generated CTN Remarks.
|
DEV-417262 |
|
When over 500 records are being updated, Vault fails to complete the Generate Study Risk Assessment action.
|
DEV-417293 |
|
In some cases, Vault shows the incorrect state of a steady state SiteVault document.
|
DEV-417304 |
|
When copying into a Content Plan with an existing Submission Nonclinical Study join, Vault incorrectly creates a duplicate join.
|
DEV-418289 |
|
Vault fails to create related User Role Setup records when creating Study Persons in bulk via API or Vault Loader, even with create_urs__v = TRUE.
|
DEV-418713 |
|
When the Milestone Autocomplete field is set to "All Dependencies" or "Any Dependencies," Vault will incorrectly roll up actual finish dates even with Autocomplete enabled.
|
DEV-419255 |
|
The Notification Target of Development Termination CTN Notifications populates incorrectly, leading to incorrect header text in CTN documents.
|
DEV-419615 |
|
When performing the Complete action in the Document Inbox on a document that the TMF Bot has auto-classified, Vault requires the user to select a Document Type.
|
DEV-420627 |
| Description |
Issue No. |
|
On the Library tab in Tabular View, the Unmodified Source download option appears for users without the correct permissions.
|
DEV-326823 |
|
Vault generates blank pages with headers and footers from source documents with hidden text.
|
DEV-335393 |
|
In some cases, the table of contents generated for a document rendition may contain inconsistent ellipses.
|
DEV-347912 |
|
Vault fails to re-render previous versions of video files.
|
DEV-355493 |
|
Attempts to render files fail with an "unsupported file type" error message when Vault is in Document Migration mode.
|
DEV-370685 |
|
In some cases, users experience a server error when executing the Make a Copy action on documents with text annotations.
|
DEV-380636 |
|
Vault fails to render large .CSV files.
|
DEV-380725 |
|
When the user is a Vault Owner, clicking Download on a document with a Read & Understood task downloads the unmodified source file instead of the viewable rendition.
|
DEV-380937 |
|
In some cases, PDF files fail to render when "Allow viewing and annotation of protected PDF files" is enabled.
|
DEV-381040 |
|
Vault fails to finish rendering documents if a user promotes the document to a major version before the OCR process is complete.
|
DEV-383490 |
|
In some scenarios, users cannot change document owners in bulk and receive the email "An unexpected error occurred while processing the action."
|
DEV-383553 |
|
When using Vault in Internet Explorer 11, when a user removes a linked document relationship from a document in Mixed View, then goes to Field View and returns to Mixed View, the linked document relationship persists and the user experiences a server error when attempting to remove is a second time.
|
DEV-383833 |
|
When a user adds a link annotation to a document, Vault does not display the relationship in the Linked Documents section when the user first returns to Mixed View.
|
DEV-384226 |
|
In some cases, eSignatures are missing from documents after a user completes an eSignature approval.
|
DEV-388009 |
|
When a user downloads a PDF with annotations, if a single page fails to generate, the entire download fails.
|
DEV-389162 |
|
In some vaults, users can see the Import Document Links option in the document Actions menu and the Linked Documents section in the fields panel of the Doc Info page when the Allow creation of link annotations setting is not enabled.
|
DEV-389775 |
|
When one link annotation is active and a user selects Link to Content on another link annotation, Vault makes both link annotations active.
|
DEV-389965 |
|
After a signee updates their name, Vault changes their signature.
|
DEV-391234 |
|
Users experience an error when editing anchors with titles that contain the "%" character.
|
DEV-392499 |
|
In vaults where the standard Library tab is inactive, when a user uploads multiple documents, Vault redirects users who are Vault Owners to the inactivated Library tab, while users who are not Vault Owners are stuck on the upload screen.
|
DEV-392838 |
|
When users render a Microsoft Excel™ file with merge fields, Vault generates a text file with different formatting than the source file.
|
DEV-395079 |
|
When creating documents, Vault does not validate certain date fields, resulting in documents with invalid fields appearing in the Library.
|
DEV-395364 |
|
In some cases, creating a document from an Adobe® InDesign® package ZIP file may result in a "Missing fonts" error even if the font is present in the package.
|
DEV-395650 |
|
Under certain circumstances, deleting a viewable rendition and uploading a manual rendition results in an error.
|
DEV-397397 |
|
If the Binder Display Options: Unbound Documents setting on a document type is set to anything other than Latest Version, the Binder Document Viewer displays "null" instead of the product name.
|
DEV-398464 |
|
When a PromoMats Admin rapidly adds, removes, and re-adds anchors to an Auto Claim object record, Vault sometimes displays an unhelpful error message.
|
DEV-398573 |
|
Vault clears the Author and Tags filters on a document's annotations when a user creates, edits, or replies to an annotation.
|
DEV-398760 |
|
In some cases, Vault replaces filenames in headers and footers with rendition data.
|
DEV-399974 |
|
In some cases, Vault fails to generate OCR renditions.
|
DEV-401656 |
|
In some cases, documents fail to render due to missing font glyphs.
|
DEV-403022 |
|
When creating a document from a template, the "Choose document type" dialog shows document types that do not have a template, and selecting one of them results in a "Server having problems" error.
|
DEV-403090 |
|
In some cases, creating a document from a document template uses a superseded version of that template.
|
DEV-403104 |
|
Performing a Where Used search from a Library tab view may have unexpected or inconsistent results since the Library tab applies its own filters.
|
DEV-403629 |
|
After upversioning a document, Vault does not bring forward document metadata.
|
DEV-406148 |
|
In some cases, the Make a Copy action produces a document with a format of "Unknown".
|
DEV-406369 |
|
Under certain circumstances, Vault fails to generate PDF/A compliant renditions from .ZIP and .MSG files.
|
DEV-406376 |
|
Increasing the width of a line annotation placemark may cause a section at either end of the placemark to disappear.
|
DEV-406779 |
|
When a binder contains more than 25 documents, the binder pagination on the first page shows a range from 1 to the total number of documents instead of 1 to 25.
|
DEV-408170 |
|
Under certain circumstances, when a user attempts to approve a CrossLink document, Vault displays a "Server having problems" error.
|
DEV-408547 |
|
With the latest versions of Chrome and Safari, the annotation count appears at the bottom of the Annotate button instead of at the top.
|
DEV-408898 |
|
In some cases, users are unable to download rendered PDF documents with form fields.
|
DEV-409450 |
|
After a user runs the Compare Version action, Vault may display a "Cannot Show Changes" error that disappears when the user reloads the page. The error states there are more than 5,000 changes between versions.
|
DEV-410807 |
|
When the browser is zoomed to >100%, video annotations appear at the bottom of the document viewer.
|
DEV-413809 |
|
In some cases, Vault fails to render merge fields documents with tables and merged rows.
|
DEV-413820 |
|
When classifying an Inbox Document, Vault does not carry over certain custom and standard fields to the classified document.
|
DEV-413954 |
|
When a Vault's document types consist of only Base Document and one unclassified document type, users are unable to create documents of type Base Document.
|
DEV-414044 |
|
In non-English vaults, the "Too many merged rows" message on the Rendition Status page does not specify the tokens affected.
|
DEV-414327 |
|
Workflow actions may not update the Timeline View until a user navigates away and back.
|
DEV-414339 |
|
When a document has attachments and a user reclassifies it to a document type with attachments disabled, the attachments do not appear in the document's Information panel.
|
DEV-414781 |
|
As a user is moving a video annotation to a different time signature, the annotation's Actions menu appears.
|
DEV-414844 |
|
On a document with many annotations, using Infinite Document Scrolling and navigating annotations may cause some annotations to disappear and reappear inconsistently.
|
DEV-414859 |
|
When an annotation is in focus and a user repeatedly changes the applied view (Document Information, Relationships, Document Files, Sharing Settings, or none), the document may jump or move to the wrong page.
|
DEV-415120 |
|
On the Grid View of the Document Inbox, if a user selects a document and navigates to the next page of documents, the "Clearing selected documents" warning message does not appear.
|
DEV-415359 |
|
When a user is creating a new line annotation, the pending annotation card may not appear next to the line placemark.
|
DEV-415734 |
|
Users cannot set default document fields to be blank using MDL.
|
DEV-416063 |
|
On the Library tab, the Save to Vault item label in the Actions menu contains extra spaces.
|
DEV-416377 |
|
The Find in Document search sometimes does not match words that contain capital Cyrillic characters.
|
DEV-417358 |
|
Permalink relationship creation methods are inconsistent and may cause incorrect source page numbers.
|
DEV-420074 |
|
In Overlay mode, the annotation traversal component and the number of hidden notes unexpectedly appear, and the displayed number of hidden notes may not be accurate.
|
DEV-420763 |
|
User mentions that contain spaces are not correctly inserted into annotation comments.
|
DEV-420869 |
|
When a user clicks the "Show more" button on a link annotation with more than four (4) references or an anchor with more than four (4) incoming relationships, only the first four (4) appear.
|
DEV-421255 |
|
If Push to Staging is not enabled for Vault Digital Publishing, the Information Panel does not display the Staging CDN URL, and the CDN Staging actions do not appear in the Actions menu.
|
DEV-421394 |
|
In some cases, after a user downloads a PDF with annotations, the Download with Annotations dialog does not appear before the PDF begins downloading.
|
DEV-421466 |
|
Users are unable to delete annotation replies in Notes view.
|
DEV-421517 |
|
The "PDF with Annotations" download option appears for video documents after a user creates video annotations.
|
DEV-423785 |
| Description |
Issue No. |
|
In rare cases, Vault fails to load the Create menu when a user clicks the Create button from their Home tab.
|
DEV-382473 |
|
Vault experienced performance degradation for creating documents, document versions, and renditions.
|
DEV-382961 |
|
Some tooltip text in the Notification and Email Preferences section of the User Profile page does not fully describe the UI elements' functionality.
|
DEV-385510 |
|
On the Create Layout Rule page, the caret icon is missing from the Type drop-down under the "Hide the following Page Layout Items" option.
|
DEV-390293 |
|
When users select multiple values while responding to a multiple-choice checklist question, all selected values do not appear on the checklist's Review page.
|
DEV-391118 |
|
When adding a reference lookup to an existing integration rule, the "Source Key" field is misaligned.
|
DEV-395906 |
|
In some scenarios, Layout Rules do not apply immediately on page load and instead load after a short delay.
|
DEV-396884 |
|
In some cases, hovering over a group label may display an incorrect count of members. This fix catches additional cases which were missed for this issue in 21R1.
|
DEV-398467 |
|
The Action menu does not function as expected after viewing a record from a report and returning to the report viewer.
|
DEV-398622 |
|
In some cases, the domain logo does not appear on a user's My Vaults page.
|
DEV-399384 |
|
Vault displays incorrect timestamps for new notifications.
|
DEV-401280 |
|
Under certain conditions, sandbox vaults have poor performance. For example, page loads taking several seconds and creating records taking several minutes.
|
DEV-405609 |
|
In some cases, Vault allows text entry into a read-only field. The user can enter text, but Vault does not save it.
|
DEV-409752 |
|
In some cases, Rich Text Fields do not have a "…Show more" link, hiding some text from viewers.
|
DEV-410094 |
|
When using Internet Explorer™️ 11, selecting Display Fields using the Shift key causes Vault to highlight other text on the page.
|
DEV-413255 |
|
Vault shows two chevron icons in the dropdown lists for Job Definitions.
|
DEV-413835 |
|
The Notifications page and Notifications panel may have minor UI misalignments.
|
DEV-414358 |
|
When editing a filter expression, the text cursor may move unexpectedly.
|
DEV-414464 |
|
Some vaults may experience slow performance.
|
DEV-414663 |
|
In some cases, the first section in the document Relationships panel does not expand as expected if the first document name within the section begins with a letter in the alphabet after 'L'.
|
DEV-414753 |
|
After applying filters to a view, the Save View As button may be partially obscured.
|
DEV-415159 |
|
In some cases, Vault users are unable to view the What's New page.
|
DEV-416113 |
|
Clicking the Favorites star on hovercards for documents in object reference fields does not add the document to Favorites.
|
DEV-416411 |
|
In some cases, with Action UI enabled, Vault opens links meant for the mini-browser in both the mini-browser and navigate to the page directly.
|
DEV-418255 |
|
In some cases, the Complete button is incorrectly placed on Content Plans with a workflow task.
|
DEV-419243 |
| Description |
Issue No. |
|
The Create Content Plan action fails when a constraint is configured on the Country (section_country__rim) field.
|
DEV-302042 |
|
When users run on-demand publishing on a Content Plan Item record, Vault doesn't include the correct attributes in the leaf metadata.
|
DEV-331002 |
|
Vault does not include a placeholder AdPromo leaf in the regional XML when a document is not matched to the AdPromo Content Plan Item.
|
DEV-331469 |
|
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 |
|
In some cases, Vault unmatches documents in a copied content plan after the content plan copy moves to a new lifecycle state or when a user unlocks matched documents.
|
DEV-372087 |
|
In some cases, imported documents don't appear in the Submissions Archive Viewer.
|
DEV-374424 |
|
After importing a submission and the Dossier Status is Import Successful, Vault displays an orange icon in the Publishing Status field rather than a green icon.
|
DEV-376713 |
|
Vault Historical Lifecycle logic marks the Replace > New leaf operation as invalid.
|
DEV-377047 |
|
When users import a submission dossier via the FTP root folder, the drop-down to select the folder in the Submissions Archive Import dialog sometimes includes ZIP files or other incorrect files.
|
DEV-380958 |
|
After users first publish a non-eCTD submission, the Validation Result Status on Submission Validation Results is Not Executed rather than Pass or Fail.
|
DEV-381524 |
|
After selecting a large number of Regulatory Objectives in the bundling wizard, the Define Regulatory Objectives page is unresponsive.
|
DEV-384017 |
|
In some cases, Vault incorrectly reports Rules 2002 and 2012 as Fail.
|
DEV-384248 |
|
Under certain circumstances, Vault fails to copy certain Content Plan sections and matched documents if the Submission contains duplicate Submission Product join records.
|
DEV-386972 |
|
On the Admin > Settings > Application Settings page, there is an unnecessary checkbox below the RIM Settings section.
|
DEV-388360 |
|
Users cannot see correspondence documents in the Submissions Archive Viewer when the documents are associated with a published submission.
|
DEV-391953 |
|
When users update an XML field value in a published submission, Vault creates incomplete Submission Metadata records.
|
DEV-392092 |
|
An error occurs when users click Hide Inactive in the Content Plan Hierarchy Viewer if an inactive parent Content Plan record is expanded and child records are active.
|
DEV-393083 |
|
Re-rendering a Submission's Study Tagging File does not update the stylesheet name, resulting in unexpected styles.
|
DEV-393619 |
|
When a user selects Run On-Demand Publishing from a Content Plan Item with a matched document that has the Ready for Publishing field set to No, Vault does not publish the document.
|
DEV-394029 |
|
The Publishing Status indicator may not reflect the current status of continuous or on-demand publishing or validation activities.
|
DEV-395368 |
|
After users unmatch a document and match a new one in a published submission and continuous publishing runs, Vault does not display the latest XML in the viewer and the Publishing Status icon doesn't update correctly.
|
DEV-395678 |
|
In some cases, Vault does not publish links when the link's target document is in a newly-imported submission.
|
DEV-396054 |
|
Vault validation does not verify that the selected Controlled Vocabulary value is included in the approved list of EMA values for XEVMPD Denominator and Unit of Presentation.
|
DEV-397152 |
|
When a document is not matched to the AdPromo Content Plan Item, Vault doesn't populate Submission Metadata correctly for the AdPromo leaf or the parent Content Plan record.
|
DEV-397347 |
|
In vaults with eCTD metadata mapping enabled, the Metadata Mapping page is sometimes blank when users import submissions in bulk.
|
DEV-398183 |
|
When a Content Plan Item has Continuous Publishing set to "Yes" and a user changes the state to Baseline, Vault does not publish some Content Plan Items even though they have matching documents.
|
DEV-399083 |
|
In some cases, importing a submission content plan fails if the "Enable tree grid" option is disabled in the vault.
|
DEV-399990 |
|
In some cases, Vault does not render and generate viewable renditions for XML files that are imported as part of a submission.
|
DEV-400091 |
|
In some cases, users can click the Next button on the Additional Details page of the Create Related Records wizard without populating required fields.
|
DEV-402677 |
|
Vault does not up-version a published CrossLink document in a target vault when a user uploads a new version of the source document in the source vault.
|
DEV-403790 |
|
Vault does not send a failure notification when users export the content plan hierarchy from the Content Plan Hierarchy Viewer and the Content Plan record has already been deleted.
|
DEV-403844 |
|
When continuous publishing runs after users match or unmatch a document on an AdPromo leaf, Vault does not update the binder with the correct AdPromo attributes.
|
DEV-404644 |
|
In some cases, users see a "Server having problems" error when attempting to run an Impact Assessment report with report prompts.
|
DEV-405188 |
|
Users see ERROR in the Submissions Archive Status field when the Submission object type doesn't include the Dossier Details field.
|
DEV-405291 |
|
Creating related records for Impact Assessment Reports results in an error.
|
DEV-405961 |
|
When a user uploads a new version of the source document in a source vault, Vault does not up-version the published CrossLink document in the target vault if the CrossLink Document is matched to a Content Plan Item record where Source for Published Document field is set to Source Document.
|
DEV-406454 |
|
A re-render of an XML rendition may not be consistent with the rendition Vault created after import.
|
DEV-409167 |
|
In some cases, Vault does not auto-populate the Sequence ID (xml_submission_id__v) field when users create a new Submission record.
|
DEV-409183 |
|
After a user re-orders an Active Dossier column, the column may not appear where expected.
|
DEV-409434 |
|
When an Admin runs the Create Related Records wizard from an Event record, the Use for Content Planning field shows a value of "No" on a Submission Product join record, even if the default value is set to "TRUE".
|
DEV-410147 |
|
Vault displays the incorrect status icon while the Content Plan Hierarchy State Change asynchronous action is in progress.
|
DEV-413975 |
|
If a user copies one Submission Content Plan into another and changes the first Content Plan's state from Draft to Inactive while the copy is in progress, Vault displays a success message and error message at the same time.
|
DEV-414013 |
|
If the target is a Content Plan Item, running the Copy into Content Plan action and then performing a hierarchy state change from Draft to Inactive causes the copy to fail.
|
DEV-414114 |
|
When a user has added all columns to the Active Dossier Editor and exports the records to Excel™️, Vault exports only the root folder.
|
DEV-414504 |
|
Vault does not truncate the Name column in the Active Dossier Editor.
|
DEV-414636 |
|
Document Reconciliation is not activated automatically when Site Connected is added.
|
DEV-415253 |
|
In some cases, importing a Submission may fail when duplicate detection is enabled.
|
DEV-415585 |
|
When a user creates an activity with the Activity Scope Level set to Application Country, Vault creates Activity Registration join records on the Application record but not the Country record.
|
DEV-416256 |
|
In some cases, Vault does not display the Submissions Archive Viewer button consistently between Application records.
|
DEV-416924 |
|
Submission join validation prevents the Create Related Records action from creating records when not all prerequisites are registered.
|
DEV-419576 |
|
When a user adds columns to the Active Dossier Editor for document metadata fields and then exports the grid, the resulting CSV file may be missing certain values.
|
DEV-419747 |
|
Correspondence documents do not appear in the Submissions Archive Viewer if they were imported while Vault was in Document Migration Mode.
|
DEV-419912 |
|
In some cases, certain inactive custom fields appear in the Manage Registered Details wizard.
|
DEV-420159 |
|
In some cases, using the Create Related Record wizard on a Impact Assessment Report results in inconsistent record names.
|
DEV-422069 |
| Description |
Issue No. |
|
Fixed an issue where an error message that appeared when creating an Email Transmission Profile did not meet the standard format.
|
SAF-11594 |
|
Fixed an issue where an error appeared when setting the Case-level Study field that did not match the Study Product.
|
SAF-11704 |
|
Fixed an issue where the G.4 field on the FDA 3500A and CIOMS I form was populated with Receipt Date instead of New Info Date.
|
SAF-13197 |
|
Fixed an issue where the translation for the invalid_patient_section_exceeds_limits__v error has an extra "n".
|
SAF-14548 |
|
Fixed an issue where you could select a Product (Study) on a Case Product that was not associated with the Case-level Study, causing a mismatch between the Case Product and Study.
|
SAF-15176 |
|
Fixed an issue with aggregate reports where the Data Period End was not a required field but after saving the report, an error message appeared stating this field is required.
|
SAF-15478 |
|
Fixed an issue where the correspondence records were not generated when a combination product is selected on a template questionnaire.
|
SAF-15991 |
|
Fixed an issue where the Case Assessment Results were not created after importing the E2B file and promoting it to Case.
|
SAF-16018 |
|
Fixed an issue where duplicate detection did not find any potential matches for Cases with matching Worldwide UIDs.
|
SAF-16097 |
|
Fixed an issue with logging during CIOMS I and FDA 3500A form generation where, when forms failed to generate due to issues with the case narrative document, the error logs did not provide sufficient troubleshooting information. The system now logs the Document ID of the case narrative.
|
SAF-16181 |
|
Fixed an issue where, if there are multiple Localized Cases, the H.5.r section is duplicated with a local narrative translation for each Localized Case.
|
SAF-16303 |
|
Fixed an issue where a "NullPointerException" error appeared when evaluating reporting obligations for a Case.
|
SAF-16309 |
|
Fixed an issue where a warning was appearing for the ICH.D.7.1.r.6 validation rule when the parent and patient have different Medical History records.
|
SAF-16352 |
|
Fixed an issue where, after selecting Show More on the Source Data pane, the header is not displayed on the pop-up for the Patient, Detail, and Custom sections.
|
SAF-16368 |
|
Fixed an issue where Substance TermID and TermID Version always passed the FDA.G.k.2.3.r.2a validation rule.
|
SAF-16407 |
|
Fixed an issue where there was extra padding on the Potential Match screen for Firefox browsers.
|
SAF-16463 |
|
Fixed an issue where a console error appeared if a user without 'Read' permission for Gender Controlled Variables tried to view the Patient section on an Inbox Item.
|
SAF-16544 |
|
Fixed an issue where a user could successfully edit the Age Group field on an Inbox Item when their permissions for Age Group Controlled Variables was disabled.
|
SAF-16547 |
|
Fixed an issue where a user could successfully view Dose form and RoA Object IDs on an Inbox Item when their Object permissions for these forms was disabled.
|
SAF-16552 |
|
Fixed an issue where the FDA.FDA.D.12-1 and FDA.FDA.D.11-1 validation rules failed for Ethnicity and Race with valid nullFlavors.
|
SAF-16554 |
|
Fixed an issue where a second Case Contact Record for an Inbox Item was created after Case Promotion.
|
SAF-16653 |
|
Fixed an issue where, if a case with Registration in U.S. had invalid nullFlavors, it passed the FDA.D.1*-3 validation rule.
|
SAF-16663 |
|
Fixed an issue where a warning was not appearing for FDA VAERS validation rule FDA.FDA.D.8.r.8a when the Patient Age at Vaccination value exceeded three digits.
|
SAF-16672 |
|
Fixed an issue where the user was unable to save the Case page after editing if the Gestation value was 0.
|
SAF-16738 |
|
Fixed an issue where the Last Dose Latency value was not populated on the Case from the imported E2B(R2) file.
|
SAF-16741 |
|
Fixed an issue where the DME watchlist tag was not updated on the case if the product has Registration in UK.
|
SAF-16747 |
|
Fixed an issue with VAERS E2B validation where the Validation Result listed Autopsy Performed as a required field when the Date of Death field was left blank, set to a Reason Omitted, or masked.
|
SAF-16797 |
|
Fixed an issue where there was a blank option in the Study Arm field dropdown.
|
SAF-16817 |
|
Fixed an issue where E2B-imported Follow-Up Cases were not tagged with a Case Tag or Watchlist Tag.
|
SAF-16825 |
|
Fixed an issue where, when an E2B file containing multiple ICSRs was imported, if one of the cases resulted in an error, an Inbound Transmission for that single case was not generated.
|
SAF-16856 |
|
Fixed an issue where, when a user selected "Re-evaluate Submission/Distribution" and completed the transmission error task on the generated submission record, the system skipped the current workflow and moved the Case to the next workflow.
|
SAF-16857 |
|
Fixed an issue where the vault object case_version_v was being used instead of case_drug_history_v for validation criterias FDA.FDA.D.8.r.8b-1 and FDA.FDA.D.8.r.8b-2.
|
SAF-16952 |
|
Fixed an issue where some sections in ACK were missing when a single E2B file was not imported with errors.
|
SAF-16971 |
|
Fixed an issue where the system generated duplicate MedDRA records when a user uploaded the same MedDRA version zip file locally more than once.
|
SAF-16997 |
|
Fixed an issue where, after modifying the reported MedDRA term, the strikethrough was in the wrong position and did not strike the coded term.
|
SAF-17019 |
|
Fixed an issue where the blind protected case narrative was generated in the E2B(R2) submission instead of the updated case narrative.
|
SAF-17047 |
|
Fixed an issue where a Case was being blind protected even when there was no blinded study in the Library.
|
SAF-17051 |
|
Fixed an issue where a warning notification did not appear for conflicting registration number when importing E2B(R2) merged products.
|
SAF-17135 |
|
Fixed an issue where the Multi-Case E2B Import via API/AS2 enhancement was not automatically enabled in the initial release of Vault Safety 21R1.0.
|
SAF-17216 |
|
Fixed an issue where the VAERS Certification Enhancement was not automatically enabled in the initial release of Vault Safety 21R1.0.
|
SAF-17234 |
|
Fixed an issue where a server error appeared when a user with Business Admin permissions tried to navigate to the Dictionary page.
|
SAF-17265 |
|
Fixed an issue where the DSUR Interval Line Listings report was being generated with the incorrect file tab name.
|
SAF-17286 |
|
Fixed an issue where you could not promote AERs to Cases if there was an inactive custom Drug Role Controlled Vocabulary with an E2B code of 1 (suspect) in the Vault.
|
SAF-17288 |
|
Fixed an issue where there was a blank option in the Report Type field dropdown.
|
SAF-17296 |
|
Fixed an issue where an incorrect failure notification appeared for manual E2B imports.
|
SAF-17310 |
|
Fixed an issue where system-generated E2B(R2) acknowledgment messages (ACKs) were not being populated with any value in the M.1.4 Message Number field.
|
SAF-17334 |
|
Fixed an issue with VAERS E2B(R3) validation where the FDA.FDA.D.2.1b-2 validation rule failed when a valid decade unit was entered.
|
SAF-17373 |
|
Fixed an issue where, after changing the vault language, the translatated 'New' icon did not adjust its size on the Inbox Item sections.
|
SAF-17379 |
|
Fixed an issue where the E2B R3 top-level acknowledgment message was not generated for inbound multi-case E2B R3 transmissions.
|
SAF-17389 |
|
Fixed an issue where submissions to Health Canada went to Error state due to the encryption certificate not being recognized in Vault Safety.
|
SAF-17427 |
|
Fixed an issue where, when an E2B file containing a single ICSR was imported successfully, two Message Acknowledgments (ACKs) appeared, one of which incorrectly stated that the message could not be parsed (transmissionacknowledgementcode = 03).
|
SAF-17428 |
|
Fixed an issue where duplicate MedDRA records were created when updating local MedDRA to a new version.
|
SAF-17449 |
|
Fixed an issue where the Inbound Transmission Origin field was not being set by the source document's Origin field.
|
SAF-17467 |
|
Fixed an issue where, if one record failed when updating records in batch, all the records in the batch failed.
|
SAF-17501 |
|
Fixed an issue where, when importing an E2B(R2) file, the Source field in the second generated Case Assessment Result was populated with Non Health Care Professional instead of being left blank.
|
SAF-17522 |
|
Fixed an issue where an E2B file and Inbound Transmission could not be imported due to an invalid value on the Origin field.
|
SAF-17545 |
|
Fixed an issue where, when importing an E2B(R2) file, the Case Assessments and Case Assessment Results were created for non-suspect or concomitant Products.
|
SAF-17592 |
|
Fixed an issue where a Case Assessment and Case Assessment Result were generated for an E2B imported Case with a non serious adverse event.
|
SAF-17618 |
|
Fixed an issue where the system was not populating certain tokens in the created Email Distribution.
|
SAF-17637 |
|
Fixed an issue where the watchlist tag did not update on the Case even though the Include Lower Levels field was set to Yes on the watchlist.
|
SAF-17702 |
|
Fixed an issue where, after removing a field from the Case Assessment, an error appeared during duplicate detection and the Follow-Up Case failed to create.
|
SAF-17719 |
|
Fixed an issue where, if the US Local Datasheet wasn't configured for the user's vault, the Case was not populated after generating PADER Tabulations with a non-15 day Case.
|
SAF-17750 |
|
Fixed an issue where duplicate dosage records were created on E2B(R2) import if the Product had multiple indications and if the dosage information was repeated in all E2B drug sections.
|
SAF-17754 |
|
Fixed an issue where field G.7 Type of Report was not being populated with the appropriate report type for FDA 3500A generated previews.
|
SAF-17766 |
|
Fixed an issue where Vaults that do not have the event_meddra_pt__c field were unable to generate the PADER Non-Primary Suspect Product Report.
|
SAF-17768 |
|
Fixed an issue where encrypted Inbox Item field values were not shown in the audit trail.
|
SAF-17847 |
|
Fixed an issue with EMA validation where the EMA.F.r.1-1 validation rule failed when the Reason Omitted field for Test Date was set as Unknown.
|
SAF-17855 |
|
Fixed an issue where, when importing an E2B(R2) file, the generated ACK for A.1.3 (icsrmessagesenderidentifer) was left blank on the Inbound Transmission.
|
SAF-17872 |
|
Fixed an issue with EMA validation where the EMA.C.1.8.1 validation rule passed for a transmission with invalid format.
|
SAF-17905 |
|
Fixed an issue where field G.7 Type of Report was not populating on FDA 3500A forms for manually created Submissions or Distributions.
|
SAF-17932 |
|
Fixed an issue where the Reason Omitted field was hidden in the Case Product Indication section after selecting Clear Selection.
|
SAF-17973 |
|
Fixed an issue where some EMA-supported units of measurement were unavailable in Vault Safety.
|
SAF-17995 |
|
Fixed an issue where there was no spacing between the narrative translation and lanuage on the narrative text for E2B(R2) export.
|
SAF-17997 |
|
Fixed an issue where if the Patient section was collapsed, after verifying the Date of Death validation error ("The date cannot be later than the Date of Death"), the user could not save the section and the error persisted.
|
SAF-18038 |
|
Fixed an issue where two Inbound Transmissions were generated for a single E2B file during manual import.
|
SAF-18050 |
|
Fixed an issue where the ICH.E.i.7 validation rule was missing at the Case level and Submission level for the EMA E2B(R3) file format.
|
SAF-18243 |
|
Fixed an issue where the system didn't auto-generate a GUID in the E2B Message ID field for a manually created E2B transmission, which led to the Batch Number field not being populated on the FDA E2B(R2) document. This resulted in a failed submission to the FDA.
|
SAF-18258 |
|
Fixed an issue where the Strength field on Case Product Substances did not support decimals.
|
SAF-18268 |
|
Fixed an issue where the Cumulative Dose was not calculated correctly on the Case Product.
|
SAF-18289 |
|
Fixed an issue where a generated DSUR aggregate report for List of Subjects Who Died During the Reporting Period included the superseded version of the Case.
|
SAF-18362 |
|
Fixed an issue where a conflict warning appeared during E2B import when some Case Assessment Results were left blank or null.
|
SAF-18389 |
|
Fixed an issue where, after promoting an AER to Case and specifying it as a Follow-Up Case during duplicate detection, a duplicate Reporter Case Contact record was created.
|
SAF-18442 |
|
Fixed an issue where there was a large amount of spacing between rows on the Potential Matches page after promoting Inbox Item or AER to Case.
|
SAF-18447 |
|
Fixed an issue where the Outcome field on the Case Adverse Event record was not populated with "Unknown" and was left blank when the E2B(R2) source file had an invalid code for B.2.i.8 (reactionoutcome).
|
SAF-18449 |
|
Fixed an issue where, when the Drug Role field was set to Similar Device, "null" appeared in the Product header.
|
SAF-18490 |
|
Fixed an issue where partial dates were not accepted for the Date of Death field (D.9.1) on E2B(R3) import.
|
SAF-18560 |
|
Fixed an issue with E2B imported Cases where, the Study Product was not set as Primary if the Study was Blinded.
|
SAF-18735 |
|
Fixed an issue with E2B imported Cases where, the Relatedness field was set to Unknown even when the Assessment Result was set to Reasonable Possibility.
|
SAF-18737 |
|
Fixed an issue where, when an E2B file was imported manually or through the API to an AS2 Transmission Profile, the logs displayed a NullPointerException (NPE) error.
|
SAF-18759 |
|
Fixed an issue where AS2 gateway communication failed if the name of the incoming E2B file was not specified in the http request.
|
SAF-18760 |
|
Fixed an issue where the Narrative Preview field was left blank on Imported Cases even when the narrative document was created.
|
SAF-18799 |
|
Fixed an issue where the Country Obtained field was present in the generated submission file when it was absent in the source file.
|
SAF-18841 |
|
Fixed an issue where the reporting rules engine did not generate Submissions when the Event Country did not match the Product or Study Registration Country, even if both countries share the same agency (such as EMA).
|
SAF-18881 |
|
Fixed an issue where E2B imports were failing due to an intermittent conflict with vault rendition processes. Document renditions will now be suppressed during the E2B import process and will generate once a user views the document.
|
SAF-18902 |
|
Fixed an issue where the case promotion action failed when configured as part of an automated system job (for example, SDK) due to a notification failure to System User.
|
SAF-18910 |
|
Fixed an issue with EMA reporting by supporting the import of Patient Drug History Name Parts (D.8.r.1.EU.1 to D.8.r.1.EU.8) and Parent Drug History Name Parts (D.10.r.8.r.1.EU.1 to D.10.r.8.r.1.EU.8) from EMA E2B(R3).
|
SAF-19343 |
|
Fixed an issue with EMA reporting by supporting the export of Patient Drug History Name Parts (D.8.r.1.EU.1 to D.8.r.1.EU.8) and Parent Drug History Name Parts (D.10.r.8.r.1.EU.1 to D.10.r.8.r.1.EU.8) from EMA E2B(R3).
|
SAF-19344 |
|
Fixed an issue with EMA reporting by supporting the import of Patient Drug History Substance fields section (D.8.r.EU.r) and Parent Drug History Substance fields section (D.10.8.r.EU.r) from EMA E2B(R3).
|
SAF-19345 |
|
Fixed an issue with EMA reporting by supporting the export of Patient Drug History Substance fields section (D.8.r.EU.r) and Parent Drug History Substance fields section (D.10.8.r.EU.r) from EMA E2B(R3).
|
SAF-19346 |
|
Fixed an issue where the Drug Name (Reported) field in Case Drug History was not imported correctly from E2B(R3).
|
SAF-19347 |
|
Fixed an issue with EMA reporting and EVHUMAN submissions by prioritizing the export of assessment source, method, and result (G.k.9.i.2.r.1, G.k.9.i.2.r.2, G.k.9.i.2.r.3) code values instead of text values.
|
SAF-19348 |
|
Fixed an issue with central MedDRA where the generated auto-expectedness didn't adhere to the Include Lower Levels option on the Local Datasheet. This resulted in the Expectedness field being incorrectly populated on the Expectedness record.
|
SAF-19406 |
|
Fixed an issue where the Inbound Transmission was going to Error state with no error message on manual E2B import.
|
SAF-19411 |
|
Fixed an issue where Dose Unit ug/g was not available in the Case Product Dosage record after ICH/EMA E2B(R3) import or manual AER creation.
|
SAF-19440 |
|
Fixed an issue where an empty section was created on the transmission for EMA E2B(R3) when there was no patient menstrual information.
|
SAF-19565 |
|
Fixed an issue where an empty section was created on the transmission for EMA E2B(R3) when there was no study data.
|
SAF-19566 |
|
Fixed an issue where a server error appeared after saving a new Product with Patient ROA information on an Inbox Item.
|
SAF-19686 |
|
Fixed an issue where asynchronous MDNs were not sent after receiving an ICSR through the AS2 gateway. This resulted in the same ICSR being resent and duplicate AERs being created. A temporary configuration fix was deployed last week for a customer who experienced this issue. This maintenance release deploys a permanent fix for all Safety customers.
|
SAF-19759 |
|
Fixed an issue where a VAERS submission was rejected due to the D.7.3 (Concomitant Therapies) value being set to false.
|
SAF-19911 |
|
Fixed an issue with MHRA (UK) Submissions where, when the Re-evaluate Submission/Distribution user action was run on a Follow-Up Case, the Case went to Transmission Error State and an error appeared stating the Submission to MHRA could not be created because no transmission profile was found in the populate_transmission_profile__v rule function.
|
SAF-20546 |