Description |
Issue No. |
In some cases, Vault may fail to export annotations for PDF files with unused images.
|
DEV-288036* |
In rare cases, documents utilizing Merge Fields may not correctly merge upon initial rendering and may require a field update to correct the rendition.
|
DEV-271258* |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-273220 |
Vault fails to render Microsoft Word™ document.
|
DEV-283034 |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-249731 |
Vault fails to render Microsoft Word™ document.
|
DEV-283941 |
Microsoft Word™ document rendition contains formatting issues.
|
DEV-291210 |
In some cases, Microsoft PowerPoint documents contain formatting issues.
|
DEV-258850 |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-304060 |
Vault fails to render Microsoft Word™ document.
|
DEV-272760 |
Vault fails to render Microsoft Word™ document.
|
DEV-259871 |
Vault fails to render Microsoft Word™ document.
|
DEV-295619 |
Microsoft Word™ document rendition contains formatting issues.
|
DEV-308141 |
Vault fails to render Microsoft Word™ document.
|
DEV-259218 |
Vault fails to render Microsoft Word™ document.
|
DEV-241996 |
Vault fails to render Microsoft Word™ document.
|
DEV-306255 |
Vault fails to render Microsoft Word™ document.
|
DEV-294526 |
Vault fails to render Microsoft Word™ document.
|
DEV-263397 |
Vault fails to render Microsoft Word™ document.
|
DEV-260187 |
Vault fails to render Microsoft Word™ document.
|
DEV-260909 |
Vault fails to render Microsoft Word™ document.
|
DEV-259514 |
Vault fails to render Microsoft Word™ document.
|
DEV-275583 |
In some cases, Microsoft PowerPoint documents contain formatting issues.
|
DEV-306295 |
Vault fails to render Microsoft Word™ document.
|
DEV-308939 |
Vault fails to render Microsoft Word™ document.
|
DEV-235058 |
Vault fails to render Microsoft Word™ document.
|
DEV-307291 |
Microsoft Word™ document rendition contains formatting issues.
|
DEV-276875 |
Vault fails to render Microsoft Word™ document.
|
DEV-288422 |
When viewing a document in the mini browser window, the note position and filter options are not functional.
|
DEV-308487* |
Vault does not show a warning when a user removes the last reference from an Approved Claim.
|
DEV-308145* |
Make a Copy may fail if the document contains annotations with replies. It may also misplace annotations and not copy annotation tags if the document contains area annotations. Re-rendering documents, or merging fields, may drop annotations until the document is re-rendered again if the document contains annotations with replies.
|
DEV-314262* |
When comparing certain documents, users are seeing more changes reported than expected.
|
DEV-306950, DEV-312338 |
When a video is over 1 hour long, users cannot add a time-stamped comment beyond the 1-hour point.
|
DEV-312394 |
When running an Import Annotations action, the process continued running without showing that it completed. After refreshing the document, users found that Vault had imported the annotations multiple times.
|
DEV-310722 |
When adding references to a claim, users see an error message if they select anchors with over 128 characters in the title.
|
DEV-313771 |
When using the Import Document Links document action, users see a blank screen while Vault loads the data. Users will now see a spinning icon to indicate the action in progress.
|
DEV-308633* |
When using the Bring Forward Annotations action, Vault does not bring forward link annotations if the user does not have access to view the linked documents.
|
DEV-307079 |
When selecting anchors for a link annotation, Vault does not correctly show a red minus icon on already-selected anchors if the target document has over three anchors.
|
DEV-310686* |
In some cases, users see a server error when they attempt to update document fields.
|
DEV-313406 |
An error may occur if Vault is restarted while a bulk document rendition process is running.
|
DEV-301532* |
Microsoft Word™ document rendition contains formatting issues.
|
DEV-272909 |
Vault fails to render Microsoft Word™ document.
|
DEV-284817 |
In some cases, Microsoft PowerPoint™ documents contain formatting issues.
|
DEV-280907 |
Vault fails to render Microsoft Word™ document.
|
DEV-274322 |
Vault fails to render Microsoft Word™ document.
|
DEV-308239 |
Vault fails to render Microsoft Word™ document.
|
DEV-303835 |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-260260* |
Vault fails to render Microsoft Word™ document.
|
DEV-233227 |
When exporting more than 100 documents where there are duplicate documents, the export summary may contain duplicate entries.
|
DEV-308440 |
In some scenarios, putting a document into steady state with a Template Document Type configured does not create a Controlled Document Template for that document.
|
DEV-303602 |
In rare cases, a valid document does not appear in the Library but can be accessed directly through the document URL.
|
DEV-289119 |
Audit-trail export failures during a Binder Bulk Export or Document Bulk Export may result in an unexpected error.
|
DEV-301148 |
When creating a document from a placeholder, automated language changes based on the document language do not show up in the audit trail.
|
DEV-304095 |
In some cases, users cannot download upload files larger than 4GB via FTP as Large Size Assets.
|
DEV-313015 |
Under certain conditions, the Document Relationship Type may be incorrect when performing a comparison.
|
DEV-235588 |
Users with the Edit Relationship permission on the Doc Info page can see the expand icon for the Renditions section.
|
DEV-302512 |
Uploading an attachment with long filenames that include non-English characters may result in a “server having problems” error.
|
DEV-306084 |
Using Collaborative Authoring to check out and then check in the same document may result in an “Unable to check in from Microsoft Office” error due to a permissions issue with Microsoft servers.
|
DEV-302506 |
Under certain conditions, making a copy of a previously copied document may fail and redirect the user to the original document.
|
DEV-310861 |
When editing a Binder in the List View, attempting to perform actions after deleting a newly created sibling section results in a server error.
|
DEV-313712 |
Vault fails to send a notification after a Large Size Asset rendition has been uploaded.
|
DEV-297366 |
Deleting a document version also deletes the document template even when the document version is unrelated to the template.
|
DEV-312025 |
When viewing the Doc Info page, an old Template Document Type may show in the UI even after the Template Document Type has been updated.
|
DEV-306749 |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-246844 |
Microsoft Word™ document rendition contains formatting issues.
|
DEV-276746 |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-260841 |
Vault fails to render Microsoft Word™ document.
|
DEV-253458 |
Vault fails to render Microsoft Word™ document.
|
DEV-251131 |
Fonts fail to render as expected in a Microsoft Word™ document.
|
DEV-290446 |
Microsoft Word™ document rendition contains formatting issues.
|
DEV-303848 |
Vault fails to render Microsoft Word™ document.
|
DEV-301100 |
Vault fails to render Microsoft Word™ document.
|
DEV-240914 |
Vault fails to render Microsoft Word™ document.
|
DEV-279117 |
In some cases, adding a product to a binder results in an error.
|
DEV-313393 |
Vault fails to render Microsoft Word™ document.
|
DEV-312185 |
Source documents are re-rendered when a viewable rendition is manually uploaded.
|
DEV-305860* |
When rendered with advanced overlays, links within documents are inactive in downloaded viewable renditions.
|
DEV-302018 |
In some cases, eSignature pages are not correctly applied to viewable renditions.
|
DEV-297441 |
In some cases, applying an overlay to a document with fillable fields may remove the values of said fields.
|
DEV-290381 |
Description |
Issue No. |
In the Manage Registered Details wizard, users are unable to double click the Lifecycle State field in the grid to open the Update Fields dialog for some Registered Details records.
|
DEV-303151* |
If an Admin has modified the Lifecycle State field label, Vault doesn't show the updated label in the Update Fields dialog within the Manage Registered Details wizard.
|
DEV-309632 |
In some cases, users can't create Regulatory Objective or Submission records in the Create Related Records wizard because filters in the wizard conflict with custom Criteria VQL on certain fields.
|
DEV-309036 |
In the Manage Registered Details Wizard, users see an error when they click the Update Fields button if records are selected but the Country row is collapsed.
|
DEV-307399* |
Users without the Read permission on the Event Regulatory Objective object see an Errors Encountered result when they attempt to create Regulatory Objective records via the Create Related Records wizard.
|
DEV-309811* |
When users filter by a Matched Document field in the new Content Plan Hierarchy Viewer, the icon for the matched document's Content Plan Item record in the name column appears collapsed instead of expanded.
|
DEV-306234* |
After continuous publishing or the Manage Submission Administrative Information job, Vault incorrectly changes the STF_Info on an Australian Submission from Informational to Fail.
|
DEV-303427* |
When a user deletes the root Content Plan record in the Content Plan Hierarchy Grid Viewer, Vault does not return the user to the related Submission record or Report Level Content Plan record.
|
DEV-310617* |
After a user removes a matched document from the Content Plan Item record detail page, it still appears in the Content Plan Hierarchy Viewer when users expand the parent Content Plan record until the page is refreshed.
|
DEV-301121* |
Vault doesn't update the binder structure correctly when a user sets an STF XML Content Plan Item record to Inactive.
|
DEV-275240* |
In the Submission Administrative Information viewer, Vault should display excluded values at the bottom of the screen.
|
DEV-274059* |
When a published CH submission has a Submission Country join record, the Agency and Article 13 TPA fields appear blank in the XML and in the Submission Administrative Information viewer.
|
DEV-303623* |
In some cases, Vault doesn't export files when users perform bulk submission exports.
|
DEV-308089* |
In some cases, users experience slower than usual performance when exporting large Content Plans.
|
DEV-261984* |
Users experience slow performance when importing submissions in bulk.
|
DEV-308645* |
Vault does not include all forms when a user exports a grouped US submission.
|
DEV-310750 |
In some cases, users experience slow performance when creating a Content Plan.
|
DEV-307723* |
The Job Status for the Submissions Archive Bulk Export job shows as Running when the job has completed with an error.
|
DEV-302156* |
Users receive an error when attempting to import a submission to a Submission record that has a blank required custom field.
|
DEV-299286* |
After initially failing during validation, Vault deletes some Submission Validation Result records rather than updating them to the Pass status when validation runs again.
|
DEV-311952* |
Users experience slow performance when filtering on Matched Document fields in the new Content Plan Hierarchy Viewer.
|
DEV-303754* |
In some cases, Vault reports an error when users import a submission via the FTP.
|
DEV-309439 |
When copying a content plan, Vault fails to create a Content Plan Item record if it was excluded under an inactive parent Content Plan record in the source Content Plan.
|
DEV-309287* |
Report level publishing fails with a “No target document found for this permalink” error when a document link points to two different target documents.
|
DEV-303994* |
When the “Show eCTD Metadata Mapping to users on submission import” setting is not enabled on the Application Settings page, Vault does not display the submission mapping page when users import a grouped submission.
|
DEV-306706* |
In some cases, the Create Content Plan action may not create all of the expected Content Plan Items on all Content Plans.
|
DEV-190723* |
Users see an error when they open and expand the Dossier Review Panel from the Submissions Archive Viewer.
|
DEV-303752 |
The “Show eCTD Metadata Mapping to users on submission import” enablement checkbox does not appear on the Admin > Settings > Application Settings page.
|
DEV-311028 |
Some users experience slow performance when bundling regulatory objectives.
|
DEV-302695 |
The Summary page in the Manage Registered Details wizard appears blank when users select Registration records with no selected records in the Product Variant or Product fields.
|
DEV-309362* |
In the Manage Registered Details wizard, users cannot create Registered Drug Product join records for a Registration that has related complex drug products and simple drug products.
|
DEV-301395* |
When generating a product report, users receive an error for the Presentation Name Element if Language Codes are not capitalized.
|
DEV-303390 |
Vault fails to report EU rule 16.BP10 when the PDF contains JavaScript in a bookmark or hyperlink.
|
DEV-262038* |
Users with the Read permission on the Submission Metadata object cannot add a filter in the Submissions Archive Viewer.
|
DEV-304140* |
When users publish a submission, Vault includes inactive Submission Country records in the Submission Administrative Information envelope.
|
DEV-305885* |
Vault fails to import a subsequent submission when documents have the same href attribute but different checksums across the submission.
|
DEV-306973* |
When users update the Continuous Publishing field from “No” to “Yes” for the Index.xml Content Plan Item on a published submission, continuous publishing fails to publish the Index.
|
DEV-267467* |
Users experience slow performance when they click Expand All in the Submissions Archive Viewer.
|
DEV-303399 |
Vault fails display applied filter values under the header in the Submissions Archive Viewer when users select a single filter value.
|
DEV-303695* |
Vault includes an unnecessary warning after users import a submission that contains a document that already exists in Vault.
|
DEV-302948 |
When users set the Continuous Publishing field to “No”, Vault incorrectly runs the continuous validation job.
|
DEV-307559* |
Vault doesn't set the name of the root Content Plan record correctly if a user selects the Create Content Plan action or the Copy Content Plan action and content plan creation fails.
|
DEV-261886* |
Vault doesn't report rule CA F09 as Fail if a user updates the Sequence Description to a different letter case in the Submission Administrative Information viewer.
|
DEV-305989* |
The Safety release, including all Platform fixed issues, is targeted for tentative availability on May 12, 2020.
Description |
Issue No. |
Fixed an issue where the combined MedDRA control could not be created or updated in the Case Product Indication Section Control.
|
SAF-5079* |
Fixed an issue that was causing a “ProtectedRollbackException” error when promoting an AER to a Follow-Up Case.
|
SAF-5444* |
Fixed an issue where the Delete overlay was misplaced after selecting the MedDRA Auto-code button.
|
SAF-5474 |
Fixed an issue where Follow-Up Cases promoted from a non-E2B AER did not have the Case Number populated.
|
SAF-5501* |
Fixed an issue where a "Product record not found" error appeared when promoting an E2B AER with a high number of Case Products with dosages.
|
SAF-5526* |
Fixed an issue where the Age at Onset field was not being recalculated correctly on Cases imported from an E2B file with multiple Case Adverse Event records.
|
SAF-5632 |
Fixed an issue where the “Transmission Profile already exists” error was displaying incorrectly.
|
SAF-5662 |
Fixed an issue where users could create duplicate Cases by clicking “Back to the previous page" after promoting an AER to a Case.
|
SAF-5781 |
Fixed an issue where the Case Expedited field was being populated when the Event MedDRA was on the DME watchlist and the Product Registration Agency was FDA.
|
SAF-5802 & SAF-5795 |
Fixed an issue where, when an AER was promoted to Case with an empty Seriousness field, the Expectedness field on the resulting field is set to Yes when there were no preconfigured Product Datasheets.
|
SAF-5834 |
Fixed an issue where the value from the Event (Reported) - English field was not populated in section 7+13 of the CIOMS I form.
|
SAF-5871 |
Fixed an issue where users were unable to open links to documents or Cases from vault notifications.
|
SAF-5874 |
Fixed an issue where the Expected (expectedness) fields on Follow-Up Cases did not match the field values from the initial Case.
|
SAF-6096 |
Fixed an issue where after you manually changed the auto-calculated Expected field to set the value to Yes (Overriden), the system updated the Expedited field to No instead of leaving the Expedited field as-is.
|
SAF-6123 |
Fixed an issue where you could not create a Follow-Up Case from a Case containing multiple Case Product or Case Adverse Event records with identical names.
|
SAF-6157 |
Fixed an issue where the system was not automatically calculating the Latency field on Case Assessment records after a Case was created from an imported E2B file.
|
SAF-6374 |