Integrations

A job is failing with an unexpected error message (former known issue)

Integration managers: For an integration between the Oracle Clinical One Platform and Oracle InForm, you can now send data on a subject who previously failed screening. Previously, after you successfully screened a subject and ran the integration, a job would fail with the following message: “The initial submit for a subject is not the screening form.”

Retracted workaround: None. (Issue 34313755)

An integration may not send screening data to Oracle InForm

Integration managers: Now, for an integration between Oracle Clinical One Platform and Oracle InForm, data related to screen failures is sent to Oracle InForm, as expected. Previously, you may have noticed that jobs associated with an integration were marked as successful in the system, even though the appropriate screen failure data wasn't even sent through the integration. (Issue 34145697)

Oracle Digital Gateway Builder integrations cannot be properly configured

Oracle Services: Now, you can configure and run integration with the Oracle Digital Gateway Builder applica

Unable to properly view a job’s details in Oracle Clinical One Digital Gateway (former known issue)

Integration managers: Now, while an integration is running, you can properly view details about its associated jobs on the Job side panel. Previously, the Jobs side panel did not expand enough for you to view any of the details of a job.

Retracted workaround: You no longer have to check your browser’s resolution settings and adjust them in a way that will make the Jobs side panel expand. Job details display as expected already. (Issue 34276537)

Treatment arm details cannot be integrated with Oracle InForm (former known issue)

Integration managers: Now, for an integration between the Oracle Clinical One Platform and Oracle InForm, you can integrate treatment arm details for a randomized subject, as expected. Previously, when you attempted to do this, an error message stated that it could not find certain parameters to synchronize the data between the two applications. This issue was caused by a misconfiguration between parameters in the integration configuration file.

Retracted workaround: You no longer need to use the GUID of the treatment arm to ensure that data is synchronized between the two applications. For more information on this fixed issue, contact your Oracle Project Manager. (Issue 34334378)