Site users and subject data

Characters are missing when typing quickly in text fields

When typing quickly in text fields, all characters are now captured correctly. Previously, some characters would be lost when typing at high speeds, especially when the network connection was slow. This issue only occurred when typing quickly and was not reproducible with normal or moderate typing speeds.

(Issue 35763244)

Subject History timezones display incorrectly

The Subject History sidebar no longer displays time zones for actions related to screen failures.

(Issue 36836388)

Indication and Route of Administration are not present in Oracle Central Coding (former Known Issue)

The Indication and Route of Administration values are now available in Oracle Central Coding.

Retracted recommended action:
  1. A site user must do one of the following to resolve the immediate issue of missing context item values in Oracle Central Coding:
    1. Clear and re-select the option (accept Other, see option 2) originally selected from the drop-down.
    2. Clear and re-enter the value entered manually when Other was originally selected from the drop-down. You do not need to re-select Other.
  2. To ensure you don’t encounter the same issue, implement the following study design change:
    1. Create a new calculation rule to populate a new read-only field for the verbatim term.
    2. Map the new read-only field as a Oracle Central Coding question on the Advanced sidebar. For more information, see task 1 in Create a coding question and coding target field.

      Doing this ensures the data entered for the verbatim and context values are copied to the read-only fields at the same time, resulting in all data being collected when the Oracle Central Coding integration process runs.

(Issue 37044789)

Incorrect user role displays on the Query List page for closed queries

Now, the Query List page displays the correct user role for manually closed queries. Previously, when a query was closed, the role of the user that answered the query was displayed..

(Issue 37649070)

Coding target items are not cleared when the verbatim term is cleared

Now, when a verbatim term is cleared, the data populated in the coding target items is cleared as well.

(Issue 37570275)

Subjects are left unsigned due to Sign API code

Now, all items for a subject are signed and remain signed when a signature is applied. Previously, the API code responsible for signatures was referring to the Study Version instead of the Associated Study Version, causing newly added items for a subject to be left unsigned.

(Issue 37330940)

An error occurs when attempting to update the subject status to withdrawn for a previously withdrawn subject

When users attempt to change a previously withdrawn subject's status to Withdrawn, they encounter a new validation error, indicating an invalid subject state transition.

New validation error text: Invalid State Transition from Withdrawn to Withdrawn.

Previously, the system presented an incorrect error, causing confusion.

(Issue 36180645)

Users encounter system errors when submitting data meant to trigger dynamic forms

Now, only one form-level SDV status record exists per form, so there is no longer a conflict when a dynamic form is hidden. Previously, if a user navigated between visits for a subject too quickly, duplicate form-level SDV status records could be created. These duplicate records would cause an error in Oracle Clinical One Platform if a dynamic form with duplicate records was subsequently hidden.

(Issue 36113979)

Parent topic: Fixed issues