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.

Version 85 is a landmark release for TrialGrid. Our Veeva EDC support is now production-ready, with the first studies going live in April, and we've significantly expanded our AI Agent capabilities to help you build and review study designs faster.

For more information see the release notes for Version 85.

Veeva EDC: Ready for Production

Since announcing our Veeva Technology Partnership last year, we've been steadily building out our Veeva EDC support across multiple releases. With Version 85, that work reaches a milestone: the first Veeva studies with TrialGrid are going live in April.

This release includes a comprehensive Form Review experience for Veeva forms, complete with progressive display support, so you can preview exactly how forms will appear to site users. We've also added dozens of improvements to the Veeva automated testing framework, including new test steps for progressive display visibility checks, event date verification, form submission control, and smarter query comparison that accounts for whitespace and case differences. The Test Case editor now auto-corrects date formats, warns about invalid values, and provides richer helpers with labels and repeat number support. The Test Case generator has also been improved with better event handling and support for unknown dates.

New diagnostics are available for Veeva studies too, including checks for trailing whitespace and double spaces in text fields, as well as new similarity diagnostics that catch near-duplicate Item Labels and Rule query messages before they cause confusion in production.

AI Agents: More Capabilities, More Control

TrialGrid now offers a growing suite of AI Agents that assist with study build tasks. In Version 85 we've added agents to create Edit Checks, create Custom Functions, review Custom Function code, and review Specification custom objects. The Custom Function Review agent supports follow-up questions after its initial review, and the Specification Review Agent can now assess whether a Custom Function is needed and run across multiple specification objects at once.

Version 85 introduces Agent Hooks, a mechanism to connect AI agents to your study workflow, notifying users that action may be required, assigning workflow states and actions.

Form Review

There is a new Form Review experience that lets you see exactly how your Rave EDC forms will look, including field visibility edit checks and view restrictions by EDC role. You can click on any row to inspect field properties, download HTML copies of forms, and print directly from the review page.

Standard Rules and Custom Properties

Standard Rules now have a full-featured object editor with a sidebar for labels, tickets, comments, and activities. You can see which drafts have a rule activated and how many, and custom properties are now supported on Standard Rules for additional metadata.

Custom Properties gain several enhancements: layouts can hide unassigned fields, layout definitions can be cloned and copied between URLs, HTML is now a first-class property type, and text properties support maximum length and regex pattern validation.

To learn more, visit trialgrid.com or reach out at info@trialgrid.com to schedule a demo.

This post was auto-generated by a LLM.

Version 84 brings a significant upgrade to Custom Properties with the introduction of Reference-type navigation, expanded Veeva automated testing capabilities, and several quality-of-life improvements across the platform.

For more information see the release notes for Version 84.

Custom Property References

Custom Properties of type Reference can now refer to Rave draft objects, and we've built out a full navigation experience around them. When a Reference property appears in a list view, it links directly to the referenced object. The same applies in the object editor, where you'll find a clickable link to navigate to the target. If your object is referenced by another custom object, you'll see a convenient link in the editor sidebar back to the referencing object. When a Reference property is part of an object identifier, the link appears right alongside the identifier in the custom objects list.

These navigational links make it much easier to work with related objects without having to search or browse manually. When you copy a custom object with a Reference property into a draft, the reference is automatically resolved to the corresponding object in the destination draft when it exists.

Beyond References, we've added support for custom properties on Unit Dictionary Entries, giving you the same extensibility for units that you already have for other object types. Custom object layouts also now support a read-only mode for fields and containers — fields marked as read-only display a lock icon and cannot be edited, and child elements can override their parent container's setting when needed.

Veeva Automated Testing

We've continued to expand our Veeva testing capabilities in this release. The Test Case Advisor is now available for Comparison Rules, helping you generate test scenarios for this rule type just as it does for other Veeva rules.

Several new test steps improve how you work with subjects in Veeva test cases. You can now check the value of a subject's name and status directly in your test scenarios. The Test Case editor will also warn you if a data entry step could change the subject name without a subsequent step to verify or re-select the subject, helping you catch potential issues before execution.

Query steps now display their status in user-friendly text rather than raw values, making test results easier to read. We've also improved the messaging when a Form is restricted and the test runner account doesn't have restricted data access — you'll see a clear explanation if a Form isn't found due to permissions rather than a generic error.

AI Agent Controls

Organizations now have finer-grained control over AI Agent availability with a new URL/Vault level setting. This allows you to enable or disable AI Agents on a per-URL or per-Vault basis, giving administrators more flexibility in rolling out agent capabilities across their organization.

Veeva Reserved Words Diagnostic

A new diagnostic for Veeva studies checks whether Items are using reserved words. This helps you catch potential conflicts early in the study build process before they cause issues in your Vault environment.

This article was auto-generated by an LLM.