Fixed Issues in 24R2.3 Release

Release Date: September 27, 2024

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.

Blank & Detail PDFs

Issue Description Issue No.
Detail PDF jobs with audit fail with an error. VDC-165339

CDB - Checks & Queries

Issue Description Issue No.
CDB doesn't set the @QRY.OriginSystem to "CDB" for queries created in CDB for OpenEDC studies. VDC-165853
Queries previously missing an appropriate value for @QRY.OriginSystem now have the appropriate value. VDC-166277
When incremental import is enabled, checks only run after the full, daily incremental import. VDC-166918*
Checks don't re-run after the import of a third-party data package. VDC-167078*
In some cases, the 3PD check fails to execute if the last execution date exceeds 12 hours. VDC-167305*
In some cases, a 12-hour check fails to run for the Review Dashboard. VDC-167331*

CDB - CQL

Issue Description Issue No.
CQL doesn't return the appropriate error message when a Core Listing has 410 or more columns. VDC-162087
For repeating Event Groups, the attribute @HDr.EventGroup.Label in SYS_FORMS shows the Display Label instead of the Repeating Event Override. VDC-164208*
For studies using labs, CALL Sys_ILB returns an unknown column error. VDC-165057*
CALL Sys_Forms doesn't return the data for @Form.SDVOverridePlan or @Form.DMROverridePlan. VDC-165239*
The Last Modified Date for an Event Date is labeled as Event.EventDateModifiedDate instead of Event.EventDateLastModifiedDate. VDC-165372*
In incremental-enabled studies, CQL may not return all possible rows when filtering on @Form.SeqNbr. VDC-167218*

CDB - Export

Issue Description Issue No.
Export package generation may fail unexpectedly. VDC-165308
When incremental import is enabled, scheduled exports may not run as expected. VDC-166919*

CDB - Import

Issue Description Issue No.
The Imported Date may be incorrect in the audit log. VDC-161107*
Incremental imports may get stuck in the Pending status. VDC-162946*
The Last Design Change date isn't updated after a new deployment. VDC-163545*
The datetime displayed for incremental data is the datetime in the user's time zone VDC-163711*
In incremental-enabled studies, CDB sends a package approved notification when reprocessing a third party data package succeeds. VDC-165221
Incremental import fails when the Lab Item's Item Definition has a lower precision than is defined in the Analyte. VDC-165318
Reference data imports may fail unexpectedly in OpenEDC studies. VDC-165672
Listings referencing third party data may be unexpectedly marked as invalid in incremental import studies. VDC-166954*
Incremental import may not ingest frozen, locked, or signed statuses correctly for log-type Events. VDC-166962*
Upgrading to incremental import may decrease the number of rows returned by a check listing. VDC-166986*
Incremental import may not ingest frozen, locked, or signed statuses correctly for log-type Events. VDC-167003*
Incremental import may take longer than expected. VDC-167895*
Values may change unexpectedly in columns related to codelist item Labels in incremental import studies. VDC-167971*
For incremental import studies, when a form contains only a repeating item group, form review status and review dates are blank. VDC-167995*
The Reset and Complete filter buttons are missing in Import > Packages for incremental import studies. VDC-168152*
When there is an in progress swap, and the study is upgraded to incremental imports, the first full ingestion uses that same swap. VDC-168438*

CDB - Listings

Issue Description Issue No.
The Last Updated Date field for Core Listings shows the date of the last full package instead of the last incremental update. VDC-163940

Clinical Reporting

Issue Description Issue No.
Translated lab unit values may not match the data from the Study Data Extract in EDC. VDC-167931

Coding

Issue Description Issue No.
In some cases, queries are displayed with the "Site Responded" status in Coder, even though the system message says the query status is "Closed". VDC-167019
In some cases, queries are displayed with the "Site Responded" status in Coder, even though the system message says the query status is "Closed". VDC-167019

Data Entry

Issue Description Issue No.
Users shouldn't be able to mark a form with externally-owned data as ILB. VDC-167276

Data Loader

Issue Description Issue No.
If a user copies a Form from another Study, then creates a data loader configuration, they will receive errors when accessing that configuration after deleting a unit-type Item from that Form. VDC-164813*
Users may be unable to map unit-type items. VDC-165016*

Deployment

Issue Description Issue No.
In some cases, study deployment can unexpectedly fail in the Dev environment. VDC-166418*

Developer Features

Issue Description Issue No.
CDB API calls may take longer than usual. VDC-165670

Integrations

Issue Description Issue No.
In some cases, a CDMS Vault Training course or curriculum could have an empty completion date, despite having the completed status. VDC-168231*
Users with multiple user accounts with the same email address may encounter an error during enrollment reconciliation for CDMS Vault Training. VDC-168232*

Jobs

Issue Description Issue No.
The Audit Trail Export by Study job fails in some cases. VDC-165299
When a study has a deleted Lab Location, the Audit Trail Export job fails. VDC-165328
Some users encounter failures when attempting to run the User Activity Report job. VDC-165687
In some cases, the Difference report includes unexpected differences. VDC-168312

Labs

Issue Description Issue No.
In some cases, the Update Outdated Lab Normals Job does not update records as expected based on the Age Ranges. Some Normal records that were previously not updated may be updated after this fix. If those Normals are in SDV, DMR, or Signed status, then the status will break the next time the Update Outdated Lab Normals job is run. VDC-167213

Localization

Issue Description Issue No.
In some cases, certain words or phrases are translated incorrectly when translating to Chinese in Data Entry. VDC-150797

Publishing Validation

Issue Description Issue No.
The Casebook validation error for invalid rules will be removed for StringArray data type for certain functions. VDC-166581

Review Plan Assignment

Issue Description Issue No.
Creating a new Review Plan Assignment Rule based on Subject Status should clear previous Review Plan Assignments. VDC-165152*

Role & User Management

Issue Description Issue No.
With this release, users require the API Access permission to access CDB Workbench. VDC-166782*

Rule Execution

Issue Description Issue No.
In some cases, the system does not inactivate a Protocol Deviation record even when the conditions for the Protocol Deviation rule evaluate as false. VDC-164151
In some cases, users encounter an error when running Protocol Deviation rules. VDC-165813
Some users encounter an error when running dynamic rules in batch mode. VDC-168361

Safety Integration

Issue Description Issue No.
Safety cases aren't marked with the Nullified status after the late acknowledgement is processed. VDC-161608*
When the Safety integration settings are configured with Use Screen / Entered Value, the Subject JSON file should also display the datetime as entered, rather than in UTC. VDC-162147*
When a user attempts to edit the Safety settings, Vault clears the Study Name and Sponsor Study Number values upon save. VDC-165133*
E2B package generation may fail unexpectedly. VDC-165212
The Safety Value (To) column in the Safety Form Configuration tab of the SDS export does not display the mapped Vault Safety fields even though they are available in the UI. VDC-166392
The Safety Follow-up Scan doesn't include all cases. VDC-166446*
In some cases, when an Adverse event is submitted from Vault EDC to Safety, when the inbox item in Safety is promoted to a Case, the New Info Date and the Receipt Date have different timestamps. VDC-166863
When using the Vault Safety EDC Connection, Vault doesn't save changes to safety study settings after the user clicks Save. VDC-167298*
For lab items, result text may be missing the modifier. VDC-167508*

SDS & Annotated PDFs

Issue Description Issue No.
Coding related items in Study Data Specifications should have the same ordering as shown in the coding UI. VDC-165894
The SDS may not have the correct information for safety-related study settings. VDC-167310*, VDC-167315*

Study Administration

Issue Description Issue No.
In some cases, when a study name contains special characters or spaces, the Enable CDB Incremental setting does not appear in Study Settings, even though the feature is enabled for the vault. VDC-165648*

Study Data Extracts

Issue Description Issue No.
In some cases, coding item columns are missing for SDE jobs. VDC-164579

Study Design

Issue Description Issue No.
When copying forms with safety configuration, the form order is incorrect for study drug forms. VDC-162397*
In some cases, changes to Open Query configuration for Event Window in the Properties panel do not save. VDC-162476*
In some cases, item configurations are not copied as expected. VDC-164864*
Some users encounter an error when attempting to copy event groups from one DEV environment to another. VDC-164870
The SDTM name property is not displayed consistently at the item level in the Study Design Specifications export. VDC-167563
In some cases, the system does not update event windows as expected after a retrospective amendment is performed. VDC-167829

UI & Performance

Issue Description Issue No.
In some cases, copy forms operations fail. VDC-165449*
Only the first page of subjects is sorted when sorting by subject in the Subjects grid. VDC-165547
In some cases, cross domain SSO users encounter an error when attempting to log in. VDC-165878
In some cases, Casebooks take an overly long time to load in the Review tab. VDC-166120
In studies using incremental imports, certain listings may take longer to load than before incremental import was enabled. VDC-166575*
Some users encounter a server error when entering event dates. VDC-166807
The "Custom" label is not displayed when a custom date range is selected for the Data Change Extract job. VDC-166823*
In some cases, very large forms fail to load. VDC-167159
In some cases, users are unable to delete a site even though it does not have any subjects. VDC-167410
Users are shown an incorrect error message when manually entering an event date in Data Entry. VDC-167713