Version 90 brings Project Roles up to the organization level, so they are defined once rather than once per URL. Actions can now calculate the values they set. Automated test runs check their own work more carefully, and do it faster. Veeva test generation reaches rules that span linked forms, and Document Templates can now run from the object lists you already work in.

For more information see the release notes for Version 90.

Project Roles, Defined Once

Until now, each URL in an organization had its own set of Project Role definitions. If you have more than a handful of URLs, keeping those sets consistent was tedious and easy to get wrong. In Version 90, Project Roles are defined and managed at the organization level and shared across all of an organization's URLs. Organization administrators manage them from the organization navigation, and a new bulk merge folds duplicate roles together. Role descriptions can now be edited too. We explained the thinking behind this change in Project Roles consolidated within an Organization.

Actions That Calculate

Actions could already collect a custom property value from the user or clear it. Now they can set a property to a fixed value, or to the result of an expression evaluated when the action runs. For example, a due date can be set to today() + days(10), a property can be set to the acting user, or one property can be copied from another on the same object. If an expression or a data collection step comes out empty, the property is cleared, just as Clear Property does. Action preconditions and standards rule logic also gain int() and float() conversions, and HTML custom properties collected by an action are now entered through a rich-text editor.

Custom Properties that belong to the built-in definition of an object type are now protected. They can no longer be edited, deleted or copied, so the properties TrialGrid relies on stay the way TrialGrid expects them.

Working Together in List Views

Spreadsheet views now have an Assignments column. It shows who is assigned to each object and lets you assign users to many objects at once. Columns for Labels, Standards, Test Cases and Custom Properties can now be chosen in the column picker even when they have no data yet, and every column you show is included in CSV, Excel, PDF, clipboard and print exports.

Document Templates Where You Need Them

Document Template reports can now be run directly from Draft object listings such as Forms, Fields and Custom Objects. The report receives the objects you have selected, plus those that match your current search and filters, so the list you see becomes the input to the report.

The AI tag inside Document Templates has also improved. It supports effort levels, and if output is truncated it now says so rather than quietly cutting it off. The new ai_json_list and ai_json_object functions return structured data, so the template controls the layout instead of the model.

Reusing Your Standard Library

A new Import Applicable Library Objects command on the Draft home page searches the Draft's Standard Library for Matrices, Edit Checks and Derivations whose Folders, Forms and Fields already exist in the Draft. You choose which ones to bring across, and any Custom Functions they depend on come with them. When you build a study from a standard, this fills in the logic that already fits the forms you have.

Test Runs That Check Their Own Work

Data entry steps now confirm that the values TrialGrid entered were actually stored. If a save stored nothing, the step retries it, and if the stored values differ from what was entered, the step fails and says so. Data entry is also faster. TrialGrid now reads Rave's own response to each save to see whether the Subject's Folders or Forms changed, and re-reads the Subject only when they did. When a step looking for a Folder name doesn't find it, a screenshot of the subject's folders is now captured so you can see what was there instead.

Email steps are easier to write and easier to trust. Subject and message matching now ignores differences in whitespace, line breaks and case. Expected text can include placeholders such as {subject_name} and {testcase_name}. The email forwarded as evidence now records the Scenario name, the line number of the email step and the step text, including the expected message, so each piece of evidence can be traced back to the step that produced it.

iMedidata service accounts are now held per organization, and TrialGrid rotates their stored passwords automatically on a schedule.

Veeva

The Veeva Test Case Advisor now generates test cases for rules that read an item on a linked form. The generated test enters data on both forms and links them with the "I link form" step, including when the rule reaches the linked form through a Form Link item. Setting up a run is simpler too: the Test Set Run wizard now lists the studies and sites the Vault account can reach, so you no longer have to type them in.

Veeva Lab Codelists and Lab Unit Codelists are now imported as object types of their own. A Lab codelist and a study codelist with the same name can therefore both be held in the same draft, and items that reference a Lab codelist resolve to it through new Lab Codelist and Lab Unit Codelist properties. Existing drafts are converted automatically. Lab codelists that were previously skipped because of a name collision need a re-import from the SDS.

AI Usage Limits

AI usage is now limited by cost rather than by tokens. Each organization has a monthly AI budget and each user has a daily cost limit. The AI usage report shows the cost of each day's usage, so it is clear where the budget is going.

This post was auto-generated by a LLM.