Integrations

Incorrect values display in Oracle DMW for Advanced Study Version (ASV) changes

Now, ASV changes are correctly applies only to the latest active study version when moving from Test to Active mode, ensuring the correct values are displayed. Previously, when moving a study from Test to Active mode, ASV changes were incorrectly applied to older versions, resulting in data discrepancies and incorrect values displaying in the active study version.

(Issue 38278228)

Multiple visit ID instances appear in Data Capture Service

Now, the system ensures visits records are processed and updated correctly. Previously, the system retrieved incorrect study version data, resulting in multiple IDs generated for the same visit and visit status inconsistencies.

(Issue 38120683)

Verbatim and context item statuses are marked incorrectly

Both verbatim and context items are now validated together successfully when coding returns are processed. Previously, when verbatim or context items were updated after form submission, and before coding returns completed, the items were marked with an incorrect status.

(Issue 37010117)

Large CSV files now reliably sent to SFTP for each country

The VCT integration now successfully sends large CSV files to the SFTP location for every country, as expected. Previously, files over 20MB could not be sent due to a system limit, causing output deliveries to stop unexpectedly and disrupting shipment operations. This fix increases the supported file size, ensuring that even large files are consistently transferred. As a result, operations and downstream integrations continue smoothly without missed output or manual intervention.

(Issue 38259231)

Emails now sent to correct depot address despite extra spaces

Emails triggered by the Almac integration are now correctly sent to the intended depot address, even if the Depot ID from the Oracle Clinical One Platform includes extra spaces. Previously, if a depot's name had a trailing space, the integration couldn't match it with the ID in the code list. As a result, emails were sent to a default address instead of the depot's address. The fix ensures that depot IDs are now "trimmed" before matching, allowing proper email routing.

(Issue 38172469)

SAP Shipment Rejection integration cannot process XML files

XML files are now successfully processed even if their namespace differs from the expected format. Previously, files with a valid structure but mismatched XML namespaces caused de-serialization errors during integration - such as “unexpected element” errors - leading to failed processing. The fix ensures that the XML namespace is ignored during de-serialization, allowing integrations to continue working as long as the file structure remains unchanged.

(Issue 37815624)

Withdrawal dates and the reason for withdrawal do not integrate with CTMS

Now, when a subject is withdrawn from a study, the date and reason for withdrawal, entered by the user performing the withdrawal visit in Oracle Clinical One Platform, integrates successfully with CTMS.

(Issue 37878378)

CTMS Site integration fails when the country name contains a comma

A site associated with a country that contains commas in their name is now successfully integrated into Oracle Clinical One Platform. For example, if a site is associated with "Tanzania, United Republic of", the integration job no longer fails with a site status code of 400, stating that no country was found.

(Issue 37426697)

Integrated forms that include instructional text create system error

Now, instructional text is hidden for integrated forms. Previously, forms integrated to Oracle InForm that included instructional text would receive a system error.

(Issue 37750681)