The issues listed below are fixed in the 20R1 release.
| Description |
Issue No. |
|
In some cases, Admins experience an error when entering Microsoft user email credentials in a case-insensitive manner in Admin > Settings > Checkout Settings.
|
DEV-300942 |
|
Users are able to delete a Checklist Type with a target object lifecycle state containing a reference to a Start Checklist action.
|
DEV-300697 |
|
Under certain conditions, long filter criteria may be truncated in the UI for a configuration migration dataset.
|
DEV-299983 |
|
System Audit History does not track deletion of a document message or object message if the message is not in use.
|
DEV-298546 |
|
Exporting the full audit trail may time out prior to export completion.
|
DEV-297052 |
|
Because timestamps in filenames are generated using a 12 hour clock instead of a 24 hour clock, in rare cases, Vault Loader jobs generate output files with duplicate names.
|
DEV-294454 |
|
In some instances, when a user is on the Assigned Study Sites tab of a user account, they are unable to return to the user list by clicking the "Users" breadcrumb link.
|
DEV-293267 |
|
When creating a Configuration Migration package which includes the User object, the default Key Field is chosen alphabetically. With this fix, the Key Field is chosen based on the most relevant fields.
|
DEV-292697 |
|
Admins are unable to clear the "Allow selection in configuration" setting on a user group. The error message indicates the group is used in a configuration, but the User Role Setup records that reference the group have been deleted.
|
DEV-291973 |
|
If a referenced external ID contains quotes, Vault Loader may generate a CSV file with additional double-quotes around the value.
|
DEV-290193 |
|
Some vaults may not correctly display the 'Allow creation of links to whole documents' Admin setting.
|
DEV-288123 |
|
In rare cases, updating a permission set may incorrectly remove permissions.
|
DEV-287290 |
|
Users with the Power Delete permission cannot delete a document on a Lifted Legal Hold through the UI.
|
DEV-280173 |
|
Users receive an error when downloading an exported checklist design with a forward slash “/” or backslash “\” in the Checklist Design Name field (checklist_design_sys.name__v).
|
DEV-278054 |
|
Entry actions that populate a field using a formula add extra spaces to new lines.
|
DEV-270647 |
|
Under certain circumstances, Vault Compare cannot identify differences in document type groups when comparing document types.
|
DEV-270379 |
|
Occasionally, users see a server error when creating a cross-domain user.
|
DEV-303812 |
|
On vaults that have exceeded their allowed sandbox entitlements (usually because of expired temporary entitlements) users cannot refresh pre-release or other sandboxes.
|
DEV-305890 |
|
Vault cannot deactivate User Exception Messages when the number of child records exceeds 1500.
|
DEV-302487, DEV-305736 |
|
In Admin > Settings > Domain Settings, the "see override settings" link appears with the Authentication API limits, even if no override rules exist.
|
DEV-307582 |
|
In some cases, when a user edits a dataset in a Configuration Migration package, Vault does not preserve Record Migration Mode settings for that data object.
|
DEV-303700 |
|
In some cases, Vault allows users to save datasets in Test Data type outbound packages that contain invalid reference lookup fields, which causes exporting the package to fail.
|
DEV-303438 |
|
In some scenarios, clicking into a Job Definition results in a "Server having problems" error.
|
DEV-303093 |
|
For certain Job Definition configurations, Vault displays duplicate document relationship types in the Relationship Types drop-down.
|
DEV-303071 |
|
In some scenarios, the object audit trail may show entries out of order despite a correct timestamp.
|
DEV-299029 |
|
After disabling multilingual document handling and multilingual labels settings, the "localized_language__sys" still appears on the user detail page.
|
DEV-303581 |
|
When a customer has exceeded their sandbox entitlements, they are not allowed to refresh.
|
DEV-305903 |
| Description |
Issue No. |
|
The error message that shows when the Create Binders user action fails is not helpful to users.
|
DEV-303034 |
|
Vault is no longer automatically populating Expected Visits and Expected Visits Not Planned fields for CTMS.
|
DEV-302062 |
|
In some cases, users see an unexpected error when loading Quality Issue records.
|
DEV-301669 |
|
Viewing a Milestone Record that includes an inactive document field in the layout may result in a server error.
|
DEV-300885 |
|
With a specific sequence of steps to upload an unclassified document, Vault incorrectly shows an error indicating that a Study has not been selected.
|
DEV-300432 |
|
When a user exports multiple versions of a document and its attachments, Vault exports all attachments into a single folder instead of placing each attachment into a version-specific folder.
|
DEV-300349 |
|
When saving a Study Product record without filling out the required Study and Product fields, Vault displays a server error instead of indicating required fields.
|
DEV-299488 |
|
If the Product document field uses field-level security for "read-only", Vault does not auto-populate it based on Study values during the Classify action.
|
DEV-299186 |
|
When selecting a user to reassign a workflow task for a Quality Issue record, Vault includes users who are not allowed because of object reference constraints. The user reassigning a task then sees an error message when attempting to save.
|
DEV-298606 |
|
Users cannot upload source files to placeholder documents without Edit Fields permission. This action should only require Edit Document permission.
|
DEV-298121 |
|
While creating arm-specific Metrics Over Time, the system fails to create arm-specific Metrics at the Study Country and Study levels.
|
DEV-297936 |
|
Updates to the Timeliness document field value, the CDX ID document field, and Study field updates as a result of the Streamlined Document Reuse feature in the create new document version context are not audited.
|
DEV-297925 |
|
Error message uses the wrong label value for an object field where the label has been modified.
|
DEV-294938 |
|
Some users see the error message, "Product not valid for specific study" when they attempt to complete a workflow on documents related to two or more products or studies.
|
DEV-294476 |
|
In certain situations, Milestone Completeness is not updating to 100% when it should.
|
DEV-292532 |
|
In cases where users have a picklist used for creation of a Confirmation Letter, users experience a server error.
|
DEV-291485 |
|
When a milestone job fails, some users don't see an error message explaining the failure, just a general message.
|
DEV-291024 |
|
In some cases, Admins experience a network error when attempting to edit page layout configuration for the Study object.
|
DEV-289546 |
|
After upgrade, some CRO users may not be able to view sites in Clinical environments.
|
DEV-288091 |
|
When some users complete an Multi-site Document Distribution task, the task is not set to Completed status.
|
DEV-287452 |
|
Some users see a server error when they try to update the Study Team Role field and set Grant Access to Related Records on a study person record in the same update.
|
DEV-287275 |
|
When some users attempt to update study person records, they see an error message for the first few records and then the update fails.
|
DEV-285292 |
|
When navigating from Tasks Requiring Attention to the list of tasks and then back, Vault displays the widget for a second before reloading it so that it appears to load twice.
|
DEV-284226 |
|
When a user uploads a document and selects Classify documents later, Vault does not carry over Study, Study Country, and Study Site values that users enter on the Upload Files step to the Doc Info page.
|
DEV-283843 |
|
Users are able to create duplicate Study Team Assignment records.
|
DEV-283815 |
|
In certain cases, the crosslink version is being set incorrectly
|
DEV-305690, DEV-305922 |
|
The trigger on Study Team Role is allowing edits to fields that should be uneditable when the Study Team Role is in use by a User Role Setup record.
|
DEV-303164 |
|
Vault does not auto-populate the Create Content field to indicate Blinded/Unblinded/Blank.
|
DEV-306180 |
|
Vault does not display values for the File Name field in the TMF Viewer.
|
DEV-303996 |
|
Users can't see inactive document types within the TMF Viewer.
|
DEV-282599 |
|
Streamlined Document Defaulting can run when Document Migration Mode is on. Defaulting should be skipped when a vault is in Migration Mode.
|
DEV-303536 |
|
In certain cases, users cannot complete the "Resolve Study" step when accepting a Clinical Network Agreement using the new Agreement Wizard.
|
DEV-304704 |
|
If the Product document field is read-only, Vault clears any value when users classify a document.
|
DEV-304762 |
| Description |
Issue No. |
|
For specific PDF files, MD5 checksum values in Vault do not match checksum values for the downloaded files.
|
DEV-302828 |
|
In rare cases, large documents may appear to correctly render and then display an error message.
|
DEV-301082 |
|
A document created from a controlled template is displaying the incorrect rendition.
|
DEV-300403 |
|
When users try to check in or cancel checkout on a document via Collaborative Authoring, they see a 404 error.
|
DEV-298361 |
|
Some users are initially unable to see some annotation replies.
|
DEV-297180 |
|
Clicking a link to another document in the document viewer takes users to the bottom of the specified document page instead of the top.
|
DEV-297093 |
|
Users cannot check out documents with Collaborative Authoring which contain a tab or newline in the document name.
|
DEV-296628 |
|
In some cases, non-text shapes in uploaded files may not render as expected.
|
DEV-296219 |
|
When some users navigate to the Doc Info page from a custom tab view with a filter, the menu in the top right doesn't use the same search filters as the custom view.
|
DEV-295693 |
|
The Undo Last Import confirmation pop-up contains a misspelled word.
|
DEV-295555 |
|
In some cases, XFA forms with dynamic content may fail to render.
|
DEV-295291 |
|
In some cases, Chinese characters may not render as expected.
|
DEV-294242 |
|
In rare cases, Vault may not correctly render signature pages for very large documents.
|
DEV-294041 |
|
In some instances, large PDF documents appear blank in the document viewer.
|
DEV-293572 |
|
Certain Chinese fonts may not render as expected.
|
DEV-293265 |
|
Sandbox refreshes fail intermittently for some users.
|
DEV-293022 |
|
Link URLs ending in colons in uploaded PDF files may not be recognized as valid links.
|
DEV-292507 |
|
In some cases, XFA forms produced with Adobe Experience Designer fail to render.
|
DEV-292135 |
|
Certain configurations in uploaded MS Word files utilizing Merge Fields may cause the rendition to fail.
|
DEV-291877 |
|
Some users see an "unable to retrieve security tokens error message" when they attempt to use collaborative authoring 90 days after configuring it.
|
DEV-291323 |
|
The results of the Create Presentation action may incorrectly include speaker notes.
|
DEV-291216 |
|
Some Submission Archive links may not function correctly when viewed in Vault.
|
DEV-291205 |
|
Certain page size configurations may result in signature pages being incorrectly cut off when the PDF rendition is downloaded.
|
DEV-291020 |
|
When some users click a link to a rotated page in the RIM Submissions Archive, the link takes them to the bottom of the page instead of the top.
|
DEV-290243 |
|
Some users are unable to change the lifecycle of some document types if the lifecycle is associated with field dependencies.
|
DEV-290090 |
|
Certain table of contents configurations in uploaded MS Word files utilizing Merge Fields may cause the rendition to fail.
|
DEV-289250 |
|
When some users make changes to Engage content in Vault, the changes are not reflected in Engage.
|
DEV-289246 |
|
Some users see an error message when they attempt to update a template file.
|
DEV-288432 |
|
For some users, document renditions are taking longer than expected to load.
|
DEV-288398 |
|
In some instances, when a user has their sandbox and production environments located on two different PODs, they will see an error message when they attempt an FTP link.
|
DEV-288178 |
|
For some users, the document viewer is loading more slowly than expected.
|
DEV-288065 |
|
When creating a document from template with Vault cloning, the cloned rendition and source file may not process properly, resulting in data corruption.
|
DEV-287876 |
|
In some vaults, users see rendition errors. Note that this issue is limited to specific vaults.
|
DEV-287692 |
|
Users cannot update documents created by batch creation API. Note that this issue is limited to specific vaults.
|
DEV-286577 |
|
In some cases, MS Word files with Track Changes enabled fail to render.
|
DEV-284778 |
|
In some cases, when uploading an Excel file as a new version, Merge Fields in sheets after the first sheet are not updated.
|
DEV-283953 |
|
In some cases, Indesign files with two-page spread layouts may incorrectly render as individual pages.
|
DEV-283013 |
|
When performing checkout through Collaborative Authoring, it's possible the file name of a OneDrive document exactly matches the file name of a previously checked out document version. This issue occurs when a user checks out with Collaborative Authoring, cancels the checkout, and then checks out again after the file has been deleted.
|
DEV-280388 |
|
Users see a timeout error when uploading a 12.5GB Large Size Asset file via FTP.
|
DEV-278617 |
|
Vault may display an Export Failed error message when attempting to export annotations.
|
DEV-277456 |
|
In vaults where specific annotation note colors are assigned to document roles, switching between annotation styles (strikethrough, highlight, etc.) sets the note to the wrong color.
|
DEV-277363 |
|
Users see issues loading Large Size Asset files via FTP. Audit logs show the same file being loaded and removed multiple times for a single attempt.
|
DEV-276248 |
|
Users cannot remove an annotation comment. Refreshing causes the removed comment to reappear.
|
DEV-276222 |
|
When playing a video file, there is no sound. Note that this issue was limited to specific video files.
|
DEV-274317 |
|
In some cases, adding a Document Field Dependency in a custom document lifecycle may incorrectly result in a blank screen.
|
DEV-273043 |
|
Some security settings configurations may incorrectly disallow the Re-render Document action.
|
DEV-272485 |
|
In certain cases, the modified source file does not correctly retain MS Word "Content Control" settings in documents utilizing Merge Fields in tables.
|
DEV-266641 |
|
CrossLinks which reference a missing document produce a Document Not Found error. With this fix, documents which were deleted no longer produce an error and instead the field is blank. Documents which appeared to be missing because they are in an inactive vault now appear normally.
|
DEV-172988 |
|
In rare cases, when searching using the Find in Document feature, Vault may fail to find some instances of a word.
|
DEV-167358 |
|
The Performance Statistics metric "Total Docs Checked Out with Office" does not track document checkout in the same way as document filters. Performance Statistics lists total checkouts, including documents that have since been checked in. Performance Statistics tracking should match filters.
|
DEV-304464 |
|
In some cases, image files uploaded via bulk API may render partially or fail to render.
|
DEV-303375 |
|
Users can start workflows on documents currently checked out to Microsoft Office 365.
|
DEV-303073 |
|
The "Copy to Another Vault" action can fail due to differing configurations for lifecycle stage between the two vaults.
|
DEV-294227 |
|
For some documents with large source document files, Vault does not display bookmarks in the document viewer.
|
DEV-306864 |
|
When a user downloads a document using the Download PDF with Annotations action, text annotations in right-to-left languages are displayed backwards.
|
DEV-303599 |
|
Switching between Annotate mode and View mode causes suggested links to disappear in Annotate mode.
|
DEV-306320 |
|
For certain standard document fields such as Description, updating the field value from a workflow dialog does not actually update the field value.
|
DEV-307493 |
| Description |
Issue No. |
|
Users experience slow performance when saving updates to object lifecycle state entry actions, entry criteria, and user actions, as well as when loading the object lifecycle state detail page.
|
DEV-300274 |
|
Users experience a server error when attempting to view document lifecycle state entry criteria.
|
DEV-299311 |
|
When an lifecycle does not include the "Set previous steady-state to superseded" entry action, state changes are not properly represented in the document timeline view.
|
DEV-297450 |
|
In some configurations, the Delete Minor Versions entry action does not properly delete versions.
|
DEV-295184 |
|
In some instances, users with read only permissions cannot be assigned a Read & Understood workflow task as part of a group.
|
DEV-295031 |
|
Some users see an "internal error" message when they attempt to approve and complete an assigned workflow task.
|
DEV-293671 |
|
In some instances, the Actions menu on a multi-document workflow task doesn't work for the task owner.
|
DEV-293008 |
|
When some users start an object workflow, the user selection page loads very slowly if the list of users is long.
|
DEV-292057 |
|
When users cancel a workflow, the task cancellation dates sometimes appear to precede the workflow cancellation date.
|
DEV-291917 |
|
For some users, Vault sends email notifications with blank fields.
|
DEV-291661 |
|
For some users, the "Prompt for verdict only on documents of document type" picklist in any lifecycle multi-document workflow tasks only displays up to 100 document types.
|
DEV-290361 |
|
Some users are unable to cancel a workflow after the workflow initiator's user profile has been deactivated because the Action menu icon disappears from the workflow.
|
DEV-288511 |
|
In some instances, workflows are not documenting the correct document version in the audit trails.
|
DEV-288213 |
|
In situations where multiple users are simultaneously completing an object workflow task, users sometimes see a server error.
|
DEV-287815 |
|
In some cases, Admins see a Page Not Found error when they create a new document workflow, add a new step, and select the "Edit step details on save" checkbox.
|
DEV-286747 |
|
Some users are able to delete a document version that is in an active multi-document workflow.
|
DEV-285453 |
|
Some users see no results listed in the Recent Multi-Document Workflows view.
|
DEV-285186 |
|
In situations where multiple users are simultaneously completing a document workflow task, users sometimes see a server error.
|
DEV-270975 |
|
In situations where multiple users are simultaneously completing a multi-document workflow task, Vault sometimes fails to assign the subsequent task.
|
DEV-270458 |
|
In situations where multiple users are simultaneously completing the same Read & Understood task, users sometimes see a server error.
|
DEV-268833 |
|
When some users attempt to complete a workflow task with a required verdict without selecting a verdict, the error message informing them that the field is required does not appear.
|
DEV-255284 |
| Description |
Issue No. |
|
Some field labels and buttons on record detail pages may not display as expected for users using Internet Explorer 11.
|
DEV-302036 |
|
Text and Long Text field values that wrap over multiple lines may be cut off without an indication that there is cut-off text.
|
DEV-299869 |
|
Vault does not show a custom document field named comment__v in the UI because it matches the naming convention used to display icons.
|
DEV-299719 |
|
The Lifecycle Stages Chevron does not highlight the correct stage.
|
DEV-299094 |
|
In some cases, field values that are too long for the field display area may be cut off with part of the field value hidden.
|
DEV-297461 |
|
If the Enable User Object Reference Link is disabled, the displayed user name in user the Last Modified By and Created By fields may be incorrect.
|
DEV-297261 |
|
The date picker on the Record Details page may not reflect the current locale settings.
|
DEV-297040 |
|
The Vault Viewer won't display in Salesforce in Chrome 80.
|
DEV-295113 |
|
When users edit columns in the My Tasks Tabular View, Vault doesn't update the sort order for all columns.
|
DEV-293295 |
|
For some users, the selector window may not render properly during scrolling.
|
DEV-292971 |
|
In some cases, DateTime object fields display incorrect values in Business Admin. custom tabs, and Show in Tab.
|
DEV-292035 |
|
When some users download an image of a dashboard chart grouped by % stacked, the downloaded image will display record counts instead of percentages.
|
DEV-291876 |
|
In some cases where documents contain password-protected files and renditions, when a user deletes a viewable rendition of a document and replaces it with an updated version, Vault is unable to generate the viewable rendition until the user refreshes their browser.
|
DEV-290917 |
|
Some users are unable to remove a document from a document reference field by pressing backspace.
|
DEV-289251 |
|
Some users with slower network connections are intermittently logged out of Vault.
|
DEV-288648 |
|
When a user creates or views a picklist dependency, the pagination on the Picklist Dependency Matrix page displays on the left side of the page instead of the right.
|
DEV-288098 |
|
When some users hover over the Create button on the Study Country record page, they see an error message that states that their license limit has been reached even if they have more licenses available.
|
DEV-287432 |
|
When some users try to start a workflow, they are unable to select an option from a picklist field.
|
DEV-285260 |
|
Scrolling animation on the Record Details page may lag.
|
DEV-282547 |
|
Fields overlap on the Lifecycle Field Dependencies page.
|
DEV-300206 |
|
There are various UI changes on the EDL hovercard.
|
DEV-305876 |
|
Users are unable to complete a checklist when the checklist is aggregated and at least one of the sub checklists is not weighted and does not have any multiple choice questions.
|
DEV-306183 |
|
Vault experiences performance problems when updating documents with over 1,000 object references.
|
DEV-297049 |
|
Some system-managed messages may be editable via the UI.
|
DEV-307474 |
|
Required fields may have incorrect background color.
|
DEV-306858 |
|
When switching quickly between the Admin and Vault Home, Vault loads a blank page.
|
DEV-296369 |
|
After creating a date range picker, fields are shortened and misaligned with previous filter rows and columns.
|
DEV-303474 |
|
While clicking the Object breadcrumb without saving the page contents, the "Stay on Page"/"Leave Page" dialog is not appearing.
|
DEV-303352 |
|
Browser "back" button is not functioning as expected when users switch between tabs.
|
DEV-302233 |
| Description |
Issue No. |
|
Some customers are experiencing performance issues when adding, deleting, or updating entry criteria and entry actions on an object lifecycle.
|
DEV-300575 |
|
In some cases, when a user clicks into a training document, the document may display with an incorrect zoom level.
|
DEV-298844 |
|
Some orders of actions may result in a Class Schedule record details page appearing as blank.
|
DEV-297775 |
|
For some users, the document Actions menu loads slowly on lifecycles that include multiple Download Controlled Document Copy actions.
|
DEV-296356 |
|
Some users are experiencing slow loading times when they change states on document change control records.
|
DEV-296159 |
|
When some users attempt to clone a vault with Connection objects that have a "created by" value of a user other than "System," that user reference is copied from the source to the target vault.
|
DEV-295217 |
|
In some instances, training assignments are cancelled when one of the parent training requirements is changed before its associated training records are made eligible for training.
|
DEV-293499 |
|
Some users see an SDK error when they attempt to change the version of a document training requirement record.
|
DEV-289236 |
|
Some users are able to take a training quiz again after passing it the first time.
|
DEV-287272 |
|
In some cases, the Open Change Control action does not work from custom document tabs.
|
DEV-287053 |
|
Configuration reports may fail to include the 'Distribute Controlled Copy' permission.
|
DEV-249497 |
|
Configuration reports may fail to include the 'Distribute Controlled Copy' permission.
|
DEV-248681 |
|
In vaults using Quality Teams for a process with child records that have multiple types, team cascading does not work as expected when the types of child records have teams specific to those types, and those teams are both configured to inherit team role membership from the parent record via the same object reference field.
|
DEV-306808 |
|
In some cases, Vault displays an error when a workflow initiator attempts to start a workflow without the Quality Approver(s) checkbox selected.
|
DEV-303786 |
|
Navigating between assigned Document and External training assignments may result in Vault displaying a blank page.
|
DEV-303696 |
|
In vaults using the QMS to Registrations Spark Connection, field rules may not correctly update the impact assessment record in the QMS vault upon the completion of the impact assessment in the RIM vault.
|
DEV-306504 |
|
Attempting to view a migrated and completed document training assignment may result in an error.
|
DEV-306282 |
|
Non-learners may incorrectly see the training assignment task page when clicking into a training assignment in the Completed lifecycle state.
|
DEV-306144 |
| Description |
Issue No. |
|
When removing submissions, users sometimes wait for a long time (over an hour) for processing and then the operation fails.
|
DEV-303435 |
|
In some cases, the regulatory bulk record creation wizards experience slow performance when creating records, which, in turn, slows down processing for all other jobs using the same queue. This affects Create Registrations and Create Related Records wizards.
|
DEV-299167 |
|
When an Admin configures a custom Regulatory Objective object type with a required custom field and sets it as the Default Object Type, Vault doesn't display the custom field as required in the Regulatory Objective bundling wizard.
|
DEV-299154 |
|
When the Set Bookmarks & Hyperlinks to Page & Coordinates setting is not enabled, Vault sets Named Destinations to the incorrect page number after users publish a document.
|
DEV-298915 |
|
When content plan creation is automated, such as through a workflow, Vault does not notify the person who triggered the action and instead notifies the user who created the Submission record.
|
DEV-298717 |
|
Some content plan items are not included when creating a submission ready binder.
|
DEV-297500 |
|
Under certain conditions, editing a Health Authority filed may result in a server error.
|
DEV-296873 |
|
When the Published Output Location is changed, Vault does not report PDF rules correctly and previous failures are reported as Pass or Not Executed.
|
DEV-296678 |
|
In some cases, the Regulatory Objective Bundling wizard does not finish and Vault does not link newly-created Submission records to related submissions or regulatory objectives.
|
DEV-295181 |
|
Vault does not update results correctly for Rule 11.12 after continuous publishing.
|
DEV-294518 |
|
Users may be unable to delete Content Plan Items when the Delete permission is enabled in Sharing Settings.
|
DEV-294374 |
|
In some cases, when users export a Submission to the FTP, the export contains duplicate files that are not listed in the Manifest log file or the Export Summary file.
|
DEV-294254 |
|
Some users experience slow performance in their sandbox vaults while using the Registrations wizards.
|
DEV-293288 |
|
Vault does not report EU Rule 7.1 as a Fail.
|
DEV-292142 |
|
In some cases, users see an error when attempting to split a content plan item.
|
DEV-291514 |
|
When a user updates a published submission to add a content plan item within a node extension, the Continuous Publishing job does not create submission metadata, and the new content plan item doesn't display in the binder view.
|
DEV-291285 |
|
Some users do not see the "Expand All" and "Collapse All" options in the Submissions Archive Viewer when the page first loads. The button only appears if the user navigates away and then back to the Viewer.
|
DEV-291207 |
|
When some users attempt to remove a submission, the submission status changes to "error."
|
DEV-290894 |
|
For some users, RIM Submissions Archive binder sections that relate to different products are being merged so that they cannot be accessed separately.
|
DEV-290718 |
|
From the Submissions Archive Viewer, some users are unable to expand in outline view or display in list view when they are viewing an application with a large number of non-eCTD submissions.
|
DEV-290283 |
|
Vault reports fewer Submission Validation Results after the continuous validation job runs if there are no failures on the Content Plan Item.
|
DEV-290256 |
|
Vault populates the Submission Metadata TAG ID using the submission folder name on FTP instead of the submission folder name in Vault.
|
DEV-290255 |
|
On EU submissions, Vault should prevent users from setting the XML STF DTD / XSD Version field and also setting the Create Node Extension field to Yes.
|
DEV-290224 |
|
On the Common Administrative Information page, Procedure Tracking Number and Invented Name have empty rows even when default values exist.
|
DEV-289451 |
|
For some users, RIM Submissions Archive binder sections that relate to different products are being merged so that they cannot be accessed separately.
|
DEV-289054 |
|
When some users attempt to open the dossier panel in the RIM submission archive viewer, the panel doesn't open and their browser crashes.
|
DEV-288619 |
|
The leaf title is not visible to Submissions Archive users in outline view when the browser is resized.
|
DEV-288573 |
|
The Bundle Regulatory Objectives wizard selects all submissions for inactivation instead of just the submissions associated with the bundled regulatory objectives."
|
DEV-287451 |
|
Some users receive a Page Not Found error when attempting to change the object type on a Content Plan record.
|
DEV-284944 |
|
In some vaults with SDK record triggers configured, Vault fails to change the state of related records.
|
DEV-284502 |
|
For some users, files and folders in the Submissions Archive Viewer are sorted differently between sandbox and production vaults.
|
DEV-282983 |
|
Users experience slower than usual performance after selecting the Excel Tree with All Descendants export option from the Hierarchy Viewer.
|
DEV-280455 |
|
Vault truncates unresolved tokens during publishing.
|
DEV-280376 |
|
Vault fails to apply a defined dossier format to eCTDs imported via the FTP.
|
DEV-277662 |
|
Some users see an error message when they use the Manage Details Wizard to create a registered drug product record if a record with the same name already exists.
|
DEV-277529 |
|
In the Submissions Archive Viewer, when a user selects the Historical Lifecycle for the document and clicks the document link, Vault should open the Doc Info page with the Dossier Review Panel displayed.
|
DEV-276513 |
|
Vault is unable to create viewable renditions of XML files for some SPL imports.
|
DEV-262088 |
|
Vault doesn't populate some columns in validation result CSV files for links or bookmarks that are internal.
|
DEV-261585 |
|
Vault displays values in the wrong columns for Rule 5200 in the Detailed Publishing Results section on the Submission Validation Result record, and the continuous validation job clears the values in the table and leaves the columns blank.
|
DEV-261140 |
|
Users see a server error after opening a Submission record and then attempting to view the content plan hierarchy viewer.
|
DEV-305956 |
|
When users update lifecycle states in the Manage Registered Details wizard, Vault ignores entry criteria conditions and always updates the target fields.
|
DEV-306115 |
|
When users add additional columns in the new Content Plan Hierarchy Viewer and then drag and drop to match a document to a Content Plan Item, Vault doesn't update the values in the newly added columns.
|
DEV-303614 |
|
After a user drags and drops to match a document to a Content Plan Item in the new Content Plan Hierarchy Viewer, Vault refreshes the whole grid instead of only the Content Plan Item and doesn't return the user to the same location in the tree.
|
DEV-302660 |
|
As part of the Submissions and eTMF Spark Connection, Vault does not create a new version of a CrossLink document in the Submissions vault when the source document is updated and approved in the eTMF vault.
|
DEV-306091, DEV-303016 |
|
In some cases, filters are applied incorrectly after navigating to the Submissions Archive Viewer.
|
DEV-302817 |
|
When a user copies a content plan, Vault fails to copy a Content Plan Item record with a Submission Country token.
|
DEV-303163 |
|
Users can't start a multi-document workflow from the Hierarchy Viewer when the Status column isn't included in the grid.
|
DEV-302630 |
|
When users don't select the Authorised Product Element during XEVMPD bulk update, Vault includes the incorrect <authorisedproduct operationtype> in the Product Data Message XML and the file name for attached ZIP file is incorrect.
|
DEV-303297 |
|
Users cannot use inline editing to clear values in object-type fields in the Manage Registered Details wizard.
|
DEV-303415 |
|
Columns don't appear in the correct order in the Add: Registered Details dialog within the Manage Registered Details wizard.
|
DEV-302785 |
|
When users add new details in the Manage Registered Details wizard, long field labels get cut off in the Add: Registered Details dialog.
|
DEV-302748 |
|
After users drag and drop to match documents in the new Content Plan Hierarchy Viewer, Vault scrolls in the grid so the matched document and content plan item appear at the bottom of the screen.
|
DEV-302224 |
|
As part of the Submissions and eTMF Spark Connection, Vault does not create a new version of a CrossLink document in the Submissions vault when the source document is updated and approved in the eTMF vault.
|
DEV-303016, DEV-306091 |
|
When multiple submissions are imported to the same application and users without the Read permission on the Submission Metadata object select the All Submissions view in the Viewer tab, Vault incorrectly displays the Expand All or Collapse All buttons.
|
DEV-304099 |
|
Vault sometimes fails to render the XML when users import a submission.
|
DEV-303402 |
|
Vault fails to display the Expand All and Collapse All buttons in the Viewer tab when a single submission is imported to an application and a user selects the All Submissions view.
|
DEV-302673 |
|
Users experience slow performance when publishing a report level content plan with merged documents.
|
DEV-291989 |
|
Leaf titles that contain multi-byte characters are not visible to Submissions Archive users in outline view when the browser is resized.
|
DEV-292190 |
|
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-307549 |
|
When a user updates existing records and adds new records of the same type in the Manage Registered Details wizard, Vault sets the updated records to the lifecycle state the user selected for the new records.
|
DEV-307392 |
|
Vault doesn't sort the list of submissions in the Submission filter within the Submissions Archive Viewer tab.
|
DEV-290215 |
| Description |
Issue No. |
|
In some cases, when a user creates a copy of a report and changes a filter alias on the copy, Vault overwrites the alias on the original report.
|
DEV-300178 |
|
When a user creates a Multi-Pass Report with conditional fields and assigns colors to those fields, Vault does not honor the assigned colors when creating a Dashboard from the report.
|
DEV-299334 |
|
When creating Pareto charts, Vault orders values on the X axis incorrectly.
|
DEV-298089 |
|
In some vaults with large amounts of data, role fields in reports take longer than expected to load
|
DEV-297814 |
|
Users experience a server error when running an Object with Document report where the Document is the up object and contains a hidden field.
|
DEV-297005 |
|
Some multi-pass reports with conditional fields fail to run.
|
DEV-296557 |
|
Some users encounter a permissions error when trying to access documents from links in reports.
|
DEV-296326 |
|
Users incorrectly encounter a permissions error instead of an inaccessible fields error when trying to run EDL with Matched Document reports that reference hidden fields.
|
DEV-294942 |
|
For some users, certain scheduled multipass flash reports will not run, and they receive an error message when they attempt to run the reports manually.
|
DEV-292367 |
|
Some users see a timeout error message when they attempt to run a flash report at certain times.
|
DEV-292143 |
|
When some users try to expand a group in a report, the report freezes.
|
DEV-289159 |
|
In rare cases, Vault may display a server error when attempting to run a Multi-Pass report.
|
DEV-288286 |
|
For some users, standard reports are not visible after a migration.
|
DEV-287260 |
|
In certain cases, users experience server errors when running reports configured with summary calculations on document formula fields that return dates.
|
DEV-277367 |
|
When running a Multi-Pass report on a workflow view after removing the Workflow Name column, users experience an error.
|
DEV-271975 |
|
When a user attempts to export a Multi-Pass report containing views with documents which contain hidden fields, Vault fails to generate an error message.
|
DEV-301287 |
|
In cases where an MDW document is also associated with a standard workflow instance, the task name and verdict fields may display as blank in a workflow history report.
|
DEV-306993 |
|
Users experience an error when creating a Multi-Pass report with Workflow Owner as a join field.
|
DEV-302202 |
|
In certain report setups, users see errors when editing the report or when adding it to a dashboard component.
|
DEV-306452 |
|
In certain dashboard and report setups, users see "error processing this dashboard component" when attempting to view a dashboard.
|
DEV-301682 |
|
When a user downloads the sample Excel template from the report builder while in edit mode, they encounter a "Changes you made may not be saved" error.
|
DEV-303414 |
|
In some cases, Binder report type and Section with Binder report type are not consistent.
|
DEV-222248 |
|
Users experience an internal error when exporting a report to an Excel template.
|
DEV-308287 |
|
Some users experience timeout errors when generating reports which contain multi-value object reference fields.
|
DEV-303656 |
| Description |
Issue No. |
|
Fixed an issue where the Age Group was disappearing if the Date of Birth on an Adverse Event Report was removed.
|
SAF-1345 |
|
Fixed an issue where users who were assigned the Safety Writer application role could only generate aggregate reports using workflow tasks and not with the Generate Report Tabulations user action.
|
SAF-1729 |
|
Fixed an issue where a server error was appearing when generating the next Aggregate Report if the IBD and Reporting Period were not populated on the Reporting Family.
|
SAF-1784 |
|
Fixed an issue where, when importing an E2B file from a Gateway Transmission or the Receive E2B API, the transmission message name format on the Inbound Transmission was incorrect.
|
SAF-2332 |
|
Fixed an issue where form generation was failing when a Case Narrative Template included a merge field token that exceeded the field's character limit on FDA 3500A forms.
|
SAF-3039 |
|
Fixed an issue where a trailing space or double space in the Product (Reported) field was causing issues with automatically populating and running the WHODrug search query.
|
SAF-3337 |
|
Fixed an issue where Unblinded Cases with blind-protection enabled were not being counted in DSUR and PBRER aggregate reports.
|
SAF-3404 & SAF-3394 |
|
Fixed an E2B import issue where the Case Receipt Date was set to the date when the E2B file was uploaded instead of mapping the Date of Creation from the E2B file.
|
SAF-3458 |
|
Fixed an issue where the Case was not being counted in DSUR and PBRER aggregate reports if the Study Blinded field was not set to a value (Yes or No).
|
SAF-3466 |
|
Fixed an issue where the Foreign checkbox was filled in section G.3 on the FDA 3500A form when the reporter country was blank on the Case.
|
SAF-3467* |
|
Fixed an issue where an Illegal Argument Exception was reported if a product did not have a placeholder in a case with a Blinded Arm.
|
SAF-3474* |
|
Fixed an issue where users were unable to add new Drug Products to a Case because the page would not load with Indication Section Control was enabled.
|
SAF-3476* |
|
Fixed an issue where, if some text was entered into an Indication record, it remained open on the Case Product Page even after the user selected Cancel.
|
SAF-3478* |
|
Fixed an issue with content-protected E2B R2 files where the Continuing field in Medical History was not being masked.
|
SAF-3484* |
|
Fixed an issue with content-protected E2B R2 files where the patient's Date of Birth field was empty instead of being masked when a Reason Omitted was entered.
|
SAF-3486* |
|
Fixed an issue where the system was saving a blank Product Indication after the user deleted the text entered.
|
SAF-3497* |
|
Fixed an issue where generating multiple Transmission records for the same Case, such as a Submission and a Distribution, sometimes lead to the same E2B file being attached to each Transmission.
|
SAF-3498* |
|
Fixed an issue where Study Submissions were being created for all serious cases. Submission generation will now be limited to Study Cases and follow-ups that are classified as SUSAR, and follow-ups that meet downgrade SUSAR criteria.
|
SAF-3503 |
|
Fixed an issue where narrative text describing the Adverse Event was not cropped when the 100K character limit was reached on the FDA 3500A and CIOMS I forms.
|
SAF-3537* |
|
Fixed an issue where the dropdown menu for Reason Omitted in the Patient Initials/ID field was not appearing correctly.
|
SAF-3544* |
|
Fixed an issue where the Frequency field in Product Dosage Details was not appearing correctly on Microsoft Edge.
|
SAF-3549* |
|
Fixed an issue where a system error appeared if the Event Onset Date was before the patient's Date of Birth on an Adverse Event Report.
|
SAF-3553* |
|
Fixed an issue where product registration numbers were populated in section C.1 on the FDA 3500A form.
|
SAF-3720 |
|
Fixed an issue where the Initial Reporter's address was being cut off in Section E.1 of FDA 3500A forms.
|
SAF-3721 |
|
Fixed an issue where the name of the Manufacturer/Compounder was being cut off in Section G.1 of FDA 3500A forms.
|
SAF-3722 |
|
Fixed an issue where only primary suspect drugs, doses, indications, and RoAs were appearing in Section II of CIOMS I forms.
|
SAF-3723 |
|
Fixed an issue where blank dates were populated as question marks (???) on FDA 3500A and CIOMS I forms. To improve clarity, blank dates are now populated as dashes (---).
|
SAF-3727 & SAF-3726 |
|
Fixed an issue where the Foreign checkbox was filled in section G.3 on the FDA 3500A form when the reporter country was blank on the Case.
|
SAF-3729 |
|
Fixed an issue where the reported (verbatim) event text was not populated before the MedDRA term on the FDA 3500A form.
|
SAF-3730 |
|
Fixed an issue where the reported (verbatim) event text and the MedDRA term for adverse events were not populated at the start of section 7+13 on the CIOMS I form.
|
SAF-3731 |
|
Fixed an issue where calculated ages were populated as a decimal number instead of a whole number on the FDA 3500A and CIOMS I forms.
|
SAF-3732 |
|
Fixed an issue where only country codes were being used in Sections E.1 and G.1 on FDA 3500A forms and Sections 1a and 24a on CIOMS I forms. The system will now populate these fields with both the country code and the full country name.
|
SAF-3733 |
|
Fixed an issue where the full name and address of the manufacturer was not appearing in Section 24a of CIOMS I forms.
|
SAF-3735 |
|
Fixed an issue where the global manufacturer name and address were not populated on FDA 3500A and CIOMS I forms when generated to preview the Case. This issue did not affect FDA 3500A and CIOMS I forms generated for Distributions and Submissions.
|
SAF-3736 |
|
Fixed an issue where concomitant product generic names were not populated on the FDA 3500A and CIOMS I forms.
|
SAF-3738 |
|
Fixed an issue where dates were being populated in a YYYY-MM-DD format instead of a DD-MMM-YYYY format on CIOMS I forms.
|
SAF-3739 |
|
Fixed an issue where, during an E2B import, an assessment method and result were used to populate two Case Assessments when the second assessment was missing the method and result.
|
SAF-3740 |
|
Fixed an issue so that the patient’s age in Section 2a is populated with the patient’s age group if no other age details are available on CIOMS I forms.
|
SAF-3741 |
|
Fixed an issue where the outcome of the primary adverse event was not being displayed as a Case-Level outcome in Section 7+13 of CIOMS I forms.
|
SAF-3742 |
|
Fixed an issue where Section 25b detailing Reporter Information was missing from CIOMS I forms.
|
SAF-3774 |
|
Fixed an issue where product registration numbers were populated in Section 14 on the CIOMS I form.
|
SAF-3775 |
|
Fixed an issue where some auto-created DME records were being duplicated during MedDRA imports.
|
SAF-3840* |
|
Fixed an issue where country codes were being used instead of full country names in Section G.1 of FDA 3500A forms and Section 24a of CIOMS I forms.
|
SAF-3847 |
|
Fixed an issue where, in the absence of information about the product being compounded, Section C.6 was populated with No on FDA 3500A forms.
|
SAF-3867 |
|
Fixed an issue where single-digit dates were being populated in an incorrect format in Section A.2 of FDA 3500A forms.
|
SAF-3875 |
|
Fixed an issue where incorrect report type checkboxes were populated for SAEs and Serious Cases on FDA 3500A forms.
|
SAF-3879 |
|
Fixed an issue where the form title and the space between Sections C.8 and D was misaligned on FDA 3500A forms.
|
SAF-3880 |
|
Fixed an issue where the initial Receipt Date instead of the New Info Date was mapped to Section G.4 on FDA 3500A forms.
|
SAF-3957 |
|
Fixed an issue where the initial Receipt Date instead of the New Info Date was mapped to Section 24c on CIOMS I forms for Follow-Up Cases.
|
SAF-3961 |
|
Fixed an issue where test result ranges were not appearing in Section B6 of FDA 3500A forms and Section 7+13 of CIOMS I forms if data was entered in the Result (text) field.
|
SAF-3964 & SAF-3959 |
|
Fixed an issue where codes were being populated instead of simplified descriptors when users selected Reason Omitted values for Start and End dates on FDA 3500A and CIOMS I forms.
|
SAF-4005 |
|
Fixed an issue where Dose amounts in Sections C.2 and C.3 were being rounded off on FDA 3500A forms.
|
SAF-4009 |
|
Fixed an issue where the patient’s weight in Section A.4 was being rounded off on FDA 3500A forms.
|
SAF-4013 |
|
Fixed an issue with the Case Product Dosage subsection where the Reason Omitted fields were not being replaced by disabled Time/Time Zone fields unless the user entered a complete date for the First or Last Admin Date.
|
SAF-4058* |
|
Fixed an issue where the Case name was being cut off when it exceeded 20 characters in Section G9 of FDA 3500A forms.
|
SAF-4061* |
|
Fixed an issue with E2B imports where the most recent New Info Date was not being mapped onto the Date Received by Manufacturer field on CIOMS I and FDA 3500A forms.
|
SAF-4106 |
|
Fixed an issue where the Merge Binder to PDF function was failing without an error notification when users did not have the required permissions.
|
SAF-4116 |
|
Fixed an issue where Aggregate Report line listings did not include follow-up cases that had New Info Dates within the Reporting Period.
|
SAF-4239* |
|
Fixed an issue where Frequency was not being displayed correctly and expected notifications were not being sent if the value in the Dose Text field exceeded 3 digits.
|
SAF-4326* |
|
Fixed an issue where Additional Company Remarks were not being populated onto Section 26 of CIOMS I forms.
|
SAF-4336 |
|
Fixed an issue where you could not create a Follow-Up Case from a potential match if the Worldwide UIDs were capitalized differently.
|
SAF-4352* |
|
Fixed an issue where blinded E2B (R2) files were not being imported successfully.
|
SAF-4359* |
|
Fixed an issue where users could not create Adverse Event Reports if the MedDRA auto-code control was enabled and Case Products could not be created or edited if the Indication section control was enabled.
|
SAF-4404* |
|
Fixed an issue where Sender’s Comments were not appearing in the overflow field of Section 7+13 on CIOMS I forms.
|
SAF-4405 |
|
Fixed an issue where the Dosage Text field was not being mapped onto Section 15 of CIOMS I forms.
|
SAF-4406 |
|
Fixed an issue where an inactive Head of Safety user was being selected as the Sender User for a Transmission record instead of the current Head of Safety.
|
SAF-4435 |
|
Fixed an issue where the Receipt Date field was not appearing highlighted to indicate that it is a required field on AER, Case, and Imported Case.
|
SAF-4525 |
|
Fixed an issue with DSUR table generation where all cases were included in line listings, regardless of relatedness. Only cases with Adverse Events related to the suspect product will now be included.
|
SAF-4532 |
|
Fixed an issue where there was no indication of information being continued onto an overflow page when information of more than 2 Suspect Drugs was entered on CIOMS I forms. The message (Continued on Additional Page) will now appear at the end of the section.
|
SAF-4541 |
|
Fixed an issue where the coded MedDRA term was being populated onto the Event (Reported) field rather than the Event (MedDRA) field if the Event (Reported) field was blank.
|
SAF-4546* |
|
Fixed an issue where users were unable to move to a specific page of search results on the MedDRA Browser.
|
SAF-4551* |
|
Fixed an issue where a gear icon was appearing when you hovered over a result in the MedDRA Browser.
|
SAF-4599* |
|
Fixed an issue where the MedDRA control was not showing up correctly on the Case Product Indication page.
|
SAF-4637* |
|
Fixed an issue where users with an assigned User Role were seeing an error on the Case Products page when Dosage or Indication section controls were enabled.
|
SAF-4639* |
|
Fixed an issue where, during an E2B import, the correct TermID Version was not being mapped when there was an RoA TermID match.
|
SAF-4683* |
|
Fixed an issue when opening a Follow-Up Case, where Case Adverse Events from the initial Case were being renamed with a name differentiation suffix instead of those records on the Follow-Up Case.
|
SAF-4705 |
|
Fixed an issue where a warning appeared about rounding the Dose value to an acceptable number of characters when a custom Dose Unit was used in E2B (R2) imported files.
|
SAF-4718* |
|
Fixed an issue where, if text was entered in the Medical History Text field on the original Case but Reason Omitted was entered on the Follow-up, both text and Reason Omitted were appearing on the Follow-up Case.
|
SAF-4755* |
|
Fixed an issue where the Frequency control in the Dosages tab was not behaving correctly when more than one product was added.
|
SAF-4756* |
|
Fixed an issue where Dose Unit Text was being populated with {} if no value was entered and {non standard} if a custom unit was entered in E2B (R2) imported files.
|
SAF-4757* |
|
Fixed an issue where, when both Age Value and Age Unit were entered, only the Age Unit was appearing on the AER.
|
SAF-4772* |
|
Fixed an issue where Study Registration was not being copied over from a Study to an E2B-imported open Case if the E2B files did not contain the Study Registration.
|
SAF-4773* |
|
Fixed an issue where a line break was not appearing between multiple Suspect Drugs on the overflow page of CIOMS I forms.
|
SAF-4789* |
|
Fixed an issue where Dosage information was not appearing correctly when Dose Unit was left blank but Dose Unit Text was populated on FDA 3500A and CIOMS I forms.
|
SAF-4819* |
|
Fixed an issue where PADER Summary tabulations counted Cases with a New Info Date set outside of the aggregate report reporting period.
|
SAF-4827* |
|
Fixed an issue where users with the Case Processing security profile were encountering an error when trying to view the Case Product Dosages screen.
|
SAF-4839* |
|
Fixed an issue where Age appeared as -10 years on FDA 3500A forms when the value entered on the Case was 0 decades.
|
SAF-4849* |
|
Fixed an issue where an error was appearing when saving a Case Product Substance.
|
SAF-4895* |
|
Fixed an issue where the Expedited flag was not being updated when a Case was updated to add Case Adverse Event MedRA term that matched the AESI Watchlist.
|
SAF-4901* |
|
Fixed an issue where age, weight, and height values were not appearing in normalized formats on the AER.
|
SAF-4925* |
|
Fixed an issue where CIOMS I form generation failed if the Case Version field was left blank.
|
SAF-4936 |
|
Fixed an issue with Case child records that have unit value controls where values without normalization fields were showing up as null.
|
SAF-4942* |
|
Fixed an issue where the Esc and Enter keys were not producing the expected reactions of exiting and showing search results on the WHODrug Browser.
|
SAF-4943 |