The following applications may have different release dates: RegulatoryOne, Safety, and Veeva Claims.
| Description |
Issue No. |
|
When 'Allow viewing and annotation of Protected PDF files' is disabled, the attachment document rendition status is incorrectly marked as "Success"
|
DEV-768077 |
|
Notifications for ending collaborative authoring sessions may not display the correct date and time of when the session ended.
|
DEV-803196 |
|
Rendering RTF files in RIM may lead to the files appearing with incorrect page breaks.
|
DEV-807475 |
|
When a workflow on a previous document version attempts to upversion the document, the document version in which the workflow is on gets upversioned instead of the latest document version.
|
DEV-808617 |
|
Vault may delay rendering of CrossLinks when they are created from a bulk operation.
|
DEV-813282* |
|
Vault fails to render write password protected .doc files.
|
DEV-814168* |
|
In rare circumstances, an error is displayed when using the Download to PDF action.
|
DEV-815854* |
|
In some cases, excel renditions fail due to a merge field error.
|
DEV-815909 |
|
When uploading a document and initiating a steady state transition without an upversion entry action, the rendition generation fails.
|
DEV-816634 |
|
When a document is in the Approved state, merge field tokens display the wrong value.
|
DEV-816665 |
|
Text may not be wrapped correctly in Form 3455 PDF files.
|
DEV-818790* |
|
Line breaks are incorrectly rendered as spaces in Form 3455 PDF files.
|
DEV-818806* |
|
When creating a document version with suppressRendition as true, the previous document version has its rendition created.
|
DEV-819175* |
|
eSignatures are not displayed on downloaded Form 3455 PDF files.
|
DEV-819540* |
|
Users cannot edit or annotate an archived document, even though the Document Readiness panel indicates that the Annotation status is Successful.
|
DEV-821485* |
|
Including a leading or trailing space in the Name of a Docrelationshiptype component may result in inconsistencies in migration packages, Vault Configuration reports, and Vault Comparison reports.
|
DEV-822046* |
|
Under certain circumstances, viewable renditions may show "recoverable signature" text in place of the Date on a signature.
|
DEV-822406 |
|
In some cases, users are unable to traverse annotations or scroll to previous pages on a large document when the Line annotation tool is selected.
|
DEV-822980* |
|
The Item column in the System Audit History may display as blank for changes to a document type's Document Number Format.
|
DEV-823734 |
|
Vault incorrectly ignores the Repeat header row on top of each page Word Table property for viewable renditions, which causes them to appear differently than expected.
|
DEV-825682 |
|
In some cases,updating the description of a document's attachment on a previous document version updates the same description on the document's latest version.
|
DEV-825937* |
|
When users delete the latest version of a document attachment, the content of the deleted version is still searchable in Vault.
|
DEV-826541* |
|
When enhanced overlays are enabled, downloaded PDF/A files with a rich-text overlay and a watermark have an excessively large file size.
|
DEV-829489* |
|
If a CrossLink is created by a non-source Vault user or an inactive user in the source Vault, users receive a permissions-related error message.
|
DEV-830976* |
|
In some cases, downloaded signature pages generated from a document, signature page template previews, and overlay template previews may not load immediately and have the incorrect PDF version.
|
DEV-831030* |
|
When creating an object reference field on a document, clicking the labels for the property checkboxes may fail to toggle the checkboxes.
|
DEV-831072* |
|
Re-render fails for documents with brought forward annotations created by delegate users if they were created before a certain point.
|
DEV-832255* |
|
Clicking on the sender's name in a document viewer opened from a Send as Link Vault notification or email may direct users to the incorrect destination.
|
DEV-832472* |
|
When using Download to PDF, a section may be blank when its leftmost table column exceeds the printable width.
|
DEV-833163 |
|
In cases where a user updates the Template Document Type field of a document created from a Controlled Document Template before clicking the Save button, Vault shows an unhelpful error message.
|
DEV-836447 |
|
If a controlling field dependency is modified, the values may also be retroactively changed in system audit logs.
|
DEV-837405* |
|
In some cases, users were able to create new versions of Crosslinks.
|
DEV-839939* |
|
Under certain circumstances, PDF documents may fail to render.
|
DEV-840339 |
|
Vault does not indicate whether header or footer content fits within the height limit when designing an enhanced overlay template.
|
DEV-846844* |
|
In some cases, Vault may fail to update the Document Number field with the correct token value from the Document Number Format field.
|
DEV-857167* |
|
In some cases, Lookup fields used in document event actions may not populate a value.
|
DEV-857496* |
|
Custom note annotation titles are not retained when annotations are brought forward.
|
DEV-859020* |
| Description |
Issue No. |
|
Under certain circumstances, users may receive errors when performing a Content Plan Deep Copy.
|
DEV-516215* |
|
Users may receive the incorrect error message when attempting to delete an object that does not exist via the API.
|
DEV-817633* |
|
Users may encounter duplicate picklist values and the inability to select values after editing.
|
DEV-823271 |
|
When changing the uniqueness of a field using an online alter, the change may not be applied correctly.
|
DEV-825471 |
|
In dialogs with a two-column layout, selected values in multi-value picklists stretch across the entire width of the picklist. In addition, the Date, Time, and DateTime fields appear out of alignment.
|
DEV-825549* |
|
In some cases, the width of Number fields with a format mask may cut off the formatted value.
|
DEV-826276* |
|
If there is an action trigger associated with an object, it can not be deleted.
|
DEV-826557* |
|
Users may experience errors caused by custom objects and standard objects that share the same name.
|
DEV-827472* |
|
If a Document Change Control section includes a document with a CrossLink, the Actions menu may not display.
|
DEV-828865 |
|
In some cases, users receive a null response when updating an object layout profile.
|
DEV-835578 |
|
Enabling custom or matching sharing rules on an object may result in incorrect attachment field data in list views and VQL query results.
|
DEV-843165* |
|
Refreshing a sandbox from a snapshot may fail if the snapshot contains a system-managed object name with special characters.
|
DEV-844126 |
|
In some cases, users may encounter a server error when editing details on an object with a Source value of Application and when changing the Source value from Custom to Application.
|
DEV-846852* |
|
Default values for expressions referencing multiple object levels may not function as expected.
|
DEV-859492 |
| Description |
Issue No. |
|
When users revise a Batch Disposition Plan, Vault copies the Batch Disposition Plan Check Requirement records but not the Owner field from the existing record. This can cause users to have to manually set the Owner field for each Batch Disposition Plan Check Requirement record.
|
DEV-732246* |
|
Vault does not show an error message to Document Control Homepage users attempting to execute user actions for which they do not have permission.
|
DEV-769725* |
|
When the TRIA object page layout is configured with the Training Requirement Training Matrix section, Vault displays a server error to users attempting to manually create a TRIA record in Business Admin.
|
DEV-792933* |
|
A server error occurs when users attempt to resubmit a Spark message from a User Exception Item.
|
DEV-819139* |
|
The Save functionality on the Reassign External Collaborator dialog seems to respond slowly when users reassign a task to a different external collaborator. If a user clicks the Save button again, an unexpected error occurs.
|
DEV-822362* |
|
An unexpected error occurs when users attempt to create a Related Event record without a related record.
|
DEV-826542* |
|
If an Action Step has no Read permission for the Step ID, Step Status, or Step Name fields, an unexpected error occurs when a user executes the Download as PDF action.
|
DEV-829211* |
|
When users execute the Run Quality Record Check user action, Vault sorts the Type list alphabetically by API name rather than alphanumerically by label.
|
DEV-831355 |
|
The Risk Builder tool is not respecting the Create permissions for the Assessment Risk Mitigation object.
|
DEV-832807 |
|
When the Email Body section control is configured on one of the layouts for the Quality Event object, an unexpected error occurs when a user attempts to view a standard Quality Event record.
|
DEV-833248 |
|
Vault displays the object API name instead of the record name in the subject heading for notification emails created with the Create Record from Template Job Complete template.
|
DEV-843887 |
|
Vault does not populate the Creation Reason field on Training Assignments generated as a result of the Require Retraining action.
|
DEV-845049* |
|
When a customer enables dry run for test scripts and uses the Dry Run Authoring Review state as part of their pre-approval workflow, and an Author or Co-Author who is assigned a task uses the Author Test application page, the workflow Complete button does not appear.
|
DEV-846057* |
|
When users remove some Suggested Match Terms while running a new recurrence check, Vault incorrectly displays the removed terms in the View Match Criteria and the Refresh Results dialogs. However, the search results are correct and do not consider any of the removed Suggested Match Terms. This issue occurs only when terms are removed and does not apply to the Refresh Results process.
|
DEV-847946 |
|
Clicking Save in the Risk Builder tool does not trigger the Save functionality until some other cell is double-clicked.
|
DEV-854893* |
| Description |
Issue No. |
|
When the target is up-versioned with a corrupted document, the Permalink navigates to an older version of the target document.
|
DEV-726451* |
|
In some cases, direct data manger jobs fail due to an error in processing the active_dossier_loader__v object.
|
DEV-825791* |
|
When the comparison viewer is opened on an existing browser tab where a different comparison is already opened, Page Not Found is displayed.
|
DEV-826405* |
|
When a user opens the comparison viewer by directly copy and pasting the URL, the user is redirected to the dispatch message detail page.
|
DEV-828469* |
|
In some cases, Vault generates an exception when creating Edit API Requests.
|
DEV-829116* |
|
In some cases, Vaults displays an empty Data Listing Data Definition folder in the Submissions Archive Viewer.
|
DEV-835671 |
|
Vault incorrectly clears filtered records for users selecting Drug Product Details while creating Registrations in bulk.
|
DEV-838556* |
|
When application triggers are applies, a loading batch error is displayed
|
DEV-843597 |
|
The Split Activity wizard allows users to advance past Activity records with blank custom required Activity object fields.
|
DEV-845492* |
|
Users encounter a misleading error message when the Merged Document field is not available.
|
DEV-845713* |
|
Under certain circumstances. users may not receive validation errors on ZA v3.1 - Rule 2.2.1 when they should.
|
DEV-845794 |
|
The Object/User search picklist in the Content Plan Viewer is returning incorrect results.
|
DEV-846453* |
|
When a user selects a Change Item to be created but does not select an Application, the Create Related Records wizard creates Activity Change Items according to the results CSV, but does not display them in the preview.
|
DEV-846485* |
|
In some cases, the file extension in the Published Output Location is removed for MP4 files created by the RIM-PromoMats Connector.
|
DEV-846918 |
|
When a parallel on-demand publishing job fails, the job name is not populated.
|
DEV-847932* |
|
In some cases, Vault Admins cannot remove a verification group from the corresponding sub-setting on the “Send manage registered details for verification” Application Setting.
|
DEV-848047 |
|
In some cases, users receive validation error 1850 due to leaf life cycling between multiple publishing active submissions.
|
DEV-850454 |
|
When generating a UDI Submission and Publishing validation rule BR-UDID-722a is violated, the results CSV indicates a generic unexpected error instead of detailing the specific failure.
|
DEV-850668* |
|
Users may receive a false negative on EU 11.10 in cases where source and target CPIs for non-new operations have different language attributes.
|
DEV-851011 |
|
When previewing Activity Change Item records created in bulk, the results CSV displays “Not Applicable” instead of the Event Change Item ID.
|
DEV-852633* |
| Description |
Issue No. |
|
During Case promotion through the Inbox Item to Case Compare page, when the Case Compare Followup layout excludes both a field and its Reason Omitted counterpart, Vault displays an error message and prevents follow-up Case creation.
|
SAF-69200 |
|
When running the Upgrade to Latest action to update a Vault's active MedDRA dictionary version, the update sometimes times out, and Vault displays an error message.
|
SAF-69245 |
|
Users may experience slow performance when running reports in Workbench.
|
SAF-71400* |
|
If follow-up information adds a new Case Product to a Case that is reportable to the PMDA, when Vault performs the one-time data sync to the Japan Localized Case, it generates duplicate Localized Case Assessments for the original Case Product.
|
SAF-73127 |
|
When an Inbox Item with a Localization value is being merged to an in-flight Case or promoted to a follow-up Case and is matched to a global Case, if two (2) or more Case Products are being deleted, Vault displays an error message and prevents the action.
|
SAF-73311* |
|
In some cases in Vaults with the Load Terms for Abstract Highlighting setting enabled, SafetyDocs unexpectedly does not highlight MedDRA Query or MedDRA Synonym terms in the Abstract field of a Literature Article.
|
SAF-73812* |
|
When conducting automatic literature searches in Vaults with the Literature Article Automatic Search job enabled, SafetyDocs unexpectedly displays an error notification stating that no records were created for Literature Standard Search Terms with Enable Automatic Search turned off or when the Vault contains no Literature Standard Search Terms.
|
SAF-73815 |
|
When creating a follow-up Case through the Inbox Item to Case Compare page, when duplicate Localized Case Assessment Results exist on at least one (1) Localized Case, Vault prevents creation but does not provide a clear error message about the required data correction.
|
SAF-74075 |
|
When generating E2B(R3) files for a Case linked to a Literature Article in a SafetyDocs Vault, Vault encodes multiple articles in a single C.4.r.1 block and concatenates the data with a semicolon, instead of encoding each article in a separate block.
|
SAF-74166 |
|
On generated readable renditions of EMA E2B(R3) files, the G.k.2.2.EU.9.r.1 data element does not appear.
|
SAF-74456 |
|
When transferring data through the Medical-Safety Connection, if the data includes an emoji, transfer to the Safety Vault fails, preventing Inbox Item creation.
|
SAF-74750 |
|
In some cases, if SafetyDocs encounters an error when generating reports while running the Schedule Obligation action, Vault does not send an error notification.
|
SAF-74920 |
|
Cases generated from the Copy Case action do not have Case Unique Number values.
|
SAF-75134 |
|
Vault does not generate CIOMS I Distributions for Cases with multiple Case Test Result records when at least one (1) includes a partial date in the Test Date field.
|
SAF-75181 |
|
When a domestic Case is merged to a global in-flight Case or promoted to follow-up for a global initial Case, Vault does not set the Use Domestic State Code field to Yes.
|
SAF-75198 |
|
When generating Transmissions from Transmission Output Templates that include a Reporting Family, Vault considers the Exceptions to PII Masking field of the related reporting rule parameter instead of the Exceptions to Patient Content Protection field on the Transmission Output Template.
|
SAF-75209 |
|
When generating an MFDS E2B(R3) file for a domestic study Case with a value in the Local Assessment Result field on the Localized Case Assessment Result, Vault populates an E2B code in the G.k.9.i.2.r.3.KR.1 data element.
|
SAF-75313 |
|
When promoting an Inbox Item to a follow-up Case through the Inbox Item to Case Compare page, in some cases Vault removes capitalization, punctuation, spacing, and some special characters when comparing WWUIDs and prevents promotion to follow-up.
|
SAF-75330 |
|
When evaluating a Case with custom Validation Criteria, in some cases, the Vault Section field on Validation Results does not contain a hyperlink to the affected record.
|
SAF-75413 |
|
In Vaults configured to isolate blinded clinical trial information, when promoting a domestic Case as a follow-up to an imported, unblinded global Case through the Inbox Item to Case Compare page, Vault generates duplicate blinded records on the Localized Case.
|
SAF-75414* |
|
In Vaults configured to isolate blinded clinical trial information, when a new adverse event is added through a follow-up Case, Vault does not populate the Blinded Reference on Localized Case Assessment Results related to the new Case Adverse Event.
|
SAF-75715 |
|
In Vaults configured to isolate blinded clinical trial information, after generating a Transmission with PMDA as the destination for an unblinded global Case, when Vault performs the one-time data sync to the Japan Localized Case, it populates the Blinded Reference field on unblinded Localized Case Assessment and Localized Case Assessment Results records.
|
SAF-75888 |
|
If the version number of an initial Case is updated to a previously existing version number on the related follow-up Case and the follow-up includes a Validation Result Summary, after running Evaluate Regulatory Conformance on the initial Case an error message appears and indicates Vault cannot generate the Validation Summary Result record due to a duplicate name issue.
|
SAF-75915 |
|
When a user runs the Generate Local Reporting Details action on a follow-up Case reportable to the PMDA and the Destination Case ID of the Local Reporting Details record contains a value, Vault sets the Reason on the Transmission to Initial instead of Follow-up.
|
SAF-76026 |
|
When a user copies a Case with a value in the Initial Case field, Vault copies the Initial Case value to the new Case.
|
SAF-76035* |
|
If a Study Product Group is selected during Study Arm creation, Vault does not apply the Study Product Group selection upon Save.
|
SAF-76060 |
|
If any Inbox Item or Case that generates email correspondence is missing a Reporter-type Case Contact, Vault cannot send any scheduled email correspondence.
|
SAF-76062 |
|
When attempting to generate Health Canada E2B(R2) files that use custom SDK, Vault does not generate the file and provides an unclear description of the issue in the error message.
|
SAF-76065 |
|
When attempting automatic Case promotion using the Override merge method for an imported E2B file, if the matching Case is in a prohibited state based on the Allow Mark Follow-up application settings, Vault does not promote the Inbox Item to a follow-up Case.
|
SAF-76205 |
|
FDA E2B(R3) generation fails for Cases with attachments in the .docx format.
|
SAF-76262 |
|
On generated FDA E2B(R3) files, the FDA.E.i.3.2h data element tag appears as E.i.3.2h and the FDA.G.k.10.1 tag appears as FDA.G.k.10.r.1.
|
SAF-76291 |
|
For exported NMPA E2B(R3) files, Vault does not populate the C.1.CN.3 data element as expected.
|
SAF-76439 |
|
Vault populates the C.2.r.3 Reporter's Country Code data element on PMDA E2B(R3) files for non-primary reporter Reporter-type Case Contacts.
|
SAF-76457 |
|
In Vaults configured to isolate blinded clinical trial information and with the Exclude reporting rule parameter set to Placebo, for a double-blinded study Case with an unblinded Case Product record for the Placebo, the reporting rule engine evaluates the blinded record instead of the unblinded record.
|
SAF-76513 |
|
For JSON-imported Cases created using tabular data format import, if a Case includes a Parent Information Case, after import the Inbox Item is blank.
|
SAF-76676 |
|
When generating E2B files for a Case in the Superseded state, Vault exports the date of report generation instead of the Approval Date on the Case to the N.2.r.4 and C.1.2 data elements of E2B(R3) formats and to the A.1.3b data element of E2B(R2) formats.
|
SAF-76734 |
|
In some cases in Vaults with the Literature Article Automatic Search job enabled, SafetyDocs encounters an error when searching the PubMed database and does not generate the expected Literature Review and Literature Article records.
|
SAF-76781 |
|
On readable renditions of FDA E2B(R3) files, Vault displays nullFlavors outside of tables.
|
SAF-76819 |
|
For Inbox Items imported through a multi-Case tabular CSV file or multi-CSV ZIP file, after Case promotion Vault duplicates Case Assessments.
|
SAF-77174* |
|
SafetyDocs cannot save a Product Alias with an Alias value longer than 128 characters.
|
SAF-77216 |
|
After importing a multi-Case tabular CSV file or a multi-CSV ZIP file to Inbox Item, Vault does not map values for the Study Type of the Case or the Reaction Recurrence of Case Assessments.
|
SAF-77217 |
|
After importing a multi-Case tabular CSV file or a multi-CSV ZIP file to Inbox Item, Vault does not map the Gestation (Unit) value.
|
SAF-77245* |
|
After auto-coding an Adverse Event on an Inbox Item, if the user collapses and re-expands the Adverse Event section, Vault clears the MedDRA code.
|
SAF-77297 |
|
For manually created Transmissions with blank Transmission Reason values, Vault does not generate Distribution documents and does not send a notification with the reason to the user.
|
SAF-72835* |