A visit branch is not triggered as expected

Now, the expected visit branches are displayed when the appropriate data is collected for the triggering question, as configured in study design, for the Form Item Settings field. Previously, when data was updated in a cycling branch visit to exit the branch, the specified branch was not shown as expected. This issue was caused by the system prioritizing the visit order and branch order in the study's design over the specified form item triggers.

(Issue 37777103)

Withdrawal visit is displayed for a complete subject (former Known Issue)

After you withdraw a subject from a study, undo the withdrawal, and then set the subject's status to Complete from the Manage Subjects menu, the Withdrawal visit no longer appears in the Next Visits column.

(Issue 33131649)

Dynamic visits display incorrectly

Now, a dynamic visit that is triggered from an optional visit, after a subsequent visit has been started, displays as expected when the triggered visit is not complete.

(Issue 36846469)

Visit status remains In Progress after a subject's status is updated to Complete

Unscheduled visits update to the correct status after a subject has finished their Completion visit and their status has been updated to Completed. Previously, when a subject was marked as Complete, the unscheduled visits remained in a state of In Progress.

For additional information, see Manage subject event related data and visits better.

(Issue 34663292)

Subjects become unverified after a withdrawal visit is undone

After Undo Withdrawal is performed for a Withdrawal visit and the visit is hidden from the visit train, a subject's status remains verified.

For additional information, see Manage subject event related data and visits better.

(Issue 36908511)

Withdrawal visits with cleared data that are not visible in the User Interface (UI) are signed by the system

Now, only the respective visits for screen failed subjects are signed successfully. Previously, withdrawal visits containing cleared data were signed by the system, even if they were not visible in the UI.

For additional information, see Manage subject event related data and visits better.

(Issue 37222257)

Users encounter an error when attempting to close a query from the Queries side panel for Withdrawn and Completed subjects

After processing the undo withdrawal and study completion actions for a subject, you can now successfully close the queries you opened and answered during subject withdrawal. Previously, you would encounter an error when trying to close the query.

The problem also arose when a user initiated a study completion visit, which included data and a query, and then withdrew the subject.

In both cases, the DC POST API did not return visit withdrawal or completion details, resulting in the inability to close the query.

(Issue 36874703)

Visit branching is not based on the last registered visit (former Known Issue)

Returning to a previous visit and updating the answer to a branching question no longer results in the incorrect branch being triggered for a subject.

(Issue 35358331)

Forms with more than two hundred (200) questions can encounter issues

Now, forms with more than two hundred (200) questions no longer encounter issues with Oracle Clinical One Analytics datasets and downstream applications like Data Management Workbench (DMW).

(Issue 37615271)

Rule does not execute properly for repeating form items

Now, when a query is created for an initial repeating form item, then a second repeating form item using an identical Assessment Timepoint value is created, the initial query is closed as a result of the rule execution. Previously, the executed rule did not close the target query and an additional query was created.

(Issue 37583470)