Auto-lock failure notifications were triggerred without auto-lock set

The system now correctly avoids sending Auto-lock failure notifications when no auto-lock is set up for a visit. Previously, the system mistakenly triggered these notifications even when there was no auto-lock rule configured in a visit, due to an error that wasn’t properly handled. This caused unnecessary failure alerts under those conditions.

(Issue 37664506)

Auto-lock failure notifications sent due to insufficient retries

Now, the application tries 3 times to determine whether there are any Auto-lock validation rules configured for a visit. Previously, if no rules were configured for a visit the application was sometimes unable to determine this with only a single retry and would send an Auto-lock failure notification to designated users.

(Issue 37644881)

Some Auto-lock failure notifications may be sent to the wrong users

Going forward, Auto-lock failure notifications will only be sent to users with the Lock Subject Data permission who are specifically assigned to a site in the corresponding study mode (Testing, Training, or Production). Previously, these notifications were sent to a broader group of users, including those not directly associated with the site in the specific study mode. For example, a user with the appropriate permission, assigned to site A in Production mode also received an Auto-lock failure notification for site A in Testing mode.

(Issue 37669116)

The User Assignment report retrieves incorrect data when generated

Now, when you generate the User Assignment report, it retrieves all the correct data and does not include duplicate data.

(Issue 37330486)

Submission PDF archives generate with failures

Users no longer encounter system errors, and Submission archive requests complete successfully. Previously, the blank forms included in the request could cause a max connection limit to be reached, leading to submission requests failing.

(Issue 37538595)

CO:extension data isn't visible in the clinical data and metadata extracts

We fixed an issue where CO:extension data was not showing up in the clinical data and metadata extracts, even when the include Co:Extension flag was set to True. The applied fix ensures that CO:extension data is visible and you can successfully extract data in an ODM-XML format.

(Issue 37522360)

The Kit Chain of Custody (Blinded and Unblinded) reports are failing

The Kit Chain of Custody (Blinded) and Kit Chain of Custody (Unblinded) reports now generate successfully when kit numbers contain alpha and numeric characters. Previously, the reports would fail due to the alpha characters.

(Issue 37257750)

Training reminders are being sent when training is disabled

Only when you enable the Product User Training toggle under Global Settings will Oracle Clinical One Platform training reminders be sent. Previously, automatic training reminders were sent to study users even with the toggle turned off.

(Issue 36515001)

Oracle CRF Submit shared server bug fix details