Site users and subject data

Subject IDs are truncated in Oracle Clinical One Platform

Site users: Now, a subject’s full ID (up to 20 characters) is visible in Oracle Clinical One Platform on the Subjects page and on a visit's page. Previously, subject IDs were abbreviated if the ID exceeded 13 characters. (Issue 35171156)

A cleared form cannot be unlinked from another form (former known issue)

Site users: Now, as you clear all data in a form that is linked to another form, the link between these two forms is also removed. Previously, after you cleared all data in a form that was linked to another form, you may have noticed that you couldn't clear the question that determined the linking between the two forms. This issue has been observed with repeating forms.

Retracted workaround: You no longer have to clear questions in a linked form in any particular order. As long as you clear a form its links are also removed. (Issue 34713911)

Cannot add new subjects in a migrated study

Site users and study managers: Now, when a site user attempts to add a new subject in a migrated study, they can create that subject successfully and select a specific subject number for the subject, as well. Previously, even though a study manager configured the Allow Site to Select Subject Number setting to Yes, a site user could still not add a subject in a migrated study. (Issue 34245534)

Rule targets are not updated after starting a skipped visit

Site users, rule designers, and API developers: Now, when a site user enters the visit date for a visit that was previously skipped, any existing custom rules are refreshed and their target fields are highlighted accordingly, depending on the data entered in those fields. Previously, when a site user re-started a skipped visit, they may have noticed that the existing custom rules weren't working in the associated forms anymore. The custom rules may have started working only after a site user refreshed their browser's page.

This issue is now fixed, but it was initially caused by an API refresh operation that did not take place when a skipped visit was re-started. (Issue 34882471)