Forms, visits, and rules

Associated Form rows in repeating forms display correctly

Now, when opening a repeating for through Query Management then selecting View in Form, previously linked Associated Form rows appear correctly checked for repeating forms.

(Issue 38703070)

Repeating form questions in a reopened skipped visit can be edited

Now, when a skipped visit is reopened, repeating form questions are able to be modified as expected.

(Issue 35975766)

Visit Date properly saves when selecting Save & Close

Now, Visit Dates save properly when you click Save & Close, even if you do not click outside of the Visit Date field first.

(Issue 36017816)

Queries are handled correctly when clearing or deleting repeating form data

Now, when the last value in a repeating form instance is cleared, or the instance is removed, the system now processes rules before closing queries, ensuring any rule-generated queries are handled correctly and preventing duplicate auto-queries on items that no longer contain data. Additionally, query behavior is now consistent and accurate when repeating form data is cleared.

(Issue 36670592)

Dispensation remains in a visit when the visit schedule is changed to zero

Now, the dispensation associated with a visit remains, even when the visit schedule (Days setting) is changed to zero, ensuring that you have the ability to randomize subjects and dispense drugs in a study properly.

(Issue 37640069)

Drug Reconciliation forms generate correctly

Now, the Drug Reconciliation form opens, generates, and prints properly. Additionally, existing forms can also now be viewed without loading issues, ensuring reliability when accessing drug reconciliation records.

(Issue 38845252)

Choice question options created from existing code list begin at the correct parameter

Now, choice question options created from an existing code list have their value parameter starting correctly at 1, aligning with the option sequence and ensuring option values are assigned consistently.

(Issue 38973782)

Only one unsign action is performed per form

Now, updating a signed record triggers the unsign process only once per form. The system prevents duplicate unsign actions, so only a single unsigned record is created and form signature history remains accurate.

(Issue 38602792)