Fixed Issues in 20R1.4 ReleaseRelease Date: July 17, 2020
This week's release includes fixes for the following issues:
A * next to the issue number denotes an internally found defect filed during the development of Limited Release features.
|When a custom object includes a currency-type field, automated deployments including that object's configuration fail.
|When a Vault includes two custom objects, and those objects reference each other using an object reference field, deployments fail.
|If a deployment occurs after upversioning, duplicate records are created in the Item Definition and Synonym List Objects.
|During study creation, users may not be able to select certain vaults when creating their production environment.
|Vault no longer includes Do Not Autocode Lists or Synonym Lists in study deployment packages.
|Users receive a server error when deploying certain studies.
|Deployments fail inexplicably for certain vaults.
|Layouts in Studio are not removed when deploying a package that deletes an item group along with its associated layout.
|Prospective and retrospective amendment jobs stop at the first Casebook that cannot be successfully amended, instead of processing all selected Casebooks.
Clinical Query Language (CQL)
|CQL statements that use IS and IS NOT in the WHERE clause return an unknown column error.
|Filtering on @Form variables only works with a single Form.
|SELECT DISTINCT for @Form.Status returns non-unique instances of Form Status.
|SELECT DISTINCT returns duplicate rows.
|Ordering by any Items within a repeating Item Group may not return results in the expected order or paginate correctly.
|On a core listing, if a user comments out the original CQL statement and then adds SHOW FORMs, Workbench clears the CQL from the CQL panel when applied.
|CQL returns an unknown form error when the statement includes @HDR only aliasing.
|CQL returns a mismatched input error for statements that include the LEFT() function.
|CQL may return a "Duplicate form context" error on some listings after EDC import.
|After upversioning a MedDRA form, users may receive a server error when navigating to the Code Request listing page.
|The Reconstitute Code Requests job updates the Last Modified Date on all Code Requests.
|The user's private key used when creating a Link-Form definition corresponds to the wrong item location if the item belongs to less than one form.
|In certain cases, some forms are unable to generate a Code Request.
|Users are able to post queries on grouped coding requests.
|Users receive a server error when attempting to code certain Verbatims.
|Vault may show the Reset Entered Values dialog twice when a user navigates to and clears the controlling Item using keyboard shortcuts.
|When using version 2 of the data entry UI, Vault allows users to edit a form while in signature mode.
|Vault doesn't sort Forms alphabetically in the Link and Copy dialog.
|The user receives a server error when using progressive display in the Data Entry tab and unchecking the criteria that is dependent on progressive display. The form is then unable to be saved.
|Certain users may be unable to enter Event Dates for repeating Events because they don't have edit permissions on the Facade field. In this release, any user with permission to do so may enter an Event Date.
|Users are able to add events to Event Groups that are unscheduled and have a repeat maximum value of "1."
|Users receive an error when attempting to complete Adverse Events forms.
|Header items do not appear in the Data Entry tab.
|Composite Items are missing from item groups when the item group has been added to the form via progressive display.
|Users receive a server error when attempting to open a Subject that's been transferred.
|Workbench can't match Events based on External ID when the External ID uses escaped characters.
|For 3rd party data import packages that match on event definition Names and the Names aren't normalized, import fails.
|A user may receive an error when creating a repeating Item Group within a Form added by another user via the Create Casebook API.
|The Open Query API can't create a query on on Item when the Form is blank.
|The user should receive a warning message when attempting to clear signatures on locked forms.
|The Veeva Learning integration can only be enabled in non-development environments, but the Study Configuration record can't be edited in non-development environments.
|With the CDMS/CTMS spark connection, CTMS doesn't receive the SDV Complete Date.
|The Reconstitute Code Requests job fails when Items are loaded via Vault Loader.
|Under certain circumstances, Lead Data Managers can't run the Delete Site Data job.
|In some Studies, the JReview® Listing job status is stuck as "In Progress."
|The Data Listing job fails when run for certain forms.
|The JReview® job fails for JReview® users.
|The "EDC Review State" job fails with errors.
|Running a Data Listings job results in a CSV with duplicate coding columns.
|Vault fails to generate the User Activity Report job for some users.
|The ability to generate blank and detail PDFs isn't controlled by the Generate Blank PDF and Generate Detail PDF Study Role permissions in vaults with Role by Study enabled.
|Running validation updates rules with incorrect values when marking them as valid.
|Queries continue to fire on forms that have been reset.
|Users receive an unexpected error when responding to or closing queries created in EDC.
|If progressive display removes an Item that has an open query, and then someone runs the Query Rules job in the study, Vault shows the Open Query status badge on the Form, even though there is no open query.
Reports & Dashboards
|Users receive an error when attempting to run a Diff Report.*
|If an admin creates a user-managed Group that automatically includes the Security Profile for a newly added custom Study Role, and then renames that custom Study Role, Vault creates a duplicate Security Profile.
|Standard Application roles with the "Edit Form Linking" permission can't view form links.
|Renaming a role causes an exception error if the application role doesn't exist in the old ARF record.
|Users receive a server error when attempting to sort Rules by Expression in the Copy from Study dialog.
|When the rule expression contains a syntax error, the Save Now link in the View Bindings callout doesn't display.
|Progressive Display columns continue to be displayed after being deleted in SDS.
|Reciprocal mode does not execute properly.
|Users are unable to save a Rule after updating.
|The source Form name is visible in the SDS Rules tab for copied rules.
|In certain cases, dynamic forms aren't added in accordance with certain rules.
SDV & DMR
|SDV dates are not calculated properly after a form is reviewed.
|Items that are set to "No Review" in a DMR plan are still available to review.
Search & Filter
|In the Review tab's Subject listing, the filters for Frozen and Locked status don't filter the listing.
|There is no way to in the Studio UI to delete Progressive Display configuration for this Item. With this release, we added the ability to delete Progressive Display configuration for an Item.
|If a user attempts to import a study that contains Email Groups and Form Links into a study on an earlier version, or compare those two studies, the job fails.
|Version comparison may not include all differences between Coding configuration for a Form.
|The Rules worksheet of the SDS isn't sorted alphabetically by Name.
|Synonym Lists and Do Not Autocode Lists are no longer included in version comparison, the SDS, or Copy from Study.
|The version comparison job may fail when the version removed and then re-added identical Progressive Display configuration for a single Item.
|In certain circumstances, Vault may fail to generate the Study Design Specification.
|Annotated PDFs don't include all Forms when multiple Forms share the same Name. The PDF only includes the first Form with that Name.
|In some cases, users may receive an error when attempting to copy Forms from another Study.
|With this release, we removed the 5 form limit from Form Link configuration, and users may now link to non-repeating Forms.
UI & Performance
|In Studio > Settings, moving the cursor away from the Signature Definition Actions menu closes the Actions menu.
|In the Review tab, the Change Indicator is missing in forms with repeating Item Groups with two-column layout items.
|The Progressive Display Indicator doesn't display in Internet Explorer™.
|Users receive an error when comparing the SDV completed date for a non-required form.
|When copying a form from a previous study, the progress bar freezes and the user must refresh the page to see that the form has been copied.
|The query comment window overlaps with the text when the user attempts to resize the window to view all text.
|Users receive a server error when copying rules from a study then unselecting that study.
|Users are able to add new sections while using Progressive Display when all items in a repeating item group use a controlling item.
|Users receive a server error when attempting to access forms with a Lab field.
|Standard roles can "edit" but not "view" Form Linking selections in the Data Entry tab.
|Users with a CRA permission can't see the review status in the Review tab on Forms/Events after performing SDV.
|Users using Chrome® receive a server error when attempting to access Study Sites in the Review tab.
|New repeating forms are missing Item Labels in the Data Entry tab.
|Items marked as "Read-only" or "Derived" are not hidden in Progressive Display.
|Users can't select a value from a codelist when navigating with the tab key.
|Workbench may take a long time to load Listings for Forms containing many repeating Item Groups.
|Items in repeating Item Groups that are configured as hidden are shown via Progressive Display.
|Certain users are shown a blank page when navigating to the first event in any given subject in the Review tab.
|Codelist objects with coded values that contain special characters are displayed incorrectly with progressive display.
|Users receive an error when attempting to generate an SDS from Sandbox.
|Users receive a server error when changing data in Studio that results in an event being rolled back.
|Users receive a server error and a blank page when attempting to open forms in Review Assessment.
|Users are unable to select an unscheduled Event Group via the dropdown menu in the Rule Editor.
|In the Review tab, the Event Date label doesn't appear on the correct panel.
|PDFs generated in Studio do not show "Display Override" Form names.
|Vault does not enter Signature mode when prompted by the user.
|Inactivating Query Rules in EDC Tools results in an error.
|Clicking on a repeating form within an Event that is currently selected in the Review tab does not scroll to the selected form.
|Longer Codelist Item labels don't wrap inside of the drop-down menu.
|In the Rule Editor, when using the Set Subject Status action, Vault shows "Event" for "Set status change date to", even when the rule is using an Item as the status change date.
|Users receive an error message when resetting a Baseline Event in the Data Entry tab.
|The Review page doesn't load for users with the Lead Data Manager study role.
|The property panel in Coder doesn't load in Data Model 2.0.