Version : 88.17
Released : 2026-07-24
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
4979 |
Bug |
When running a test against the new Rave EDC, the 'I should see ... has value' step no longer fails for a field that is view restricted to the running user's role: if the user also holds a subject-admin role that can see the field, that role is borrowed to read and verify the value and the evidence screenshot is captured under that role. |
|
4981 |
Bug |
A query-state check ('I should see/not see the following query') on Rave EDC 2026.2.0 could intermittently fail when the query had not yet settled into its expected status. |
|
4982 |
Bug |
On the new Rave EDC, a data-entry step could fail with 'Form not saved after 60 seconds' when the record was left in Rave's 'form updated by another user or the system' state by a prior save's asynchronous edit-check/derivation processing. The runner now waits for the datapage's server version to settle before saving, and when the Save button cannot enable because of that conflict it refreshes and re-enters instead of waiting out the full timeout. |
|
4983 |
Bug |
A data-entry step could fail to find a field ("was not found on the form for data entry") when the field's draft PreText contained markup the browser renders differently from how the draft was matched — HTML entities such as used for indentation, a malformed </br> line break, or an invisible/zero-width character. These are now decoded, stripped, or normalized to match the label the form renders. |
|
4985 |
Bug |
Fixed an error generating test data for edit checks that reference a field derived by a derivation containing an extra datapoint trigger reference. |