Description |
Issue No. |
In some scenarios, deploying the ‘Objectlifecyclestagegroup' component either with a VPK or MDL does work properly.
|
DEV-319275 |
In some scenarios, users may receive a “WFL-FADDS-II-11903” error during package deployment.
|
DEV-337034 |
In some cases, Vault does not prevent the deletion of standard document subtypes and classifications.
|
DEV-338670* |
In IE11™, navigating away from the Review and Select Steps and Deployment Confirmation pages when importing a VPK package results in an incorrect message from webpage.
|
DEV-340298* |
In some cases, Admins with sufficient privileges are unable to save User Permission Sets
|
DEV-341652* |
Using the Deployment Migration Tool for configuration migration may fail due to improperly addressed dependencies.
|
DEV-343015 |
In some scenarios, migrated viewable renditions do not properly attach to the correct documents.
|
DEV-343046 |
In certain cases, Admins can grant permissions to users that they do not have themselves.
|
DEV-345296 |
In some cases, audit logs do not export the entire selected range, showing “EXCEPTION” in the log.
|
DEV-345627 |
The Vault Config Report does not have information for the Permissionset component.
|
DEV-348273* |
Description |
Issue No. |
In certain scenarios, the Milestone autocomplete job completes Milestones before all EDL Items are complete.
|
DEV-319740 |
The Organization field is blank on Distribution Tasks transferred to Clinical Operations Vaults from SiteVault Vaults.
|
DEV-328522* |
In some cases, users with only Read permission on EDLs and EDL Items are able to drag and drop files into Expected Documents.
|
DEV-338335 |
Placeholders and other documents without content may prevent other documents of the same type from transferring
|
DEV-339594 |
Under certain conditions, the Plan Study workflow does not create Milestones from the Template Milestone Master Set.
|
DEV-340404 |
FTP loader files remain available after they expire, though they do not contain content.
|
DEV-341001 |
Simple TMF Transfer fails to transfer documents with accents and other non-English characters.
|
DEV-341457 |
Vault does not provide a notification that the Principal Investigator field for a corresponding site cannot be updated when users create Study Person records for archived Study Sites.
|
DEV-342262* |
In some cases, users cannot apply in-line edits to the Expected Documents section of a Milestone record.
|
DEV-342347 |
If object types are configured for the Study object and a user attempts to change the Study type, Vault displays an error if the Arm-Based Metrics? field is not populated.
|
DEV-342370 |
Users that do not have Read permission on the Model object are unable to use the TMF Viewer.
|
DEV-343584 |
Study Person records cannot be created when the Enable CDX checkbox is set
|
DEV-346168 |
If the Risk Score of a Study Risk is blank, Vault does not update or calculate Risk scores.
|
DEV-346544* |
Description |
Issue No. |
The error message displayed when a document file name exceeds the character or byte limit is incorrect.
|
DEV-265390 |
When performing a bulk action on documents as a delegated user, there may be discrepancies in the audit trail.
|
DEV-328654* |
If users do not have the annotate permission, @user mentions in video annotation don't pause the video at the timestamp.
|
DEV-334554* |
In some cases, renditions exported via Vault Loader to an FTP server are corrupted and cannot be opened
|
DEV-341724 |
Clicking Save to upload a document to a binder does not add it to the binder if there are picklist fields on the document that are required but disabled.
|
DEV-341864 |
In some cases, documents with permalinks are published with an incorrect zoom level.
|
DEV-341922* |
Suggested Links do not work if the link target is missing the Document Version field.
|
DEV-342309* |
Users without add/remove permissions for the EDL item object are able to make changes.
|
DEV-342529* |
In some cases, Export Annotations results in an error.
|
DEV-343467 |
During a Collaborative Authoring session, Vault does not properly display the dividing line on the Save to Vault and Check In button in the Doc Viewer.
|
DEV-343609* |
.DOTM files fail to render.
|
DEV-343867* |
Under certain conditions, checking in a collaboration document after editing it in Office Online™, the file's size is displayed as 0 KB and does not render.
|
DEV-345299 |
The Suggest Links button is not available on documents without automatic renditions.
|
DEV-346811 |
In some cases, page-level annotations are not brought forward.
|
DEV-347455* |
When “Dynamic ordering within Submissions Archive viewer” is on, exported submissions folder structures are incorrect.
|
DEV-348244* |
In some cases, image annotations are not brought forward.
|
DEV-348418* |
Description |
Issue No. |
In some cases, it is possible to assign an object workflow task to the same user multiple times.
|
DEV-317692 |
Users see a server error when attempting to open the timeline view if the history includes a workflow with a deleted system action.
|
DEV-321291* |
In some scenarios, users receive a server error after starting a multi-document workflow.
|
DEV-339595* |
If there is a Participant Control and an Object Field which both have the same public key (name), users may receive a workflow error which states that values for required fields are missing, even when all required fields have values.
|
DEV-339839 |
An error message may incorrectly display as blank when updating sharing settings in a workflow task to remove the Owner.
|
DEV-340332* |
Certain workflow configurations may result in a task failing to complete as expected.
|
DEV-340972* |
Task Verdict tokens may not correctly resolve if there are no users tasks after the notification step.
|
DEV-341959* |
Admins experience an error when trying to change the name of an object lifecycle state if the state has a Change related object lifecycle state entry action.
|
DEV-342380* |
Vault may fail to send a Task Verdict notifications if the notification template configuration causes the notification to be in excess of character limits. Postponed to later release.
|
DEV-342555* |
Deployment is blocked when the VPK contains certain components with incorrect component relationships.
|
DEV-344645* |
Description |
Issue No. |
Continuous inline editing may not work properly on related record lists.
|
DEV-339987* |
The More drop-down menu disappears when using zoom with IE11.
|
DEV-340997 |
When using Vault in Chrome, some fields are blocked by an autocomplete menu.
|
DEV-341132* |
In some scenarios, a document disappears from the binder tree view after performing a multi-document workflow.
|
DEV-341616 |
In certain cases, clicking on a related object may not correctly open the object details page.
|
DEV-341655 |
On the object record details page, sections with a carousel are not expanded by default.
|
DEV-341795* |
When a user reassigns a workflow task in a Vault with a high number of Pending users, all users in that domain experience slow performance.
|
DEV-342433* |
Mouse cursor disappears in the user selection area when starting a workflow in IE11.
|
DEV-342608 |
When correctly entering a password to verify an eSignature on Android devices, Vault may return an error that the user's keyboard is in the wrong language.
|
DEV-342901 |
Creating a new Checklist Design may result in a “Server having problems” error message.
|
DEV-343067 |
Picklist values may not display correctly near the bottom of the screen.
|
DEV-343462 |
The Vault Compare UI is misaligned when selecting a component in Safari.
|
DEV-343505* |
Downloading audit log CSVs can take a very long time.
|
DEV-344349 |
Users are unable to save checklists.
|
DEV-344458 |
Under certain conditions, it is possible to save a job definition without setting all required fields.
|
DEV-345330 |
In some scenarios, the File Size of a viewable rendition appears as 0.0 KB.
|
DEV-345455* |
When users create a new checklist version for a checklist design with a multi-select picklist field, the multiple values are not copied correctly to the new checklist version.
|
DEV-346501* |
Description |
Issue No. |
Under certain conditions, duplicate records may be created when the user clicks the Finish button multiple times in the Create Related Records wizard.
|
DEV-326130 |
When users attempt to import multiple non-eCTD folders to a submission using Vault File Manager, the first folder is imported instead of the entire import failing.
|
DEV-327936* |
Currency fields that were modified in the Manage Registered Details grid do not retain the new value when the users edit the field a second time.
|
DEV-331267* |
An error occurs when users attempt to create a binder from a content plan.
|
DEV-335531 |
Under certain conditions, the Manage Registered Details wizard does not display all of the required columns.
|
DEV-335629 |
When users start the Create Related Records wizard from an Impact Assessment Report, unnecessary hover text appears when users hover over some fields.
|
DEV-339214 |
When submissions are imported out of order, the Submissions Archive Harmonization job does not correct the lifecycle.
|
DEV-339980* |
When users lock or unlock a document version to a content plan item for a link target, continuous publishing does not up-version the source document.
|
DEV-340215* |
Correspondence folders remain in Submissions Archive binders after disabling the Show Correspondence in Viewer feature.
|
DEV-340564 |
When applying a filter in the Content Plan Hierarchy Viewer, if users click into the drop-down in the filter to see available values but don't select a value, and then attempt to filter on another column of the same type, the values from the drop-down in the first column appear.
|
DEV-340680* |
In some cases, importing a submission results in a server error after a successful import.
|
DEV-341121 |
Inline editing on a Content Plan may freeze the page, making other actions impossible.
|
DEV-341282* |
In some cases, when users generate an XEVMPD Product Report, Vault doesn't populate the Local Number field for the attachment Product Report Items when the XEVMPD attachment operation is Insert.
|
DEV-341325 |
Users experience slow performance when exporting a content plan.
|
DEV-341463* |
Users experience slow performance when publishing a Report Level Content Plan that contains documents with hyperlinks.
|
DEV-341651* |
After Report Level Content Plan publishing, permalinks from the published source document pointing to bookmarks navigate to the wrong place.
|
DEV-341689* |
When users run on-demand publishing on content plan items that are matched to link target documents, Vault does not publish the permalink.
|
DEV-341772* |
In some cases, when users apply the “Is blank” or “Is not blank” operators in dynamic filters in the Content Plan Hierarchy Viewer, no results appear in the grid.
|
DEV-341787* |
Users see an error when attempting to filter by Type or filter on the Global ID or Hierarchy Path fields in the Content Plan Hierarchy Viewer.
|
DEV-341788* |
When a Report Level Content Plan is published, Vault sets the owner of the published documents to System instead of the user who initiated the publishing action, and the user cannot see the documents.
|
DEV-341794* |
When the Primary Application and Primary Submission fields are blank on a Content Plan, Vault fails to publish links.
|
DEV-341872* |
After users drag and drop to match one document in the Content Plan Hierarchy Viewer, the orange highlight box does not appear around Content Plan Item records when users attempt to drag and drop a second document to match it.
|
DEV-341944* |
When a Submission-Ready Binder and the merged PDF move to the Final lifecycle state, Vault merges the published document again and up-versions the document, but the merged PDF remains in the Final lifecycle state.
|
DEV-342662 |
On-demand publishing jobs sometimes get stuck and don't complete for several hours.
|
DEV-342734* |
During publishing, Vault fails to report CH 1.4 Rule 16.3 correctly for some leaves.
|
DEV-342809* |
When a submission leaf points to a document in a prior submission and the new submission contains a duplicate document, Vault creates a placeholder for the new document instead of linking to the document in the original submission.
|
DEV-342915* |
In some Vaults, filters are not available on the Created By and Last Modified By columns in the Content Plan Hierarchy Viewer.
|
DEV-342991* |
When continuous publishing is enabled and a user adds a new Content Plan Item, Vault updates the XML but the new section does not appear in the Viewer.
|
DEV-345120* |
The Create Related Records “Next” button does not work in IE11.
|
DEV-345615 |
Users are not able to see the Submission Administrative Information when the content plan associated to the published submission is locked.
|
DEV-346444 |
When continuous publishing is enabled and users delete a Form Content Plan Item, Vault updates the XML to remove the leaf but does not update the binder.
|
DEV-346479* |
After a Report Level Content Plan has been published, if a user up-versions a matched document and runs publishing again, Vault creates a new published document in the Submission-Ready binder instead of up-versioning the original document.
|
DEV-346505* |
When bundling Regulatory Objectives within the same Application, Vault doesn't create the appropriate join records or send users a notification when bundling is complete.
|
DEV-347173 |
Vault fails to report Rule CA B46 correctly for some leaves.
|
DEV-348206* |
In some cases, Vault fails to create some Regulatory Objective records when users run the Create Related Records wizard.
|
DEV-349516 |
The Safety release, including all Platform fixed issues, is targeted for tentative availability on October 1, 2020.
Description |
Issue No. |
Fixed an issue where an E2B import would fail if the user input a non-numeric entry into a value field.
|
SAF-8043 |
Fixed an issue where device codes were not included with vaccine-type product constituents in the FDA MedWatch 3500A form.
|
SAF-9039* |
Fixed an issue where Vault would provide incorrect suggestion text in the awareness details section, and incorrect product and event type text for particular user profiles.
|
SAF-9148 |
Fixed an issue where no indication was displayed to users that a frequency value and unit must be entered before an AER can be created.
|
SAF-9205 |
Fixed an issue where the Product Section label displayed to a user with the baseline security profile was incorrect.
|
SAF-9301* |
Fixed an issue where Follow-Up Cases could not be created from the Potential Matches page if the original Case had both Reporter and Sender Case Contacts listed.
|
SAF-9419 |
Fixed an issue where the Country and Street Line 2 Reason Omitted fields were not enabled by default on the Facility object type.
|
SAF-9420 |
Fixed an issue where the Test Name (Reported) field on Case Test Result was labelled incorrectly.
|
SAF-9484 |
Fixed an issue where a Follow-Up Case could not be created upon upgrading MedDRA.
|
SAF-9503 |
Fixed an issue where after creating a Follow-Up Case from an initial Case in the Closed state, Case descendant objects did not transition to the Active state.
|
SAF-9589 |
Fixed an issue where the Reporter Language field was still enabled when the Reporter checkbox was unchecked in the Create Reporter Record page.
|
SAF-9736* |
Fixed an issue where case correspondence records failed to be created when 5 or more matching templates are used on a case.
|
SAF-9737* |
Fixed an issue where the Product Types were not displayed in alphabetical order.
|
SAF-9749* |
Fixed an issue where a server issue would occur when the user accessed an inbox item with a Transmission ID selected.
|
SAF-9794* |
Fixed an issue where an incorrect error message would display when running the Evaluating Reporting Obligations action with a Transmission profile that has an empty Format field.
|
SAF-9882 |
Fixed an issue where AERs could not be promoted to Cases when the AER Report Type was Study, the Study was double-blinded, and the Study Product was external (not in the product library).
|
SAF-9893 |
Fixed an issue where the Primary Phone field can still be selected under Contact #2 when Contact #1 is using the Primary Phone field.
|
SAF-9905* |
Fixed an issue where transmissions would not proceed past the Sending ICSR State.
|
SAF-10046 |
Fixed an issue where a Correspondence fails to be created when an invalid email format is used for the Primary Reporter.
|
SAF-10056* |
Fixed an issue where the "Unsaved data will be lost" message was displayed to users when there was no unsaved data.
|
SAF-10081* |
Fixed an issue where Inbound Transmissions received through AS2 Gateway failed to return an ACK to the sender.
|
SAF-10114 |
Fixed an issue where AERs created from an E2B import cannot be promoted to a case if the Auto-Follow-Up action has been run.
|
SAF-10171 |
Fixed an issue that prevented an AER promotion to a case that was accompanied by a "Record Null" error.
|
SAF-10188 |
Fixed an issue where the Organization, Department, and associated Reason Omitted fields were not disabled when the qualification was set to patient on the Contact record.
|
SAF-10204 |
Fixed an issue where Parent Gender was not being exported in Masked E2B (R3) files.
|
SAF-10272 |
Fixed an issue with central MedDRA where non-primary SOC terms were not updated when the central dictionary was updated to a new version.
|
SAF-10293* |
Fixed an issue where the Reporter checkbox was not enabled upon case intake.
|
SAF-10461 |
Fixed an issue where the file name was being populated in an incorrect format when auto-generating E2B (R2), (R3), and FDA E2B (R2) files through a Transmission.
|
SAF-10472 |
Fixed an issue where the FDA MedWatch 3500A form had an invalid expiration date at the top of the form.
|
SAF-10477 |
Fixed an issue where E2B exports from a Transmission record did not consider the Expedited field on the Transmission record when populating the Does This Case Fulfill the Local Criteria for an Expedited Report? data element.
|
SAF-10480 |
Fixed an issue where Follow-Up Cases could not be created if the Case contained a Facility-type Case Contact that was selected in the Administration Facility field on the Case Product Dosage.
|
SAF-10548 |
Fixed an issue where reporter first and last names defaulted to Not_Provided on emails when the corresponding fields are blank.
|
SAF-10553* |
Fixed an issue where a warning about the Dose Form value being truncated was appearing when generating E2B (R3), EMA E2B (R3), and FDA VAERS E2B (R3) files.
|
SAF-10578 |
Fixed an issue where, if Dosage Frequency was not entered, a warning about a non-standard frequency being entered was appearing when generating E2B (R2) files.
|
SAF-10585 |
Description |
Issue No. |
The Library supported document filter may clear when adding additional filters.
|
DEV-321580 |
Vault returns unexpected results for saved views that contain filters using quotation marks on the Document Number field.
|
DEV-341105* |
Vault returns unexpected results for document searches that include search modifiers on text fields.
|
DEV-341227 |
Exporting the Object Grid View after searching for a term results in blank long-text values.
|
DEV-341327 |
When a user edits the columns in a saved view in a tab, Vault does not preserve the changes.
|
DEV-341476 |
In advanced searches using the ‘Include content' option with many results, there may be a long delay when clicking the ‘5000+' link to display the total result count.
|
DEV-341578 |
In some cases, Vault fails to return search results for lookup values with leading zeros when a user enters only the trailing non-zero numbers.
|
DEV-341678 |
Searching for ID patterns returns more results than expected.
|
DEV-341685 |
Users experience a server error when filtering for Pending users from the Lifecycle State facet of the Vault Users page.
|
DEV-342588 |
When performing an Advanced Search for documents which includes content, Vault does not inform users when the number of results exceeds the 5000 document limit.
|
DEV-342755 |
When a user opens Advanced Search from a custom view, Vault does not populate search fields with saved view criteria unless the user first modifies the view.
|
DEV-342939 |
Advanced Searches for an archived document by document number result in a “No items found” message instead of suggestions for matching document numbers.
|
DEV-343154 |
When searching from an object reference field's faceted field filter in the library tab, Vault may exclude some results if the object has more than 100 records containing similar search terms.
|
DEV-344028 |
In some cases, when a user opens a saved view and advances past the first page of results, Vault displays incorrect total counts of documents and pages.
|
DEV-346512 |
When performing an All Documents search in Japanese, Vault is unable to find results for keywords unless「」is included.
|
DEV-347845 |