Forms, visits, and rules

A Subject's visit data of event type Visit_Inserted is not reaching Data hub

Now, Visit_Inserted records for new visits applied to a study via advanced study versioning (ASV) are inserted into the DC_VISITS_INFO table in Data Hub, making the data available in Oracle Clinical One Analytics.

Retracted workaround: None. (Issue 35560725)

Subject PDFs generated under the Archives tab include incorrect usernames

Now, when multiple users sign forms in a single visit, subject PDFs generated under the Archives tab show the username associated with the signing action. Previously, the username of one signatory showed for all form signatures.

Retracted workaround: None. (Issue 35692719)

The next logical visit does not appear after answering a branch visit exit question

Now, when the rule execution occurs only for the current visit and does not impact the previously calculated or answered target questions in the previous visits, no issues are observed, and the next logical visit appears as expected. Previously, when branch exit questions were answered in a certain way, the next logical visit did not appear in the visit train. Instead, the Next Visits column was populated with three (3) dashes (---).

Retracted workaround: None. (Issue 35726231)

Error encountered when multiple rules try to update the same form or visit

Now, errors no longer occur when multiple rules attempt to update the same form or visit simultaneously.

Retracted workaround: None. (Issue 35401876)

A visit remains IN PROGRESS after clearing all form data, limiting the ability to skip the visit

Now, a visit no longer remains in the status of IN PROGRESS after clearing all data in the visit, allowing the visit to be skipped. Previously, the visit would be stuck at IN PROGRESS after clearing all form data, limiting the ability to skip the visit.

Retracted workaround: PL SQL script execution to version end the active data element record with a null value and version end the currently active IN PROGRESS visit status. This results in a new record introduced in the visit status table with a status of NEW. (Issue 35541809)

The Visit Date field for a new visit displays the date of the previously completed visit

Now, the Visit Date field for a new visit is blank after clicking a previously completed visit, followed by returning to the new visit. Previously, the date from the previously completed visit was displayed in the Visit Date field for the new visit.

Retracted workaround: None. (Issue 35741399)

Clicking Start Visit multiple times for a skipped visit can result in system slowness (former known issue)

Now, after clicking Start Visit (for a skipped visit), the system blocks the ability to click Start Visit again. Previously, the system allowed Start Visit to be clicked multiple times, impacting study performance.

Retracted workaround: None. (Issue 35654270)

An auto-assigned query is not appearing in a Screen Fail visit after being generated

Now, auto-assigned queries are visible in a Screen Fail visit. Previously, the auto-assigned query would generate successfully, but it was not visible in the visit, as queries could not be assigned to a Screen Fail visit.

Retracted workaround: None. (Issue 35333522)

A source data verified (SDV) visit gets unverified after a read-only item is populated by a rule in another visit

Now, a source data verified visit (ex. Visit_1) is no longer unverified when a new read-only item (not eligible for verification) is populated by a rule generated in another visit (ex. Visit_2).

Retracted workaround: None. (Issue 35266051)

Rules fail to populate multiple items when the visit date is a variable in the rule

Now, when Visit Date is referenced as a variable in a rule, rule target items are populated correctly when the Visit Date is entered or updated.

Retracted workaround: To avoid screen-blocking issues related to this bug, mark your rules as 'unblocking' in the rule-design dialog. This allows a user to proceed to enter data without getting blocked. The rule executes in the background, and the user must reopen/refresh the visit to see the rule execution results. (Issue 34526808)

No action takes place when clicking Save or Save and Close after completing a form association (former known issue)

Now, you are automatically taken back to the All Subjects page when clicking Save or Save and Close after completing a form association.

Retracted workaround: After saving, click into the white space of the visit to return to the All Subjects page. (Issue 35139761)

Users can delete a Library study even when it includes forms and associated visits (former known issue)

A Library study can be deleted if its design objects have not yet been imported into another study. If library objects have been imported into another study, end-users are now presented with a message stating why the study cannot be deleted.

Retracted workaround: None. (Issue 35283510)

An automated query is not being displayed for an age field (former known issue)

Now, when the target field of an automated query is an age (read-only) field, the query is displayed automatically without the need to refresh the browser.

Retracted workaround: Use the time and date (date of birth) question as the target field of the automated query rule. (Issue 31895089)

A predefined label included in a rule does not work (former known issue)

Now, for a tabular form, rules work as expected when you define a rule that includes the tabular form’s predefined labels as variables.

Retracted workaround: Use an OR clause in the rule expression that includes the item value string and index. For example, if the first record in the predefined block is "Glucose", the rule expression would be: if (var1 == "Glucose" || var1 == 0) (Issue 31979445)

Dynamically displayed forms do not behave as expected in an Adverse Event (former known issue)

Now, a dynamic child form in the Adverse Event visit is not hidden based on the answer to the determining question in another scheduled visit.

Retracted workaround: None. (Issue 34287388)

The delete form confirmation window remains after clicking Delete for a two-section form (former known issue)

Now, when deleting a two-section form, the delete form confirmation window no longer remains open after clicking Delete.

Retracted workaround: Manually close the window, then refresh your browser. (Issue 35293584)

The validation rule error message does not change when a rule is copied

Now, the error message associated with a copied validation rule changes correctly based on the type of validation rule selected and no longer displays the error message associated with the original validation rule.

For example, if you create a validation rule, Select at Least, then copy that rule and change the type to Select at Most, the correct error message is displayed for the second rule instead of the error message associated with the initial validation rule.

Retracted workaround: None. (Issue 35552799)

The Share Form drop-down does not include all expected users

Now, when you double-click a form (in the test container) and select Preview, then Share, all relevant users are available in the Share Form drop-down. Previously, a fifteen (15) user maximum was enforced.

Retracted workaround: None. (Issue 35528467)

Error encountered after entering data in a two-section form and clicking Save (former known issue)

The error no longer occurs if you have different values stored for the Label and Value in a codelist.

Retracted workaround: Create a new form and assign the corrected codelist to the label question. (Issue 35508707)

A deleted row on a repeating form is visible after verification

Now, if you clear an item on a repeating form and then delete that row, the row does not appear after verifying the visit.

Retracted Workaround: None. (Issue 35487676)

Rule execution fails when trying to write to a question on a form in a skipped visit (former known issue)

Rule execution no longer occurs when the rule target items are in a skipped visit. The rule runs as expected on all other visits.

Retracted workaround: None. (Issue 35386395)

Queries closed automatically after clearing a visit date are not reflected on the screen (former known issue)

Now, when you clear a visit date, queries automatically closed on a form in that visit show as closed on the screen without requiring a screen refresh

Retracted workaround: Refresh your browser’s page to see the updates on your screen. (Issue 35143313)

Auto-queries are applied when the rule logic controlling the query is not met

Now, auto-queries are no longer applied incorrectly on associated form items when the query rule logic controlling the query is not met. Previously, the system misinterpreted the dateTimeValueUTC as null for date/time items resulting in the query being applied.

Retracted workaround: None. (Issue 35338504)

Repeating Label form status shows Incomplete, but the visit status shows Completed

Now, the system considers label form items, Label (Repeating table only), as data when calculating the visit status for lab forms.

Retracted workaround: None. (Issue 35281506)

Clinical ODM API call returns different record counts when no toTimestamp parameter is passed

Now, when no toTimestamp is specified in the output ODM, the toTimestamp is set to the maximum value (the most current DHTimeStamp transaction) of all available levels (visit, subject, form, item, and query).

Retracted workaround: None. (Issue 35260813)

Queries display as Opened on the Query side panel but are not present on the form

Now, queries created in an unscheduled visit are visible on the associated form and the Query side panel.

Retracted workaround: Action the queries from the Queries tab. (Issue 35111514)

Visit status is stuck at In Progress when it should be Complete

Now, if you have a visit containing, for example, a lab form and a standard form and save the data entered on each simultaneously, the visit status is changed to Complete.

Retracted workaround: None. (Issue 35554827)

Kit dispensed for an In Progress visit

Now, kits are no longer dispensed for an In Progress visit. Previously, this occurred when form data for multiple forms was saved simultaneously (see bug 35554827), resulting in a completed visit being stuck at an in-progress status.

Retracted workaround: None. (Issue 32975691)

A screening visit may remain incomplete (former known issue)

Now, a screening visit no longer remains incomplete after dispensing kits or randomizing a subject.

Retracted workaround: None. (Issue 34314545)

Using an API to hide a dynamic dispensation visit marks the visit status as New instead of Incomplete

Now, when using an API to clear all data in a dynamic dispensation visit, including changing the determining question and hiding the visit, the user is presented with the following dialog related to the determining question; You cannot change this answer at this time. Some visits are available based on the data in this answer. To update the answer, you must clear any data that is included in those related visits. This results in the status of the visit being set to Incomplete.

Retracted workaround: None. (Issue 35201062)

Question hint text for an item in the flat portion of a two-section form persists after navigating away from the item

Now, the question hint text associated with an item in the flat portion of a two-section form, displayed under the Question Hint text in the right-side panel, is no longer displayed after moving to the repeating section of the same form.

Retracted workaround: None. (Issue 34275441)

The unlock icon is not orange for a required in-progress visit

Now, the unlock icon displays in orange for a required in-progress visit making it easy for users to distinguish between the locked and unlocked icons.

Retracted workaround: None. (Issue 34722585)

Dynamic form in a future visit – Visit reordering occurring

Now, multiple updates to a determining question which results in a change to the visit status, for example, Complete to Incomplete for future completed visits, no longer results in visits appearing out of order or repeatedly changing positions in the visit train.

Previously, for example, entering No for the Childbearing Potential determining question, then changing to Yes, then back to No would result in inconsistent visit order in the visit train.

Retracted workaround: None. (Issue 35388908)