Module : Agents
Issue |
Type |
TrialGrid Version |
Description |
|---|---|---|---|
4999 |
Feature |
89 |
The Edit Check and Test Case agents are better at recognising specifications that need a custom function. Conditions on a single date component (such as "the month is unknown but the day is entered") and conditions on a form's status (such as "the form is not submitted") are now flagged as needing a custom function instead of being turned into a comparison that doesn't match the specification. After generating a check the agent now also verifies that the logic actually matches the specification and stops rather than offering a check that doesn't. |
5000 |
Feature |
89 |
A new bulk Edit Check Creator agent builds edit checks from specifications in bulk — either the metadata attached to existing empty checks (which it fills in) or custom specification objects (from which it creates new checks). Each specification's outcome is classified — created with high confidence, created but review required, custom function required, or failed — and drives configurable per-outcome action hooks. Each result is shown in the chat as soon as it is built, so progress is visible throughout the run. |
4991 |
Feature |
89 |
The Edit Check and Test Case agents now guard range comparisons with an IsNotEmpty step. |
4992 |
Feature |
89 |
When the Edit Check Agent opens on a check that has a specification but no logic yet, it now offers to build that check's logic from its specification and writes the result back onto the same check. Checks that already have logic offer to regenerate from the specification or edit the existing logic, and the "metadata" wording is now "specification" throughout. When working on a specific check the generated logic saves straight onto that check with one click ("Save to <name>"), with a "Save as new check" option to spin the same logic into a separate check. |
4993 |
Feature |
89 |
The Edit Check and Test Case agents now see the URL's configured marking groups when generating a query action, so they pick a real marking group by its exact name instead of inventing one. A new per-URL default marking group can be set by TrialGrid admins. |
4994 |
Feature |
89 |
The Edit Check and Test Case agents now recognise when a specification can only be satisfied by a custom function (for example regex matching, extracting date components, or aggregating across records) — logic that Rave edit check steps cannot express. In that case the agent explains that a custom function is required and stops instead of producing an invalid edit check. |
4997 |
Feature |
89 |
When a specification says its behaviour is handled by a named custom function, the Edit Check and Test Case agents now build the check correctly — a trigger step on the field (its .DataPoint.IsPresent) plus a single CustomFunction action that calls the function, with no separate Open Query. If the named custom function isn't in the draft yet, the check is still offered with a warning rather than being blocked. |
4998 |
Feature |
89 |
Improved Agents ability to recover after an unexpected failure. |
4986 |
Bug |
89 |
The Edit Check and Test Case agents now recognise fields that have a data dictionary and compare them using the coded value (the .CodedValue suffix). A value that is not in the field's dictionary blocks the save. When the value is valid but the request never clearly named it, the agent shows a "did you mean" suggestion but still lets you save. Editing an existing check no longer re-flags a coded value it already contained. |
4987 |
Bug |
89 |
The Test Case Agent now writes date values using the separators of the field's own Rave format (for example "15 MAR 2024" for a "dd MMM yyyy" field) instead of a fixed hyphenated format, so generated test cases no longer raise a "does not match the field format" warning. |
4988 |
Bug |
89 |
The Custom Function Agent now knows how to change field visibility (setting the DataPoint's IsVisible property) and generates the show/hide code when asked to make fields visible or hidden, instead of only clearing the field values. |
4989 |
Feature |
89 |
When a user explicitly asks the Custom Function Agent for a function using Medidata's new V2 custom function API, the agent now explains that only the V1 API is supported so far and asks them to describe the function using V1, instead of generating V1 code for a V2 request. |
4970 |
Feature |
89 |
Organization administrators can enable or disable Agents for individual team members from the team user edit page; the option is shown only when the organization has Agents enabled. |
4929 |
Feature |
89 |
The Custom Function AI assistant now recognises the action a function performs (merge/un-merge a matrix, add a form, derive a value, and more) and generates the correct action instead of always raising a query. |
4844 |
Feature |
88 |
The Test Case creator agent now supports selection of one or more folders. |
4841 |
Bug |
88 |
The Test Case Creator agent was incorrectly requiring a field to be chosen for the AddForm check action. This has been corrected. |
4779 |
System |
88 |
The Help agent and development Test agent have been migrated to the new orchestrator framework. |
4811 |
System |
87 |
All agents converted to the new orchestrator framework. |
4781 |
Feature |
87 |
The Test Case search agent has been migrated to the new orchestrator framework. |
4760 |
Feature |
87 |
The Test Case Creator agents have been migrated to the new orchestrator framework. |
4763 |
Feature |
87 |
The Custom Function creator agent has been migrated to the new orchestrator framework. |
4757 |
Feature |
87 |
The Custom Function Review agent has been migrated to the new orchestrator framework. |
4756 |
Feature |
87 |
The Field Visibility Advisor (Medidata) and Progressive Display Advisor (Veeva) agents have been updated for a more responsive and consistent experience. Any in-progress conversations with these agents will be cleared when this release is deployed; just start a fresh chat to continue. |
4752 |
System |
87 |
An Orchestration Framework has been introduced to help TrialGrid Ltd design and develop Agents. |
4751 |
Bug |
87 |
The Custom Diagnostic agent was creating a diagnostic when running tests; it should not have created a diagnostic at this point. This has been corrected. |
4647 |
Feature |
86 |
AI Summary document templates allow customers to create templates that render context data into an LLM prompt. The rendered prompt is sent to the AI for summarization, with the response saved as a text document. |
4636 |
Bug |
86 |
The Progressive Display Advisor agent now saves the Choice Code (not the Choice Label) when configuring Controlling Item Values on fields with code lists. |
4637 |
Bug |
86 |
The Medidata Agents were not always using the Coded Value for dictionary Fields. This has been corrected. |
4638 |
Feature |
86 |
The Medidata Test Case Agent can now use Edit Check custom properties. |
4632 |
Feature |
86 |
The Specification Review agent's object discovery has been improved. |
4609 |
Feature |
86 |
The Edit Check Agent can now generate CQL logic and actions from an edit check's metadata properties, allowing users to define specifications via Property Definitions and then use the agent to implement them. |
4611 |
Feature |
86 |
The Custom Function Agent can now generate custom functions from Custom Object properties or Edit Check metadata, allowing users to define specifications via Property Definitions and then use the agent to implement them. |
4603 |
Feature |
86 |
The Field Visibility Agent will run on the Forms selected in the Forms list. |
4604 |
Feature |
86 |
The Progressive Display Agent is now available from the Veeva forms list and runs on selected forms when invoked. If no forms are selected, it analyzes all forms. |
4605 |
Feature |
86 |
The Field Visibility Agent now displays analysis results progressively as each form is analyzed, rather than waiting for all forms to complete. |
4606 |
Feature |
86 |
The Progressive Display Agent now displays analysis results progressively as each form is analyzed, rather than waiting for all forms to complete. |
4607 |
Feature |
86 |
The Progressive Display Agent now offers a fix option to set Controlling Item and Controlling Item Values on items that are missing progressive display configuration. |
4589 |
Feature |
86 |
The 'Review' column in the Custom Function list has been removed. The Custom Function Review agent supports action hooks which can be used to add Labels or other actions to reviewed Custom Functions. |
4585 |
Feature |
86 |
Agents will now search for Folders by OID and Name. |
4586 |
Feature |
86 |
The Custom Function Review agent was producing too many low-quality findings and now focuses on errors. |
4579 |
Feature |
86 |
The Test Case Creator agent can also create Edit Checks at the same time as Test Cases. |
4552 |
Bug |
85 |
The Veeva and Medidata Test Case agents should have similar workflow and features. |
4554 |
Feature |
85 |
The Custom Diagnostic agent is now aware of TSDV configurations. |
4543 |
Feature |
85 |
There are Action Hooks for the Test Case creator agent. |
4544 |
Feature |
85 |
There are Action Hooks for the Edit Check creator agent. |
4545 |
Feature |
85 |
There are Agent Hooks for the Custom Function review agent. |
4531 |
Feature |
85 |
The Specification Review Agent can run on multiple specification objects. |
4532 |
Feature |
85 |
Agents now require user confirmation before running Actions. |
4508 |
Feature |
85 |
The Specification Review Agent will assess whether or not a Custom Function is required. |
4486 |
Feature |
85 |
Agents can be configured to run Actions. |
4489 |
Feature |
85 |
The Field Visibility agent is now available on the Form Review page. |
4480 |
Feature |
85 |
There is a URL Agent configuration page to control which objects Agents can operate on. |
4466 |
Feature |
85 |
The Test Case creator agent now lets users select multiple folders for the test scenarios. |
4467 |
Feature |
85 |
The Test Case creator agent now uses for loops for testing scenarios with multiple folders. |
4468 |
Feature |
85 |
The discovery of forms and fields by Agents has been improved. |
4452 |
Feature |
85 |
The Custom Function Review agent will respond to follow up questions after the initial review. |
4445 |
Feature |
85 |
There is an Agent to check the progressive display settings on Veeva forms. |
4442 |
Feature |
85 |
There is an Agent to review Specification custom objects. |
4441 |
Feature |
85 |
Changes made during an Agent session will be identified with the Agent name in Activity listings. |
4423 |
Feature |
85 |
There is an Agent to help create Custom Functions. |
4409 |
Feature |
85 |
There is an Agent to review Custom Function code and look for possible issues. |
4371 |
Feature |
85 |
There is an AI Agent to help create Edit Checks. |
4375 |
Feature |
84 |
There is a new URL/Vault level setting controlling whether AI Agents are enabled for that URL/Vault. |
4370 |
Feature |
83 |
When the test case creator agent creates a test case from an object it will include it as a related object. |
4345 |
Feature |
83 |
There is a Custom Diagnostic agent to help create and edit Custom Diagnostics. |
4348 |
Feature |
83 |
New Field Visibility Agent helps users assess whether form fields have appropriate visibility settings and corresponding edit checks to show/hide fields dynamically. |
4343 |
Feature |
83 |
There is a Test Case creator agent for Veeva drafts. |
4331 |
Feature |
83 |
The Test Case creator agent supports all Rave Check actions, except Balance and CTMS check actions. |
4333 |
Feature |
83 |
The Test Case creator agent is context aware, if opened from an Edit Check, Custom Function or Custom Object page it will have details of that object available to use. |
4334 |
Feature |
83 |
The Test Case creator agent can use the Test Case Advisor to create test cases from existing edit checks and custom functions. |
4335 |
Feature |
83 |
Object definitions have a property which can be used to provide a description of the properties for AI Agents. This property can only be set by TrialGrid Ltd staff. |
4330 |
Feature |
83 |
Organization settings page now displays the status of AI Features and AI Agents settings. |
4329 |
Feature |
83 |
There is a user confirmation step before Agents create, update or delete objects. |
4234 |
Feature |
83 |
AI Agents can be enabled for users. Contact support@trialgrid.com if you are interested in this feature. |
4324 |
Feature |
83 |
A flag now controls whether users can access AI Agents. |
4327 |
Feature |
83 |
It is now possible for users to rate the performance of the agent in a particular session. Rating the agent performance will allow TrialGrid Ltd to gather metrics to improve agent performance. |
4311 |
Feature |
83 |
There is an AI agent to search Test Cases. |
4310 |
Feature |
83 |
There is an Agent to create and edit Test Cases. |
4304 |
Feature |
83 |
There is Help agent which will search TrialGrid documentation to answer questions. |
4299 |
Feature |
83 |
There is now a framework for introducing AI Agents into TrialGrid. AI Agents are not yet generally available. |
4300 |
Feature |
83 |
AI Agent sessions are stored and can be viewed. |
4301 |
Feature |
83 |
Previous AI Agent sessions can be soft-deleted. |
4302 |
Feature |
83 |
AI Agent sessions can be exported to PDF documents. |