Integrations

Study version retrieval includes deleted data elements

Now, deleted data elements are correctly included when determining the study version for a subject event, ensuring consistent and accurate version handling, preventing validation errors during import, and supporting edge cases where deleted elements are involved.

(Issue 38451978)

Integrations are not available after being retired

Now, integrations remain disabled when its integration group is retired, even after the study is taken out of maintenance, ensuring consistent management of integrations during study maintenance and retirement.

(Issue 38581061)

Data processes correctly for CTMS integrations

Now, the system no longer triggers unnecessary data reprocessing when performing locking, freezing, verifying, or signing actions on subject visits, also allowing integration jobs to process data correctly and efficiently.

(Issue 38155037)

CTMS subject visit integration jobs complete successfully

Now, the system uses the correct visit study version, rather than the subject study version, to determine visit branch information, ensuring accuracy in visit schedules and branch assignments.

(Issue 38418928)

MUL integration now properly assigns users to appropriate sites based on compounding site logic

Now, the Master User List (MUL)—User Integration can process site numbers that include a trailing alpha character (for example, 1004A) by ignoring the alpha suffix and assigning the user to the corresponding primary numeric site (1004).

For existing integrations: To apply this fix, update your MUL integration configuration to set ProcessCompoundSite to true.

(Issue 38921650)