Site users and subject data

Signing subject visit fails if screening starts and completes in different study versions

Site users: Now, signing data is error-free, and the status is updated in the correct study version. Previously, signing subjects’ data failed whenever they were screened in a different study version. You could not sign data as expected because the screening data was associated with the wrong study version. (Issue 34625379)

Coded terms are not properly formatted to be send to Oracle Central Coding (former known issue)

Site users: Now, you can no longer copy and paste coded terms into a repeating form table cell, to avoid any potential errors in the coding process. Previously, not only did the application not remove any extra spaces that you added into the form, but it also did not prevent you from copying and pasting data that must have been integrated with another system. Because extra spaces were not cleared or avoided, the integration of those coded terms with Oracle Central Coding may have failed.

Retracted workaround: Although this issue is now fixed, we recommend you avoid adding coded terms straight into the repeating form table. Instead, open a repeating form instance in a separate dialog and enter your coded terms. (Issue 34027154)

New validation error message for exceeding a text field's character limit

Site users: Now, when you exceed the character limit of a text field in a form, an appropriate validation error message is displayed. The new validation message states that the value cannot exceed a specified number of characters in length. Previously, the validation message stated that the value in that field must be less than a specified number of characters. (Issue 34151882)

Cannot update kit status from Expired to Misallocated (former known issue)

Site users and sponsor users: Now, on the Site Inventory tab, you can update an expired kit's status to Misallocated. Previously, you did not have that option. When clicking Update Kit, the Misallocated option was not displayed. (Issue 33920822)

Frozen icon is missing from a frozen adverse event

Data managers: In Oracle Clinical One Platform, on the Subjects page, every adverse that contains frozen data is marked with the Frozen icon, as expected. Previously, even though data was frozen in an adverse event (and this status was reflected in reports in both the Oracle Clinical One Platform and the Oracle Clinical One Analytics), the Oracle Clinical One Platform UI did not display the expected icon on the visit card. (Issue 34217709)

Manually entering a date does not work in a repeating form table (former known issue)

Site users: Now, when Japanese is set as your preferred language in the application, and you attempt to manually enter a date in the repeating form table view, the date remains the way you set it. Previously, you may have noticed that the date was automatically set to the current date.

Retracted workaround: You can always update a date field either by using the calendar widget or opening the repeating form instance in a new pop-up window. (Issue 33698622)

Dynamic form not displayed when multiple answers are selected (former known issue)

Site users: Now, when a one-section form contains multiple questions with a Show Form dynamic rule that is supposed to display the same dynamic form, this configuration works, as expected. The same dynamic form can be dynamically displayed when multiple determining questions are answered. Previously, this was not possible.

Retracted workaround: None. (Issue 33282026)

Field incorrectly displaying as frozen

Site users: Now, fields not frozen by a user do not appear as frozen in the Oracle Clinical One Platform user interface and audit trail. Previously, a field could appear as frozen in the user interface even when the field was not frozen by a user.

Retracted workaround: You no longer have to manually freeze the field again, and then unfreeze it. (Issue 34086892)