Integrations

Form data fails to load in Oracle DMW

Now, for an integration between the Oracle Clinical One Platform and Oracle DMW, data for repeating form records loads completely without timing out.

(Issue 36176038)

Standard reports fail to generate when initiated during an Oracle Clinical One Platform upgrade

(Details for bug 35239014) Standard reports such as Subject Visits, Subject Data, and Subject Events now generate successfully when initiated during an Oracle Clinical One Platform upgrade.

The reports previously failed during an upgrade because a particular file was updated before the metadata in the database, resulting in incompatible files and report failures. In future upgrades, the file and metadata will be updated together, ensuring the file is always compatible.

Note:

The fix for bug 35239014 also resolved bug 35237829 related to CTMS report integration failures.

(Details for bug 35237829) The CTMS report integration initiates a call to the reporting service to generate the Subject Data for CTMS standard report. The integration then places the output file on the Oracle sFTP server for customer consumption. Bug 35239014 caused report failures for reports generated manually in the user interface and when initiated by the CTMS report integration.

(Issues: Fixing the base bug 35239014 (incompatible file issue) also resolved bug 35237829 (CMTS report integration failure).

The lab integration fails if the study version in the request body does not match the production version

The request body for the lab data intake integration now contains the correct study version, ensuring the job completes successfully.

Previously, the job would fail if a new study version was created and applied to a site while subjects were still active in the visit where the study version change was applied. A study version mismatch between Oracle Clinical One Platform and the integration request body caused the integration failure.

(Issue 36695050)