Stability improvements for integrations

Oracle Clinical One Platform to Catalent Clinical Supply Services: Shipment Receipt and Shipment Dispatch files validation

Integration managers: An error message now appears if names of the Shipment Receipt and Shipment Dispatch files don't match the content in these files. This alerts you to any inconsistencies within the files so you can reach out to Catalent Clinical Supply Services to have them resolved. Oracle Clinical One Integration Hub will not process the files unless values are consistent. The error message contains information about the issue and a solution for it: "Error: One or more files could not be processed due to file name and contents mismatch. If the job detected any other files which were accurate, those will be retained internally but not processed until such time the corrupted file(s) are corrected. Remediation: Correct the corrupted file(s). Oracle Clinical One Integration Hub will then ensure that all files are correctly processed, including any retained files no longer visible on sFTP."

Previously, the job didn't validate that the values present in the file name and file contents matched, since it's not expected that Catalent Clinical Supply Services would ever send corrupted files. Oracle Clinical One Integration Hub now explicitly validates and fails the job if the <Protocol>, <PerformCode>, <RequestorCode> or <ShipmentID> used in a file name don’t match the same tags used within a file. (Issue 30781401)

Oracle Clinical One Platform to Oracle Siebel CTMS: Reports failing due to missing data

When you now remove data from a form, jobs in Oracle Clinical One Integration Hub are no longer failing. The Subject Data for CTMS report is also successfully generated without showing the data you removed. Previously, whenever you removed data from a form, jobs were failing and the report couldn't be generated. (Issue 30893883)