| Description |
Issue No. |
|
In some cases, Vault does not save radio button responses on Trip Reports.
|
DEV-436937 |
|
Users are not able to create more than 500 EDL Items at once when creating a milestone using milestone template automation.
|
DEV-458952 |
|
In cases where a user with limited permissions adds a USN to an Organization, Vault fails to establish a Site Connect connection.
|
DEV-460451 |
|
If a user attempts to update the status of a Site Fee record and the Payee Override field is blank, Vault fails to save the update and gives a server error.
|
DEV-460962 |
|
In some cases, the Recalculate Enrollment Metrics job runs for 24 hours before failing with errors.
|
DEV-463463* |
|
Updates to the Metrics Over Time planned__v field fail to roll up to the Study.
|
DEV-463668 |
|
"Allow attachments" and "Audit data changes in this object" fields on Agreement Transfer records are not read-only.
|
DEV-464315* |
|
Vaults that were cloned after 21R3 are missing Global Subject Metric Enablement records.
|
DEV-464402 |
|
In some cases, using a search query that should match one (1) row exactly within the Site Document Exchange section of a Study Site results in multiple rows being displayed.
|
DEV-464554* |
|
In some cases of high traffic, the Send Safety Distributions job may leave some Distribution Task Recipient records in Sending rather than updating them to Sent.
|
DEV-464569 |
|
In some cases, Vault creates duplicate Safety Distribution Tasks and displays multiple copies of documents in the external viewer.
|
DEV-464594 |
|
In some cases, Vault fails to display comments on documents in the "Received from site" state.
|
DEV-464946*, DEV-465748* |
|
When training TMF Bot models using the Attached CSV method and there are document IDs in the CSV that do not exist in Vault, the document extraction job fails with an unexpected error.
|
DEV-465955* |
|
Vault displays unhelpful text on the Mark Rescinded dialog.
|
DEV-466099* |
|
In some cases, the TMF Transfer Items CSV displays a status of EXCLUDED where it should display FAILURE.
|
DEV-466120* |
|
When a user attempts to run the Create Milestone from Template job and there are more than 200 expected document types for the milestone, Vault fails to create milestone items for the expected document types after the first 200.
|
DEV-467154* |
|
In some cases, TMF transfers fail and show a server error.
|
DEV-467308 |
|
Model training that takes longer than 30 minutes times out and fails.
|
DEV-467593 |
|
In some cases, inbound documents integration with a RIM Vault will fail and users will be unable to receive inbound documents in the RIM Vault.
|
DEV-470630* |
| Description |
Issue No. |
|
In some cases, Vault fails to render Microsoft Word documents with mail merge data.
|
DEV-452688 |
|
In rare cases, the Export Annotation action fails due to invalid area border colors.
|
DEV-460667* |
|
When a user attempts to zoom in on an unsaved annotation, the annotation falls out of focus.
|
DEV-464305* |
|
When an Admin removes a shared field from a document type, Vault does not properly clear the field value from existing documents or reflect the change in the document audit trail.
|
DEV-464601* |
|
In Firefox, the annotation color menu does not appear correctly.
|
DEV-464683* |
|
After a user rotates all pages of a document in the doc viewer mini browser, some annotations may be misaligned.
|
DEV-464703* |
|
Users are unable to export archived documents using the document export bulk action.
|
DEV-464752 |
|
If a user cancels an edit to an annotation's tags then attempts to edit the tags again, Vault fails to correctly disable the functions in the annotate toolbar.
|
DEV-465005* |
|
If a user changes the size of a document in Overlay mode with pending changes to an annotation's tags, Vault fails to save the tag values.
|
DEV-465011* |
|
In the Notes view, users are unable to expand or collapse the containers of relationships within link or anchor annotations.
|
DEV-465387* |
|
In the Notes view, users are unable to access the relationship's target document by selecting it within the relationship's container in a link or anchor annotation.
|
DEV-465467* |
|
In the Show all attachments view on a document, users can delete attachments in the Attachment Version History dialog.
|
DEV-465854 |
|
Video files larger than 2GB may fail to render in Vault, even though files up to 4GB are supported.
|
DEV-466449 |
|
When a user creates a draft from a document with the "Require Certified Copy?" field set to "Yes", the field is still set to "Yes" on the new version.
|
DEV-467395* |
|
In some cases, match text that includes smart quotation marks and apostrophes does not appear in Suggest Links.
|
DEV-467464* |
|
When users use Download Notes to CSV for a document with anchor names that have been updated, the CSV uses the old anchor names instead of the new ones.
|
DEV-467690 |
|
In some cases, users are unable to open TOC links in doc viewer.
|
DEV-467724* |
|
Uploading an Unclassified document from Google Drive results in an error.
|
DEV-467949 |
|
Users cannot authenticate a Google Drive account when using the marketplace application.
|
DEV-468261* |
| Description |
Issue No. |
|
Vault may display an incorrect error message when a user adds a non-latest version of a document to a Documents to be Released section on a Multi-Document Change Control record.
|
DEV-451616* |
|
In some cases, Vault Training does not correctly ignore pending substitute Training Assignments while processing a Facilitated Training Request.
|
DEV-458169* |
|
Under certain circumstances, Training Assignments that fail to be transitioned to the Assigned or Cancelled states may remain stuck in the Created state.
|
DEV-458174* |
|
In some cases, QMS process records become stuck in a starting state and cannot exit without configuration changes.
|
DEV-459387 |
|
Drop-down menus in the Manage Invalid Team Members dialog may display as smaller than intended.
|
DEV-459600* |
|
When a user performs an action to send External Notifications to a large number of recipients, Vault may take longer than expected to complete the action.
|
DEV-462849* |
|
Vault does not correctly display a useful error message when attempting to run the Send External Notification entry action while the recipient's Person record lacks an email address.
|
DEV-463236* |
|
If a substitute Training Assignment substitutes for a primary Training Assignment that contains an error, the substitute Training Assignment may incorrectly appear on the Curriculum View on the Learner Homepage.
|
DEV-463290* |
|
When a user performs an action to send External Notifications for an unsupported object, Vault may not correctly display a useful error message.
|
DEV-463325* |
|
In some cases, when Vault attempts to cascade Quality Team roles to inactive records, the system does not display a helpful error message.
|
DEV-463534 |
|
If a complex object relationship is changed to a simple relationship when in use by a Quality Record Check configuration, attempting to view the record check configuration page or comparison page may result in Vault displaying a server error.
|
DEV-464335 |
|
Vault may display a server error rather than a helpful error message when a user attempts to view or add duplicates of a document to a Training Requirement.
|
DEV-464473* |
|
When executing the Send External Notification action, Vault displays a server error if the object message includes an automatically generated number field created from a document reference field.
|
DEV-464680* |
|
The Curriculum page may not display Training Assignments in the expected order.
|
DEV-464960* |
|
In some cases, the Auto-Start Periodic Review job may not successfully complete if it targets documents which have been deleted.
|
DEV-465473 |
|
In some cases, after saving changes to Substitute or Prerequisite rules on a Training Requirement with active Training Assignments, the impact alert link may not function as expected.
|
DEV-466034* |
|
In some cases, Vault may incorrectly display an error when attempting to execute the Generate Document from Report action with the Excel Template selected as the Report Export Type.
|
DEV-466230* |
|
Learners are able to bypass the maximum number of attempts for a quiz by taking the quiz in a new tab.
|
DEV-466497 |
| Description |
Issue No. |
|
Users cannot update Efficacy and Description values when managing Submission Administrative Information for a South African application and submission if a Submission Country record exists for South Africa.
|
DEV-335018* |
|
The content plan creation job fails when a related Submission Language record’s Country field is blank.
|
DEV-432100* |
|
During validation, Vault incompletely reports Rule C03 failures in some cases.
|
DEV-438170 |
|
The Generate IDMP Elements job results in errors when the data contains only Medicinal Product and IDMP Product Data Submission records.
|
DEV-446486* |
|
The publishing progress indicator shows a failure when the Enable Continuous Publishing field is changed from blank to ‘No’.
|
DEV-451154 |
|
Submissions Publishing fails when active Content Plan Items are contained within inactive Content Plans
|
DEV-451885* |
|
When creating a GCC Submission, the Agency value fails to populate for countries with multiple Health Authorities.
|
DEV-456452 |
|
When a non-primary Submission record field is updated, Vault fails to trigger continuous publishing for the primary Submission and update Regional XML.
|
DEV-458517* |
|
The content plan viewer UI freezes when a user drags and drops an unlocked matched document to which they do not have access.
|
DEV-462371* |
|
The RIM Submission Publishing job fails in some cases when the Content Plan field XML Element Name is blank on the Content Plan root node.
|
DEV-463373 |
|
When attempting to select verification groups in a Registration Verification Workflow, Vault fails to load the participant list.
|
DEV-464709 |
|
Content plan sections fail to copy when a Content Plan Template record’s Name field contains more than one token along with the Submission Pharmaceutical Form object token.
|
DEV-464904* |
|
Links to Report Level Content Plan module Tables of Contents (TOC) are not clickable within resulting merged PDFs.
|
DEV-465391* |
|
In some cases, the Submissions Archive Empty Section Indicator job fails to process all existing Submission Archive binders upon feature enablement.
|
DEV-466630 |
The RegulatoryOne release, including all Platform fixed issues, is targeted for tentative availability on March 15, 2022.
| Description |
Issue No. |
|
When the Local Impact Assessment action is configured on the Registration Item object but the action is not assigned to a specific object type, Vault displays an unexpected error message when users trigger the action on a record of the unassigned object type.
|
OLS-9264 |
|
When the Generate Requirements action is configured on the Request or Registration object and the action is not assigned to a specific object type, Vault displays an unexpected error message when users trigger the action on a record of the unassigned object type.
|
OLS-9278 |
|
After users trigger the Local Impact Assessment action and click on the Search Registration dialog, long field values are not truncated in Safari, Chrome, and Edge browsers.
|
OLS-9401 |
|
Vault only adds a maximum of 1,000 matched documents to Dossier Binders.
|
OLS-9418 |
|
When users trigger the Generate Registration Data action on an inactive Registration Item, the job completes successfully but no fields are updated. When the action is triggered on a Registration Item that references an inactive object Field Mapping, the job completes successfully and fields are mapped.
|
OLS-9449 |
|
When users trigger the Local Impact Assessment or Create Registration and Objective actions on an inactive Registration Item, the jobs completes successfully as if the record is active.
|
OLS-9475 |
|
Formulation questionnaire emails to respondents to do not display as expected when viewed outside of Gmail.
|
OLS-9518 |
|
When the Regulated Category field is blank on a Registration Item record and users trigger the Local Impact Assessment action, Vault matches all Registrations with related Registration Items rather than only Registrations related to Registration Items with blank Regulated Categories
|
OLS-9536 |
|
When the Registration object is not assigned a lifecycle and the Registration Item includes the Matching Registration Objective and Matching Registration fields, users get a server error when they attempt to open a Registration Item record.
|
OLS-9552 |
|
When users trigger the Generate Requirements action on a Registration or Registration Item record, the job fails if that record has descendant records at the same level with both Relational Token-generated Names and non-Relational Token generated Names.
|
OLS-9572 |
|
When users trigger the Generate Requirements action and there is an inactive Object Mapping, the job completes without mapping the defined fields. If there is an inactive object Field Mapping, the job completes and fields are mapped.
|
OLS-9603 |
|
Certain field labels on Registration Request and Regulated Category Attribute Impact records are not translated when a user's Vault is set to Chinese or German language.
|
OLS-9719 |
| Description |
Issue No. |
|
Under certain conditions, after performing a bulk action on a Workflow with Document report, the Refine Selection page is blank.
|
DEV-414547* |
|
In some cases, the Refine Selection page is blank when users perform a bulk action for all records in a Multi-Pass report.
|
DEV-461682* |
|
In rare cases, running a Multi-Pass ladder report results in an error.
|
DEV-464187* |
|
While editing a Multi-Pass ladder report, Vault may incorrectly shift the view order in the Selected Report View.
|
DEV-464267* |
|
While attempting to perform a bulk action for all records in an object report, the Refine Selection page is blank if the report is grouped.
|
DEV-464507* |
|
In some cases, adding formula fields to a Multi-Pass ladder report results in an error if the formula fields are on fields in another view.
|
DEV-464655* |
|
In some cases, skipping an optional DateTime prompt on a dashboard results in an error.
|
DEV-465509* |
|
After users skip an optional prompt on a dashboard, Vault incorrectly displays the Filters section as editable.
|
DEV-465538* |
|
Vault incorrectly defaults the value of boolean fields on optional prompts to "No". Additionally, after users skip the prompt, the input value field disappears.
|
DEV-465539* |
|
When running a VQL query on legacy workflows, Vault may incorrectly attempt to join non-required data, which causes an error.
|
DEV-465541 |
The Safety release, including all Platform fixed issues, is targeted for tentative availability on March 10, 2022.
| Description |
Issue No. |
|
Fixed an issue where some Japanese terms used in Controlled Vocabularies were incorrect or not aligned with the Health Authority.
|
SAF-22748* |
|
Fixed an issue with E2B(R3) export where the Dosage Text (G.k.4.r.8) field was not truncated to 2000 characters upon export.
|
SAF-23775 |
|
Fixed an issue where a submission to the FDA containing Northern Ireland country code "XI was rejected. Now, submissions to the FDA will use the country code "GB" for Northern Ireland whereas submissions to all other destinations will use the 2-character country code in Vault.
|
SAF-24493 |
|
Fixed an issue where, when an ICH E2B(R2) regulatory report was generated, the header contained "FDA".
|
SAF-24548 |
|
Fixed an issue where an error message appeared and a Follow-Up Case was unable to be created after deleting the Product Indication and Dosage record on the Case Compare page from an initial domestic Case.
|
SAF-24724* |
|
Fixed an issue where, when a case processing user attempted to mark an Inbox Item as Mark as Follow-Up on the Potential Matches page, an error appeared stating the user does not have permission.
|
SAF-24866* |
|
Fixed an issue where using Vault Loader to update Study Persons was unsuccessful if the First Name and Email fields were left blank. This is due to system-managed validation rules for the Person object which limit the number of characters and does not accept null fields. Now, First Name Length and Email Address Length validation rules can be edited.
|
SAF-24993 |
|
Fixed an issue where, when any Inbox Item section or record was verified with no changes made, the old and new values on the audit trail still displayed all the fields.
|
SAF-25025 |
|
Fixed an issue where the Result (qualifier) picklist field in the Case Test Result object contained invalid values.
|
SAF-25032* |
|
Fixed an issue where, when a PADER Non-Primary Suspect Product Report was generated, an older Case version with a non-primary suspect product was included.
|
SAF-25207 |
|
Fixed an issue where inconsistent timezones were used to determine the date in generated forms. Now, CIOMS I and FDA 3500A reports will use Vault's default timezone. For E2B exports, users can convert the date to use the appropriate timezone.
|
SAF-25344 |
|
Fixed an issue where, when the bulk unblind operation was run, the Case was still included in the blue category (closed Cases that have not been unblinded) and a follow-up version was created.
|
SAF-25368* |
|
Fixed an issue where the user was not notified when D.2.2a (Age at Time of Onset of Reaction / Event (number)) was truncated from an imported E2B file.
|
SAF-25411 |
|
Fixed an issue with the local MedDRA dictionary where, when the Terms Hierarchy was applied, no results were shown.
|
SAF-25416* |
|
Fixed an issue where, when the Terms Hierarchy was applied and a term is entered in any MedDRA language except English and Japanese, the LLT term under the hierarchy could not be found.
|
SAF-25419* |
|
Fixed an issue where, when the Void Case user action was triggered, the pop-up message to indicate the user does not have permission was displayed as an error.
|
SAF-25446* |
|
Fixed an issue with system-generated AERs and Inbox Items where, if the field value for Case Contact Rank is not 1, the Primary Source in the Case Contact record was left blank upon Case promotion.
|
SAF-25447 |
|
Fixed an issue where an incorrect error message was displayed when the New Info Date was blank during Inbox Item promotion to Case.
|
SAF-25454 |
|
Fixed an issue with Date Received by Manufacturer (24c) field mapping when generating the CIOMS I form. Now, the New Info Date field will be used to populate Date Received by Manufacturer on the form for both Initial and Follow-Up Cases.
|
SAF-25679 |
|
Fixed an issue where, when a Case Product or Case Adverse Event was deleted, the Matching Contents record was not updated and these records were still being considered in duplicate detection.
|
SAF-25711* |
|
Fixed an issue with E2B(R3) export where, when the Mask Reporter for Postmarket Non-Literature Case setting was enabled, the nullFlavor values were not masked upon generating the report.
|
SAF-25725* |
|
Fixed an issue with E2B(R2) export where, when the Patient Content Protection was set to Mask PII, the Date of Birth field was not exported when it should have been exported as PRIVACY.
|
SAF-25753* |
|
Fixed an issue where, after deleting an Inbox Item subsection or editing a Product Dosage record, these changes were not saved on the Inbox Item upon selecting the global save button.
|
SAF-25762* |
|
Fixed an issue where, after importing an open Study to Inbox Item and promoting to Case, the Product and Product Registration fields were blank.
|
SAF-25765* |
|
Fixed an issue where, when importing an E2B(R2) file to AER or Inbox Item, the test Result (B.3.1d) and Test Result (unit) (B.3.1e) were mapped to Normal Low Value (B.3.1.1) and Normal High Value (B.3.1.2) fields.
|
SAF-25802 |
|
Fixed an issue with E2B(R2 and R3) form generation where validations were not triggered and the transmission document was successfully generated with an error notification stating the document was not generated.
|
SAF-25912 |
|
Fixed an issue where, when importing an E2B(R2) file to AER, Inbox Item, or Case, the Case Seriousness (A.1.5) was mapped to all Adverse Events instead of considering the Term highlighted by the reporter (B.2.i.3) field value for each Adverse Event.
|
SAF-25996 |
|
Fixed an issue where an error appeared when a user tried to load more than 250 Case Assessment records in one batch using Vault Loader.
|
SAF-26073* |
|
Fixed an issue where vaults provisioned after the 20R1 release contained at least one controlled vocabulary API name that did not match that of vaults provisioned before the 20R1 release.
|
SAF-26091 |
|
Fixed an issue with CIOMS I and FDA MedWatch 3500A report generation where, when the Study Product dosage was blinded, the Frequency on the report was blank instead of displaying *****.
|
SAF-26092* |
|
Fixed an issue with CIOMS I form generation for Cases with Combination Products where assessment results were generated for device constituents. Assessment results should only be generated for products listed in Section 14 (drug constituents).
|
SAF-26125 |
|
Fixed an issue where, when exporting to E2B(R2 and R3), G.k.4.r.6a (Duration of Drug Administration (number)) did not truncate to 5 characters.
|
SAF-26277 |
|
Fixed an issue where, when an FDA MedWatch 3500A form was generated, the UID/MFR Report # was not completely printed on the form for some cases.
|
SAF-26416 |
|
Fixed an issue where, duplicate Transmission records were generated for the same destination if multiple Transmission Profiles exist for the origin and destination pair.
|
SAF-26518* |
The Veeva Claims release, including all Platform fixed issues, is targeted for tentative availability on March 15, 2022.