Forms, visits, and rules
Error encountered when a user tried to clear a selected lab when no data was previously saved
Now, when a user selects Clear Lab Selection from the Lab drop-down and no data has been captured for that lab, the system clears the previously selected lab without error.
Previously, the system displayed the following error: “An issue occurred in the system. Try performing this action again.” The lab value was not cleared.
(Issue 38198138)
Details for the Visit Date are not displayed for users assigned to a non-data entry study role
Now, the Answer & Visit History sidebar displays the Visit Date details for users assigned to a non–data entry study role when the visit date has an associated (active) rule.
Previously, the visit date was skipped, and the system displayed the answer and visit history for the first question on the first form.
(Issue 38504328)
View-only users can select from the Select Lab dropdown on a lab form
Now, users assigned to a view-only study role can no longer select from the Select Lab value dropdown. The dropdown is now disabled and displays the previously selected lab.
Previously, the dropdown appeared editable, but the change was blocked at submission, which caused confusion.
(Issue 37246186)
Source Data Verification (SDV) checkboxes do not appear for lab form and two-section repeating form rows
Now, data verification checkboxes appear, where applicable, for each row in lab forms and two-section repeating forms.
Previously, due to the Redwood upgrade, the checkboxes were rendered but were obscured by the repeating form's rows. As a result, users had to validate data at the question level, adding unnecessary effort.
(Issue 38540346)
Route of Administration and Indication are missing in Oracle Central Coding for restored rows
Note:
The Concomitant Medications form typically includes Route of Administration and Indication, which are used during medical coding.Previously, the data for these fields was not fully restored, resulting in missing values in both the applicable system tables and Oracle Central Coding.
(Issue 38553728)
Users prevented from entering data in a Logs visit after a site’s study version was updated
Now, site users no longer encounter errors when entering data in a Logs visit after the site’s study version changes.
Previously, this occurred if a repeating form was deleted and the visit contained no data when the new study version was applied to the site. This was due to a conflict between the study version stamped on the Logs visit and the one assigned to the site.
(Issue 38528093)
Fully verified visits containing lab forms are incorrectly shown as unverified (former Known Issue)
Now, the green check mark appears, indicating that all data for a visit, including those with lab forms, has been verified.
Previously, if a user verified some data, exited, and later reentered the visit to complete verification, the green check mark did not display. This made it appear that verification remained incomplete.
(Issue 36122564)
The Create Visit Schedule (POST) API creates Adverse Event (AE) events when instance number is not null
Now, validation added to the Create Visit Schedule (POST) API enforces that eventInstanceNum is null when creating Adverse Events.
If a request attempts to create an adverse event visit with a non-null instance number, the API returns an error. This prevents integration failures by allowing event creation only when eventInstanceNum is null.
(Issue 38552905)
Parent topic: Fixed issues in 25.2.1.5