Version : 89.1
Released : 2026-08-08
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
5062 |
Bug |
When Rave returns an error on save but the data was actually saved, TrialGrid keeps the error screenshot and takes a further screenshot of the record once it has been re-opened. |
|
5063 |
Bug |
Test case generation no longer fails for date edit checks that use large minute-based date windows, and now derives boundary dates using the time unit the check actually uses. |
|
5068 |
Bug |
Test Case PDFs are now generated correctly when a step's data table contains a value too long to fit on a single page; previously the PDF failed to generate and the test case was omitted from the output. |
|
5074 |
Bug |
Slow new EDC form saves no longer fail a test case: the save wait is now a configurable timeout, and a save that outlasts it is checked against the server before being reported as failed. |
|
5078 |
Bug |
Vault notification banners no longer block the site breadcrumb click when a Veeva Test Case takes a screenshot of the subject status in the site's subject list. |
|
5079 |
Bug |
Veeva Test Cases no longer intermittently fail to create a subject with 'the New Casebook button did not appear' when the study uses By Site Subject ID Generation. |
|
5081 |
Bug |
Veeva Test Cases can create a subject By Site after an earlier step has used the browser to view a subject. |
|
5082 |
Bug |
Veeva data entry steps report when the form could not be opened in the browser, so it is clear why the step has no form screenshot. |
|
5083 |
Bug |
Veeva Test Case steps name the Vault API call that returned an internal error, instead of showing the raw response body. |
|
5085 |
Bug |
AI test case generation now handles unexpected AI response formats, retrying instead of silently producing no test case, and a generation run which creates nothing is now reported as failed. |
|
5086 |
Bug |
Veeva rules using aggregate functions with separate arguments, such as NoBlanks(A, B, C), now generate test data correctly. |
|
5087 |
Bug |
Test data generation now handles rules which compare dates against numeric timestamps, and rules which apply arithmetic to numeric text values, instead of silently generating no data for them. |
|
5090 |
Bug |
Test Case data entry could fail on empty forms when the first enterable field could trigger a field visibility change without any data being entered into that first enterable field. |
|
5091 |
Feature |
Veeva test case runs now use the study label for UI navigation, so studies whose name and label differ run correctly. |
|
5078 |
Bug |
Vault notification banners no longer block the site breadcrumb click when a Veeva Test Case takes a screenshot of the subject status in the site's subject list. |
|
5079 |
Bug |
Veeva Test Cases no longer intermittently fail to create a subject with 'the New Casebook button did not appear' when the study uses By Site Subject ID Generation. |
|
5081 |
Bug |
Veeva Test Cases can create a subject By Site after an earlier step has used the browser to view a subject. |
|
5082 |
Bug |
Veeva data entry steps report when the form could not be opened in the browser, so it is clear why the step has no form screenshot. |
|
5083 |
Bug |
Veeva Test Case steps name the Vault API call that returned an internal error, instead of showing the raw response body. |
|
5086 |
Bug |
Veeva rules using aggregate functions with separate arguments, such as NoBlanks(A, B, C), now generate test data correctly. |
|
5091 |
Feature |
Veeva test case runs now use the study label for UI navigation, so studies whose name and label differ run correctly. |