Site users and subject data

Unit of measure values save and populate correctly

Now, unit of measure values for number-type questions, number questions within a Question Group, and age-type questions are saved and displayed correctly in the Answer History, ensuring complete and accurate data during subject screening.

(Issue 39175694)

Verify, Freeze, and Lock options remain disabled until the repeating form dialog loads completely

When navigating to a repeating form instance using the view in form button on the query list page, the verify, freeze, and lock options now are remain disabled until the repeating form fully loads.

(Issue 37212352)

Queries are only triggered for non-deleted repeating form instances

Queries are now triggered only for non-deleted repeating form instances, ensuring that there are no unnecessary auto-queries created that require manual closing.

(Issue 37771932)

Subject number assignment at screening reliability improved

For studies using the Assign Subject Number at Screening setting, Clinical One Cloud Service now ensures subject number assignment happens only after all designer-level rule validations pass.

• When you click Submit during screening, the system automatically confirms there are no designer-level rule validation errors.
• If any validation errors are found, the system guides you to resolve them first—screening is paused until corrections are made.
• A subject number is generated and assigned only after the validation errors are corrected, helping maintain clean and consistent subject identification.
• An informative message at the top of the page highlights that validation errors must be addressed before screening can be completed and a subject number assigned.

  This fix helps promote higher data quality and reduces rework by keeping screening and subject number assignment aligned with your study's configured rules.

(Issue 39219300)

API query updates validate the visit instance correctly

The system keeps queries specific to each visit instance, so if there are two unscheduled visits and you open a query on the Date of Assessment , as an example, for the first visit, updating the Date of Assessment for the second visit will not impact the query on the first visit. This behavior was only applies with API-driven updates.

(Issue 36862807)