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.

Version 83 introduces AI Agents to TrialGrid — intelligent assistants that work alongside you to speed up common tasks. This release also brings new automated testing steps, a new diagnostic, and improvements to custom object management.

For more information see the release notes for Version 83.

AI Agents

The biggest addition in Version 83 is the introduction of AI Agents into TrialGrid. Agents are AI-powered assistants embedded directly in the application that can help you with tasks that would otherwise require manual effort.

The Help Agent searches TrialGrid documentation to answer your questions without leaving the app. Need to know how a feature works or what a setting does? Just ask.

The Test Case Creator Agent can draft and edit test cases for both Rave and Veeva studies. It supports all Rave Check actions (except Balance and CTMS), and it's context-aware — if you open the agent from an edit check, custom function, or custom object page, it already knows which object you're working with. It can also use the Test Case Advisor under the hood to generate test cases from existing edit checks and custom functions.

The Test Case Search Agent lets you find test cases across your drafts using natural language queries, and the Custom Diagnostic Agent helps you create and edit custom diagnostics.

A new Field Visibility Agent assesses whether your form fields have appropriate visibility settings and corresponding edit checks to show or hide fields dynamically.

For safety, agents always ask for your confirmation before creating, updating, or deleting any objects. AI Agents can be enabled per-user by your organization — contact us if you're interested in trying them out.

Automated Testing

We've added several new test steps that give you finer-grained control over record lifecycle testing. You can now check whether a field is read-only or editable, and there are new steps to lock and unlock, freeze and unfreeze, verify and un-verify, and review and un-review log records.

There is also a new Project-level Test Cases view that shows test cases across all drafts in a project, making it easier to see the full picture without navigating draft by draft.

Diagnostics

New Diagnostic 0179 identifies double spaces in Form Names, HelpText, Folder Names, Field labels, and Edit Check Actions. It shows exactly where the double space occurs and offers an auto-fix option to replace double spaces with single spaces — a small but common issue that can now be caught automatically.

Custom Properties and Objects

Organizations can now add custom icons to TrialGrid, and users can create, edit, and manage layouts for Custom Object Definitions, including generating 1-column and 2-column layout templates.

This post was auto-generated by an LLM.

Version 82 represents a major leap forward for Veeva automated testing in TrialGrid. With comprehensive test case generation, full reporting capabilities, and a polished editing experience, Veeva users now have access to the same depth of automated testing that Rave users have relied on for years.

For more information see the release notes for Version 82.

Test Case Views and Reporting

Veeva Test Cases now have the same rich viewing experience as their Rave counterparts. The Test Case view and data view are both available for Veeva drafts, giving you clear visibility into your test scenarios and the data they use. Screenshots can be captured during test runs, and PDF reports can be generated for your validation packages. We've also added AI-generated summaries for Veeva Test Cases and their runs, helping you quickly understand what a test covers and how it performed.

Expanded Test Case Generation

The Veeva Test Case generator has gained significant new capabilities in this release. It now supports Add Event, Add Event Group, and Add Form rule actions, broadening the range of rules you can automatically generate tests for.

A Smoother Editing Experience

We've added editor helpers across all major Veeva step types — event steps, form steps, data value steps, and query steps. These helpers guide you through building test steps without needing to remember the exact syntax. Veeva event steps now include the event group and event for clarity, and there are new steps to check whether events exist or don't exist in a test scenario. Tooltips throughout the editor and run results view display object labels, so you can quickly identify what each object reference means without switching context.

Test Case Management

Veeva Test Cases can now be copied between drafts, just as you can with Rave test cases. This makes it easy to reuse test scenarios across studies or versions. We've also added the ability for users with the 'Can manage Vault settings' permission to view and register Veeva Vaults directly in TrialGrid.

New Diagnostic for Rave 2025.2.0

Diagnostic 0178 has been added to validate Observation Date settings against Rave 2025.2.0 requirements. It ensures that standard form fields only use 'Observation Date of Form' and log form fields only use 'Observation Date of Log/Form', catching misconfigurations before they reach your Rave environment.

This article was auto-generated by an LLM.