The issues listed below are fixed in the 21R3 release.
| Description |
Issue No. |
|
When configuring integration field rules, users receive a server error when configuring a type__v, subtype__v, or classification__v on a field rule for a document.
|
DEV-370973 |
|
It is possible for Administrators to create picklist values with blank labels.
|
DEV-402106 |
|
When setting a Start and End date for a delegated user, the date picker references the user's hardware timezone (for example, their laptop timezone) rather than Vault timezone.
|
DEV-412412 |
|
While a queue is in Edit mode, users cannot delete or edit any Queue Connections associated with that queue.
|
DEV-414531 |
|
Under certain conditions, Jobs remain stuck in the queue.
|
DEV-415793 |
|
In some cases, if a job is configured to send a notification based on a trigger date, users may continue to receive duplicate notifications after the initial notification
|
DEV-418228 |
|
When exporting documents with Vault Loader or the API, commas in picklist field values are sometimes duplicated.
|
DEV-419577 |
|
In Vaults configured to send summary emails with a 24 hour delivery interval, users who have not previously received summary emails receive their first emails at irregular times.
|
DEV-422335 |
|
When attempting to delegate access from the Users & Groups tab, users may not appear in the Delegates tab until the page is refreshed.
|
DEV-423524 |
|
When deploying an inbound migration package containing object reference type document fields without reference constraints, Vault does not properly overwrite existing reference constraints.
|
DEV-424182 |
|
After an Admin updates the Label value of a Page object and clicks Save, Vault displays a "Server having problems" error.
|
DEV-424309 |
|
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-426512 |
|
In some scenarios, admins cannot create new cross domain users.
|
DEV-427362 |
|
In certain scenarios, Admins cannot refresh sandbox vaults.
|
DEV-427713 |
|
Inbound package deployment fails for packages updating existing object lifecycles where multiple lifecycle roles are associated with the same application role.
|
DEV-428984 |
|
In some scenarios, Avg Time Login is not recorded on the Performance Statistics object.
|
DEV-430220 |
|
Input values for Vault loader which contain double commas (,,) cause errors.
|
DEV-432410 |
|
In some cases, Vault incorrectly creates duplicate User Role Setup records.
|
DEV-433919 |
|
Vault does not display an understandable message in the Details column of the Email Log when a user sends an email to a disabled email processor.
|
DEV-435177 |
|
In rare cases, navigating to a binder directly with a URL immediately creation of that binder may result in blank values for DateTime fields.
|
DEV-436126 |
|
In certain scenarios, changing the label of a standard Number field (such as copy_depth__v) changes the maximum length of that standard field to 1,000.
|
DEV-437922 |
|
When a document state entry action is configured to send a notification to a group which includes inactive members, Vault may fail to send the notification.
|
DEV-438149 |
|
When a job is configured to change the Latest Steady State for a document from Approved to Withdrawn based on a document date, the job fails to change the state if the Latest Steady State is not the current state.
This fix has been postponed to a later release.
|
DEV-440849 |
| Description |
Issue No. |
|
Updating the Actual Finish Date field does not immediately update the related milestone at the Country level.
|
DEV-330347 |
|
In some cases, Vault schedules another Milestone Autocomplete job when the job is already scheduled.
|
DEV-379433 |
|
Safety Distributions are not viewable from the links in Vault email to sites.
|
DEV-384791 |
|
In some cases, Vault displays "Server having problems" when trying to access the TMF Viewer without first selecting a model.
|
DEV-394652 |
|
Vault resets the Study Selector to All Studies after refreshing the Library page.
|
DEV-397548 |
|
When a SiteVault user accepts an Agreement from a Clinical Vault and there are no studies to show in the Agreement wizard, Vault displays a "Loading" message with a continuously spinning loading animation.
|
DEV-407039 |
|
Vault shows Vault Owners incorrect counts in the Completeness Unapproved Documents, Timeliness, and Quality Issues widgets on the TMF Homepage.
|
DEV-408346 |
|
In some cases when changing the default workflow for a document lifecycle, Vault does not save the change.
|
DEV-409679 |
|
When added using the + button, Monitoring Follow Up Item and Issue records are not saved.
|
DEV-410720 |
|
Vault occasionally displays the incorrect Delivery Status of survey Invitations.
|
DEV-411307 |
|
In some cases, after changing a Monitored Event's study lineage, the Update Monitored Metrics job fails.
|
DEV-412793 |
|
Vault fails to show an error when attempting to export more than 10,000 records to CSV or Excel from TMF Viewer.
|
DEV-412845 |
|
If the Content (blinding__v) document field has a default value, uploading a document using the global Create button does not provide the Content field with a default value.
|
DEV-412969 |
|
Vault inserts the incorrect CTN Submission Date in the Administration Information document.
|
DEV-413086 |
|
When over 500 records are being updated, Vault fails to complete the Generate Study Risk Assessment action.
|
DEV-414653 |
|
In some cases, the Create Site Budget Records action incorrectly creates Budget Items multiple times.
|
DEV-415694 |
|
Vault includes CTN Remarks in a CTN when no deletions are found in the related CTN Change Log, even when "Include in CTN" for Remarks is set to Off.
|
DEV-415788 |
|
In some cases where a document sent from a Clinical Operations Vault to SiteVault is in a non-steady state, Vault incorrectly reports "Site missing latest Steady State" after Document Reconciliation.
|
DEV-416815 |
|
In some cases where a document sent from a Clinical Operations Vault to SiteVault is in a non-steady state, Vault incorrectly reports "Site missing latest Steady State" after Document Reconciliation.
|
DEV-416815 |
|
In some cases, Vault deletes necessary User Role Setup records.
|
DEV-417166 |
|
If a user attempts to inactivate a Person record that is linked to a Study Personnel record with "Grant Access to Related Records" set to "Yes", Vault displays a "Server having problems" error.
|
DEV-418712 |
|
When the USN App Control field label is not specified, it does not inherit the existing usn__v field label.
|
DEV-418832 |
|
Document Reconciliation includes documents mapped to the Expedited Safety Report artifact.
|
DEV-418836 |
|
Users are unable to sort columns in the TMF Viewer by clicking the column headers.
|
DEV-419019 |
|
The Notification Target of Development Termination CTN Notifications populates incorrectly, leading to incorrect header text in CTN documents.
|
DEV-419239 |
|
Vault to Vault connections fail when more than one Clinical Transfer user exists due to a cross-domain user's creation.
|
DEV-420164 |
|
When no Countries are found to match the country exclusion filter for a Safety Distribution, Vault performs no filtering and selects all available Sites.
|
DEV-420272 |
|
When uploading via Vault Loader, Vault fails to create Site Package Documents.
|
DEV-421074 |
|
There may be performance issues when sharing a large number of inbox documents on Clinical Vaults.
|
DEV-421103 |
|
In some cases, after removing permissions for users to a Study Site, Study, or Site, those users cannot access the TMF Viewer at all.
|
DEV-421182 |
|
In cases where the Study, Study Country, or Study Site for a Monitoring Event is inactive, Vault fails to run the Seed Trip Report Question Responses action and displays a server error.
|
DEV-423066 |
|
In some cases, Vault fails to create Subject records for Sites with 500 or more Milestones.
|
DEV-424129 |
|
When reclassifying a document from a Document Type that does not contain the Content field to one with the Content field, Vault fails to set a default value in the Content field.
|
DEV-424561 |
|
Users can edit the unique ID of Trained Model records.
|
DEV-424798 |
|
In cases where CTN Remarks are linked but included, Vault fails to generate the CTN.
|
DEV-426741 |
|
TMF Bot cannot train models using Document Types with names longer than 128 characters.
|
DEV-426823 |
|
In some cases, after a Study assignment is reactivated, distribution tasks from SiteVault to a Clinical Operations Vault fail.
|
DEV-426842 |
|
After auto-classifying a document, Vault fails to properly apply auto-numbering.
|
DEV-427775 |
|
When more than 1000 clinical document types exist, Vault fails to show all clinical document types to some users.
|
DEV-428065 |
|
In some cases, Vault incorrectly reports successful TMF Bot training as failed.
|
DEV-428279 |
|
Field defaults are not applied when using Reclassify on auto-classified documents in the Document Inbox.
|
DEV-428504 |
|
Vault fails to auto-classify documents with file names containing commas.
|
DEV-428807 |
|
Auto-classified documents with related Milestones cannot be completed in the Document Inbox.
|
DEV-431669 |
|
When a document is eSigned in SiteVault and returned to the Clinical Vault, the signed rendition is not included.
|
DEV-433029 |
|
In some cases, Vault improperly classifies documents associated with Sub-I Study Person records coming from SiteVault.
|
DEV-434020 |
|
In some cases, Vault fails to create Site Packages correctly, causing the Send Site Packages job to fail.
|
DEV-435922 |
|
In some cases, adding large volumes of data to CDMS will cause the CMDS & Clinical Operations Vault Connection to fail.
|
DEV-438662 |
|
When using a Study Selector filter, Vault fails to show all content within a Study Site binder
|
DEV-439254 |
|
When the Autocomplete Milestones job updates metrics on a milestone, Vault logs that update on behalf of the user whose actions first scheduled the job to run.
|
DEV-439492 |
|
In some cases, Vault prevents the reuse of documents across Studies for users without Manage Archive permissions at the time of document creation.
|
DEV-439663 |
|
Vault does not populate the Text Response field of dependent Trip Report questions when they become uneditable.
|
DEV-441021 |
|
In some cases, auto-classified documents are missing renditions.
|
DEV-441295 |
|
When creating a CTN, Vault fails to include the Study and Study Country for the Study Person and Study Organization records.
|
DEV-441758 |
|
Vault displays an unhelpful error when an admin can not create a Study Person due to configuration issues.
|
DEV-442369 |
|
Vault fails to populate the Actual Finish Date on a Subject-related milestone when No New Subjects on the Site is not checked.
|
DEV-442678 |
|
If a production Vault contains a document type that isn't present in a sandbox, attempts to train a Trained Model in that sandbox fail.
|
DEV-443221 |
|
In some cases, automated Training jobs may fail if a document's state is such that it can be pulled multiple times into the Training job.
|
DEV-443457 |
|
Training a model from production data in a sandbox or prerelease Vault fails to use archived documents.
|
DEV-443524 |
|
Vault displays an incorrect error message when a user executes the Distribute to Sites action from a Safety Distribution record and the related Study record does not have any Study Products.
|
DEV-444304 |
|
TMF Transfer fails if document attachments contain a leading space.
|
DEV-445217 |
|
In a Vault with a CDMS to CTMS connection, if a user deletes the Subject from a Casebook in the CDMS Vault, the Inbound and Inbound Worker jobs fail with errors in the CTMS Vault.
|
DEV-445596 |
|
Creating documents while Vault is auto-training a model can cause training to fail.
|
DEV-445603 |
|
TMF Bot fails to auto-classify documents uploaded from Veeva Snap.
|
DEV-445633 |
|
The TMF Quality Check dialog takes longer than expected to load.
|
DEV-445760 |
|
In some cases, Vault fails to show all events while running the Apply Milestone Template user action.
|
DEV-448063 |
|
Vault fails to provide an exception message after the Inbound Worker job fails due to Protocol Deviations/Procedures mapping issues.
|
DEV-448201 |
|
After transferring a video using TMF Transfer with a simple or complex rule set, users may see a transcoding error when attempting to play the video in the target Vault.
|
DEV-448371 |
|
In cases with more than 200 Sites, Safety Distributions fail to create more than 200 Distribution Task records.
|
DEV-449595 |
| Description |
Issue No. |
|
In some cases, Vault does not properly display images in rendered Microsoft Word™ documents in the document viewer.
|
DEV-315296 |
|
Vault incorrectly updates the Effective Date token on documents with merge fields.
|
DEV-371664 |
|
In some cases, Vault fails to generate formatted outputs.
|
DEV-377359 |
|
Vault fails to generate bookmarks based on captions when the "Caption Bookmarks" rendition option is enabled.
|
DEV-383902 |
|
In rare cases, records are missing from Formatted Outputs when the same record values are present in multiple locations, such as across several tables.
|
DEV-385091 |
|
Users are unable to update formatted output templates that include the ORDER BY clause.
|
DEV-390447 |
|
In some cases, Vault fails to render Microsoft Powerpoint™ documents with the “Speaker Notes” layout setting.
|
DEV-391379 |
|
When a user attempts to compare versions of an encrypted PDF for which Vault cannot extract text, Vault displays the incorrect error message, "Vault has detected more than 5,000 changes between these versions. Vault does not display any changes when this number is detected."
|
DEV-393925 |
|
Vault improperly renders Microsoft Powerpoint™ documents with speaker notes.
|
DEV-394454 |
|
Serif fonts are incorrectly merged from .RTF documents in Microsoft Word™.
|
DEV-400908 |
|
In some cases, Merge Field tokens merge with an additional, incorrect blank value.
|
DEV-402251 |
|
In some cases, Vault fails to render documents with merge fields.
|
DEV-404454 |
|
Korean language characters are not displayed in rich text fields on exported Formatted Outputs.
|
DEV-410634 |
|
Vault fails to render password-protected Microsoft Excel™ files.
|
DEV-413403 |
|
Vault fails to render merge fields documents using repeaters in table rows.
|
DEV-413797 |
|
When users make changes to document fields via MDL, any default values that are not defined in the changes will become blank, even if they previously had a value.
|
DEV-414275 |
|
Documents uploaded into any file path that includes the word "inbox" are considered inbox documents whether they should be or not.
|
DEV-414281 |
|
When users attempt to merge anchors from a mini-browser, the Merge Anchors dialog does not appear.
|
DEV-415053 |
|
In some cases when using track changes and merged fields, unexpected field code changes are shown in the source document.
|
DEV-416383 |
|
When resizing the browser, users may encounter the document info panel growing out of proportion with the viewer.
|
DEV-416971 |
|
When a user creates a new draft of an approved document, deletes it, and then creates another draft, Vault displays the incorrect version number in the confirmation window for the new draft but still creates the draft with the correct version number.
|
DEV-418282 |
|
On 1280 x 800 resolutions, the Information panel on the Doc Info page is too large.
|
DEV-418759 |
|
After a user edits fields in the Information Panel and then enters Annotate mode, the annotation Info Cards are no longer visible.
|
DEV-419234 |
|
Pressing the Shift key while typing an annotation comment and then saving the annotation changes the mouse cursor to a grab cursor.
|
DEV-419303 |
|
Under certain conditions, performing actions on a document cause server errors.
|
DEV-419989 |
|
If a user starts to type an annotation or reply to an annotation and then scrolls to another page in the document, Vault does not preserve the unsaved annotation data.
|
DEV-420168 |
|
When a user creates a new line annotation on the bottom of a document page with many annotations/replies, Vault sometimes places the annotation on the next page instead.
|
DEV-420189 |
|
When a user creates a new line annotation on the bottom of a document page with many annotations/replies, Vault sometimes places the annotation on the next page instead.
|
DEV-420189 |
|
Vault fails to render .EML files with attachments.
|
DEV-420431 |
|
When creating a permalink annotation using the "Select or create permalink in this document" dialog, if a user adds a page as a permalink target and then manually enters that page number in the pagination navigator, the red minus (-) icon for that page changes to a green plus (+) icon.
|
DEV-420625 |
|
In some rare cases, when a user attempts to export annotations, the export fails.
|
DEV-420679 |
|
With Action UI enabled, highlighting text in an unsaved sticky note annotation with the cursor causes the text to disappear.
|
DEV-420951 |
|
Resolved note annotations do not appear in a document's Notes view, and when a user resolves an annotation in Notes view, the annotation disappears.
|
DEV-421305 |
|
In Overlay mode with a filter for resolved annotations, if a user creates a note and switches to Sidebar mode, the new unresolved note displays on the page.
|
DEV-421331 |
|
If a user opens the Filter menu from the DocInfo page and then views annotations in Notes or Thumbnail view, the annotation view shifts to the right.
|
DEV-421332 |
|
When using Infinite Document Scrolling in Overlay mode, scrolling down from a page with annotations and then returning and clicking an annotation causes the annotation to move to the top of the page.
|
DEV-421349 |
|
In Detail and Compact view, if a document's name has over 100 characters, Vault does not display a warning, and the name overlaps the lifecycle stage badge.
|
DEV-421464 |
|
When filtering annotations, if a user both filters for Auto Links and filters out Approved Links, Approved Links are not hidden.
|
DEV-421716 |
|
In some cases, documents may fail to render when they contain a large number of Merge Fields errors.
|
DEV-421974 |
|
With Infinite Document Scrolling enabled, scrolling down and then back up to a pending annotation may cause the pagemark to disappear until the annotation is saved.
|
DEV-422334 |
|
After a user clicks the Complete button from the Actions menu of an unclassified document, the Classify Document dialog does not appear.
|
DEV-422476 |
|
In Overlay mode, if a user adds another line to a pending line annotation with a comment and then clicks anywhere on the page, the annotation is cancelled and the comment data is lost.
|
DEV-422506 |
|
After exiting fullscreen mode, adjusting the size of the browser does not correctly resize the document and moves annotations to the bottom of the document.
|
DEV-422557 |
|
In some cases, link annotations on published documents do not appear or function as expected.
|
DEV-422786 |
|
Suggested Links in Pending status are visible in the Notes view of Annotate mode.
|
DEV-422789 |
|
In some cases, tokens in documents with merge fields in tables fail to merge.
|
DEV-422845 |
|
When users attempt to upload documents using an integration, occasionally some document MD5 checksums remain in the Pending state indefinitely.
|
DEV-423033 |
|
In some cases, with Action UI enabled, the document viewer toolbar is missing after disabling Annotate mode.
|
DEV-423196 |
|
On a non-video document with many annotations that are close together, when a user selects an annotation and then resizes the document viewer, the selected annotation's infocard moves away from its placemark.
|
DEV-423465 |
|
In Notes view, when a user selects a "Group by" option, Suggested Links are not excluded.
|
DEV-423690 |
|
In some cases, links are broken in Merged & Published RLCP documents once the document is sent through Adobe Sign.
|
DEV-423815 |
|
With Infinite Document Scrolling enabled, when a user creates an annotation in Overlay mode, the annotation's infocard may appear far away from the placemark.
|
DEV-423891 |
|
Vault fails to render documents with barcode tokens.
|
DEV-423936 |
|
In some cases, Vault fails to merge password-protected files.
|
DEV-424450 |
|
After creating a Content Module record and running the Generate Approval Document action, users receive failure and success notifications if the action succeeds and duplicate failure notifications if it fails.
|
DEV-424509 |
|
In rare cases, users may be unable to execute version binding on binders that contain sufficiently large documents or other binders.
|
DEV-424723 |
|
After relabelling the Inbox lifecycle and document type, users cannot upload documents via Veeva Snap.
|
DEV-424743 |
|
When Auto Invite External Users is enabled for collaborative authoring and a new external user checks out a document, checkout fails with an error and does not automatically retry.
|
DEV-424821 |
|
The Notes and Placements filter sections might not update dynamically when annotations are resolved, reopened, or placed.
|
DEV-424974 |
|
Vault fails to generate an Approval Document if the Content Module contains a PDF, image, or Microsoft PowerPoint™ document asset.
|
DEV-425722 |
|
Vault allows users to create Linked Document relationships when the "Enable Create & Import Document Links" setting is disabled.
|
DEV-425812 |
|
Users can see and execute annotation actions from the document mini-browser.
|
DEV-425883 |
|
User mentions do not appear in Notes view.
|
DEV-425887 |
|
When users reply to deleted comments on documents, Vault creates an orphaned comment or does not save the comment at all and does not generate an error message.
|
DEV-426440 |
|
When a user attempts to hide an annotation in Notes view, Vault fails to hide it.
|
DEV-426674 |
|
In some cases, Vault displays a "Server having problems" error when a user attempts to upload a document with dynamic reference constraints on any fields.
|
DEV-426678 |
|
In some cases, annotations from prior renditions will reappear after a new rendition is uploaded.
|
DEV-427023 |
|
In some cases, Vault may unnecessarily regenerate advanced eSignature templates.
|
DEV-427110 |
|
In some cases, pending annotations will temporarily disappear when a user resizes their browser window or scrolls to another page of the document.
|
DEV-427225 |
|
In some cases, Vault fails to render documents with merge fields due to missing linked documents.
|
DEV-427743 |
|
Vault fails to render Merge Field tokens embedded in shapes within tables.
|
DEV-427752 |
|
In some cases, Vault incorrectly renders Follow Up letters and fails to populate fields.
|
DEV-427856 |
|
In some cases, Vault fails to perform the Generate Approval Document action.
|
DEV-429082 |
|
In some cases, e-signature pages regenerate unexpectedly.
|
DEV-429513 |
|
Users cannot delete annotations on videos despite having the correct permissions.
|
DEV-429539 |
|
In some scenarios when using the Share Inbox Documents feature, changing the owner role also adds the Inbox Editor Role.
|
DEV-429559 |
|
In some cases, PDF rendition bookmarks navigate to the wrong place in the document when the dynamic linking feature is enabled in the Vault.
|
DEV-430349 |
|
In some cases when users attempt to view the References section of a claim, the entire page goes blank.
|
DEV-430431 |
|
In some cases, Vault fails to remove references to deleted minor document versions from claims.
|
DEV-430433 |
|
In some rare cases, when a user highlights text, all annotations temporarily disappear until they refresh the page.
|
DEV-432425 |
|
In some cases, Vault fails to render and resolve tokens on Merge Fields documents using the “Document Number” token.
|
DEV-432719 |
|
In some cases, Shared Inbox documents are shared with the wrong users after being reclassified.
|
DEV-432897 |
|
The "major version_number_v" and "minor_version_number_v” tokens do not render correctly with concatenated static text on Excel Merge Fields documents.
|
DEV-433107 |
|
In some rare cases, Vault is unable to recognize older PPT files.
|
DEV-433110 |
|
If a user cancels editing an annotation, then makes style changes to another, the changes will also appear to be applied to the first annotation.
|
DEV-433258 |
|
Users are able to edit the max length of several fields including Document Name when these fields should not be editable.
|
DEV-433420 |
|
In some cases, Vault fails to include new data when remerging documents with nested tables.
|
DEV-433905 |
|
In some cases, users are able to bring forward annotations when the feature is disabled.
|
DEV-434005 |
|
With Action UI enabled, Vault allows users to download manually uploaded viewable renditions, but does not display them in the Files pane on the Doc Info page.
|
DEV-434347 |
|
Vault does not update the "Generating Viewable Rendition..." status in the document viewer for documents re-rendered in bulk.
|
DEV-434406 |
|
In some cases, clicking a link annotation pointing to an anchor takes the user to the wrong place in the document.
|
DEV-434446 |
|
In some cases when users attempt to edit the color of an existing text highlight, Vault fails to change the color.
|
DEV-434493 |
|
When users select "Link to Content" on video documents, Vault fails to open Annotate mode.
|
DEV-434621 |
|
Longtext boxes do not fill the entire space they should occupy in edit mode.
|
DEV-434971 |
|
When users attempt to cancel relocating a note to a different page of a document, Vault fails to close relocate mode.
|
DEV-435181 |
|
In some cases, Vault fails to apply users' color preferences to annotation replies.
|
DEV-435946 |
|
In some cases, Vault takes longer than expected to render audio and video files.
|
DEV-436376 |
|
Users are able to add links to external link annotations with the Link to Content option.
|
DEV-438020 |
|
Tags for link annotations do not persist after refreshing the page or navigating away.
|
DEV-438041 |
|
If a user selects an annotation, scrolls to another page, and then scrolls back, the placemark may no longer appear.
|
DEV-438481 |
|
In some cases, Vault does not prevent users from performing a bulk delete action on a batch of 100 or more documents that includes documents referenced by object records.
|
DEV-438571 |
|
If a user attempts to move an annotation placemark then performs a link to content without first saving the move, the + icon may not appear on the moved document.
|
DEV-439097 |
|
When a user causes a pending area placemark to be redrawn due to a window resize or scrolling across tranches, the placemark may become shifted by 6px on both the x and y axes.
|
DEV-439183 |
|
Users are able to edit anchors they authored, even without the Annotate permission.
|
DEV-439278 |
|
The "Undo Checkout to Google Drive" action is missing from the audit trail.
|
DEV-439677 |
|
When a user cancels out of a reply in progress with a custom color then begins a new reply, Vault may apply the color of the cancelled reply to the new reply.
|
DEV-439922 |
|
In some cases, when re-entering annotate mode, Vault may scroll to a different page than what the user was viewing in view mode.
|
DEV-440068 |
|
The "Open in Google Drive" action is missing from the audit trail.
|
DEV-440529 |
|
When using Microsoft Edge, users may be unable to open the document viewer within an iframe.
|
DEV-441283 |
|
In rare cases, bulk deletion may incorrectly delete a document when only some of its versions should have been deleted.
|
DEV-441657 |
|
In the Document Viewer or a rendition, some information may be missing from Draft or Obsolete documents with merge fields.
|
DEV-442039 |
|
When users edit the URLs of external links, the changes do not persist.
|
DEV-442092 |
|
When a user changes the color of a pending arrow annotation placemark, the placemark may shift right and down.
|
DEV-442152 |
|
When navigating to the File tab of the Document Info page, users receive an error if the Content Size document field is hidden from them.
|
DEV-442665 |
|
The Send as Link action fails to send to users who have permission to view the document via a group.
|
DEV-443459 |
|
When attempting to re-authorize to CollabAuthoring after exiting the page, Vault shows an "Authorizing" banner instead of the Microsoft Login page.
|
DEV-443639 |
|
After an Admin authorizes an Office 365 account, the Integration Status does not show as "Verified" until the Admin refreshes the page.
|
DEV-445820 |
|
When "Enable Google Drive Integration" is disabled and a user checks in a new version of a document, Vault displays warnings related to Google Drive.
|
DEV-446760 |
|
Documents checked out by external users with the most restrictive Sharepoint/OneDrive configuration cannot be checked back in.
|
DEV-447544 |
|
In some cases where users have configured a custom label for the Attachments field, Vault incorrectly displays "Attachments" instead of the custom label.
|
DEV-450686 |
| Description |
Issue No. |
|
When a user attempts to enter a value larger than 999 in the Order field while creating a Question Design object record, Vault displays a server error rather than a warning to enter a lesser value.
|
DEV-352703 |
|
When a user reduces the maximum length value of a text field on a High Volume type object, and existing records for that object type contain values for that field in excess of the new maximum length, Vault displays a server error rather than a more helpful error message describing the problem.
|
DEV-364136 |
|
Editing a Rich Text field to enable field-level encryption for PHI/PII results in a server error.
|
DEV-392436 |
|
Under certain circumstances, when hovering over an object reference, the hovercard may show missing or incorrect information.
|
DEV-416928 |
|
When a user changes the value of a controlling object reference or picklist field when creating or editing an object record, default field values in the controlled field may behave unexpectedly.
|
DEV-418698 |
|
When lookup field with a picklist as its source field is referenced in an expression, and an Admin edits the picklist to allow users to select multiple values, Vault does not display an error or block the action, and users experience a server error when trying to access the configuration page containing the expression.
|
DEV-421673 |
|
When a user edits the Name field of an Index on a high volume object and clicks Continue on the confirmation dialog, Vault reverts to the original name value and does not allow the user to save changes.
|
DEV-423845 |
|
When "Available in All Lifecycle States" is enabled on an SDK record action, and a user's permissions change to allow or disallow the action while the user is viewing an object record page, Vault does not update the Actions menu to add or remove the action from the dropdown each time the user clicks on it.
|
DEV-424331 |
|
When a user expands a related object section when viewing a Study record, a different section is highlighted.
|
DEV-425002 |
|
On the Create Field page with Parent Object selected, disabled objects may be listed on the same line.
|
DEV-425084 |
|
In some related sections, list, and hierarchy views, Vault does not freeze the UI while a state change action is in progress.
|
DEV-426433 |
|
Vault fails to show the "Show In Tab" button on related object sections when the Lifecycle State filter uses a "contains" operator.
|
DEV-427718 |
|
In some cases, users encounter a server error when they click the Advanced Search icon while creating object workflow action rules with Perform with conditions criteria applied.
|
DEV-429470 |
|
In some cases, Vault displays an incorrect error message when a user enters an invalid character in a text field while creating or editing an object record.
|
DEV-433138 |
|
In some cases, users are unable to search, sort, or navigate between pages in related objects sections.
|
DEV-435383 |
|
Certain validation rule configurations on objects may conflict with User timezones and cause Vault to display an error when a user attempts to save the object record.
|
DEV-436071 |
|
Vault does not display object types in alphabetical order in the Create Related Object Record pop-up dialog.
|
DEV-436921 |
|
In rare cases, Vault allows fields to contain more than the maximum 32,000 characters.
|
DEV-438952 |
|
In some cases, users may be unable to delete Site, Study, and Study Country records in bulk using the UI, Vault Loader, or API.
|
DEV-439714 |
|
In some cases, after a sandbox Vault refresh, Email to Vault may not create Email records.
|
DEV-446466 |
|
In some cases, Vault may display a "Server having problems" error when running the Create Related Records user action.
|
DEV-446945 |
| Description |
Issue No. |
|
The Domain Users list view and Record Sharing Settings pages contain small UI spacing issues.
|
DEV-394087 |
|
In some cases, when viewing a list of documents, list traversal arrows are missing.
|
DEV-411857 |
|
When attempting to specify the same query object on more than one query object rule, the error message displayed is not accurate.
|
DEV-414059 |
|
When attempting to active a query object rule which has the same query object as an existing active query object rule, the error message displayed is blank.
|
DEV-414060 |
|
On the detail page for a Spark Queue, the Sequential Message Processing and Rollback on Error checkboxes appear to be clickable even when not in Edit mode.
|
DEV-414515 |
|
When searching for an ampersand (&), Vault displays the ampersand escape code (&) in search results.
|
DEV-414626 |
|
No icon is displayed for the Activate/Inactive action on integration rules.
|
DEV-417049 |
|
Vault fails to display values for the Classification field in Read and Understood Dashboard prompts.
|
DEV-418183 |
|
In some cases, the Filter button may incorrectly display as selected in document Annotate mode.
|
DEV-418211 |
|
In some cases, certain Vaults may experience temporary performance issues.
|
DEV-419523 |
|
On certain screen resolutions, users may be unable to scroll to the bottom of the Actions menu in the Content Plan Hierarchy Viewer.
|
DEV-420945 |
|
In Tabular View, the Actions menu drop-down is missing a box-shadow and is difficult to distinguish from the background.
|
DEV-421912 |
|
In some cases, checklist creation via an entry action may fail.
|
DEV-422870 |
|
When a user sorts more than 25 tasks and switches between Grid view and Detail view, the tasks may not be sorted correctly on the second page.
|
DEV-423423 |
|
In some cases, with Action UI enabled, Vault fails to show the right arrow icon on picklist modifiers.
|
DEV-423497 |
|
In cases with slow network connections, Vault allows users to create duplicate records while the initial records are processing.
|
DEV-423839 |
|
Vault incorrectly displays "Start Multi-Document Workflow" on dialogs that should read "Start Document Workflow."
|
DEV-425355 |
|
Vault fails to show the complete color picker in Notes view.
|
DEV-425888 |
|
When a user's permissions change to allow or disallow an action while viewing an object record page and opening the All Actions menu multiple times, the Action Bar does not show a Loading animation while it updates the actions.
|
DEV-426030 |
|
After creating an item called "Placeholder" in Configuration > Document Types or Document Fields, Vault incorrectly renders the Configuration page.
|
DEV-426457 |
|
If a user opens an "Edit Annotation" menu too close to the bottom of the screen, they may be unable to scroll to see the bottom of the menu.
|
DEV-426699 |
|
In some cases, there may be performance issues when running bulk state change actions on Active Dossier Item records.
|
DEV-427099 |
|
When viewing Sharing Rules for a document lifecycle, the "Sharing Rules" text is out of place.
|
DEV-427367 |
|
When a user sorts more than 25 tasks and switches between Grid view and Detail view, the tasks may not be sorted correctly on the second page.
|
DEV-428378 |
|
Some users may experience slower UI performance when creating link annotations.
|
DEV-428881 |
|
Headers improperly overlap when printing document information pages.
|
DEV-429400 |
|
Vault fails to translate Action UI workflow state change labels into Japanese.
|
DEV-429735 |
|
The Start Step Rule definition page may not correctly change colors upon saving the rule.
|
DEV-430116 |
|
In some cases, when viewing the document viewer in the mini browser, users may be unable to see the annotate toolbar.
|
DEV-430210 |
|
With Action UI enabled, the action bar flickers while Vault renders documents.
|
DEV-431297 |
|
When a checklist has over 100 attached documents in total, some documents may not appear in the Review section.
|
DEV-433114 |
|
From list view in Business Admin > Outbound/Inbound Packages, the Actions menu does not execute actions.
|
DEV-434026 |
|
Vault displays the incorrect styling in the Workflow History printable view.
|
DEV-434836 |
|
The token ${product__v} does not work in the FavoriteDocumentNotifications message.
|
DEV-435018 |
|
In rare cases, other elements of the UI may overlap with the Vault title.
|
DEV-436402 |
|
Two favorite icons are visible on each document in compact Library view.
|
DEV-437853 |
|
When opening a record in Vault, certain users may experience buttons taking longer than expected to appear.
|
DEV-438145 |
|
In certain scenarios, users receive a Server Having Problems error on the Home tab.
|
DEV-439227 |
|
The label in the Google Drive document selector is incorrect.
|
DEV-439730 |
|
In the Library, the threshold for rounding up the total document count is slightly different for tabular and non-tabular views.
|
DEV-440850 |
|
When a user runs Create Related Records on an Event, the wizard freezes on a blank screen.
|
DEV-441483 |
|
The scheduled time for the Scheduled Data Export job cannot be changed after Daylight Savings Time ends.
|
DEV-448368 |
| Description |
Issue No. |
|
In the training materials section of a Training Requirement, Vault may display the ADD button or REMOVE action if a user does not have appropriate permissions to the Training Content Set and TrainingContentSet-Document objects. Performing these actions may cause Vault to display an error.
|
DEV-377473 |
|
In certain cases where changing a Quality Team member will cause a task reassignment, Vault may display a server error.
|
DEV-410068 |
|
When attempting to create an Effectiveness Check record via an entry action with a configured Quality Team cascade, Vault displays a non-descriptive error message.
|
DEV-415108 |
|
On Internet Explorer™️ 11, after clicking the Actions menu on a Document Change Request in the grid view for a Document Change Control record, the menu items do not appear until the user hovers over the area where they should appear.
|
DEV-416981 |
|
Under certain conditions, when a Substitute Training Rule has the condition that the Person's Status should be Active, the corresponding Substitute Training Requirement is not assigned to active Learners.
|
DEV-418887 |
|
The "Show More" link does not appear on the Learner Homepage for Training Assignment descriptions that are more than three (3) lines long.
|
DEV-420089 |
|
In some cases, the Update Training Assignments job may fail with an error when processing a Training Assignment which has no related Training Content Set.
|
DEV-423473 |
|
In certain cases where a Quality Team member has started a workflow and has an active task assigned to them from that workflow as part of the Workflow Initiator participant group, Vault displays "Server having problems" when attempting to remove that user from the Quality Team.
|
DEV-423884 |
|
Under certain circumstances, using the Manage Team button to remove a user from a Quality Team role may not remove the users or cancel workflows as expected.
|
DEV-424390 |
|
When a user attempts to change a document state to Issued, Vault displays a Server Having Problems error.
|
DEV-425809 |
|
In some cases, when attempting to remove a lifecycle from an object after deleting the Quality Team from the same object, Vault may incorrectly state that the lifecycle is still in use.
|
DEV-426229 |
|
In some cases, an External Collaborator user may receive an incorrect Goodbye email notification if removed from collaboration on multiple records.
|
DEV-426592 |
|
Vault incorrectly shows a purple banner on failed quizzes instead of a red banner.
|
DEV-427878 |
|
The "User must always enter a value (required)" setting may not be available as expected for the QMS Record Relationship Nature field.
|
DEV-429122 |
|
Creating a Quality Team for an object with a label that starts with number characters results in Vault displaying an error and failing to create the team.
|
DEV-432209 |
|
Clicking the breadcrumb on a Training Assignment record details page may not function as expected.
|
DEV-432446 |
|
If a locked Quiz is not set to Auto-Unlock, the Update Training Assignments job fails to complete.
|
DEV-435301 |
|
The Fields to Display section of a Visual Hierarchy Configuration page may not display as expected if one of the fields is inactivated.
|
DEV-435484 |
|
In some cases, the ${docNameNoLink} token may not resolve correctly in the Controlled Copy Job Completed document message.
|
DEV-435527 |
|
In some cases, Vault may fail to send a notification to the Vault Owner for failure of the Cancel Training Assignment job.
|
DEV-435917 |
|
Vault may display an error when a user attempts to delete an objects with Quality Teams configured for multiple object types.
|
DEV-437291 |
|
In Related Record Configurations, an Admin may incorrectly be able to map a picklist field to a non-matching picklist field, potentially causing errors upon related record creation.
|
DEV-440263 |
|
The Version History panel for Document Change Controls may have incorrect spacing.
|
DEV-440528 |
|
In some cases, a quiz Checklist Design record's Auto-Unlock field may not have the correct value after saving the record.
|
DEV-442525 |
|
In some cases, Vault may display an error when running the Start Periodic Review Workflow entry action.
|
DEV-442558 |
|
When a user runs a recurrence check on a Complaint record, Vault may display a "Server having problems" error if the Quality Record Check involves a related object with an empty Quality Event field.
|
DEV-442936 |
|
In some cases, when a user attempts to save a Quality Event record, Vault displays an error saying it could not save the record because it has been updated.
|
DEV-442944 |
|
When an Admin configures a record check that references a formula field as a field that must match, Vault displays a "Server having problems" error when running the recurrence check.
|
DEV-443254 |
|
In some cases, users may encounter a "Server having problems" error and be unable to complete a workflow task for a Quality Event record.
|
DEV-444595 |
|
The QMS External Collab Goodbye template for SCAR contains an invitation instead of a goodbye message.
|
DEV-444596 |
|
In cases where a workflow task triggers updates to sharing settings, Vault may display an error if the task attempts to remove a user from a set of roles that includes a role managed by a Quality Team.
|
DEV-445899 |
|
When a user attempts to update a Quiz Checklist Design record that is in the Draft state, Vault may display an error that changes are not permitted when the record is not in the Draft state.
|
DEV-446511 |
|
In cases where the Learner is not associated with a Vault User record, Vault may display a server error when a user attempts to manually update the due date of that Learner's Training Assignments.
|
DEV-448992 |
|
In some cases, the label for the Download Controlled Copy action may be blank on the Configuration page and incorrect in the Actions menu.
|
DEV-449085 |
|
In some cases, a Facilitated Training job may fail to change a Facilitated Training Request record to the Completed state if the record contains a validation rule that references today('user').
|
DEV-450545 |
| Description |
Issue No. |
|
Certain Submission Administrative Information fields display the health authority code instead of the more readable Controlled Vocabulary name.
|
DEV-293681 |
|
In some cases, moving link annotations from page to page may not function as expected.
|
DEV-341442 |
|
In some cases, after initial publishing, duplicate links may be included in link counts.
|
DEV-375927 |
|
Users cannot download Publishing Progress details for Content Plans with a failed publishing status.
|
DEV-380519 |
|
In some cases, Submissions are transmitted to the gateway more than once.
|
DEV-389576 |
|
In some cases, when users publish and merge a report level content plan, Vault doesn't publish the merged PDF, and the notification doesn't alert users of the failure.
|
DEV-394624 |
|
In some cases, Vault fails to create the Util folder during continuous publishing.
|
DEV-407211 |
|
Copying a Content Plan section into a Content Plan succeeds even if the Submission join copy fails.
|
DEV-412967 |
|
In some cases in Vaults using the RIM to PromoMats connection feature, initial publishing may incorrectly trigger continuous publishing.
|
DEV-413138 |
|
In some cases in Vaults using the RIM to PromoMats connection feature, after continuous publishing starts, a file may not be published when the Source for Published Document field value is Source Document.
|
DEV-413144 |
|
In some cases, hovercards may not display as expected in the Active Dossier Viewer.
|
DEV-413603 |
|
In the Manage Registered Details wizard, when a user clicks a date in the Marketing Start Date column, the date displayed in the calendar may be incorrect.
|
DEV-413851 |
|
In some cases in Vaults using the RIM to PromoMats connection feature, instead of creating two User Exception Item records for two different EDLs, Vault may create two User Exception Item records for the same EDL.
|
DEV-414002 |
|
RDI, DI, UDI Submission, and UDI Submission DI records can be created even when the organization record's EUDAMED code field value is invalid.
|
DEV-414599 |
|
The Add to Active Dossier pop-up dialog may have misaligned UI elements.
|
DEV-414800 |
|
After running the RMS Integration and Synchronization job, the CSV results file cannot be downloaded.
|
DEV-415160 |
|
In some cases, on-demand publishing of crosslinks, where the source for published output is set to source document, may not complete as expected.
|
DEV-415481 |
|
When an Admin makes an API request that includes a Submission file path with a user folder that does not match the user's ID, no error is displayed, and Vault stores an invalid path in the database.
|
DEV-419499 |
|
Under the Report Prompts section of the Impact Assessment Report Options dialog, there is no space between the field name and the word "in".
|
DEV-420160 |
|
When a user creates a new Active Dossier Item and provides values for the Active Substance and Manufacturer, the resulting record also contains values for other attributes such as Product Variant.
|
DEV-420673 |
|
In Vaults with Action UI enabled, the leaf icon hovercard may not behave as expected in the Submissions Archive Viewer.
|
DEV-420902 |
|
Vault displays an unexpected "Insufficient permissions" error message when a user copies a Content Plan or Content Plan Item section into a deleted Content Plan section.
|
DEV-421468 |
|
In some cases, Vault incorrectly shows continuous publishing jobs as pending in the publishing progress indicator.
|
DEV-422825 |
|
The update content plan job may fail if the XML title field contains a token that is not resolved.
|
DEV-422881 |
|
In the email notification sent when a Submission import completes, the list of omitted files includes files located outside of the Submission folder, and their file paths and names are incomplete.
|
DEV-422944 |
|
In some cases, after renaming a Country record, Vault fails to create the related Application Country record.
|
DEV-423862 |
|
Correspondence documents do not appear in the Submissions Archive Viewer when the Submission record's Dossier Status has no value.
|
DEV-423944 |
|
Vault fails to properly apply Dynamic Ordering to MSG (.msg) files in the Submissions Archive Viewer.
|
DEV-424457 |
|
When an Application has a previous Submission with a Submission Archive Status and no Dossier Status, Vault incorrectly reports US validation rule 1636.
|
DEV-424553 |
|
Under some circumstances, ZA rules Rule9.BP5, Rule9.BP6, and Rule9.BP7 are incorrectly reported.
|
DEV-425333 |
|
When a Correspondence document only has an Application value, expanding the Dossier Review panel results in an unexpected error.
|
DEV-425729 |
|
When filters are applied and a user drags a document to the Content Plan Hierarchy Viewer, the bottom orange indication line does not appear.
|
DEV-425768 |
|
When a user runs a user action for an asynchronous lifecycle state change, the job processing status icon in the Content Plan Hierarchy Viewer does not automatically turn orange to indicate a job is in progress.
|
DEV-426441 |
|
When the RIM to PromoMats connection is enabled, setting Enable Continuous Publishing to Yes incorrectly triggers an outbound job to PromoMats.
|
DEV-426809 |
|
After copying a submission content plan, the target content plan may include unexpected modules.
|
DEV-426838 |
|
In some cases, the Content Plan Hierarchy State Change action fails to complete.
|
DEV-427787 |
|
In some cases, Vault incorrectly shows the status of a completed with errors Submission Import job as still running.
|
DEV-428079 |
|
In some cases, Vault incorrectly shows continuous publishing jobs as pending in the publishing progress indicator.
|
DEV-428364 |
|
In some cases in Vaults using the RIM to Promomats connection feature, Vault sets the Source for Published Document to a viewable rendition, not the source document.
|
DEV-428919 |
|
The Submission Archive viewer displays a "Server Having Problems" error when attempting to view an application with correspondence with no filters available.
|
DEV-429117 |
|
In some cases, users may unexpectedly not be able to see the dropdown values of "Lifecycle State" in the "Registration" object when using "Edit & Verify" functionality.
|
DEV-431114 |
|
Vault fails to allow reimporting of Submissions via Vault File Manager.
|
DEV-431480 |
|
When publishing, if a UTIL file exists with a document type other than Submissions Archive, Vault Publishing may fail.
|
DEV-431519 |
|
When a user runs the Create Related Records wizard on an Event record with an Event Active Substance or Inactive Ingredients join, the wizard fails with an error.
|
DEV-431962 |
|
When there are more than 50 correspondence documents in one bulk action, the Submissions Archive Harmonization job fails.
|
DEV-432807 |
|
In some cases, the publishing progress indicator for certain Submissions jobs remains in the In Progress state for longer than expected.
|
DEV-433045 |
|
In some cases, validation of Publishing tasks fails to complete.
|
DEV-433410 |
|
In some cases, Vault displays "server having problems" when viewing the Historical Lifecycle on a Submission.
|
DEV-434228 |
|
Vault fails to complete workflow verification after a user clears the date fields on the Edit and Verify dialog.
|
DEV-434464 |
|
When a Mac user imports a Submission, the ZIP file may include the "__MACOSX" folder as the submission.
|
DEV-435426 |
|
In some cases, the View action may be available on the Product Family Application object but has no effect.
|
DEV-435650 |
|
The Report Level Content Plan Publishing job fails when a Content Plan Item record has an invalid object type reference.
|
DEV-435748 |
|
Vault incorrectly or incompletely generates FHIR message XML.
|
DEV-436134 |
|
In some cases, updating Product details fails to also update the related Packaging records when creating bulk Registrations.
|
DEV-436747 |
|
When a user exports a Submission that is configured to hide Correspondence documents in the Submissions Archive Viewer, the export includes Correspondence documents.
|
DEV-438006 |
|
Vault incorrectly applies auto-naming patterns during automatic Submission and Regulatory Objective record creation.
|
DEV-438122 |
|
Vault settings to Enable Auto Links, Enable Claim Links, and Exclude specific characters when matching Annotation Keywords to content are hidden from Admin UI.
|
DEV-438196 |
|
In some cases, Vault incorrectly sets the Published by Vault field when performing publishing tasks on unpublished Submissions.
|
DEV-438451 |
|
The Manage Registered Details wizard prevents users from editing the Last Renewal Date field on the Registration object.
|
DEV-438536 |
|
In some cases, the Report Level Content Plan Publishing job gets stuck at Running (100%), preventing subsequent job runs.
|
DEV-438608 |
|
Vault fails to generate viewable renditions for Report Level Content Plan published documents when the file extension is not defined in the Published Output Location.
|
DEV-439265 |
|
In some cases, Vault fails to generate IDMP Container Reference Item records, and the failure is not logged in the resulting CSV file.
|
DEV-439286 |
|
In some cases, Vault fails to populate non-editable fields when updating registered object records via the Manage Registered Details wizard.
|
DEV-441033 |
|
During publishing, Vault incorrectly reports US validation rule 1850 when there is a mixture of new and append STF XML.
|
DEV-441814 |
|
In some cases, Submission sections containing non-empty sections are marked as empty within the Submissions Archive Viewer.
|
DEV-442671 |
|
Vault does not include the Application Folder within the zip file for AS2 transmissions to Health Canada.
|
DEV-443132 |
|
A Submission Content Plan may include languages that XEVMPD does not require.
|
DEV-443415 |
|
In some cases, when submissions include working documents, Vault incorrectly creates hyperlinks to the working documents.
|
DEV-444179 |
|
When users first perform the re-import action on a Submission in the Publishing Inactive state, Vault performs the action as an import and merges the imported submission with the published output.
|
DEV-445336 |
|
When "Allow user to select multiple values" is enabled for the language_for_submission__v field, the notification sent after IDMP element generation may report errors in IDMP Attachment elements.
|
DEV-446178 |
|
When the related sequence ID is missing, Vault displays a "Server having problems" error when attempting to run the Update Administrative Information action.
|
DEV-447190 |
|
In some instances when there are many Content Plan Items, some records have an incorrect lineage value, causing them to not display in the Hierarchy Viewer.
|
DEV-448442 |
|
If there are unreferenced files at the root of the ZIP file for import at the submission level, Vault may import the submissions as non-eCTD instead of eCTD.
|
DEV-450185 |
| Description |
Issue No. |
|
Fixed an issue where MHRA E2B R2 Dose Forms (B.4.k.7) were imported as dose form term ID codes instead of descriptive dose form names.
|
SAF-16105 |
|
Fixed an issue where duplicate detection was not populating the Worldwide UID (WWUID) field on the Case using the data from the Case Number, if the worldwide_uid__v field was added to Case Object Type.
|
SAF-18466 |
|
Fixed an issue where, when the Evaluate Submission Obligations action was run on a Case where the non-primary assessment was a SUSAR, no FDA submissions were generated.
|
SAF-19863 |
|
Fixed an issue where, when promoting an Inbox Item to Case, the Age at Onset and Age Group fields were not calculated and were left blank on the initial Case.
|
SAF-20113 |
|
Fixed an issue with custom E2B+ SDK xml formats, where the system did not send a notification when it could not generate a custom Transmission file successfully and instead generated a blank file.
|
SAF-20139 |
|
Fixed an issue where the DSUR Appendix: Cumulative Summary Tabulation of SARS was including unrelated serious adverse events in the report.
|
SAF-20205 |
|
Fixed an issue with the DSUR Cumulative Tabulation of Serious Adverse Events from Clinical Trials report where, when a Case was downgraded from Serious to Non-Serious, the report did not display the latest Case version within the reporting period.
|
SAF-20231 |
|
Fixed an issue with the unmasked DSUR Cumulative Tabulation of Serious Adverse Events from Clinical Trials report where the same adverse event could be counted in both the Blinded and Placebo columns when there are multiple versions of the Case.
|
SAF-20353 |
|
Fixed an issue where, when generating a PADER without a local datasheet set up, only the expectedness of the primary Case Adverse Event was considered in the PADER Summary of ADR from Postmarketing Sources report. Now, the report evaluates the expectedness on the Case Assessment for each Case Adverse Event.
|
SAF-20439 |
|
Fixed an issue with the unmasked and masked DSUR Interval Line Listings of Serious Adverse Reactions where the generated report did not include the latest version for a downgraded (serious to non-serious) Case.
|
SAF-20464 |
|
Fixed an issue where the Receipt Date calendar displayed a different date than the value entered in the field.
|
SAF-20475 |
|
Fixed a data compatibility issue with custom dose units entered on Inbox Items.
|
SAF-20478 |
|
Fixed an issue where, when an AER was created from an E2B(R2) file, two additional Case Assessment Results were generated on the AER if the adverse event was populated with text but the MedDRA Code was missing.
|
SAF-20530 |
|
Fixed an issue where G.k.2.2 was not populated due to the Product (Reported) field being blank on E2B export. Now, if Product (Reported) is blank for Open-Label studies, the system populates it using Product (Coded). For Blinded studies, the system populates Product (Reported) with Blinded Name (Placeholder), when creating a Case Product. When unblinding a Study Product, if the Product (Reported) field is blank or populated with the Blinded Name (Placeholder) value, the system populates the field using Product (Coded).
|
SAF-20710 |
|
Fixed an issue where duplicates of the MRN field in the Patient section were not detected by duplicate detection and were not displayed on the Potential Matches page upon promoting an Inbox Item.
|
SAF-20781 |
|
Fixed an issue with E2B(R3) mapping where the Event (Reported) field was mapped as a native term when the language was set to English or left blank.
|
SAF-20822 |
|
Fixed an issue with manual and AS2 import where, when an E2B(R2) file with Origin ID set to MHRAUK was imported, the Origin field was not populated on the Inbound Transmission if the Destination ID fields from the E2B file and transmission profile did not match.
|
SAF-20843 |
|
Fixed an issue where a server error appeared when an Inbox Item was imported from E2B or from the Intake API with the Localization field set to Japanese.
|
SAF-20864 |
|
Fixed an issue where, when FDA CBER VAERS and FDA ESG were configured with the same Sponsor ID and Health Authority ID, an error appeared when trying to save the Gateway Profiles.
|
SAF-20881 |
|
Fixed an issue where an inactivated narrative template was being used instead of the base template when creating a narrative from a Case.
|
SAF-20898 |
|
Fixed an issue with the DSUR and PBRER Cumulative Tabulation of Serious Adverse Events and the DSUR Cumulative Tabulation of Serious Adverse Reactions, where the aggregate reports failed to generate when the dataset contained one or more Cases with no primary Case Product.
|
SAF-20947 |
|
An enhancement in 21R1 resolved an unidentified long text truncation issue affecting Case Test Result Comments (F.r.6), Result (Text) Field (F.r.3.4) and Medical History Comments (D.7.1.r.5). This occurred when a case was copied for Follow-up or AER case promotion. This fix allows Veeva to identify previously impacted cases and then, with an approved change control (CC), restore the truncated data from the original. Impacted customers have already been contacted to proceed with full impact assessment and repair.
|
SAF-21034 |
|
Fixed an issue where a server error appeared when a user tried to view a Case Test Result in Vault Management Console (VMC) > View Configuration.
|
SAF-21039 |
|
Fixed an issue where the "Date Received by Manufacturer" field was always being mapped from the Case New Info Date. Now, Vault Safety has logic to populate this field from the Case Receipt Date for initial cases, and from the New Info Date for follow-up cases.
|
SAF-21064 |
|
Fixed an issue where the MedDRA version on Follow-Up Cases was not set properly after promoting an initial Case where the MedDRA version on Follow-Ups was set to use the previous Case version's.
|
SAF-21070 |
|
Fixed an issue where, when an E2B with an External Suspect Product was imported to Inbox Item, the External Product was mapped to a Study Product.
|
SAF-21081 |
|
Fixed an issue where the Cumulative Dose field was not auto-calculated after Case promotion from an Inbox Item, AER, or from the Case Compare Followup page.
|
SAF-21083 |
|
Fixed an issue where, when two custom gateway profiles with the same Sponsor and Health Authority ID combination were saved, an error notification stated "Error updating profile" instead of stating the required details.
|
SAF-21093 |
|
Fixed an issue where, when a Japanese MedDRA term containing more than one character was searched for, the search did not return any results.
|
SAF-21109 |
|
Fixed an issue where auto-coding in Japanese MedDRA was returning the incorrect English term and code.
|
SAF-21110 |
|
Fixed an issue where the API Names of the Controlled Vocabulary records for the OTC Drug Channel field was not in sync with the corresponding picklist value names.
|
SAF-21142 |
|
Fixed an issue where localized Cases were not copied from the Inbox Item or AER when promoting to Follow-Up from the Case Compare and Potential Matches page, respectively.
|
SAF-21186 |
|
Fixed an issue by modifying the MFDS and NMPA Controlled Vocabulary Record API Names to match their corresponding picklist value names.
|
SAF-21195 |
|
Fixed an issue where system performance was slow during the Promote to Case action.
|
SAF-21262 |
|
Fixed an issue where, when promoting cases in bulk, duplicate Cases were sometimes created from an AER if multiple operations tried to promote the same AER.
|
SAF-21288 |
|
Fixed an issue where validation errors occurred for EMA.G.k.4.r.7 when the Evaluate Regulatory Conformance action was run on a Case, even when G.k.4.r.7 (Batch/Lot Number) was populated on the Case Product Dosage.
|
SAF-21336 |
|
Fixed an issue where the Product Registration information on an Open-Label or Single-Blinded Study was not carried over to the Case after promoting an Inbox Item.
|
SAF-21367 |
|
Fixed an issue where, when an Inbox Item with a set localization was promoted to Case, the adverse event reported language was overriden by the English translation on the Case.
|
SAF-21377 |
|
Fixed an issue with PADER Interval Line Listings where, if the Case Transmission Date was the same as the Data Period End, the Transmission Date was displayed as "-" in the date column on the aggregate report.
|
SAF-21393 |
|
Fixed an issue where the Case field was not populated on a promoted Inbox Item when the Inbox Item was promoted to a follow-up Case version.
|
SAF-21435 |
|
Fixed an issue with multi-Case E2B import where one of the Receipt Date fields was not populated upon import, which led to the Initial Receipt Date field being left blank on Follow-Up Cases.
|
SAF-21436 |
|
Fixed an issue where a NullPointerException error appeared when promoting an AER (from E2B import) with a null receiptdate_date__v field to a Follow-Up Case.
|
SAF-21444 |
|
Fixed an issue where, in some cases, the Merge to PDF document action could not complete successfully.
|
SAF-21486 |
|
Fixed an issue where the Local Report Number and Local Message Number fields were not populated on the generated E2B(R2) acknowledgment file.
|
SAF-21535 |
|
Fixed an issue where the normalized Height and Weight fields were not auto-calculated and were left blank upon promoting an Inbox Item to an Initial Case.
|
SAF-21604 |
|
Fixed an issue where, when the initial Case version field was not properly set by a user on Follow-Up Cases, the Worldwide UID (WWUID) field was updated on the Follow-Up Case when fields monitored by the Case UID (Event Country, Product, Study) changed. Now, once the WWUID field is populated on a Case, it does not update even if the Case UID is updated.
|
SAF-21609 |
|
Fixed an issue where Case Product Dosages could not be masked during report generation for blinded report previews and masked distributions, including CIOMS I, FDA 3500A, E2B R2, and E2B R3 report formats. You can now request, by support enablement, to mask dosage information for blinded report previews and masked distributions. Unless this behavior is requested and enabled, report generation continues to populate dosage information by default.
|
SAF-21618 |
|
Fixed an issue where the Study field was not set on an imported Case from E2B if the Product did not match any Study Products in the system.
|
SAF-21777 |
|
Fixed an issue where a "NullPointerException" error appeared when trying to promote an AER to Case if the Controlled Vocabulary Patient record was deprecated.
|
SAF-21778 |
|
Fixed an issue where an error appeared upon E2B(R3) import for the Test Result field (F.r.3.2) due to the value exceeding the maximum value limit. This resulted in the ICSR entering Error state.
|
SAF-21892 |
|
Fixed an issue where the Age field was not populated on the FDA 3500A form after report generation if only Age (normalized) was present. Now, if the Age value is blank on the Case, the Age (normalized) field (if present) will be exported and set as the Age on the FDA 3500A form.
|
SAF-22017 |
|
Fixed an issue by advising users to use Receive Port 8080 because Vault Safety does not support sending MDNs (Message Delivery Notifications) on Port 4080 at this time.
|
SAF-22099 |
|
Fixed an issue with domestic Case processing where, when an Inbox Item with a localized Product (Reported) value was promoted to Case, the localized Product (Reported) value was overriden by the global value on the Case.
|
SAF-22417 |
|
Fixed an issue where an error appeared when a migration user tried to import Cases in batch with an attached CSV file.
|
SAF-22671 |
|
Fixed an issue where, when an E2B was imported to Inbox Item and G.k.2.5 (Investigational Product Blinded) was not present for a Suspect, Interacting, or Drug not administered Product, Case Product Blinded and Case Blinded were set to No instead of null.
|
SAF-22760 |
|
Fixed an issue where, when the Re-evaluate Submission Distribution action was run on a Case, the EMA.G.k.4.r.7 validation rule failed even when there was a Case Product Dosage and G.k.4.r.7 (Batch/Lot Number) was set with a valid nullFlavour value (UNK).
|
SAF-22824 |
|
Fixed an issue where, when the Re-evaluate Submission Distribution action was run on a Case, the EMA.G.k.4.r.7 validation rule passed even when there was no Case Product Dosage and G.k.4.r.7 (Batch/Lot Number) was not exported in the EMA E2B(R3) file.
|
SAF-22825 |
|
Fixed an issue where, the generation or regeneration failed for an E2B(R2) transmission document due to the adverse event records setting the Primary field to null upon promoting an Inbox Item to a Follow-Up Case.
|
SAF-22858 |
|
Fixed an issue where, when an FDA Submission was generated for a Study with Due Date Override enabled, the incorrect FDA Report Type was selected.
|
SAF-22942 |
|
Fixed an issue where, if a Case was received from a source that was not an Agent for an E2B imported AER, the Case New Info Date was set using the original value.
|
SAF-23365 |
|
Fixed an issue where E2B(R3) files with a Dose Text (G.k.4.r.8) value exceeding 1499 characters failed to import. The E2B(R3) standard character limit is 2000 characters.
|
SAF-23559 |
|
Fixed an issue where an Inbox Item that contains a blinded study but an unblinded product could not be promoted to Case.
|
SAF-23572 |
|
Fixed an issue where localized Cases were not copied from the AER when promoting to Follow-Up from the Potential Matches page.
|
SAF-24175 |