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)