Version : 93
Released : 2026-11-29
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
5832 |
Feature |
A whole Draft can be downloaded through the API as an ALS or an Excel workbook, with the same warnings the Download button shows. |
|
5647 |
Bug |
Standard Rule logic and Action preconditions can now compare a property as a number with int() or float(), for example int(p("Max Subject Age")) < 18. |
|
5674 |
Feature |
Import Scripts can now create Test Cases with the CreateDraftObject command. Auto Actions on a Test Case, and on Custom Functions copied with an Edit Check or Derivation, now see the record's custom property values. |
|
5684 |
Bug |
Activity records for property values set or cleared by an Action now show quotes, apostrophes and the characters < > & as entered. |
|
5718 |
Bug |
Rule and Action text is now always shown as plain text. Rule logic, identifiers, attribute names and descriptions on the Standard Rules lists and the Active Rules tab, and preconditions, property values and object names in the Action dialog, display any markup literally rather than rendering it. Action names containing characters such as & now read correctly in Actions menus and the Action dialog. |
|
5886 |
Bug |
Checking which selected objects an Action can be applied to is now much faster for large selections of objects within a Draft. |
|
5747 |
Feature |
Administrators can set the output length and temperature for each AI task, and tasks without their own model use the model marked as the fallback. |
|
5789 |
Bug |
Activity recorded when a Label or Custom Property is deleted now appears in the right Organization, and older activity no longer links to unrelated objects. |
|
5895 |
Bug |
Deactivated users who had accepted their invitation no longer show as 'Expired' on the Organization and Project team pages; invitation status and the Resend button now appear only for invitations not yet accepted. |
|
5599 |
Bug |
Agents can be opened and used only by people the agent menu offers them to, and turning agents off, or losing access to the Project or URL, takes effect on the next message. |
|
5619 |
Feature |
The Custom Function review warns when a function looks for the unknown day "UN" anywhere in a value, with Contains, IndexOf or Replace. In a date with a month name this also matches "JUN", so a June date is treated as having an unknown day. |
|
5771 |
Bug |
The action buttons in the Progressive Display Advisor, Field Visibility Advisor and Custom Function Reviewer no longer show an "Invalid response type" error when clicked. |
|
5780 |
Bug |
When an AI model is set up with an API key setting the environment does not have, the agent now says the AI service is unavailable instead of asking you to reword your request. |
|
5782 |
Feature |
Import Scripts can now read the activity history of an object, and the activity of a URL or Organization limited to what you can view. |
|
5784 |
Feature |
AI answers are no longer cut short by a fixed length limit, so long test cases, summaries and document sections come back in full. |
|
5770 |
Bug |
The Bulk Edit Check agent now puts a field in the folder its specification names when the study matrix places the form there, and marks the check for review when it does not. The Edit Check Creator now uses that folder too when it builds a check from a specification. An edit that names a folder now moves the check to that folder when the study matrix allows it, and says why when it does not. An Add Form action written with a folder in front of the form is no longer reported as a missing form. |
|
5843 |
Bug |
Edit checks created by the Edit Check Creator, Bulk Edit Check, Test Case Creator and Field Visibility agents now give standard (non-log) fields Record Position 0 in their check steps and actions, as Quick Edit does, instead of leaving it blank. |
|
5852 |
Feature |
Agents now give an Object Definition's object instruction to the model as your organization's convention, followed over their own defaults but never over how the platform behaves, and agent replies have a "Knowledge used" panel listing the conventions, Draft context and Rave knowledge they were given. |
|
5856 |
Feature |
Agents that are given Rave or Veeva facts have an "Agent Knowledge" page listing those facts beside your conventions for the agent, and the knowledge names in an agent result's "Knowledge used" panel link to it. The Edit Check agent can now write checks that use a logical record position, such as comparing a value with the previous record's. The Agents list shows where each agent is available on the URL, and the Agents count on the URL home page counts the agents available somewhere. Action names in the Agents list are shown exactly as written. |
|
5595 |
Feature |
Test Cases in a Library can now be tagged with the Standard Rules they relate to. Copying custom objects that refer to a Standard Rule, and creating a Draft from a Library that contains them, no longer fails. |
|
5618 |
Feature |
When "Create scenarios with unknown dates?" is ticked and an Edit Check uses a Custom Function that tests for the unknown-day value "UN", the Test Case Advisor adds a scenario that enters a June date. A function that looks for "UN" anywhere in a date also finds it in "JUN", and this scenario catches that before a site does. The scenario is a copy of one already generated, with every date moved back by the same number of days, so the days between them are unchanged. Where the Advisor can tell which date the function tests, that is the date moved into June. It is not added when the function compares a date with today, which the move would change. |
|
5674 |
Feature |
Import Scripts can now create Test Cases with the CreateDraftObject command. Auto Actions on a Test Case, and on Custom Functions copied with an Edit Check or Derivation, now see the record's custom property values. |
|
5715 |
Feature |
Registered Veeva Vaults now use the API version of their own Veeva release, up to the newest version TrialGrid has been tested against, instead of staying on the version they were registered with. |
|
5734 |
Feature |
Inactivate and activate log record steps on Rave EDC now fail straight away with the reason when Rave does not allow the action, and the Test Case Editor warns about inactivating records on forms with fixed default values. |
|
5735 |
Bug |
A step that cannot enter a field on Rave EDC now fails without a long wait for the Save button. |
|
5736 |
Bug |
Rave EDC data entry now retries sooner when a form shows that it was updated by another user or the system. |
|
5743 |
Bug |
A Rave Classic run that Rave logs out now stops with Rave's own message, instead of reporting a TG_UAT problem on every remaining step. |
|
5744 |
Bug |
A subject step now says so when the subject page could not be opened for its screenshot. |
|
5748 |
Feature |
New Rave URLs can now use TrialGrid or individual Medidata credentials by default. support@trialgrid.com can set this for an Organization, and it is shown in Organization Settings. |
|
5787 |
Bug |
In a Rave EDC Test Case, a step entering data on a form that showed or hid a field part-way through the step could take a neighbouring field for the one being entered, and either fail with an error that named no field or enter the value into that field. A hidden field is now reported as not on the form, and a field that has moved is entered in its new place. |
|
5801 |
Bug |
Test Cases generated using AI for Edit Checks with Custom Function actions are more likely to run successfully without editing, including Dynamic Search List selections, inactivated records and non-conformant data. Scenarios which cannot run as written are left out, with the reason noted in the Test Case. |
|
5816 |
Feature |
The Test Case Advisor now generates Veeva Test Cases for rules that check whether a form is marked Intentionally Left Blank, and for rules that check whether a form has never been submitted. |
|
5769 |
Bug |
For Rave Classic URLs accessed via iMedidata, when the access check for a Test Case run, or the registration of a Rave URL, fails because your Rave account does not have the URL's TG_UAT role, the message now names the missing role. |
|
5842 |
Bug |
Test Case Runs in a Test Set Run now start in the order the Test Set Run page lists them, including when Test Case names contain underscores or other punctuation. |
|
4857 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that ask whether an item's value has changed since the form was last submitted. For a Send Email rule the Test Case enters the data that sends the email but does not check that it arrives. A Test Case for a rule that reads an item's previous submitted value no longer submits the form once too often when that value is blank. |
|
5030 |
Bug |
The Veeva test case View tab, test case PDF and Excel export now show the repeat numbers of repeating Event Groups, Forms and Item Groups in DataPoint references, event references and data tables, as they already did for the form of Form steps. |
|
5837 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that compare Form Link items, creating the linked forms each item needs and entering the links. A Form Link item the Test Case leaves empty is no longer entered, and a Test Case with a data entry step that gives a Form Link item an empty value now fails validation, because Vault's data API cannot clear a link. Remove that row from the step to run it. |
|
5839 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that read an item's change reason, changing the item with that reason. A new step, I enter and submit data with reason, enters data with a chosen change reason. |
|
5840 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that read an item another rule derives, entering the data that rule derives it from. |
|
5876 |
Feature |
When an Organization does not allow all events to be added, the Veeva test case generator now writes steps that add a non-Unscheduled event as comments instead of steps that fail validation. |
|
5877 |
Feature |
Vault Test Case Advisor templates can show a Rule's Description under the Feature heading using the new rule_description template variable. |
|
5717 |
Bug |
Veeva Item Groups and Items are listed, generated and tested in the order they appear on the Form, and the test case editor lists Forms, Events and Event Groups in the order the study defines them rather than alphabetically. Rules that sort Events by schedule follow the same order. |
|
5838 |
Feature |
The Test Case Advisor now writes Test Cases for Veeva rules that read an item's translated value (value_translated__v), entering the item in its standard unit. Rules on lab forms are still skipped, as before. |
|
5878 |
Feature |
Test cases generated for Veeva Comparison Rules that compare to a Casebook Variable now enter data on the item the variable is mapped to and check the query, instead of requiring manual authoring. |
|
5879 |
Feature |
Test cases generated for Veeva Comparison Rules whose first identifier is an event date now check that the query appears, or does not appear, on the event, instead of asking for manual verification. |
|
5617 |
Bug |
When a test case run resumes (after a pause, a browser restart or a worker restart), a scenario that had already failed is no longer continued with its remaining steps, unless the run is set to continue on failure. A run paused to free a worker now finishes the step it is on before pausing, instead of stopping part way through it. |
|
5889 |
Bug |
On new Rave EDC, the "all folders and forms in matrix … exist" step now switches to a role with Subject Administration and Create Subjects permission to add folders and forms, as the "folder exists" and "form exists" steps do. |
|
5892 |
Bug |
When the browser stops responding during a test case run, TrialGrid now relaunches it and resumes the run, instead of waiting out a timeout on every remaining command. |
|
5663 |
Feature |
Searching a Project's wiki now finds text within its pages, with each result linking to the heading where the match is. |
|
5669 |
Bug |
Wiki pages with a table that aligns a column now display instead of failing to load. |
|
5804 |
Feature |
Users can choose to receive workflow notification emails immediately, as an hourly digest, or not at all, and standards approval decisions now go only to the person who requested approval. |
|
5836 |
Bug |
A Project with no timeline now tells users who can apply a Timeline Template where to do it, with a link to the Timeline settings of the Project. |
|
5882 |
Bug |
The My Assignments page loads much faster for users with thousands of assigned objects. |
|
5642 |
Bug |
An object definition's External Name can no longer match a sheet the Draft download already writes, such as Checks or TG_Rules, downloads now include an object definition's sheet only when that object definition is selected, and draft uploads no longer fail on a sheet whose name only starts with Matrix. |
|
5661 |
Bug |
Saving a custom object from its page now updates its Updated date and the user who last changed it. |
|
5697 |
Bug |
Custom object identifiers that reference an Edit Check now always name that Edit Check. |
|
5871 |
Bug |
Rules that read a Project's custom property are now rechecked when an Action changes the property, or when one of its values is renamed, merged, converted or deleted. |
|
5890 |
Bug |
Progress for a background task, such as deleting or converting a Custom Property value, now always shows the result, even when the task finishes very quickly or the Documents dialog is closed while it is running. |
|
5622 |
Feature |
The Matrix OID settings on the All Forms and All Visits Diagnostics now accept wildcards such as UNIQUE*, and are matched without regard to upper and lower case or surrounding spaces. Projects whose Matrix OID did not previously match will start producing findings. The Field OID naming Diagnostics also have a new Regular Expression setting, for naming shapes that a fixed prefix or suffix cannot describe. The Excel version of the Diagnostics report now lists each Diagnostic's settings in the same order as the screen and the PDF. |
|
5633 |
Bug |
Copying Diagnostic settings from another Project with the Overwrite option now also copies the Allow Fix setting for Diagnostics which the Project already had. |
|
5638 |
Bug |
Copying Diagnostics now uses two clearly labelled Merge / Overwrite options that reset each time the dialog opens, names the mode in the success message, and confirms which Projects Copy to will change before writing. |
|
5263 |
Bug |
Using @= in a custom diagnostic or Import Script now behaves as it does in Python, rather than silently dividing. |
|
5641 |
Bug |
Import Scripts and Custom Diagnostics can now pass a list or dictionary as a
function's arguments with |
|
5682 |
Feature |
Diagnostic Explanations can now be edited on the Explanations tab of the Project's Manage Diagnostics page. |
|
5688 |
Bug |
The View Explanations button on a Draft's Diagnostics page now opens the Project's Explanations with the Explanations listed, and they stay listed when the page is refreshed. |
|
5689 |
Bug |
The explanations button on a Draft's Diagnostics page now reads Manage Explanations for users who can manage Diagnostics. |
|
5707 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags Codelist Items with an "Other" choice but no Item to capture the specification. The patterns that identify an "Other" choice and a specify Item are configurable. |
|
5708 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags specify Text Items with no corresponding "Other" choice, either because no Codelist in the Item Group has one or because the Item is not shown when "Other" is chosen. |
|
5709 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags Forms, Events, Items, Codelists and Rules whose names or labels contain keywords such as COPY, BACKUP, DRAFT or OLD, with configurable keywords, properties, ignored values and exclusions. Item Name Exclusions in the Double Spaces in Veeva Properties diagnostic now match Item Names starting with a pattern, such as ITEM*. |
|
5710 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags each Event where a repeating Form has no Date, Date/Time or identifier Item to tell its records apart, with configurable data types, Item Name patterns and Form and Event exclusions. |
|
5712 |
Feature |
TrialGrid now provides a Veeva diagnostic that highlights Codelist Entries marked Hidden, listing each Codelist's hidden entries in one finding, with an option to include Unit Codelist Entries. |
|
5713 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags Forms whose only data collection is a single repeating Item Group, which may be better configured as repeating Forms. |
|
5714 |
Feature |
A new Veeva diagnostic highlights repeating Event Groups whose Name or Label contains a number that could be confused with the instance number shown to study users, unless Event Group Repeat Labels are set. |
|
5739 |
Bug |
Saving a Custom Diagnostic whose code uses print now shows the problem against the code field instead of an error page. |
|
5740 |
Bug |
When a Custom Diagnostic fails in a diagnostics run, the reason shown now gives the line of the script responsible, and adding an invalid finding is reported as an error instead of crashing the test. |
|
5711 |
Feature |
TrialGrid now provides a Veeva diagnostic that reports Unit Codelists in the Vault study that no Item uses, for Drafts imported from Vault. |
|
5552 |
Feature |
Import Scripts and Document Templates can now list the URLs of an Organization that the user has permission to view and the object types defined in a URL, and read the properties of an object type without needing an object of that type. An object type also gives the name it is known by in files that go in and out of TrialGrid, so a script can tell which object type a sheet of a Draft download holds, and the properties that make up an object's identifier in the order they are joined, so a script can work out the identifier of each object listed on that sheet. Custom Properties of an object in another URL are now read from that URL. A Document Template can no longer list every object in a URL that uses a Label, a Custom Property, a Project Role or an object type. Read these from the Draft, Test Case or Ticket instead. |
|
5620 |
Bug |
The help now lists every query method, filter and built-in function an Import Script or Document Template can use, each with a worked example. An attribute or query field that does not exist is reported with the names you probably meant, an Import Script can now format a date with strftime, and an Import Script can read the objects a ticket is about. |
|
5578 |
Feature |
Import Scripts and Document Templates can read a Project's Wiki pages, including the code blocks a page holds, and can list the images a Ticket, comment or Wiki page holds. |
|
5660 |
Feature |
Document templates can call fail(message) to stop generation, and the generation fails showing that message. |
|
5666 |
Feature |
Document template settings can be marked Required. Generate stays disabled until every Required setting has a value, and the API refuses a generation request that leaves one empty. |
|
5667 |
Feature |
The Generate Document dialog shows a document template's description, and its settings' names and descriptions, exactly as typed, including their line breaks. |
|
5670 |
Feature |
Import Scripts and Document Templates can compare two objects, or an object with its Library Standard, and report the differences, rules and explanations. |
|
5781 |
Feature |
Import Scripts and Document Templates can now list the tickets that refer to a Form, Edit Check, Test Case or other object. |
|
5782 |
Feature |
Import Scripts can now read the activity history of an object, and the activity of a URL or Organization limited to what you can view. |
|
5784 |
Feature |
AI answers are no longer cut short by a fixed length limit, so long test cases, summaries and document sections come back in full. |
|
5860 |
Feature |
Document templates and scripts can list the team of a Project, showing who holds which Role in it. |
|
5863 |
Feature |
Document templates and scripts can tell whether a team member's account is active, so a report can name only the people who can sign in. |
|
5890 |
Bug |
Progress for a background task, such as deleting or converting a Custom Property value, now always shows the result, even when the task finishes very quickly or the Documents dialog is closed while it is running. |
|
5614 |
Feature |
The help is now also published as Markdown for AI assistants, with an index at /llms.txt on each TrialGrid server, so an assistant you use to write Import Scripts can read the help for the version of TrialGrid you work with. The index names the server's environment, so help from a prerelease server can be told apart from the help on the one you use day to day. |
|
5627 |
Feature |
The help now includes an Administrator Guide that walks Organization administrators through setting up roles, URL permissions, project teams and licenses. |
|
5587 |
Feature |
Posting a large Draft to Rave and generating a large Draft compare report now have a time limit. A post which has not completed after 4 hours, or a compare report after 75 minutes, is stopped and its task fails with the message "Task failed because it had not completed in the allowed time". TrialGrid Ltd can change where these two jobs run, and their time limits, without restarting the system. |
|
5593 |
Feature |
TrialGrid Ltd can change how many workers run background tasks without restarting the system. Tasks which log in to Rave or iMedidata, import a Draft from Rave or post to Rave can run on a worker of their own, separate from other background tasks. |
|
5601 |
Feature |
Background workers are replaced on a schedule without interrupting the work they are running, and only one task scheduler sends at a time. |
|
5236 |
System |
Automated checks now catch code changes that would leave some edited values unsaved. |
|
5699 |
Feature |
AI features can now run on newer AI models. A Test Case or Test Case run summary that the AI cuts off before it finishes no longer replaces the previous summary. |
|
5857 |
System |
The system script that recalculates a Draft's fingerprints one object at a time now includes custom objects. No user impact. |
|
5864 |
System |
Updated the soupsieve library to 4.1 to fix two security vulnerabilities (CVE-2026-126190 and CVE-2026-126192). No user impact. |
|
5874 |
System |
Automated browser tests now fail when a page raises a script error. Fixed a script error on the Test Case Run page for runs whose results have been deleted. |
|
5875 |
Bug |
Work that uses AI no longer fails when the AI service is briefly unavailable. |
|
5163 |
System |
Permanently removing deleted drafts skips unnecessary per-object test case updates, making the weekly removal faster. |
|
5165 |
Bug |
Permanently removing a draft, project or URL now clears its cached details immediately, so it no longer appears briefly afterwards. |
|
5881 |
Bug |
If the cache server stops responding, page updates and other background requests no longer hang waiting for it. |
|
5678 |
Bug |
Saving a large Edit Check property sheet is several times faster. |
|
5346 |
Bug |
The user list, calendar and description search on Activities pages, and filters that match few rows, are faster on URLs, Projects and Organizations with long histories. |
|
5882 |
Bug |
The My Assignments page loads much faster for users with thousands of assigned objects. |
|
5886 |
Bug |
Checking which selected objects an Action can be applied to is now much faster for large selections of objects within a Draft. |
|
5767 |
Feature |
Organization administrators can invite people from the Organization Team page with an Organization Role and no Project. Invitees accept by setting a password or signing in through the Organization's SSO. |
|
5866 |
Bug |
Deleting a Draft, uploading a Draft and importing a Draft from Rave now require the Create Draft permission, as they already do in the menus. |
|
5678 |
Bug |
Saving a large Edit Check property sheet is several times faster. |
|
5683 |
Feature |
Import Scripts can now create Matrices with the CreateDraftObject command, and set which Folders and Forms a Matrix holds with the new SetMatrixFolderForm command. A Matrix Name must now be unique within the Draft, as Rave requires, so a Matrix that shares its Name with another must be renamed before it can be saved. Saving the Matrices grid when a Folder or Form it names is no longer in the Draft now says which one, instead of failing. |
|
5749 |
Bug |
Converting a Custom Function to the V2 API keeps an assignment to a protocol deviation's Active, which V2 still allows, instead of changing it to Activate or InActivate, which a protocol deviation does not have. Such functions are no longer flagged because the converted code does not compile. |
|
5750 |
Bug |
A Custom Function that uses something with no V2 equivalent is flagged as needing a person when converting it to the V2 API, including when Rave is the first to report that it has no equivalent. It was flagged as having no conversion rule. |
|
5751 |
Feature |
Converting a Custom Function to the V2 API now converts an ID compared with 0, meaning that there is no object, such as DataDictionaryID > 0, to its Ref compared with the Ref type's default value, as Medidata advise. Such functions were left unconverted. |
|
5752 |
Feature |
Converting a Custom Function to the V2 API now converts a common way of finding a data point's latest entered value, which keeps its audits in a SortedList keyed by audit ID. V2's audits have no ID, so the converted function orders them by the time each was made, as Medidata advise. Such functions were flagged as needing a person. |
|
5753 |
Feature |
A Custom Function that converting to the V2 API takes over Rave's 8,000 character limit is laid out as the editor's Auto-indent does, and if it is still too long it is converted all the same and flagged for a person to shorten, instead of being left unconverted. |
|
5755 |
Bug |
Converting a Custom Function to the V2 API that keeps a check's or CRF version's ID in a variable starting at 0 gives the variable the Ref type's default value. It kept the 0, which does not compile for a Ref, so the function was flagged as not compiling. |
|
5760 |
Bug |
A Custom Function comparing a data point's FreezeDisplayStatus with Frozen or Unfrozen is classified as converting to the V2 API automatically, and is converted, rather than being marked as needing a person once Rave reports Frozen as having no V2 equivalent. |
|
5761 |
Feature |
Converting a Custom Function to the V2 API now converts a call adding a form to a folder with AddCRF that passes the subject's CRF version ID, a folder ID or 0 where AddCRF takes a subject matrix. V1 adds the form whatever it is given, so the call becomes AddDataPage, as one passing the subject matrix does. Such functions were flagged as having no conversion rule. |
|
5762 |
Feature |
Converting Custom Functions to the V2 API converts much more of the V1 code found in real drafts, and a function that can't be converted no longer holds back every function linked to it by calls. Only the functions it calls, and any that may pass it a list or read one back from it, stay V1 with it, each flagged with its name. Sorting the Custom Functions list by V2 Conversion now orders a flagged function by its flag. |
|
5830 |
Feature |
A public trial page lets people sign up with a work email address and convert up to 10 of their own Medidata Rave custom functions from the V1 API to V2. |
|
5719 |
Bug |
The OID mismatch list in the Rave export warnings now collapses behind "Show details", and the warnings step no longer uses inline script. |
|
5737 |
Bug |
After a failed Post to Rave or draft import, the wizard now asks for your password again before retrying, and a task that cannot start now shows as failed. |
|
5775 |
Feature |
Designer imports now bring in each field's Variable OID, which is shown and compared like any other field attribute. |
|
5779 |
Bug |
The form editor now saves new forms, new fields and field changes for Designer studies. |
|
5552 |
Feature |
Import Scripts and Document Templates can now list the URLs of an Organization that the user has permission to view and the object types defined in a URL, and read the properties of an object type without needing an object of that type. An object type also gives the name it is known by in files that go in and out of TrialGrid, so a script can tell which object type a sheet of a Draft download holds, and the properties that make up an object's identifier in the order they are joined, so a script can work out the identifier of each object listed on that sheet. Custom Properties of an object in another URL are now read from that URL. A Document Template can no longer list every object in a URL that uses a Label, a Custom Property, a Project Role or an object type. Read these from the Draft, Test Case or Ticket instead. |
|
5594 |
Feature |
An Import Script can now copy any kind of record from another draft with one command, CopyDraftObject, which is told the kind and which record to copy. A form, a folder, an edit check, a derivation, a matrix, a data or unit dictionary, a custom function, a test case and a record of a type you defined can all be copied this way, and a standard rule can be copied into a library. A record that sits inside another, such as a field on a form, is copied by naming the record it belongs to, which has to be in the draft already. It replaces CopyForm, which has been removed, so a script which copied a form now asks for CopyDraftObject with type "Form". |
|
5626 |
Feature |
Import Scripts can now write a Project's wiki. SetWikiPage writes the whole of a page, creating it if needed, AppendToWikiPage adds text to the end of a page, and EditWikiPage replaces text it finds exactly once, or everywhere when asked. AddWikiImage adds an image for pages to show, checked and re-encoded as an image pasted into the wiki is. Each change adds a version to the page's history, credited to the person who applied it. |
|
5620 |
Bug |
The help now lists every query method, filter and built-in function an Import Script or Document Template can use, each with a worked example. An attribute or query field that does not exist is reported with the names you probably meant, an Import Script can now format a date with strftime, and an Import Script can read the objects a ticket is about. |
|
5634 |
Feature |
Import Scripts can read JSON held as text with parse_json, so a script can work with the JSON in a Custom Property or a spreadsheet cell instead of picking at it with string methods. Where the text is not JSON it raises ValueError, which a script can catch to report the row that was wrong and carry on. NaN and Infinity are refused both by parse_json and in a JSON file given to a script, as are .nan and .inf in a YAML file. |
|
5263 |
Bug |
Using @= in a custom diagnostic or Import Script now behaves as it does in Python, rather than silently dividing. |
|
5564 |
Bug |
Import Scripts can now pass numbers and dates read from a JSON or YAML file to a command, and true or false to a true/false attribute. In a YAML file, values such as Yes, No and 0123 are now read as written rather than as true/false or a number. |
|
5641 |
Bug |
Import Scripts and Custom Diagnostics can now pass a list or dictionary as a
function's arguments with |
|
5655 |
Feature |
Import Scripts can now create Folders and Custom Functions with the CreateDraftObject command. |
|
5670 |
Feature |
Import Scripts and Document Templates can compare two objects, or an object with its Library Standard, and report the differences, rules and explanations. |
|
5674 |
Feature |
Import Scripts can now create Test Cases with the CreateDraftObject command. Auto Actions on a Test Case, and on Custom Functions copied with an Edit Check or Derivation, now see the record's custom property values. |
|
5683 |
Feature |
Import Scripts can now create Matrices with the CreateDraftObject command, and set which Folders and Forms a Matrix holds with the new SetMatrixFolderForm command. A Matrix Name must now be unique within the Draft, as Rave requires, so a Matrix that shares its Name with another must be renamed before it can be saved. Saving the Matrices grid when a Folder or Form it names is no longer in the Draft now says which one, instead of failing. |
|
5676 |
Feature |
Import Scripts can now create Data Dictionaries, Unit Dictionaries and their entries with the CreateDraftObject command. |
|
5730 |
Feature |
Import Script runs can now issue up to 20,000 commands. Large runs are summarised by kind of command, and the full list can be downloaded as text or JSON. A test run's log has a tab of its own, which a run that failed opens on. |
|
5758 |
Feature |
An Import Script can keep what it finds as named tables and values, and a test run shows them on a tab of their own, which a script that only looked something up opens on. A filter on text that finds nothing now says why, naming a value that differs only in upper or lower case, or listing the values that are there. A custom property can be named in any case, and naming one that is not defined says which names are. Saving or running a script that adds to a dictionary entry with += now says how to write it out in full, and a URL lists the Projects you have permission to view. |
|
5781 |
Feature |
Import Scripts and Document Templates can now list the tickets that refer to a Form, Edit Check, Test Case or other object. |
|
5782 |
Feature |
Import Scripts can now read the activity history of an object, and the activity of a URL or Organization limited to what you can view. |
|
5546 |
Feature |
Copies an Import Script makes one after another are now made together, up to 100 at a time, so a Folder and the Folder it sits in, or a Form and the Form it links to, are linked whichever of the two is copied first. |
|
5671 |
Feature |
Import Scripts can now create Fields in a Form with the CreateDraftObject command. |
|
5673 |
Feature |
Import scripts can now create Standard Rules in a library Draft with CreateDraftObject. A Standard Rule saved without an Identifier is no longer given one that another rule saved with it uses. |
|
5567 |
Bug |
On a Designer URL, CreateDraftObject no longer lets a script set Form attributes that apply only to Classic Rave. A blank value for an attribute a script cannot set now sets nothing, rather than stopping the command. |
|
5675 |
Feature |
Import Scripts can now create Edit Checks and Derivations, with their steps and actions, with the CreateDraftObject command. |
|
5860 |
Feature |
Document templates and scripts can list the team of a Project, showing who holds which Role in it. |
|
5863 |
Feature |
Document templates and scripts can tell whether a team member's account is active, so a report can name only the people who can sign in. |
|
5865 |
Feature |
Import Scripts can now change a Project's settings and custom properties with UpdateProject. Changes to custom properties across many Projects are checked against your rules together, once per set of properties changed. |
|
5859 |
Feature |
Import Scripts can change existing draft records with UpdateDraftObject, including their custom properties, the Fields of a Form, the entries of a dictionary, and the logic, steps and actions of an Edit Check or Derivation. |
|
5630 |
Bug |
Users can now be emailed when their account signs in from a new location. support@trialgrid.com can turn this on for an Organization, and it is shown in Organization Settings. |
|
5679 |
Bug |
The object compare page now checks that you can view both Drafts before comparing them. |
|
5718 |
Bug |
Standard Rule text is now shown as text on the Active Rules tab and in Standard Rules lists. Markup in a rule's description, such as PreText formatting, is displayed literally rather than applied. |
|
5718 |
Bug |
Rule and Action text is now always shown as plain text. Rule logic, identifiers, attribute names and descriptions on the Standard Rules lists and the Active Rules tab, and preconditions, property values and object names in the Action dialog, display any markup literally rather than rendering it. Action names containing characters such as & now read correctly in Actions menus and the Action dialog. |
|
5719 |
Bug |
The OID mismatch list in the Rave export warnings now collapses behind "Show details", and the warnings step no longer uses inline script. |
|
5725 |
Feature |
TrialGrid no longer sends the obsolete Expect-CT HTTP header, which browsers now ignore because they enforce Certificate Transparency by default. |
|
5738 |
System |
Two-factor codes and encrypted Rave and iMedidata credentials are no longer written to the application logs, and the iMedidata login lock and two-factor cookie log lines no longer name the account. |
|
5790 |
Bug |
Text from a Test Case script or from Vault is now shown as text in Veeva step results, rather than being interpreted as HTML. |
|
5356 |
Bug |
The Veeva test runner no longer writes any part of the Vault session id to its logs. |
|
5864 |
System |
Updated the soupsieve library to 4.1 to fix two security vulnerabilities (CVE-2026-126190 and CVE-2026-126192). No user impact. |
|
5866 |
Bug |
Deleting a Draft, uploading a Draft and importing a Draft from Rave now require the Create Draft permission, as they already do in the menus. |
|
5880 |
Feature |
Content Security Policy violation reports now include a short sample of the offending inline script, so violations can be traced to their source. |
|
5898 |
Feature |
The Content Security Policy can now be enforced in an environment rather than only reported, and violations are reported either way. Pages can no longer be shown inside a frame on another website. |
|
5595 |
Feature |
Test Cases in a Library can now be tagged with the Standard Rules they relate to. Copying custom objects that refer to a Standard Rule, and creating a Draft from a Library that contains them, no longer fails. |
|
5640 |
Bug |
A field, dictionary entry or other object covered by a May Exist rule can now be deleted from a Draft without being reported as a deviation from the standard, as the help describes. |
|
5647 |
Bug |
Standard Rule logic and Action preconditions can now compare a property as a number with int() or float(), for example int(p("Max Subject Age")) < 18. |
|
5652 |
Bug |
Standard Rules with the same priority that require the same value are now applied, instead of cancelling each other out. |
|
5653 |
Feature |
A new Rule Health tab on the Standard Rules page lists library rules that can never take effect, or that duplicate or contradict another rule, with the reason for each. |
|
5657 |
Bug |
Saving a Standard Rule on a custom object now updates compliance correctly when the Draft has custom objects of another type with the same name. |
|
5659 |
Feature |
Rule Health can now fix the rules it reports: select findings to delete or inactivate their rules, or step through a wizard that suggests a fix for each one and applies every change together once you confirm. |
|
5662 |
Bug |
The object compare page, compliance export and bulk explain now apply only the rules for a custom object's own type, so they agree with the compliance result. Testing a custom object rule's identifier now lists only objects of that type. |
|
5665 |
Feature |
Rule Health findings can now be dismissed with a reason. A dismissed finding is hidden until a rule in it changes, can be shown with a filter, and the dismissal can be withdrawn. |
|
5658 |
Bug |
After a library Standard Rule is changed, each Draft linked to the library now shows compliance worked out from its own selected rules and its own Project's explanations. Previously, a Draft holding an identical copy of a library object could be given the compliance result of another Draft. |
|
5651 |
Bug |
Must have Attribute rules can only name an attribute that standards compliance compares. The rule editor lists the attributes for every object type, a name it does not recognise is refused with the nearest valid one suggested, and neither the ALS import nor a library compare copies such a name onto a rule. |
|
5650 |
Bug |
On a Draft's Active Rules tab, a wildcard rule is no longer linked to a single object that happens to share its text. |
|
5718 |
Bug |
Standard Rule text is now shown as text on the Active Rules tab and in Standard Rules lists. Markup in a rule's description, such as PreText formatting, is displayed literally rather than applied. |
|
5718 |
Bug |
Rule and Action text is now always shown as plain text. Rule logic, identifiers, attribute names and descriptions on the Standard Rules lists and the Active Rules tab, and preconditions, property values and object names in the Action dialog, display any markup literally rather than rendering it. Action names containing characters such as & now read correctly in Actions menus and the Action dialog. |
|
5673 |
Feature |
Import scripts can now create Standard Rules in a library Draft with CreateDraftObject. A Standard Rule saved without an Identifier is no longer given one that another rule saved with it uses. |
|
5825 |
Bug |
Copying many Standard Rules at once updates the Drafts linked to the library once, rather than once per rule. |
|
5576 |
Bug |
Changes to objects in a standards library, whether made in an editor, by a diagnostic fix, by a rename, by merging an imported draft or by restoring test cases, now start a single compliance update for linked drafts instead of several. |
|
5664 |
Bug |
Compliance for a custom object now applies the Standard Rules for its child objects, as the compare page does. |
|
5658 |
Bug |
After a library Standard Rule is changed, each Draft linked to the library now shows compliance worked out from its own selected rules and its own Project's explanations. Previously, a Draft holding an identical copy of a library object could be given the compliance result of another Draft. |
|
5679 |
Bug |
The object compare page now checks that you can view both Drafts before comparing them. |
|
5741 |
Bug |
Bulk explanation of deviations now completes when a Standard rule requires a child object that the Draft does not contain, and records the explanation against that missing object. Bulk changing explanations from one state to another now changes only the explanations already in that state, so a change from Request Approval to Approved no longer approves deviations that have no explanation. |
|
5772 |
Bug |
Draft Compare no longer shows Forms from an imported ALS as Different after an edit when their content matches. |
|
5803 |
Bug |
Importing Forms, Folders, Edit Checks and Derivations into a draft linked to a library is faster, and imported Edit Checks, Derivations and Custom Functions show their correct standards compliance straight away, rather than only after their next edit. |
|
5804 |
Feature |
Users can choose to receive workflow notification emails immediately, as an hourly digest, or not at all, and standards approval decisions now go only to the person who requested approval. |
|
5683 |
Feature |
Import Scripts can now create Matrices with the CreateDraftObject command, and set which Folders and Forms a Matrix holds with the new SetMatrixFolderForm command. A Matrix Name must now be unique within the Draft, as Rave requires, so a Matrix that shares its Name with another must be renamed before it can be saved. Saving the Matrices grid when a Folder or Form it names is no longer in the Draft now says which one, instead of failing. |
|
5705 |
Feature |
Veeva drafts can now be imported straight from a Vault: choose the Vault, study and casebook version, and TrialGrid exports the study design specification and imports it. |
|
5726 |
Feature |
Drafts imported from Vault now record their Vault, study and casebook version, and list the Forms, Item Groups, Items, Codelists and Unit Codelists that exist in Vault but are not used in the study on a new Unused Objects tab on the draft home page. |
|
5721 |
Bug |
Matrix Explorer now draws Drafts containing an Edit Check with no data points, and hovering over an Edit Check or a field connector works for Edit Checks with quotes or backslashes in their names. Hovering over a View or Entry Restriction button in the Form Editor now highlights its EDC Role. |
|
5733 |
Feature |
Drafts imported from Vault can now be synced from the draft home page. Sync shows what has been added, changed and deleted in a chosen casebook version, and on confirmation applies it, keeping Test Cases, and the comments, labels and custom properties of objects that still exist. |
|
5759 |
Bug |
Clicking a column heading on the Fields list sorts the Fields within each Form again. |
|
5831 |
Bug |
Downloading a Draft is recorded in the Draft's activity again. |
|
5834 |
Feature |
Downloading a Draft as an Excel workbook gives the .xlsx file itself rather than a zip archive. |
|
5716 |
Bug |
Importing a Veeva Design Specification now keeps each Rule's Event Binding Type and Selected Events. |
|
5815 |
Bug |
Importing a Veeva Design Specification now reports a Comparison Rule that names a form no longer in the study as a single warning, instead of errors for each of its references. |
|
5867 |
Bug |
Uploading a Draft with a Custom Function whose Language is not C# or SQL now names the function and explains what to correct, instead of failing with an empty error. Names quoted in Draft upload error messages are now shown exactly as they appear in the file. |
|
5868 |
Bug |
Edit Checks whose steps cannot be converted when a Draft is uploaded are now marked as having a syntax error and reported in the upload messages. |
|
5869 |
Bug |
A Draft upload with an invalid or missing Record Position, or a similar column, in Edit Check or Derivation steps now imports with a warning instead of failing. |
|
5884 |
Bug |
Renaming Folders, Forms and other objects in Drafts linked to a library, and deleting Folders, are now much faster; standards explanation status is updated in the background. |
|
5888 |
Bug |
Edit Check and Derivation logic whose quoted values between them use every QuickEdit delimiter (| , : ; %) is now refused with a message when saved, instead of failing with an error. |
|
5781 |
Feature |
Import Scripts and Document Templates can now list the tickets that refer to a Form, Edit Check, Test Case or other object. |
|
5793 |
Bug |
Saving a ticket's due date without changing it no longer records an activity. |
|
5694 |
Bug |
Tickets are now checked the same way whichever page changes them, and closing, commenting on or labelling a Ticket no longer undoes a description change made at the same time. Saving a title or description that someone else has changed since you opened the page now asks you to reload. |
|
5720 |
Bug |
Closing a modal window immediately after saving its contents now closes it, rather than the Close button doing nothing. |
|
5764 |
System |
Drop-down lists across TrialGrid now use one updated selection control. Search, ticked multi-selects and Select All work as before. |
|
5792 |
System |
Date fields in activity search, the admin task history and ticket due dates now use the browser's own date picker. |
|
5890 |
Bug |
Progress for a background task, such as deleting or converting a Custom Property value, now always shows the result, even when the task finishes very quickly or the Documents dialog is closed while it is running. |
|
5006 |
Bug |
Republishing validation documentation now replaces the previously cached copy. |
|
5696 |
Feature |
Validation documentation generation was improved. |
|
5746 |
Bug |
Screenshots for features covered by the live Rave and Veeva tests are published in the validation documentation again. |
|
5756 |
System |
The validation documentation now shows downloading Diagnostics results as PDF and Excel, re-running Diagnostics after a fix, sorting the Fields list, deleting Fields used by a Derivation, and creating a Veeva Draft from an SDS. |
|
5766 |
Feature |
Validation documentation is opened by signing in to TrialGrid, replacing the shared password. Access is given by TrialGrid. |
|
5757 |
System |
The validation documentation now shows these agents at work, checking what each one saves or shows: Custom Diagnostic, Help, Test Case, Veeva Test Case, Test Case Search, Specification Review, Edit Check, Bulk Edit Check and Progressive Display. |
|
5768 |
Feature |
The TMS site is opened by signing in to TrialGrid, replacing the shared password. TrialGrid gives access to it separately from validation documentation. |
|
5705 |
Feature |
Veeva drafts can now be imported straight from a Vault: choose the Vault, study and casebook version, and TrialGrid exports the study design specification and imports it. |
|
5707 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags Codelist Items with an "Other" choice but no Item to capture the specification. The patterns that identify an "Other" choice and a specify Item are configurable. |
|
5708 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags specify Text Items with no corresponding "Other" choice, either because no Codelist in the Item Group has one or because the Item is not shown when "Other" is chosen. |
|
5709 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags Forms, Events, Items, Codelists and Rules whose names or labels contain keywords such as COPY, BACKUP, DRAFT or OLD, with configurable keywords, properties, ignored values and exclusions. Item Name Exclusions in the Double Spaces in Veeva Properties diagnostic now match Item Names starting with a pattern, such as ITEM*. |
|
5710 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags each Event where a repeating Form has no Date, Date/Time or identifier Item to tell its records apart, with configurable data types, Item Name patterns and Form and Event exclusions. |
|
5712 |
Feature |
TrialGrid now provides a Veeva diagnostic that highlights Codelist Entries marked Hidden, listing each Codelist's hidden entries in one finding, with an option to include Unit Codelist Entries. |
|
5713 |
Feature |
TrialGrid now provides a Veeva diagnostic that flags Forms whose only data collection is a single repeating Item Group, which may be better configured as repeating Forms. |
|
5714 |
Feature |
A new Veeva diagnostic highlights repeating Event Groups whose Name or Label contains a number that could be confused with the instance number shown to study users, unless Event Group Repeat Labels are set. |
|
5715 |
Feature |
Registered Veeva Vaults now use the API version of their own Veeva release, up to the newest version TrialGrid has been tested against, instead of staying on the version they were registered with. |
|
5726 |
Feature |
Drafts imported from Vault now record their Vault, study and casebook version, and list the Forms, Item Groups, Items, Codelists and Unit Codelists that exist in Vault but are not used in the study on a new Unused Objects tab on the draft home page. |
|
5733 |
Feature |
Drafts imported from Vault can now be synced from the draft home page. Sync shows what has been added, changed and deleted in a chosen casebook version, and on confirmation applies it, keeping Test Cases, and the comments, labels and custom properties of objects that still exist. |
|
5711 |
Feature |
TrialGrid now provides a Veeva diagnostic that reports Unit Codelists in the Vault study that no Item uses, for Drafts imported from Vault. |
|
5777 |
Feature |
In a Veeva Test Case, entering data that shows an item with a fixed default value (a Set Derived Value rule) in a form's first save now gets that default from Vault, as entering it in the EDC does. Where Vault may not apply such a default, the step's results say so. |
|
5778 |
Feature |
There are new Veeva Test Case steps to mark items Intentionally Left Blank with a reason, and to check whether an item is Intentionally Left Blank. The Test Case Advisor now generates Test Cases for rules that read whether an item is Intentionally Left Blank (intentionally_left_blank__v); a scenario that needs the mark enters the item blank and then marks it with the reason "Unknown". |
|
5790 |
Bug |
Text from a Test Case script or from Vault is now shown as text in Veeva step results, rather than being interpreted as HTML. |
|
5805 |
Bug |
In a Veeva Test Case, "I add form" failed on a form whose first item was a Label or a derived item. The form is now added through the first item a value can be entered into, and when Vault refuses to add a form the step says which item it refused and why. |
|
5806 |
Bug |
In a Veeva Test Case, entering data into a row of a repeating item group when the rows before it did not exist yet failed, because Vault creates the rows of an item group in order. The missing rows are now added blank first, and the step says which rows it added. |
|
5807 |
Bug |
The Test Case Advisor now writes Veeva Test Cases for a derived value on a form another rule adds, or on a form that is not on the event the rule is bound to. The Test Case makes the rule that adds the form run, checks the value on an event that has the form, and saves the form before checking it, because Vault derives a value only when it is saved. |
|
5808 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule that derives a date, the expected value is now the date as the form shows it, such as 29-Oct-2024 or 29-Oct-2024 00:00, instead of a number. A date formatted with Text(), on its own or inside a longer text, is expected as the date, with its month and year written in upper or lower case, such as dd-MMM-YYYY, and a format whose parts run together, such as yyyymmdd, is formatted part by part, so a rule that works out an age from two dates can now be generated. A value that is today's date from Today() or Now(), as a date or formatted with Text(), is expected as {{ today }}, which the run fills in with the date at the site. Any other value that depends on when Vault derives it, such as a date 30 days from today, an age on today's date or a time, is checked only for having a value. |
|
5809 |
Bug |
The Test Case Advisor no longer writes Veeva Test Cases that enter data Vault or the runner refuses. An item shown only when its Controlling Item has certain values is entered with one of those values in the Controlling Item. A derived item is not entered, and the text another rule derives from the data entered fits that item's length. A derived value checked on an item shown only by a Controlling Item is checked with the Controlling Item set to show it, as Vault left the value blank while the item was hidden. A rule that can only be tested by entering data into a hidden item, or into an item another rule derives, or that reads the value of a Form Link item, now says so instead of producing a Test Case that fails. A rule that only checks whether a Form Link item is blank is still generated, and where the item needs a value it is linked to an instance of its linked form. A rule that compares a codelist item with a value that is not one of its codes is named when no Test Case can be generated. In a Veeva Test Case, an item shown by a ticked checkbox can now be entered once the checkbox is ticked. |
|
5810 |
Bug |
The Test Case Advisor no longer writes a blank in a Veeva Test Case where the scenario needs the codelist choice 0. A rule that compares an item with "0" now has that choice entered as 0. |
|
5811 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a Set Subject Status rule, the scenario in which the rule does not run now expects the status another rule sets from an event the Test Case adds to its setup, such as In Screening, instead of Pre Screen. |
|
5812 |
Bug |
In a Veeva Test Case the Test Case Advisor writes, a value it enters for a text item is no longer chosen with a space at either end, which the Test Case could not enter. The value a rule derives from it is expected as Vault derives it from the value entered. A value a rule derives from the subject's name (@Casebook.subject_name__v) is expected with the placeholder {{ Subject.name }}, which the steps that check a value replace with the subject's name when they run. |
|
5817 |
Bug |
When the Background of a Veeva Test Case the Test Case Advisor writes has to give an event a date so that another Add Event rule adds an event the Test Case uses, and that date alone makes the rule under test true, the Test Case no longer has a scenario in which the Rule Actions are not run, which could never pass. A comment in the Test Case says why it was left out. |
|
5818 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for an Add Form rule, the event the form goes in is now added with a date, before the data that runs the rule. Vault gives an event no forms until it has a date, so a form whose event was added without a date was never added and the Test Case failed. |
|
5819 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule that reads an event's change reason, the step that sets the change reason now also moves the event's date by a day, within the event's window when the window allows it and with the planned date overridden when it does not. Vault keeps an event's change reason, and runs the rules that read it, only when the event's date changes, so a change reason set on its own did not run the rule and the Test Case failed. |
|
5820 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule whose Action Target is on an event the rule does not read, such as a value derived onto a form in another event group, that event is now added, with a date, before the value is checked. The Test Case used to check a form on an event the subject did not have. |
|
5821 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule that reads the previous or next record of a repeating form (@Form[-1] or @Form[+1]), the records the scenario enters are now records of that form even when an item group on it also repeats. The Test Case used to enter rows of the item group on the first record, and expected the query on a second record it never created. |
|
5822 |
Bug |
In a Veeva Test Case the Test Case Advisor writes, when the Background needs an event that an Add Event rule adds from an item the rule under test sets itself, the Background now runs that Add Event rule another way it allows, such as giving an earlier event the change reason the rule reads, before it adds the event. The Background used to add the event with nothing to make Vault add it, and every scenario failed. |
|
5816 |
Feature |
The Test Case Advisor now generates Veeva Test Cases for rules that check whether a form is marked Intentionally Left Blank, and for rules that check whether a form has never been submitted. |
|
5823 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule that derives a Boolean item, the value expected is now true or false, as Vault shows it. The Test Case used to expect 0 or 1 and failed. |
|
5824 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for an Add Event rule that reads the event it adds, a scenario in which the rule does not run no longer adds that event or marks it did not occur. Vault removes the event, while it has no data, once the rule is false, so marking it failed. |
|
5826 |
Bug |
In a Veeva Test Case the Test Case Advisor writes, an item shown only when another item has a given value is now always entered after that value, including when the rule reads both items, when the value makes another rule add a form, and for a Form Link item. The item used to be entered first, and the step failed because the item was hidden. |
|
5827 |
Bug |
A Veeva Test Case the Test Case Advisor writes no longer enters a number with more digits before the decimal point than the item's Length, which Vault refused. This happened when the item's Max Value was longer than its Length. |
|
5828 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule that reads only event dates and needs an event without a date, the scenario in which the rule runs now adds that event without a date. It used to give the event a date, which made the rule false. |
|
5829 |
Bug |
The Test Case Advisor now recognises a Veeva Add Form rule that has no Rule Bindings, taking the events its @EventGroup references name. A Veeva Test Case that enters data into a form such a rule adds now first enters the data that makes the rule add the form. It used to fail with "[Form] is not repeating". |
|
5841 |
Bug |
The Test Case Advisor now writes Veeva Test Cases for rules that compare an item's unit (unit__v) with the unit's code. It compared the unit's label instead, so such a rule was refused unless the code and the label were the same. The unit is still entered by its label. |
|
5845 |
Bug |
The Test Case Advisor now generates Veeva Test Cases for rules that read a linked form the casebook places on a different event from the rule's own form, such as an Adverse Event form on a Common Forms event. The linked form's data is entered on the event that holds it and linked to the form under test, instead of the rule being skipped. |
|
5846 |
Bug |
The Test Case Advisor no longer writes a Veeva Test Case that expects a subject status Vault cannot return to, because another rule has already moved the subject to a later status. |
|
5847 |
Bug |
In a Veeva Test Case for a rule that reads both @Form and @Event data, the Test Case Advisor now enters the @Event data on the same event as the @Form data. |
|
5848 |
Bug |
Veeva Test Cases no longer leave the Subject ID blank in studies where site users enter it. |
|
5850 |
Bug |
In a Veeva Test Case the Test Case Advisor writes for a rule that counts the forms linked to its form, a linked form that does not repeat on its event is now linked without first being added, which Vault does not allow. If a rule adds that form, the data that makes the rule add it is entered first. |
|
5356 |
Bug |
The Veeva test runner no longer writes any part of the Vault session id to its logs. |
|
5716 |
Bug |
Importing a Veeva Design Specification now keeps each Rule's Event Binding Type and Selected Events. |
|
5815 |
Bug |
Importing a Veeva Design Specification now reports a Comparison Rule that names a form no longer in the study as a single warning, instead of errors for each of its references. |
|
5858 |
Bug |
Veeva Test Cases for rules that read both how many forms are linked and the linked forms' data now link each form once, and no longer add an extra form. |
|
4857 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that ask whether an item's value has changed since the form was last submitted. For a Send Email rule the Test Case enters the data that sends the email but does not check that it arrives. A Test Case for a rule that reads an item's previous submitted value no longer submits the form once too often when that value is blank. |
|
5030 |
Bug |
The Veeva test case View tab, test case PDF and Excel export now show the repeat numbers of repeating Event Groups, Forms and Item Groups in DataPoint references, event references and data tables, as they already did for the form of Form steps. |
|
5837 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that compare Form Link items, creating the linked forms each item needs and entering the links. A Form Link item the Test Case leaves empty is no longer entered, and a Test Case with a data entry step that gives a Form Link item an empty value now fails validation, because Vault's data API cannot clear a link. Remove that row from the step to run it. |
|
5839 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that read an item's change reason, changing the item with that reason. A new step, I enter and submit data with reason, enters data with a chosen change reason. |
|
5840 |
Feature |
The Test Case Advisor now writes Veeva Test Cases for rules that read an item another rule derives, entering the data that rule derives it from. |
|
5876 |
Feature |
When an Organization does not allow all events to be added, the Veeva test case generator now writes steps that add a non-Unscheduled event as comments instead of steps that fail validation. |
|
5877 |
Feature |
Vault Test Case Advisor templates can show a Rule's Description under the Feature heading using the new rule_description template variable. |
|
5717 |
Bug |
Veeva Item Groups and Items are listed, generated and tested in the order they appear on the Form, and the test case editor lists Forms, Events and Event Groups in the order the study defines them rather than alphabetically. Rules that sort Events by schedule follow the same order. |
|
5838 |
Feature |
The Test Case Advisor now writes Test Cases for Veeva rules that read an item's translated value (value_translated__v), entering the item in its standard unit. Rules on lab forms are still skipped, as before. |
|
5878 |
Feature |
Test cases generated for Veeva Comparison Rules that compare to a Casebook Variable now enter data on the item the variable is mapped to and check the query, instead of requiring manual authoring. |
|
5879 |
Feature |
Test cases generated for Veeva Comparison Rules whose first identifier is an event date now check that the query appears, or does not appear, on the event, instead of asking for manual verification. |