The issues listed below are fixed in the 19R2 release.
| Description |
Issue No. |
|
In rare cases, Vault Loader jobs fail with the error message: “An unexpected error occurred before this record could be processed”.
|
DEV-263290 |
|
When loading data containing a comma and surrounded by double quotes, Vault Loader may not properly process the data.
|
DEV-258972 |
|
Vault allows Admins to modify the setting “Allow user to select multiple values” on document fields outside of edit mode.
|
DEV-232044 |
|
When deploying a VPK that includes a document formula field where the label has changed from its original value, Vault deploys the field using the original value rather than updated value.
|
DEV-232197 |
|
Some users experience slow performance when using Vault Loader to extract objects.
|
DEV-233959 |
|
Sometimes, Vault Loader jobs take too long to complete or fail with a “cannot process batch” error.
|
DEV-235204 |
|
For some users, attempting comparison during the review/deploy step after importing a VPK results in a server error.
|
DEV-235209 |
|
Some users are experiencing validation errors when attempting to import certain VPK packages that contain document types.
|
DEV-238610 |
|
After manually assigning a role, the document audit trail shows a picklist label where it should show the assigned role’s label.
|
DEV-241817 |
|
In some cases, users cannot create a new cross-domain user and receive the error “Invalid username or user already exists” even when the username is valid and the user does not already exist.
|
DEV-242756 |
|
Admins see a server error when attempting to rename a document classification.
|
DEV-242832 |
|
When creating Network Access Rules, users receive a “Mixing of IPv4 and IPv6 addresses are not allowed” error if the IP address has any trailing spaces.
|
DEV-243870 |
|
In Vault Compare, workflow configurations containing identical rule conditions referring to object fields may show differences.
|
DEV-243913 |
|
For some users, Vault does not properly load Controlled Copy trace object types that are used in reports.
|
DEV-244689 |
|
When configuring an event action to set a field using a formula that divides by zero, Vault displays a server error.
|
DEV-245402 |
|
When users cannot be added to a sandbox vault during create/refresh, the sandbox job will incorrectly report success.
|
DEV-245972 |
|
In some cases, scheduled jobs fail on an intermittent basis.
|
DEV-246083 |
|
In some cases, the Vault Compare report shows differences between workflows that have identical rule conditions.
|
DEV-247810 |
|
In cloned vaults, Admins see a server error when attempting grant Create Document permission on Base Document.
|
DEV-248098 |
|
When Admins access a binder template that includes planned document without an autoname format, they see a server error.
|
DEV-249123 |
|
Configuration Migration, Vault Compare, and Vault Configuration Report do not properly track changes to event actions when users modify the selected document action.
|
DEV-251955 |
|
Admins cannot inactivate a lifecycle that is referenced by a binder template planned document, although the related binder template no longer exists.
|
DEV-251965 |
|
When creating documents with the Vault Loader, some field values may not be included in the output log for verification.
|
DEV-252192 |
|
In 19R1, we fixed a bug which allowed security profile labels to exceed 60 characters. If users have existing labels which exceed 60 characters, these security profiles cannot be migrated through configuration migration. Now, for the purposes of configuration migration only, these labels may include up to 100 characters.
|
DEV-254361 |
|
Adding or removing a field for an object type also adds or removes the field for the associated lifecycle and lifecycle state.
|
DEV-254676 |
|
In some cases, the audit trail reports changes to the description field when no changes have been made.
|
DEV-255468 |
|
In some cases, Vault may display an incorrect total number of messages on the Document Messages and Object Messages pages in Admin > Configuration.
|
DEV-258128 |
|
A server error may occur if two users attempt to concurrently delete the same rendition type.
|
DEV-250257 |
|
If the source vault is in the process of enabling or upgrading a feature, creating a sandbox may result in an invalid sandbox configuration.
|
DEV-164867 |
| Description |
Issue No. |
|
For some users, updating values in an EDL Item template does not automatically update all existing EDL item records.
|
DEV-220144 |
|
In vaults with more than one multi-site document distribution workflow, a user action to begin one of those workflows does not trigger the expected workflow.
|
DEV-221866 |
|
Vault encounters an error when attempting to update person records that have other person records that reference the same user.
|
DEV-228941 |
|
Some users are not able to enable the Person & Organization Migration feature for their vaults.
|
DEV-229168 |
|
In rare situations, Vault blanks out document fields without recording an audit entry.
|
DEV-231335 |
|
When viewing records from the Site Activation Progress tab, Vault incorrectly displays the filter “All EDL Item”.
|
DEV-234733 |
|
Study Person records matched to migrating Study Team Assignment records are not updating correctly.
|
DEV-236556 |
|
Links to milestones in the Upcoming Milestones section of the SSU homepage are not working.
|
DEV-237816 |
|
#Total, # Open, # Closed Quality Issue fields on documents sometimes do not show correct values when viewed from the library or from a report.
|
DEV-241061 |
|
When attempting to start a standard job, some users are receiving the error message: “invalid VQL query”.
|
DEV-241410 |
|
Some users are receiving a server error when attempting to complete a document workflow.
|
DEV-241496 |
|
The enrollment status graph on the study manager homepage does not consider a “last subject in” date that occurs in the past. This is causing Vault to create incorrect graphs.
|
DEV-243560 |
|
Sometimes, Vault encounters an unknown error when a user attempts to add a custom role to a custom sharing rule.
|
DEV-244091 |
|
Vault does not properly link EDL item records with milestones that have a name with more than 60 characters.
|
DEV-246398 |
|
The monitoring compliance job is creating monitoring compliance object records in vaults that do not have the CTMS application.
|
DEV-246698 |
|
Some non-admin users are unable to edit EDLs despite having proper permissions to do so.
|
DEV-248169 |
|
Some users cannot complete configuration migrations.
|
DEV-250215 |
|
In a multi-site document distribution workflow, adding a site with the Distribute to Sites action does not trigger an email notification to task recipients.
|
DEV-255264 |
|
In the third step of a multisite document distribution action, Vault does not display the correct Acknowledge By date entered during the second step.
|
DEV-255263 |
|
In some cases, Vault does not create Monitored Metrics records after running the Update Monitored Metrics job.
|
DEV-256973 |
|
We cannot enable the Person and Organization and Migration feature for certain vaults.
|
DEV-240790 |
|
Tabbing does not drop to the next line in Monitoring Event Question sections.
|
DEV-244953 |
|
When users create a Quality Issue from a document, Vault re-renders the document.
|
DEV-246125 |
|
Vault does not properly link EDL item records with milestones that have a name with more than 128 characters.
|
DEV-246398 |
|
The monitoring compliance job is creating monitoring compliance object records in vaults that do not have the CTMS application.
|
DEV-247392 |
|
Some non-Admin users are unable to edit EDLs despite having proper permissions to do so.
|
DEV-248169 |
|
For some users, classifying an unclassified document sets the Quality Issue’s # Total, # Open, and # Closed fields to null.
|
DEV-252210 |
|
Clinical Operations vaults show the Study Selector on object tabs where the object does not have an outbound relationship to Study. Study Selector should not appear in these tabs.
|
DEV-252526 |
|
Some users are receiving server errors when trying to open study site records.
|
DEV-254275 |
|
For some users, executing a workflow action to update a custom document field erroneously blanks out the Content field.
|
DEV-254303 |
|
In some cases, Vault creates blank Document Type Details records that cannot be deleted.
|
DEV-254679 |
|
Some standard user task notifications may be sent even when disabled.
|
DEV-254728 |
|
This fix introduces several enhancements to the UI of the new TMF viewer.
|
DEV-255306 |
|
Vault does not create EDLs for template milestones that do not have EDL templates.
|
DEV-257992 |
|
In some situations, Vault encounters an error when a user runs the update metrics job when the recruitment planning metrics field of a study is blank.
|
DEV-258158 |
|
Vault does not automatically set permissions for the organization_role__v and selected_organization_role__v objects after the person object migration.
|
DEV-258775 |
|
Some users are encountering a “Server having problems” error when attempting to open the Study Site object or Study Site object lifecycle.
|
DEV-259231 |
|
In some cases, Vault deletes User Role Setup records for a study person record if the “Grant Access to Related Records” option on the record is updated to “No”.
|
DEV-259624 |
|
In some situations, when a template milestone does not have an associated EDL template the Apply Milestone Template job errors out.
|
DEV-260783 |
|
Some users are unable to activate agreements when using Veeva Clinical Network.
|
DEV-259164 |
| Description |
Issue No. |
|
Certain document field values do not show up correctly on a document due to name collisions with other non-document fields.
|
DEV-179346,DEV-178801,DEV-225587,DEV-246608 |
|
Renditions of documents created using the make a copy action include incorrect MD5 checksums.
|
DEV-216816 |
|
Users cannot delete a picklist value that shares the same name__v as another picklist value.
|
DEV-219351* |
|
When navigating through documents in a binder, the count of documents incorrectly shows 1 of 1, 2 of 1, etc. when there are many documents.
|
DEV-219845 |
|
When bulk document creation (via Create button) fails due to an error executing an event action, Vault displays the correct error message, but the page hangs after a user clicks “OK”.
|
DEV-224442 |
|
When attempting to delete certain shared fields from document types, some users receive the error message: “A binder template auto-filling rule currently uses this field”.
|
DEV-224565 |
|
If a text file contains an XML doctype declaration, Vault may attempt (and fail) to render it as an XML file, rather than as a text file.
|
DEV-225592 |
|
In some cases, Vault accepts tracked changes on downloaded DOCX renditions.
|
DEV-231241 |
|
In certain situations, users can create a binder using a template that does not apply to the selected document type. This occurs when a user selects a document type and template and then changes the document type.
|
DEV-231816 |
|
In certain situations, users see the “viewable rendition does not exist for this document” error incorrectly and must refresh the page to view the generated rendition.
|
DEV-232310 |
|
When users open the Doc Info page, field dependencies based on document lifecycle do not override field dependencies based on document type when each specifies an opposite behavior on the same field.
|
DEV-232621 |
|
When creating a document from a template, it’s possible to select a subtype with no valid templates causing a “server having problems” error.
|
DEV-232625 |
|
Some users report that Visio objects do not render properly in viewable renditions of word documents.
|
DEV-235636 |
|
Entry actions to blank out object and/or picklist fields do not successfully blank out those fields.
|
DEV-236462 |
|
When creating documents, Vault only saves one value when multiple values are selected in a multi-picklist field.
|
DEV-236485 |
|
Sometimes, Vault clears the value in single and/or multi-value picklist fields when creating a draft of a document or uploading a new version.
|
DEV-236492 |
|
Some users are experiencing a “server having problems” issue when executing a bulk action to create document relationships.
|
DEV-236825 |
|
When creating a new document through a Supporting Documents relationship on an existing document, document creation fails with a server error if Vault triggers an event action on the new document.
|
DEV-237147 |
|
After classifying an unclassified document, it does not render with the correct rendition profile.
|
DEV-238678 |
|
Document checksums in the binder manifest do not match source document or viewable rendition checksum values in Vault.
|
DEV-238825 |
|
In some situations, users are not able to save changes to a document.
|
DEV-238983 |
|
Some users report not being able to view PDF files with 256-bit encryption in the doc viewer.
|
DEV-239252 |
|
Vault does not properly render Indesign files with outdated links.
|
DEV-240067 |
|
In some cases, XML source files may render differently than expected.
|
DEV-240107 |
|
In some cases, when using a Merge Fields document where tokens are placed in tables, the content extends off the edge of the table.
|
DEV-240545 |
|
Some users are experiencing slowed performance when using formatted output.
|
DEV-241477 |
|
In some cases, after migrating an overlay from one vault to another, custom fields used in the overlay do not display correctly.
|
DEV-242949 |
|
When using Merge Fields, MS Word files with templates, and the setting “Automatically update document styles” enabled, Vault may unexpectedly change the source content and produce an incorrect rendition.
|
DEV-243016 |
|
Sometimes, the library’s tabular view does not show values for document fields that begin with a number.
|
DEV-243674 |
|
Some images are rotated 90 degrees in viewable rendition.
|
DEV-244707 |
|
When using protected styles in an MS Word source file, Vault may not correctly generate bookmarks for caption sub-headings and may not correctly format all-caps styles.
|
DEV-245492 |
|
During an object workflow, Vault does not auto-fill controlled fields when prompting for fields within a verdict.
|
DEV-245661 |
|
Some users report that if there are more than 10 workflow tasks that have been completed or assigned in the current workflow, only 10 of those tasks show up in the Timeline View and/or the Workflow Flyout Menu. Additionally, Vault does not sort these lists properly.
|
DEV-246467 |
|
If there are more than 10 workflow tasks completed or assigned in the current workflow, only 10 of those tasks show up in the Timeline View and/or the Workflow Flyout Menu. Additionally, Vault does not sort these lists properly. To fix these issues, we increased the Workflow Flyout Menu task limit from 10 to 25 tasks.
|
DEV-246467 |
|
In specific vaults where OCR is enabled, Vault is not generating viewable renditions for all documents.
|
DEV-246480 |
|
After uploading an imported rendition and later attempting to download it, some users report that the document downloaded is not the one expected.
|
DEV-246656 |
|
In some cases, the rendition setting to generate bookmarks based on Table of Contents may cause a rendition to differ in layout from the source file.
|
DEV-246843 |
|
Some users are not able to see annotations on documents that have over 200 anchor links.
|
DEV-246912 |
|
Vault sometimes does not allow users to create an anchor for link annotations in a document with an MS Word source file.
|
DEV-246998 |
|
Users see a server error when bulk adding unclassified documents to a binder section.
|
DEV-247051 |
|
In some cases, the download document button is missing for users who have the correct download permissions.
|
DEV-247265 |
|
Users cannot check out a document if the filename includes invalid characters.
|
DEV-247770 |
|
In some cases, Vault incorrectly renders markup in documents with Merge Fields regardless of whether ‘Do not show Markup in the Viewable Renditions for Word documents’ is enabled or disabled.
|
DEV-248923 |
|
Users cannot access Check Out to Vault File Manager action in Tabular View.
|
DEV-248956 |
|
In some cases, DOCX attachments to uploaded email documents do not correctly render.
|
DEV-249223 |
|
In some cases, Vault may mismatch between Named Destinations and their respective Bookmarks within a rendition with the Do Not Show Mark Up flag off.
|
DEV-249650 |
|
In some cases, Vault fails to render created documents.
|
DEV-250409 |
|
Embedded links on documents on the doc viewer sometimes encounter “Page Not Found” errors.
|
DEV-251639 |
|
Some users are experiencing inconsistencies with annotation timestamps.
|
DEV-251995 |
|
Vault does not apply default document field values in cases where (1) the document field setting “Do not copy this field during Make a Copy” is on or (2) the user choosing Make a Copy specifies that the field values should not be copied.
|
DEV-252384 |
|
When merging more than 40 records in a table, tokens fail to merge
|
DEV-252570 |
|
Vault may not correctly populate Document Subtype and Classification in the eSignature page and Overlay when the vault language changed from English to another language.
|
DEV-253277 |
|
Vault exports more than the expected number of documents when bulk exporting a large number of documents.
|
DEV-254960 |
|
In very rare cases, bulk-uploading multiple documents to Vault fails.
|
DEV-255786 |
|
The TMF Viewer may not properly display the correct Document Version values.
|
DEV-257751 |
|
When merging more than 40 records in a table, tokens fail to merge.
|
DEV-259382 |
|
The warning message “This action may result in misplaced and/or page level annotations, and cannot be undone.” does not appear if existing annotations are hidden by annotation filters.
|
DEV-237420 |
|
A server error may occur when manually adding documents to an Expected Document List if there is a large number of document matches.
|
DEV-252019 |
|
Vault does not automatically remove leading or trailing whitespace on default document field values created through MDL. When users later update fields on documents, they see an error because the default value contains invalid characters (spaces).
|
DEV-249594 |
|
Documents copied using the Brand Portal are incorrectly identified as created by Vault.
|
DEV-225856 |
|
When merging more than 40 records in a table, tokens fail to merge.
|
DEV-261424 |
|
If bookmark extraction fails while Vault is generating a rendition, the resulting rendition may be incomplete (for example, lacking bookmarks).
|
DEV-257555 |
|
For some users, documents checked out from Vault and opened in MS Word™ unexpectedly contain locked fields.
|
DEV-256580 |
|
Users who have links to whole documents won’t be able to see the titles of anchors on exported annotations when they export the annotations from anchor documents.
|
DEV-250365 |
|
Rendition Profiles field is set as required. With this fix, the field no longer appears as required.
|
DEV-249099* |
| Description |
Issue No. |
|
Vault shows an incorrect count of incomplete tasks in the timeline view of documents in a multi-document workflow.
|
DEV-259435 |
|
When Workflow Role Setup includes a rule criteria on a field that is hidden to the workflow owner, workflow role restriction is not applied.
|
DEV-228684 |
|
In rare cases, Vault erases document field values when a user who does not have read permission to on the field completes a workflow task on the document.
|
DEV-231141 |
|
Users are able to complete object workflow tasks while editing object records, which causes users to lose all changes to the record.
|
DEV-231954 |
|
Users are able to complete object workflow tasks while editing object records, which causes users to lose all changes to the record.
|
DEV-231954, DEV-250723 |
|
When a user changes their vault base language, some labels for multi-document workflows may disappear and the user may get server errors.
|
DEV-233883 |
|
Certain third-party AdBlock extensions for Google Chrome interfere with Vault functionality.
|
DEV-234052 |
|
When users configure an Entry Action using a formula, Vault changes multiple spaces in a value to a single space.
|
DEV-236370 |
|
The dateDiff() formula sometimes returns incorrect output when used to set a field with a formula in an entry action.
|
DEV-238230 |
|
Some users experience an error where the current state of an object record is not accurately reflected in audit entries.
|
DEV-238974 |
|
When null values exist in Document Lifecycle State Entry Criteria, users experience a server error when trying to access the entry criteria tab.
|
DEV-240362 |
|
When users attempt to edit an event action that uses a shared field after the shared field is no longer used, Vault freezes and does not allow the user to update the event action.
|
DEV-242830 |
|
Vault allows users to create event actions with invalid fields through the multidocument loader.
|
DEV-242839 |
|
Some users are unable to save when configuring entry actions for document lifecycle states.
|
DEV-243441 |
|
In some situations, Vault encounters a server error when an event action with a date field condition tries to auto-start a workflow.
|
DEV-244856 |
|
Vault encounters a server error when an event action that is configured to set a document field to a number divided by 0 is executed.
|
DEV-245402 |
|
Some users are not able to complete object workflow tasks with object fields that have dependent relationships.
|
DEV-245661 |
|
In rare cases, Vault displays an error message that does not specify the reason for the failure when users attempt to use event actions that have been disabled.
|
DEV-246102 |
|
In some cases. users experience an error message while accessing lifecycle state details.
|
DEV-246113 |
|
When users configure a lifecycle state entry action with the “dateTimeAd” function, they experience a validation error.
|
DEV-246397 |
|
Users experience an error message that is unclear when the document they are currently viewing is upversioned.
|
DEV-246874 |
|
For some users, certain document state entry and event actions encounter a server error when attempting to set a document’s text field to a referenced object’s picklist field.
|
DEV-248375 |
|
The number of available tasks on the Views menu does not match the number of tasks in the actual list.
|
DEV-248647 |
|
When the My Tasks list is filtered by status, users are shown placeholder document tasks in some cases.
|
DEV-249856 |
|
When a user applies filters, Vault displays an incorrect number of tasks in the View menu.
|
DEV-250062 |
|
In rare cases when saving changes to a workflow configuration, Vault updates the workflow version but does not apply the changes.
|
DEV-250323 |
|
In some cases, Vault displays an incorrect document count under Task Type in the Filters panel.
|
DEV-250384 |
|
In some cases, when a document workflow is started, the document owner is incorrectly added to workflow tasks.
|
DEV-251225 |
|
In rare cases, users can start a workflow with a disallowed user who was previously selected in a single user control field.
|
DEV-251432 |
|
Users are able to delete document lifecycle states that are referenced in event actions, entry actions, entry criteria, user actions, conditional overlays, and esignature conditions.
|
DEV-251795 |
|
In some vaults, configured document lifecycle state entry actions encounter a server error when attempting to set a document field value using a picklist value from a related object.
|
DEV-248375 |
|
When two separate document lifecycles contain roles that have the same name, Vault treats them as the same role.
|
DEV-215414 |
| Description |
Issue No. |
|
Vault Admins can now add fields from objects related through a simple join relationship to a Related Object section on the parent object’s page layout.
|
DEV-260996 |
|
Layout Rule Expressions configured on blank picklist values result in fields and sections not being correctly hidden in edit mode.
|
DEV-260494 |
|
Automatic person__sys creation does not work if the default value for Person Type is Internal.
|
DEV-258120 |
|
Object record Yes/No fields with “Show as checkbox” enabled sometimes show nothing rather than an unselected checkbox.
|
DEV-261390 |
|
In some cases, double-clicking the Save or Save & Create button creates two identical object records.
|
DEV-259881 |
|
A Self Reference field may not be configurable when it references the same field on a different record.
|
DEV-247488 |
|
In some cases, right-clicking the Create button within an object record may function differently than left-clicking the Create button.
|
DEV-234931 |
|
While editing an object, canceling the edit and then clicking Cancel in the Unsaved Changes dialog does not correctly reenable the Save button on the object edit page.
|
DEV-236309 |
|
In some cases, the Save button is unavailable after editing an object record field.
|
DEV-236322 |
|
On the Create page, controlled fields are disabled if the controlling field is a lookup field.
|
DEV-236427 |
|
In the object record detail page, record select dropdown fields sometimes incorrectly display “no records available” even when records are available.
|
DEV-236440 |
|
While editing an object record, adding only a single character to a text field does not correctly enable the Save button.
|
DEV-236603 |
|
When changing the object type, Vault may incorrectly display the Unsaved Changes dialog.
|
DEV-236716 |
|
Bulk edit fails to update “Rights” fields (Rights Language, Rights Contact, etc.).
|
DEV-236973 |
|
In certain cases, navigating from a My Tasks link to an object record directs the user to a blank page with two header bars.
|
DEV-238422 |
|
Users encounter an error where validation rules are incorrectly evaluated using the system timezone instead of the user timezone.
|
DEV-241451 |
|
Users experience a blank error message when attempting to configure an object page layout with more than 15 columns.
|
DEV-241588 |
|
Users who have French selected as their language in their user profile are unable to create object records.
|
DEV-243646 |
|
Vault mistakenly displays a blank page when users click an individual object record for an object where picklist values have been deleted.
|
DEV-243891 |
|
When completing a manual assignment (custom sharing rule) for a custom role on an object, users see an “unknown or unexpected error occurred” message.
|
DEV-244091 |
|
Vault sometimes encounters an unexpected error when attempting to create an object field layout rule through the Vault UI.
|
DEV-244794 |
|
Sometimes, Vault does not populate related object sections on the page layout of an object if the joining object of the relationship uses object types.
|
DEV-244854 |
|
Users must hit backspace twice to clear the value of an Object Reference field.
|
DEV-245967 |
|
Creating user reference fields that use default value expressions sometimes causes server errors.
|
DEV-246491 |
|
When opening the Related Objects section of an object record, some users experience an error message.
|
DEV-246682 |
|
Object records with layout rules applied and at least one multi-value picklist field cannot execute the “Change Type” action.
|
DEV-246718 |
|
Users are unable to trigger Change Type in an object record if it has a multi-value picklist populated and has layout rules associated.
|
DEV-248695 |
|
Some users experience failures when using hierarchical copy on a parent record which has a child record with custom sharing rules enabled.
|
DEV-251812 |
|
When a user tries to inline edit a multivalue picklist field, they are unable to save the values.
|
DEV-256475 |
|
When a user tries to inline edit a picklist which contains inactive values, they see a server error.
|
DEV-256633 |
|
Layout Rules do not properly configure an object record detail page layout when the layout rule expression refers to a picklist field.
|
DEV-257834 |
|
When viewing a parent object record, some fields in child object panels do not display data from the parent object record.
|
DEV-259004 |
|
When viewing a parent object record, some formula fields in child object panels do not display data from the parent object record.
|
DEV-259004 |
|
Vault disables controlled fields when creating object records using the pop-up dialog.
|
DEV-259559 |
| Description |
Issue No. |
|
Values display as null when users select the Select All option on the Doc Info Page for records with passthrough join relationships.
|
DEV-260235 |
|
In some cases, users mistakenly create multiple records when they double-click the Save button when creating an object record.
|
DEV-260558 |
|
Under certain conditions, the Vault Loader extract job may hang.
|
DEV-259265 |
|
A list page containing multiple records may load slowly if it contains multiple hidden values.
|
DEV-255653 |
|
In some Parent Object records, the DateTime field format is a single field instead of separate date and time fields.
|
DEV-215961 |
|
Admins experience slow performance when configuring tabs.
|
DEV-217561 |
|
When navigating through documents in binders with many documents (over 5,000), users experience slow performance.
|
DEV-219845 |
|
Vaults with more users experience decreased user creation performance.
|
DEV-225841 |
|
Users are able to edit disabled controlled record select fields if they are configured to be in a different details section than the controlling field.
|
DEV-229667 |
|
When a user creates a child field, the parent object reference field is not auto-populated.
|
DEV-229881 |
|
Users are able to complete object workflow tasks while editing object records, which causes users to lose all changes to the record.
|
DEV-231954 |
|
The Document Inbox sometimes loads slowly.
|
DEV-232272 |
|
In the object record detail page, users are unable to tab to the lookup icon in the document reference field.
|
DEV-235826 |
|
In the object record detail page, record select dropdown fields incorrectly display a “no records available” message.
|
DEV-236440 |
|
Users viewing document types, subtypes, and classifications which do not have translations appear as “null.”
|
DEV-236469 |
|
Rarely, Actions menus open in the wrong place on the screen.
|
DEV-237022 |
|
Some Workflow checkboxes in the General Settings menu appear by error and do not display labels.
|
DEV-237238 |
|
When viewing an object record detail page with no attachments, Read-Only users are unable to expand the attachments panel.
|
DEV-238307 |
|
The Edit Columns dialog does not function as expected in Google Chrome on Android.
|
DEV-240117 |
|
The Edit Columns dialog does not function as expected in Apple Mobile Safari on iOS.
|
DEV-240885 |
|
Some users experience slow performance when using Chrome with the LastPass browser extension.
|
DEV-242660 |
|
In a document tab using Tabular View, Vault does not show values for text fields that begin with numbers.
|
DEV-243754 |
|
When a user adds the ${docNumber} token to the description field in a workflow task, the token does not render in the task completion dialogue.
|
DEV-244885 |
|
Users experience slow performance when using Change Type.
|
DEV-248759 |
|
This issue only affects those using Internet Explorer 11 to access Vault. When users enter a search term in a dropdown field and then click on the scroll bar for the dropdown options, the search term disappears.
|
DEV-250460 |
|
When users open a document from the Home > Notifications page, the “Back to previous page” link does not work.
|
DEV-251278 |
|
When the user language is set to Japanese, an error may prevent the user from saving changes if the date and time formats are not based on a user’s locale.
|
DEV-253619 |
|
In some RIM vaults, users experience slow performance when they select the Export Excel tree with Descendants action for a Content Plan Item from the Content Plan Hierarchy Viewer.
|
DEV-256269 |
|
The following UI elements do not render properly: Automatch Placeholder, Info icon; Async Binder Export, Question icon; Document Hovercard Legal Hold, Favorite, and Archived icons; Document Metadata Hovercard in Submissions Archive Viewer, Leaf icon.
|
DEV-251044 |
|
Asynchronous checksum calculation performs some unnecessary processing for target vaults, potentially backing up the checksum calculation queue. This means checking for duplicate files may take longer than expected.
|
DEV-261792 |
| Description |
Issue No. |
|
In the Submissions Archive Export Summary CSV, Vault includes an extra backslash at the start of each folder’s Relative Path.
|
DEV-259280 |
|
In some cases, required fields are greyed out in the Manage Registered Details wizard.
|
DEV-258803 |
|
The publishing job fails if the Submission contains a Content Plan Item that is matched to a corrupted document.
|
DEV-258188 |
|
Vault does not display the confirmation banner after publishing a report level content plan.
|
DEV-218071 |
|
Vault does not report validation rule 5045 in cases when it should.
|
DEV-226178 |
|
In some cases, Vault fails to convert DOCX bookmarks targeting Named Destination to a relative path links during the report level content plan publishing process.
|
DEV-226269 |
|
Vault does not create an inactive submission join record when copying a US content plan to a content plan in an EU application.
|
DEV-231744 |
|
In some cases, Vault creates duplicate documents for submission imports happening for the same submission in parallel rather than reusing the existing document.
|
DEV-231758 |
|
Vault does not report Rule 16.BP2 and 16.BP3 when a bookmark target doesn’t exist on a matched document.
|
DEV-235818 |
|
Vault does not report Rule 16.BP2 when a bookmark or link targets a non-existent named destination or document page, or when a bookmark or link is inactive.
|
DEV-235863 |
|
Rule 16.1 is not reported if a version 1.3 PDF is matched to a Content Plan Item and a user sets the Source of Published Document to the Source Document.
|
DEV-235968 |
|
Rule 16.BP4 is not reported when a document matched to a Content Plan Item contains a hyperlink and the PDF zoom level is not set to Inherit Zoom.
|
DEV-236356 |
|
In some cases, imported EU submissions get stuck in the In Progress state.
|
DEV-236385 |
|
For Grouped Submissions, Vault does not include the Cross Reference Application Number in the US Regional XML.
|
DEV-236631 |
|
Vault should not report validation Rule 16.BP2 if a hyperlink exists that targets a document matched to a Content Plan Item and the document is updated so the hyperlink points to a new target page.
|
DEV-236638 |
|
When a user adds links to a published document and the continuous publishing job runs, published links don’t navigate to specific pages within the document.
|
DEV-240364 |
|
Links in Study Tagging File (STF) sections don’t work after a user updates the Published Output Location for a target in a published submission.
|
DEV-240540 |
|
When a document is published using report level content plans and contains a vault link annotation, the PDF does not have Fast Web View enabled.
|
DEV-240640 |
|
Vault does not remove related Publishing Validation Results records when EDL or EDL Item records are deleted or set to inactive while continuous publishing is enabled.
|
DEV-241023 |
|
Sometimes, the On Demand Publishing job fails unexpectedly if an EDL had been set to inactive.
|
DEV-241062 |
|
In the Manage Registered Details wizard, Vault doesn’t sort records correctly when users click a custom field column header to sort on the Select Registered Details page.
|
DEV-241197 |
|
The order of published documents in the Viewer tab is incorrect if the published submission contains placeholder documents for EDL Items that do not have matched documents.
|
DEV-241491 |
|
Vault erroneously reports Rule 5055 when a Content Plan Item is matched to a PDF document that is a fillable form.
|
DEV-241523 |
|
The Gateway Submission confirmation dialog appears blank for applications of type Rest of World (ROW).
|
DEV-241584 |
|
When continuous publishing is enabled, Vault does not remove Publishing Validation Results after a user clears the submission’s related Content Plan.
|
DEV-242513 |
|
When users Create Related Records from an Event record, Vault doesn’t save all values that users select in multi-value picklist fields.
|
DEV-242838 |
|
With RIM Dynamic Linking, named destinations do not work properly on viewable renditions where an overlay is applied.
|
DEV-243047 |
|
The continuous validation job incorrectly creates Publishing Validation Result records for inactive EDL Items.
|
DEV-243186 |
|
Vault fails to report Rule 1734 and Rule 1736 when Module 4 Section 4.3.2.1 is missing the correct files.
|
DEV-243459 |
|
Vault erroneously reports Rule 1255 for PDF, XML, and XTP file types in Modules 4 and 5.
|
DEV-243534 |
|
In some cases, when users view imported and mapped submissions in the Viewer, section names do not display correctly.
|
DEV-243652 |
|
Users are unable to remove the Lead Market filter in the Search: Application dialog when only creating Submissions and Regulatory Objectives via the Create Related Records action.
|
DEV-243662 |
|
Vault erroneously reports Rule 5215 when a Vault link’s source and target are the same matched document.
|
DEV-244097 |
|
For published submissions, Vault incorrectly reports validation rules for EDL Item records with Continuous Validation set to No.
|
DEV-244922 |
|
Vault fails to update Publishing Validation Result records after users upload a new document version and continuous publishing runs.
|
DEV-245471 |
|
When using the Create Related Records Wizard, users are not able to select event relationships when their permissions should allow it.
|
DEV-245543 |
|
Vault erroneously reports Rule 5005 when published submissions include FDA form 1571.
|
DEV-245732 |
|
Vault does not report validation rule 1636 in cases when it should.
|
DEV-245757 |
|
Links to Content Plan records in Vault notifications navigate users to the Content Plan object record details page instead of the Hierarchy Viewer.
|
DEV-246359 |
|
For some users, Vault shows duplicate files and unexpected folders on imported submissions.
|
DEV-246366 |
|
When bulk creating complex drug products, Vault displays incorrect records in the Registration record’s Registered Drug Products section.
|
DEV-246611 |
|
Some users are unable to create binders for content plans due to Vault not considering EDL fields with the “__c” namespace when matching.
|
DEV-247797 |
|
In some cases, when documents are matched to multiple content plans in various states, Vault does not publish document links.
|
DEV-249341 |
|
Setting an EDL Item in an STF section from inactive to active causes Vault to not publish the matched document.
|
DEV-249575 |
|
After unmatching a document from a Content Plan Item in a published submission, Vault fails to match the document again when a user selects the Match Document user action.
|
DEV-250200 |
|
Some users are experiencing performance issues when creating content plans.
|
DEV-250675 |
|
Some users are not able to update the lifecycle states for registered detail records in the Manage Registered Details wizard.
|
DEV-251381 |
|
In some cases, when users create a grouped submission, the Submission ID and Sequence Number for the primary submission are missing from the XML.
|
DEV-251868 |
|
In some cases, after the first version of a binder is created during Report Level Content Plan binder creation, subsequent versions will not have binder fields updated, which can result in fields being blanked out even if they are required.
|
DEV-251904 |
|
In some cases, when users bulk-create related records, Vault does not show join object records on the Define Relationships page.
|
DEV-252180 |
|
The submission bundling wizard erroneously requires dynamic constraints for the Submission Type field.
|
DEV-252434 |
|
In some cases, the master pane and grid pane do not load when viewing a Content Plan in the Hierarchy Viewer in Firefox.
|
DEV-253398 |
|
Users must have Read permission on the Submission Metadata object to use the Viewer for submission archives. In previous versions, this permission was not required.
|
DEV-253538 |
|
When working with multiple submissions, the Select Leaf Operation Target window does not allow users to select an STF XML to append.
|
DEV-253614 |
|
When initially publishing a submission that contains a link’s target document and the target document has been manually excluded, Vault erroneously creates a link on the published source document.
|
DEV-254364 |
|
When creating links using the Copy Link option from the document’s action menu in Vault, links point to the wrong page after publishing a report level content plan.
|
DEV-254516 |
|
When users import an empty ZIP file via the UI or API, the Submissions Archive Status should be ERROR, and Vault should report warnings in the notification.
|
DEV-255729 |
|
Vault fails to publish a content plan when the Open Validation Results field is not available on an object type.
|
DEV-255792 |
|
On vaults using Inline Validation Results, Vault fails to publish report level content plans.
|
DEV-255861 |
|
In some cases, when users import a submission via the FTP, Vault creates the STF_Leaf node as a placeholder instead of creating a file.
|
DEV-256141 |
|
If the “Import files not referenced in the eCTD XML” setting is not enabled but the Dossier Format field on the Submission record is populated, when a user uploads a ZIP file with multiple submission folders, Vault erroneously imports both sibling submissions as non-eCTD submissions.
|
DEV-256581 |
|
When the content plan creation job runs, it fails if a token causes the Name field to exceed its maximum length.
|
DEV-256788 |
|
Vault may encounter message processing errors when a large amount of correspondence is triggered in concurrent events.
|
DEV-256835 |
|
Performance is slow when processing documents with many values in the Application and Submission fields while Enable Correspondence is enabled.
|
DEV-257511 |
|
In some cases, Permalinks and Vault document URLs in uploaded documents do not correctly resolve into relative paths.
|
DEV-257917 |
|
In some cases, Vault fails to import a submission if the ZIP file has an index XML file in a sub-folder of the submission folder.
|
DEV-258873 |
|
For some users, Vault fails to render the index XML file of a submission.
|
DEV-259536 |
|
Correspondence sections are not removed from outdated applications in the Viewer after users update the Document Type field.
|
DEV-182313 |
|
After publishing a Report Level Content Plan, Vault does not remove bookmark links in documents matched to Content Plan Items, and clicking a bookmark link leads users to a Document Not Found page.
|
DEV-224795 |
|
Vault fails to report Rule 15.8 when the Index XML Content Plan Item has Enable Continuous Publishing set to No for an EU submission.
|
DEV-232410 |
|
When the XML Operation field is set to delete, Vault erroneously reports Rules 10.1, 11.1, 11.5, and 11.6.
|
DEV-232665 |
|
Adding overrides on the Common Administrative Information screen and then excluding a value on a Country-specific screen does not update the override count.
|
DEV-233492 |
|
Vault erroneously reports validation Rule 14.BP3 when a user publishes an EU submission that contains specific countries but the XML Operation is set to Delete for those countries.
|
DEV-233811 |
|
In some cases, when publishing a submission with a content plan containing multiple Content Plan Items, Vault only reports validation Rule 16.BP8 instead of both Rule 16.BP8 and Rule 16.BP9.
|
DEV-235239 |
|
Vault does not report Rule 16.BP2 and 16.BP3 when a bookmark target doesn’t exist on a matched document.
|
DEV-235818 |
|
Vault does not report Rule 16.BP2 when a bookmark or link targets a non-existent named destination or document page, or when a bookmark or link is inactive.
|
DEV-235863 |
|
Rule 16.1 is not reported if a version 1.3 PDF is matched to a Content Plan Item and a user sets the Source of Published Document to the Source Document.
|
DEV-235968 |
|
Rule 16.BP4 is not reported when a document matched to a Content Plan Item contains a hyperlink and the PDF zoom level is not set to Inherit Zoom.
|
DEV-236356 |
|
Vault should not report validation Rule 16.BP2 if a hyperlink exists that targets a document matched to a Content Plan Item and the document is updated so the hyperlink points to a new target page.
|
DEV-236638 |
|
If users add or remove links to a document after it has been published, Vault does not add or remove all links in the updated version of the published document.
|
DEV-237117 |
|
During the publishing process, Vault erroneously reports Rules 11.11, 15.1, and 15.BP3 on Content Plan Items with Continuous Publishing and Continuous Validation set to No.
|
DEV-237286 |
|
When the XML Modified File field on the Content Plan Item is incorrect on a published Submission and a user updates the field to the correct value, Vault continues to report the Rule 11.9/11.BP1 validation error.
|
DEV-237290 |
|
When submissions contain Content Plan Items with matched documents in unsupported file formats, Rules 15.1 and 15.2 should only be reported for all unsupported file extensions.
|
DEV-237497 |
|
Users sometimes see a “Server Having Problems” error when importing submission archives.
|
DEV-237554 |
|
When bulk creating registrations, the “Next” button is sometimes greyed out.
|
DEV-237897 |
|
Vault does not generate viewable renditions for XML files.
|
DEV-260458 |
|
When Migration Mode is on, users may be unable to delete study person records.
|
DEV-261168 |
| Description |
Issue No. |
|
In some cases, Country filters do not function properly in the Library.
|
DEV-261796 |
|
When a user navigates to a system view in the Library, such as My Documents, navigates back to the Library, and then performs a search, Vault only searches documents in the previously selected view.
|
DEV-235232 |
|
When users search a mapping table with “Show Lookup Fields” selected, the search is limited to the object name and the hierarchical fields are ignored.
|
DEV-238046 |
|
In the Advanced Search dialog, if a user clicks Clear All, no users appear in the Search by User drop-down.
|
DEV-240007 |
|
Vault does not display search results properly when users initiate a search from a “View All” page (for example, from the View All page within the Document Type filter).
|
DEV-240492 |
|
After executing a web action, performing two searches causes Vault to encounter an error during the second search.
|
DEV-240945 |
|
In some cases, Vault returns no results when users perform an advanced search and add a search modifier, even when results are expected.
|
DEV-242885 |
|
Some users are experiencing inconsistent search results when using synonyms.
|
DEV-245561 |
|
In some cases, Vault fails to return results when users search object records and select the “Include attachments” checkbox.
|
DEV-246275 |
|
After using Advanced Search, the search term persist when the user clicks into a new view.
|
DEV-246550 |
|
When users open a saved view based on Advanced Search results, switch to Tabular View, open a different saved view, and remove a filter, Vault applies the filters from the original saved view.
|
DEV-246564 |
|
View does do not apply correctly when users apply both search modifiers and filters on the same object reference hierarchy.
|
DEV-247356 |
|
When users apply smart filters to a document search and then export the results, Vault drops the smart filters for the export.
|
DEV-248077 |
|
Vault search does not recognize the middot as a punctuation mark within Korean text and thus search results are not as expected.
|
DEV-249705 |
|
Advanced Filter Mode shows “(undefined)” when used with a document field that references the Document Type Detail object.
|
DEV-252509 |
|
In some situations, Searchable Fields are not used properly in search.
|
DEV-253193 |
|
Smart Filtering does not work on custom document tabs.
|
DEV-254632 |