Forms, visits, and rules

Partial dates and date validation rules do not work as expected (former known issue)

Study designers: Now, when you define a Date/Time type of question to accept partial dates and define a Minimum Date Answer (either YYYY or MON-YYYY), as well as a validation rule (such as an On or After type of validation rule), site users can complete these date fields successfully without encountering validation error messages despite the data being correct.

Previously, site users could not complete these Date/Time fields whether they had completed all fields of the date or just met the minimum allowed requirement. Moreover, when consulting the Study Design report, you may have noticed that the validation rule for that Date/Time type of question indicated that the date entered must be On or After the last modified date of the indicated date field.

Retracted workaround: None. (Issue 32459681)

Select Exactly validation rule does not work for drop-down question

Study designers and site users: Now, when you design a drop-down question that has an Select Exactly 1 validation rule applied to it, the validation rule will work, as expected. A site user will not be able to choose multiple options for an answer without a validation error message appearing. Previously, a site user was able to select multiple options for a drop-down question and no validation error messages were displayed. This issue was encountered when completing required questions and in repeating forms, as well. (Issue 33420928)

Advanced study version updates do not work in a two-section form (former known issue)

Study designers: Now, in a two-section form that is already included in a live study version, you can add or update a question in the Questions Before the Table section of that form (in Draft), and apply that change to another study version (including the live one). Previously, you could not do that due to a limitation of the two-section form feature and the presence of label items in the second section of the form.

Retracted workaround: None. (Issue 33146232)

Cannot insert a visit in the beginning of a branch (former known issue)

Study designers: Now, you can insert a scheduled visit as the first visit in a branch. Previously, you were only able to insert a visit as the second one in the branch and then schedule it starting from the already existing first visit in the branch.

Retracted workaround: None. (Issue 33150377)

Details of an age question are not translated in Japanese

Study designers: Now, all details that you must specify for an age question are properly translated in Japanese (the Format and Unit fields). Previously, when using the application with Japanese set as the preferred language, these two fields were still displayed in English. (Issue 32877375)

An inserted visit is not properly updated after its removal (former known issue)

Study designers: Now, when you insert a visit into the schedule of one live study version (impacting both future and past subjects enrolled in the study) and then you remove the same visit within the context of another study version, that inserted visit is updated, as expected, for all subjects in a state of New. Previously, this update was not completed as you'd expect. An inserted visit that is removed from the schedule, at one point, must be removed from the schedule of all subjects in a state of New which was not the case for this issue.

Retracted workaround: None. (Issue 3314544)

Automated queries do not work when visit start date is updated automatically (former known issue)

Rule designers and testers: Now, in a visit, whether the visit start date is automatically entered by the system or filled in manually, any automated queries that use the visit start date field as a rule operand will work. Previously, an automated query would not have worked for this use case.

Retracted workaround: You no longer have to follow the two options (listed below) to work your way around this issue.

• If you have the possibility of manually entering the visit start date, then we suggest you do so. That way, you ensure that automated queries will run.
• If you cannot enter the visit start date manually, then we recommend you add a trigger variable in the rule definition of the automated query.

(Issue 33213738)