Version 88 is a more focused release than usual, and deliberately so. We brought this release forward to the 21st of June to coincide with the rollout of Medidata's new Rave EDC release, 2026.2.0. That shortened timeframe, combined with a substantial body of behind-the-scenes work to update our automated testing framework for the EDC changes, means there are fewer headline features this time - but the ones that are here matter. Chief among them is an important change to how project access is managed: the Project Owner concept has been replaced by the more flexible Project Roles.

For more information see the release notes for Version 88.

Rave EDC 2026.2.0 Support

Medidata's Rave EDC 2026.2.0 release brings a range of changes, and much of our work this cycle went into making sure TrialGrid's automated testing framework runs cleanly against it. Automated Tests now fully support Rave EDC 2026.2.0, so your test execution stays in step with the latest EDC release from day one of its rollout - which is exactly why we aligned this release with Medidata's.

Project Roles Replace Project Owner

The single Project Owner has been removed in favor of managing users by Project Role. When creating a project you can now optionally assign a user to a Project Role directly from the Add Project page - the creator can assign the role to themselves or to any other URL user, without needing a separate "Manage Users" permission on the URL. Once created, any user with a Project Role that grants the "Assign Users" permission in that Project can add and remove members from the Project Team page, replacing the old shortcut that let owners manage their team without an explicit URL-level permission.

This is a migration as well as a feature: all existing Project Owner users have been moved to a Project Owner Role within their project, so nothing is lost in the transition. Because this is a significant change for some users, we have a dedicated post that walks through what it means for your projects. You can read it here: Retiring the Project Owner Role.

More Ways to Generate Test Cases

The Test Case generator has gained several new options that make it easier to broaden coverage without hand-writing extra scenarios. You can now repeat all scenarios across a range of folders, repeat them for record positions 1 and 2, add scenarios that specifically test blank values, and add scenarios that verify queries are closed after being opened. Together these let you exercise more of a study's behaviour - repeating data, log records, missing data and query lifecycle - from a single generation run.

Filtering and Custom Property Values

Object lists are easier to work through by assignment. You can now filter a list to show only Unassigned objects, and a new "Assigned to" dropdown lets you narrow the list to one or more specific users or roles - handy for seeing exactly what is on your plate or someone else's. And on a text Custom Property's value management page, you can now delete a value, which clears it on every record that uses it.

This post was auto-generated by a LLM.

This is one of our largest releases to date. Version 87 rounds out Custom Properties with a full set of data types, brings a wave of new Veeva diagnostics and Test Case generation improvements, makes Property Sheets far more capable, and adds Timeline tracking, finer-grained permissions, and self-service API tokens. There is a great deal here, so let's work through it theme by theme.

For more information see the release notes for Version 87.

Custom Property Data Types

Custom Properties have grown from a handful of value kinds into a complete typing system. This release adds URI properties (validated as web addresses with a scheme), Color properties (hex codes shown as swatches and edited with a color picker), Numeric properties (with optional minimum and maximum bounds and decimal-place constraints), Date and DateTime properties (native pickers, displayed in your preferred date format and stored as ISO values), and Set properties (multi-value selection from a defined list of allowed values). Short text properties under 100 characters now render as a single-line input rather than a text area, making compact values quicker to read and edit.

Working with custom objects is easier too. A new Search columns filter lets you choose exactly which columns the search box matches against, and the Copy-from dialog gains the same control so you can restrict a search to a single column. For teams building tailored layouts, custom object Field nodes now accept an optional renderer that replaces the default input with a specialised widget - a number spinner for numeric properties, radio buttons for choices, or a transfer list for sets.

Property Sheets

Property Sheets see a major round of improvements. You can now create Property Sheets for Forms, and Veeva URLs come with a default set out of the box. Sheets can be made read-only - either the whole sheet or for specific child object definitions - and a new Exclude Blanks filter option hides rows where a column has no value.

Editing in the spreadsheet view is now much smoother. Choice columns use an in-cell dropdown with type-to-filter instead of a popup dialog, and a single click selects a choice or checkbox cell rather than immediately changing it - the dropdown opens only when you click the arrow, and a checkbox toggles only when you click the box. The newer property types are fully supported in spreadsheets too: Color properties show a swatch with the hex code and edit with a color picker, Set properties edit with a multi-select dropdown, and Date and DateTime properties display in your chosen format with a date/time picker.

Veeva Diagnostics

Version 87 brings a substantial expansion of Veeva diagnostics, most with autofixes and configurable exclusion lists. Several focus on form and item presentation - flagging ItemGroups where Header Visible or Visual Group isn't enabled, Items whose Control Type doesn't suit their codelist size, Forms with mixed radio-button orientations, and codelist groups whose Items use inconsistent control types. Others tighten data definitions: Items with overly long names, Date and Date/Time Items missing 'No Future Date', Items whose Length doesn't match their codelist's maximum choice code length, and data Items that aren't marked Required.

A further set targets clinical correctness. New diagnostics check that measurement Items (height, weight, vitals and the like) have an appropriate Unit Codelist and plausible Length, Decimal and value ranges, and that Unit Codelist conversion formulas match the canonical conversion factors. Others flag objects whose External ID doesn't match their Name, classify lot, kit and accession number Items that should be Text, check for inconsistent Form ordering across Events, and catch Concomitant Medications forms that collect Total Daily Dose alongside Dose and Frequency. We've also refined several existing diagnostics to play nicely with TrialGrid's auto-created local-lab objects, excluding them by default so findings stay focused on real issues.

Veeva Data Model

We've made Veeva builds more navigable and less error-prone. The relationship objects behind EventGroup Events, EventForms, Codelist Entries and Unit Codelist Entries are now displayed as custom object definitions, so their per-relationship properties - such as Visit Method, Dynamic, Choice Label and Conversion - appear directly in lists. More significantly, properties that previously held the free-text name of another Veeva object are now reference properties: Codelist and Unit Codelist on Items, and Event Group, Event, Form, Item Group and Item references across Casebook Variables, Rules, Repeating Event Groups, Review Plans and more. This enables dropdown selection and reference validation in place of typo-prone text, with existing URLs converted automatically by migration. When adding a new Veeva Vault, you can now copy roles, labels, custom objects, custom properties, actions and other settings from an existing Vault.

Veeva Test Case Generation

The Veeva Test Case generator has become considerably more capable and robust. It now handles a much wider range of rule shapes correctly - InWindow rules over event dates, Max/Min wrappers around wildcard references, IsBlank arguments in Add Event predicates, attributes shared across events, and rules that reference previous or next instances of repeating objects via [-1]/[+1] identifiers. It sequences login-block events and data entry into cascade-driven phases so gating data is entered before the events it enables, switches to a Background section with per-scenario subjects when different events need testing, and combines rules that share query text and an action target into a single scenario instead of one per rule. It also submits unsubmitted forms before checking derived values, skips lab forms, generates the right steps for event change reasons and did-not-occur attributes, and clearly surfaces a 'Subject ID must be set' issue when it cannot choose a unique value.

Alongside the generator, there are new and improved Test Case steps: setting visit method, change reason, planned date override and externally-owned on Events; adding a reason to 'did not occur' steps; and a new step to add an empty repeating form to an existing event. The editor now warns about invalid date, datetime and time values, and 'Has value' results show both the User String and the Coded Data for fields that use a data dictionary, matching what users see in Rave.

AI Agents

Several agents have been migrated to our new orchestrator framework - the Custom Function Review, Test Case Creator, Custom Function creator and Test Case search agents - for a more consistent and maintainable foundation. The Field Visibility Advisor (Medidata) and Progressive Display Advisor (Veeva) have also been updated for a more responsive experience. Note that any in-progress conversations with the updated agents will be cleared when this release is deployed; simply start a fresh chat to continue.

Document Templates

Document Templates gain a powerful new capability: an {% ai %}...{% endai %} tag that transforms the enclosed block content using an AI call, making it easy to summarise or rewrite sections of a template at generation time. The URL Document Templates list can now be filtered by scope, format and active state, and a new REST API lets you discover, generate and download document templates for drafts and projects programmatically.

Permissions and API Tokens

Access control gets finer-grained. A new 'Merge Draft' Project Role permission controls who can use the draft merge flow, and a separate 'Assign Users' permission governs whether users can assign people to objects from lists, draft objects and property sheets. Both default to disabled on existing roles so you can grant them deliberately. Users with the new 'Can Use API Tokens' permission can now create, view and revoke their own API tokens from their profile - token values are shown only once at creation, and existing tokens continue to work and are migrated automatically.

Actions

Action preconditions can now reference more of your build's context. Alongside the existing project-property function, you can reference draft properties with d("draft_property_name"), draft labels with draft_has_label("label_name"), and project labels with project_has_label("label_name"), making preconditions far more expressive.

Study Build, Labels and Timelines

A new Amendment Advisor compares two Drafts in a Project and highlights structural, field and edit-check changes that could cause data loss when a Rave Amendment Manager migration runs. The Draft Fields list gains a 'Copy from' button so fields can be copied from another draft, and Labels can now be applied to Fields, with full support in the Draft Fields list, Form editor and Copy Form modal, plus removal conditions that auto-remove a label when a Field's attributes change. For project tracking, Timeline Templates can be created at URL level and added to Projects so you can track progress against milestones.

Standards, Security and More

URLs can now disable the standards compliance approval workflow: compliance is still calculated for drafts linked to a library, but the Request Approval, Approve and Reject UI is hidden where it isn't wanted. TrialGrid can configure a minimum password length above the system default of 9 characters on a per-organization basis, and staff can export customer-authored diagnostics and document templates and re-apply them between URLs. A number of UX touches round things out - list-view buttons consolidated into 'Add' and 'Actions' groups, instant cloning of drafts that have no user assignments, Select All / Select None on the Project Role edit page, and a spreadsheet-style URL Team list. Finally, our validation documentation now links each issue to the release notes for the version in which it was fixed.

This post was auto-generated by a LLM.

Version 86 is a substantial release that pushes forward on several fronts at once: our AI Agents get meaningfully more capable, Custom Objects and Test Cases gain full audit-and-revert history, and the testing and diagnostics tools learn to explain themselves more clearly. There's a lot here, so let's walk through the highlights.

For more information see the release notes for Version 86.

AI Agents

Our AI Agents continue to grow from helpers that describe problems into tools that build study artifacts for you. The Edit Check Agent and the Custom Function Agent can now both work from specifications: you define what you want using Property Definitions on an Edit Check or a Custom Object, and the agent generates the CQL logic, actions, or custom function to implement it. This means you can capture an intention as structured metadata and let the agent turn it into a working build object.

The Test Case Creator agent can now create Edit Checks at the same time as it creates Test Cases, and the Medidata Test Case Agent can draw on Edit Check custom properties. On the Veeva side, the Test Case agent now adds Add Event steps where they are needed and supplies a sensible default when saving a Test Case.

The Field Visibility and Progressive Display agents are now driven directly from the Forms list - select the forms you want analyzed and run the agent on just those, or run it across all forms if nothing is selected. Both agents now stream their results progressively, showing analysis for each form as it completes rather than making you wait for the whole batch. The Progressive Display Agent can also offer a fix, setting the Controlling Item and Controlling Item Values on items that are missing progressive display configuration.

We've also sharpened existing agents. The Custom Function Review agent was producing too many low-value findings, so it now concentrates on genuine errors, and the old 'Review' column has been removed from the Custom Function list in favor of action hooks that can apply Labels or other actions to reviewed functions. The Specification Review agent's object discovery has been improved, and agents can now locate Folders by both OID and Name.

Custom Objects and Custom Properties

Custom Properties gain two new data types in this release. Boolean properties render as a simple TRUE/FALSE dropdown, and Email properties validate that the entered value is a well-formed email address. Property definition listings now include a Data Type column with a matching filter, so you can quickly find every property of a given type, and a new Convert Values utility lets you bulk-replace text property values across a draft.

The child grid display for Custom Objects has been improved with ordinal change controls, sorting and filtering, and when you copy Custom Objects the list now shows any properties marked 'display in list'.

Custom Objects are now fully audited. Changes appear on the Activities tab where they can be reviewed, and reverted via the 'Revert' button. When reverting, you are no longer limited to an all-or-nothing rollback - checkboxes let you choose exactly which individual properties to revert. This same audited-change-and-revert capability now extends to Veeva core objects, matching the behavior previously available only for user-managed custom objects.

Automated Testing

Running a test set is now faster when nothing needs to change: if all settings are already configured you can click 'Run' to start immediately, and a 'Change Settings' button is there when you do need the wizard. Test Cases can be opened in a new tab from the list, their changes are now tracked on the Activities tab and can be reverted, and Test Case Templates now show only step-level validation errors rather than confusing structural warnings about missing Feature or Scenario declarations.

We've put a lot of work into making test results clearer and easier to act on. The View tab now resolves internal identifiers to human-readable names, showing event labels for 'see events' steps and the Matrix Name for Add Event steps, and the 'Link to event' in run results uses a stable URL pointing at the review tab. Field visibility steps and 'see form in event' steps now capture screenshots as evidence.

Query verification got a particularly large upgrade. When a query step finds a near-match with whitespace or case differences, the result highlights exactly where the expected and actual text diverge using color-coded markup. Run results can show a diff against the closest open query when there is no exact match, display the HTML tags in the query so they are visible, and offer a text-only diff view that ignores markup. Best of all, when a query step fails on a message mismatch you can update the expected text directly from the run results - whether that text lives in the Test Case, the Edit Check, or a Veeva Rule.

The Test Case Advisor is smarter about AI-generated scenarios. A new 'Use AI for Custom Functions' option - with an organization-level default - turns on AI generation of test cases for edit checks with custom functions. When generating those scenarios the Advisor can produce unknown date values for fields that support them, can include the marking group from the edit check action in query verification, and now generates tests for both the first and second log records while making each scenario self-contained rather than relying on values carried over from earlier steps.

Veeva Testing

Veeva test runs are cleaner and more informative. The Vault service announcement banner is removed before screenshots are taken, 'has value' and 'does not have value' steps highlight the verified field value in green for a pass and red for a fail, and each run now records the casebook version and build number. The editor helps you build correct steps too: 'see value' helpers support partial datapoint references, numeric values are validated against field definitions (warning, for example, when a decimal is entered into an Integer field), and you'll see a warning if an 'add event' step references an event group that is not Unscheduled, since only Unscheduled events can be added in the Veeva EDC UI.

Diagnostics

Diagnostics in this release are more configurable, clearer about their findings, and easier to act on. Several diagnostics now let you tune what they check — excluding fields restricted to particular EDC Roles, targeting multiple Marking Groups, or adjusting thresholds to suit your project — and the role and marking-group selectors gain Select All and Deselect All controls. Findings are more transparent too, spelling out exactly what's wrong rather than just flagging it, and a new diagnostic spots inconsistent field help text and offers a one-click fix. We've also brought several Veeva diagnostics up to par with their Rave equivalents, giving them the same fix and autofix support.

Document Templates

AI Summary document templates are a new kind of template that turn your study data into narrative. You build a template that renders context data into an LLM prompt; that prompt is sent to the AI for summarization, and the response is saved as a text document - giving you automatically generated written summaries driven by the data in your build.

Study Build, Veeva and Rave

A few build-side improvements round out the release. The Form editor no longer changes a field's data format when you select or change its data dictionary, which removes a long-standing surprise. Veeva Object Definitions for Events, Forms, Item Groups, Items and Codelist entries now carry ordinals, and when you import an SDS spreadsheet the implicit worksheet ordering is preserved as those ordinals. Standard Rules are now editable in Veeva Library drafts, and when uploading a draft to Rave you can choose to merge it with the existing draft rather than replacing it.

This post was auto-generated by a LLM.