Version 91 makes deletion both easier and safer. Deleting things is more direct than before, and more of what you delete can now be restored. The release also introduces a new User custom property type, finer control over what our AI Agents are told, and Organization Roles.

For more information see the release notes for Version 91.

Deleting With Confidence

Deletion is now easier where it used to get in the way. Fields can be deleted from the Fields list, individually or in bulk. Any object can be deleted from its own editor using the Delete option in the dropdown beside Save. Deleting a Field in the Form Editor no longer refuses when other objects depend on it. Instead, it warns you which Edit Checks, Derivations and Lab Settings will be removed with it, and they are removed when the Form is saved.

It is also safer. Deleting a Project, Draft or URL now requires you to type DELETE to confirm, so a mis-click can no longer destroy work. If something is deleted by mistake, more of it can be recovered. Deleted Drafts appear on a new Deleted tab of the Project's Drafts list, showing who deleted them and when they will be removed permanently, and they can be restored from there. Deleted Test Cases have their own Deleted page in the Test Case list, where you can select any number and restore them in the background. A restored Test Case does not get back its labels, comments, ticket links or Test Run history.

A Custom Property for People

Custom Properties can now be of type User. Setting a value opens a picker of names and email addresses, and in listings the chosen person is shown with their avatar. Actions can set a User property to whoever runs the action by using the expression user, which makes fields such as "Reviewed by" or "Owner" simple to fill in as part of a workflow.

Telling Agents What Your Data Means

Custom Properties can now carry their own agent instruction. It is sent to the AI alongside the property's value, so the model is told what that particular property means instead of relying on a single instruction for the whole object type. To see the whole picture, Object Definitions have a new Agent Instructions tab. It shows the object type's own instruction and, for each property, whether the value is sent and what guidance goes with it. Anyone who can see the URL can read it, and editing needs the Manage Agent Configuration permission.

The Bulk Edit Check Creator's action hooks now export an outcome variable naming the hook that fired. This lets you select one action under several hooks, for example with the precondition agent("outcome") in ["custom_function_required", "build_failed"].

Organization Roles

Organization-level permissions now work the same way as Project permissions, through named roles. The new Organization Roles page is where they are defined and viewed, and each role decides what its holders can do. Holding "Administer Permissions" no longer grants every other permission, and a new "Can manage Icons" permission controls who can change Organization Icons. The background to this change is covered in Organization Roles.

Automated Testing

When you register a Medidata Rave URL, you now choose whether it is Rave Classic (direct or via iMedidata) or Rave EDC (the old or new user interface). TrialGrid no longer infers this from the Rave version. Registering a URL again resets its user access, so access is checked before the next run, and any Test Case Runs in progress on it are cancelled once you confirm. A URL already on the new Rave EDC interface keeps its access when it is registered as the new interface again.

When an expected email is not received, TrialGrid now lists the emails your organization did receive during the Scenario, with their date, time and subject, and highlights the differences between the expected text and the closest match. Most missing emails turn out to be near misses, and now you can see why.

Behind the scenes, a test run worker that is being retired is now returned to service when demand picks up again, rather than sitting idle while TrialGrid starts a replacement.

Veeva

On Veeva vaults at release 26R2 or later, test runs open forms directly using Veeva EDC's stable form links, and each form screenshot in the results links to that form in Veeva EDC. The Veeva Vaults list shows which Veeva release each vault is on. The release is read automatically from the vault when it is registered and whenever test cases run.

Settings Export

The URL settings export now includes a tab for Object Definition layouts, showing each layout definition and the roles it is assigned to.

This post was auto-generated by a LLM.