Module : Veeva

Issue	Type	TrialGrid Version	Description
5733	Feature	93	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.
5726	Feature	93	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.
5705	Feature	93	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	93	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	93	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	93	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*.
5715	Feature	93	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.
5685	Bug	92.1	A Veeva Item used on several forms now takes its Controlling Item, Controlling Item Values and Display Type from each form's own row of the SDS, instead of every form showing the values from the first form that used it. Test Case checks, the Veeva Form Review and the Progressive Display agent use the values for the form they are on. Items imported before this release keep their current values until the SDS is imported again. As these values belong to an Item's place on a form, they are no longer shown on Item property sheets, and the "Controlling Items" property sheet is removed; review progressive display in the Veeva Form Review instead.
5686	Feature	92.1	The Veeva Test Case steps "I enter data" and "I enter and submit data" now fail, without entering the form's data, when a value is given to an item that is hidden by its Controlling Item, as a site user could not enter it. Test Cases that entered data into hidden items must now set the Controlling Item first.
5687	Feature	92.1	When the Veeva Test Case steps "I link form" or "I unlink form" cannot find a reference number, the step now shows which link section was searched and the reference numbers it listed, and takes a screenshot of the link dialog.
5681	Bug	92.1	Generated Veeva test cases now set up the forms and events their data is entered on when another rule adds them. A form added by a rule that names only the form, not its event, is now added before data is entered on it, using the rule's Dynamic Scope to tell which events the form is added to; previously the test entered data on a form that was never added, and Vault rejected it with "[Form] is not repeating". Test cases for such rules now check for the form in an event the rule adds it to. An event added by a rule on entered data now has that data entered before the event is dated.
5646	Bug	92	The Veeva steps "I add event group" and "I add events" no longer fail with "Invalid field with name [eventgroup_sequence]" when they name an instance of an Event Group, such as "UNS[2]".
5628	Bug	92	When neither the Test Set Run nor its Project sets them, the test run wizard now starts from the Rave URL, Veeva Vault, study settings and EDC roles of the latest run in the same Project, so they no longer have to be entered again for every new run.
5623	Feature	92	Generating Veeva test cases is faster for drafts whose rules add Events and Event Groups for one another; each rule's syntax is now read once rather than for every rule that depends on it.
5624	Feature	92	Veeva test case runs add Events a little faster; a step no longer asks Vault to create an Event Group the subject already has.
5625	Feature	92	A new Veeva step, "I add events", adds a table of Events to a subject, each with its date and optionally its method, change reason and planned-date override, in a few calls to Vault rather than several for each Event. Generated Veeva test cases use it wherever they add two or more dated Events in a row, so their runs take less time. When the organization allows all Events to be added, adding an Event that is not Unscheduled no longer gives a validation warning that it will be added through the API.
5615	Bug	92	Veeva rule test cases now create and link a linked Form that is on another Event, such as an Adverse Event on a log Event, instead of leaving a note to do it manually. A rule that counts the links of a Form it names, without being bound to that Form, now gets its links.
5616	Bug	92	The Veeva test case step "I link form" now links a Form that already has a link, instead of failing with "reference does not exist".
5602	Bug	92	Uploading a downloaded Veeva draft file now validates its Test Cases as Veeva Test Cases, so they keep the validity they had in the draft they were downloaded from instead of all being marked invalid.
5609	Bug	92	In a Veeva study whose Subject ID Generation Type is Manual, a Test Case can enter {unique subject id} as the value of the Subject ID item (the Status item of a form on a Screened Event). When the Test Case runs, the next Subject ID in the study's Subject ID Generation Format that no other subject at the site uses is entered. When the Subject ID item is Derived, {unique subject id} is entered into the item its rule derives it from, such as a Subject Number, and a Test Case generated for that rule checks the Subject ID item against {unique subject id}, the Subject ID chosen for the subject. A Test Case generated for any other rule that enters its own value there, or leaves it blank, has a comment saying that a second run, or the scenario with the blank value, will fail. After data entry that derives a Subject ID, later steps use the subject's new name. Values that use a Site or Study Country attribute, such as {{ Site.name__v }}, are filled in from the site the Test Case runs at.
5610	Bug	92	Veeva test case runs now take screenshots only for the step types selected; a Given step no longer takes screenshots when only When and Then are selected. A step now waits up to two minutes for Vault to answer each request before it fails, and a step that fails because Vault did not answer in time says so.
5585	Bug	92	Veeva Test Cases: a rule that holds one item against more than one number, such as a high and a low limit, or a date item against the date of a later Event, now gets a scenario for each of its OR alternatives.
5586	Bug	92	Veeva Test Cases: a rule with an InWindow given in hours, or in more than 1440 minutes, now gets a scenario in which its actions are not run.
5591	Feature	92	The Veeva Test Case generator has better support for sequences of Events, time windows, unknown time values and link items. Generated Rave and Veeva Test Cases no longer enter a value with more decimal places than its field allows, for example 49.4 rather than 49.40 for a field with one decimal place.
5575	Bug	92	Veeva test cases are now generated for rules that read items through @PreviousEvent when the rule does not name an Event, including rules that count or aggregate those items.
5577	Feature	92	The Veeva test case generator checks each scenario against its rule before the Test Case is written, and reports an error when it cannot tell what a rule reference refers to instead of treating it as blank.
5579	Bug	92	Veeva Test Cases: an additional boundary scenario for a comparison inside Not(...) or an If(...) condition now expects the outcome the rule gives for the data entered.
5580	Bug	92	Veeva Test Cases: the scenario in which a rule's actions are run now enters every item the rule needs when the rule also compares a Count(...) with zero.
5582	Bug	92	Veeva Test Cases: a rule that reads an item through @EventGroup and has Rule Bindings only for another form now has its Test Case generated, with the Event Group taken from the study design. Where more than one Event Group holds the Event and Form, a comment names them and the one used.
5583	Feature	92	Veeva Test Cases: a rule that names several Events with @Event.name__v, and has no Event in its Rule Details, now has a scenario in which its actions are run on each of those Events. An Event that cannot be given a scenario is named in the Test Case's comments with the reason.
5447	Bug	92	The Veeva test case generator now reports an error when a rule uses an unsupported system attribute or an incomplete path in a fully-qualified reference, instead of generating a test case that ignores it.
5453	Bug	92	Veeva test cases for Set Derived Value rules now expect the correct value when the rule expression references an item or Site attribute directly, without a #define.
5460	Bug	92	Additional scenarios for Veeva rules that compare two fields now use values either side of the boundary, including when a #define name differs from its item name.
5462	Bug	92	Veeva test cases no longer add an event to the Background when the rule that adds it requires another event to be absent through a #define, and now recognise IsBlank(...) = false as requiring the event.
5464	Bug	92	Veeva test cases for Set Subject Status rules now expect the status the subject already has when another rule sets one from an event the test case adds, instead of always expecting Pre Screen.
5465	Bug	92	Veeva test cases for derivations now enter data for every repeat a rule reads through a fully-qualified #define, keep codes such as 01 as text in the expected value, and give each #define the value of its own repeat or event.
5467	Bug	92	A derived value containing a quotation mark or line break is now compared correctly when a Veeva test case checks it.
5524	Bug	92	Veeva test cases that compare Time items now enter times in the order the rule needs, whatever time of day the test case is generated.
5568	Bug	92	Veeva test cases are now generated for rules whose Action Target names only an Item Group and Item when the rule reads its data from another form or through a linked form.
5569	Bug	92	Veeva test cases now treat an Item's Length as the number of digits before the decimal point, so test cases are generated for Items whose Decimal is equal to or greater than their Length and generated values can use the full Length.
5570	Bug	92	Veeva rules containing a number written without a leading zero, such as .10, can now be parsed and have test cases generated.
5571	Bug	92	Veeva test cases no longer enter a unit for an item that is left blank.
5572	Bug	92	Veeva test cases for an Add Form rule whose Action Target names an event without its event group now place that event in the event group that holds it.
5443	Bug	92	Veeva Test Cases now offer the entries of a Lab Codelist as values for items that use one, including sex and fasting items on non-lab forms.
5444	Bug	92	Veeva Test Cases no longer choose a Hidden codelist entry or unit as a test value, and pick codelist entries in their defined order so regenerated Test Cases use the same values.
5457	Bug	92	Veeva Test Cases now handle an event that belongs to more than one event group, using the forms, visit method and event window of the group the rule refers to.
5458	Bug	92	Veeva Test Cases now resolve each Rule Binding within its own event group and event, so forms, events and event groups that share a label are matched to the right one.
5435	Bug	92	Generated Veeva Test Cases now include a method when they add or update an event that has Visit Methods configured. Adding such an event uses the 'I add event ... with options' step, so the Test Case is valid instead of needing attention, and updating one, for example to set its change reason, no longer fails with "[Method] is required for this event".
5437	Bug	92	Generated Veeva Test Cases now enter data on an event added by a reciprocal Add Event rule before the item that controls that rule, so the event is not removed before its data is entered.
5438	Bug	92	Generated Veeva Test Cases for Rules with OR conditions now test each OR branch in its own scenario, up to 32 per Rule, including branches on event change reasons and dates, and the main scenario satisfies one branch instead of all of them.
5439	Bug	92	In generated Veeva Test Cases for Rules with OR conditions, each OR branch's scenario now adds only the events that branch refers to, so another branch (such as an event date being entered) no longer fires the Rule and hides whether the tested branch works.
5440	Bug	92	Generated Veeva Comparison Rule Test Cases now enter each date in its own Item's Data Type. A Rule whose Data Type differs from its Items' produced values that could not be entered, for example a date without a time for a Date/Time Item.
5441	Bug	92	Generated Veeva InWindow boundary scenarios now enter Date Items as dates and test one day either side of each boundary. They previously added a time to Date Items and moved the boundary by one minute, so two scenarios with opposite outcomes entered the same date.
5442	Bug	92	Generated Veeva Test Cases now enter a time, such as 10:29, into Time Items, and always include a time for Date/Time Items, including those whose Mask has no time.
5445	Bug	92	Generated Veeva Test Cases no longer split an OR condition inside Not(...), ! or an If(...) into separate scenarios. Such scenarios could enter a value the Rule excludes and still expect the Rule's action, for example a query from a Rule written as Not(A = '1' || A = '2') with A entered as '2'.
5446	Bug	92	Generated Veeva Test Cases now test the 'did not occur' branch of a Rule that also accepts an Event date: a separate scenario adds the Event without a date and sets it to did not occur. Events in Unscheduled Event Groups, which Vault cannot add without a date, get a comment instead. The 'I add event' step now accepts an Event with visit methods when no date is given and its Event Group is not Unscheduled.
5448	Bug	92	Generated Veeva Test Cases for Rules using an Event Group or Form sequence now enter the data in the instance whose sequence the scenario tests, never create more instances of an Event Group or Form than the draft allows, date Events referenced through @EventGroup, and accept a Rule Binding that names an Event.
5449	Bug	92	Generated Veeva Comparison Rule Test Cases now test the source date after, equal to and before the target date for every operator. Previously a Rule built with the wrong operator, such as <= in place of <, could pass every scenario.
5454	Bug	92	Test Cases are no longer generated for Veeva Comparison Rules whose Rule Status is Inactive. They are reported as skipped, as Inactive Rules are.
5455	Bug	92	Generated Veeva Test Cases now date an Event whose visit window is offset from the Previous Event inside that window, counting from the nearest earlier Event the Subject has, and add Events in schedule order. Vault no longer rejects these dates as outside the expected range.
5456	Bug	92	Generated Veeva Test Cases now add the instances of a repeating Event Group in numeric order, so instance 10 is no longer added before instance 2.
5459	Bug	92	When a Veeva Rule has more OR branches than the 32 scenarios generated for it, the Test Case now says how many branches have no scenario and which fields they refer to. OR conditions combined with AND now need only as many scenarios as their longest list of alternatives, rather than one for every combination, so most such Rules are covered in full.
5461	Feature	92	Generated Veeva Comparison Rule Test Cases now test Unknown Handling. When the Rule's Unknown Handling is Min or Max and an Item's Mask allows an unknown day, a scenario enters a date with an unknown day and checks the query treats it as the first or last day of the month. Where that scenario expects no query, a second one checks the query does fire for a date with an unknown day.
5463	Bug	92	Veeva Test Case generation no longer reads unknown minutes (mm*) in a Date/Time Mask as an unknown month when choosing test dates.
5466	Bug	92	OR path and additional scenarios in generated Veeva Test Cases now add Events the same way as the main scenarios: an Event whose Event Group the Rule itself adds is no longer added before the data that adds it, and each scenario uses its own Event dates. The Login scenario no longer takes its Event dates from the negative scenario.
5416	Bug	92	The Veeva 'I should see form' and 'I should not see form' steps now match what the user sees in the casebook, including forms shown with no entries, report a form as not found when the subject does not have it, and no longer change subject data while checking.
5417	Bug	92	Veeva form screenshots are now taken once the whole form has loaded, including every row of its tabular sections, and a screenshot that had to be taken while the form was still loading is noted on the step.
5418	Feature	92	Veeva query steps now screenshot the whole form the query is on, with the query outlined, including queries in tabular sections, so the evidence shows which form, event and item the query belongs to.
5419	Bug	92	Veeva form screenshots now show every column of wide tabular sections instead of cutting them off at the right edge.
5412	Feature	92	Veeva test cases that enter data into a read-only item with 'I enter data' or 'I enter and submit data' are now invalid; use 'I enter and submit external data' for these items. Generated test cases enter read-only items with the external data step.
5421	Bug	92	When Veeva Vault refuses the browser login for a Veeva Test Case, the "I am logged in" step now fails with Vault's error message and the Test Case stops. Previously the Test Case continued without a logged-in browser. The refusal is also now reported as soon as it appears, instead of after a 30 second timeout.
5405	System	92	Automated testing settings are now stored as individual overrides on top of code-defined defaults, so new settings can be added without a database migration.
5394	Feature	92	Service account credentials for iMedidata, Rave Classic and Veeva are now stored once and shared by every TrialGrid environment, so a password rotation reaches all environments immediately. Veeva Vaults are registered on the production site, and reach the other sites at their next refresh.
5516	Bug	91.1	The test run wizard now starts from the Test Set Run's own Rave URL, Veeva Vault, EDC roles and study settings, then the Project's, instead of values last used on another project, and recognises a run-on URL typed with a trailing slash or in different case. Draft import and export no longer preselect a Rave project chosen for another Project.
5261	Feature	91	On Veeva vaults at release 26R2 or later, test runs open forms directly with Veeva EDC's stable form links, and each form screenshot in the results links to that form in Veeva EDC.
5357	Bug	91	The maximum number of concurrent Test Case Runs set for a Rave URL or Veeva Vault now applies to your Organization's own runs, and the progress message shown when your Organization is at its limit now shows the right count.
5362	Feature	91	The Veeva Vaults list shows which Veeva release each vault is on, read automatically from the vault when it is registered and when test cases run.
5364	Bug	91	The Veeva Vaults list now shows each vault's latest test case run and number of test case runs, including runs made before this release.
5367	Bug	91	Veeva Comparison Rules whose identifiers are fully qualified ($) paths now reference the Event Groups, Events, Forms, Item Groups and Items those paths name, so they appear in those objects' 'in use' lists and are counted when checking whether an object can be deleted.
5273	Bug	90	Organization activity lists now include activity from Veeva Vaults.
5268	Bug	90	Test Cases in a Veeva Draft can now be exported to Excel. The Test Data upload, which reads a Rave Folder/Form/Field file, is no longer offered for Veeva Drafts.
5270	Bug	90	Editing a Test Case Template in a Veeva Draft now updates the Test Cases that include it.
5219	Bug	90	A Vault domain can be registered by more than one organization, each with its own account, and a duplicate registration no longer fails a Test Case Run at start-up
5249	Bug	90	Veeva rules that add or subtract a date interval - for example EVENTDATE + Days(28) - now generate test cases instead of silently producing none.
5250	Bug	90	Query screenshots now show the whole query panel and reliably outline the verified query, and report it on the step when the outline could not be applied.
5218	Bug	90	Veeva rule bindings containing a hyphen in a form label are now parsed correctly. When a rule references a form TrialGrid cannot resolve, the error now names the Rule Bindings that were skipped and the level each name actually sits at, instead of reporting an unrelated missing form. A rule stops only when none of its Rule Bindings can be parsed.
5230	Bug	90	Rules that call a function Veeva does not support in rules now report which function is the problem, instead of a low-level parser error.
5220	Bug	90	Veeva Rules that use the And() and Or() functions, or that do numeric comparisons on codelist items such as severity or grade scales, now generate Test Cases correctly instead of producing nothing. When an optional additional scenario cannot be generated, the Test Case is still created and records the reason as a comment, and internal errors during Test Case generation are now reported instead of silently producing no scenarios.
5094	Feature	90	The Veeva Test Set Run wizard now offers the studies and sites the Vault account can reach rather than asking for them to be typed.
5204	Bug	90	Veeva data entry steps now recover when the browser is lost mid-run: TrialGrid relaunches the browser and resumes instead of ending the run as Cancelled.
5162	Bug	90	Veeva test steps that cannot capture a screenshot now report the missing evidence instead of passing silently, and TrialGrid restarts the browser when screenshots repeatedly fail.
5131	Bug	90	Comparing two Veeva Drafts with 'Ignore Custom Properties' now compares the built-in Veeva object types on their standard properties, ignoring only Custom Properties added by users.
5133	System	90	Whether a Property is part of a Veeva object's built-in definition or was added by a user is now recorded on the Property itself, so Draft compares which ignore Custom Properties stay correct as the Veeva schema changes.
5103	Feature	90	Veeva Rules that read an item on a linked form now generate test cases. 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.
5064	System	90	Veeva Vault API rate limits are now recognised and waited out.
5058	Feature	90	Veeva Lab Codelists and Lab Unit Codelists now import into TrialGrid as object types in their own right, so a Lab codelist and a study codelist sharing a name can both be held in the same draft. Items referencing a Lab codelist resolve to it via new Lab Codelist and Lab Unit Codelist properties. Existing drafts are converted automatically; Lab codelists previously skipped because of a name collision need a re-import from the SDS.
5160	Bug	89.3	Screenshots of a Subject in the site list no longer fail when Vault is showing a service announcement. The runner moves announcement banners out of the way before clicking, but it was checking a point half a pixel away from the one the click actually uses, so a banner overlapping the target by a single pixel was left in place and intercepted the click. The check now uses the same point as the click.
5128	Bug	89.3	A Test Case run whose browser crashes or stops responding is now recovered as soon as the problem occurs, on both Veeva and Rave. Previously some browser operations, such as taking a screenshot of a form or opening a page after data entry, hid the failure, so the run carried on issuing commands to a browser that was no longer there. Each of those commands waited for the full timeout before failing, and runs could continue in this state for several hours before finishing or being cancelled. The browser is now relaunched and the run resumed at the point it was interrupted.
5091	Feature	89.1	Veeva test case runs now use the study label for UI navigation, so studies whose name and label differ run correctly.
5078	Bug	89.1	Vault notification banners no longer block the site breadcrumb click when a Veeva Test Case takes a screenshot of the subject status in the site's subject list.
5079	Bug	89.1	Veeva Test Cases no longer intermittently fail to create a subject with 'the New Casebook button did not appear' when the study uses By Site Subject ID Generation.
5081	Bug	89.1	Veeva Test Cases can create a subject By Site after an earlier step has used the browser to view a subject.
5082	Bug	89.1	Veeva data entry steps report when the form could not be opened in the browser, so it is clear why the step has no form screenshot.
5083	Bug	89.1	Veeva Test Case steps name the Vault API call that returned an internal error, instead of showing the raw response body.
5086	Bug	89.1	Veeva rules using aggregate functions with separate arguments, such as NoBlanks(A, B, C), now generate test data correctly.
5056	Bug	89	Veeva SDS uploads where a Lab Codelist has the same Name as a study Codelist no longer fail with a duplicate identifier error. The Lab Codelist is skipped and reported as a warning on the import.
5015	Bug	89	Test case data entry steps now accept an empty value for item-to-form link items, allowing an existing link to be cleared.
5019	Bug	89	Screenshots for Veeva query verification steps now highlight only the query being checked, rather than every open query on the page.
5020	Bug	89	The Veeva test case View tab now shows Form labels for the link form and unlink form steps, and for repeating forms on all Form steps, which previously showed the Form name.
5021	Bug	89	Generated Veeva test cases now include the required sequence number on repeating event groups, forms and item groups in query, value and visibility steps.
5027	Feature	89	The mark-as-blank test step now re-opens an already submitted form for edit, so submitted forms can be marked as intentionally left blank.
4966	Bug	89	Veeva SDS uploads containing multiple Safety Form Configuration entries with the same Form Name no longer fail with a duplicate identifier error; the Safety Form Configuration object no longer uses the non-unique Form Name as an identifier.
4969	Feature	89	The Veeva drafts page now has an 'Add' menu offering 'Upload SDS' and 'Upload Draft'. 'Upload Draft' re-imports a downloaded TrialGrid draft to recreate its Veeva objects, test cases and properties.
4972	Bug	89	Creating a Vault with 'Copy Settings from Vault' no longer corrupts custom object metadata (duplicated identifier properties and reference properties left pointing at the source Vault), which previously caused Codelist Entries and other referenced objects to be rejected on SDS upload.
4973	Bug	89	When generating a test case for a Veeva Add Form rule in a study with two event groups sharing the same name, the Test Case Advisor now targets the event group that actually contains the bound event, avoiding a redundant 'add event' step and an invalid form check. Additionally, when the same step is repeated in a test case, validation errors are now reported on each step's own line rather than the first occurrence's line.
4957	Bug	89	Data entry and assertion steps now correctly recognise repeating Veeva event groups, so a repeating event group's sequence number (e.g. eg_HEPA[1]) is accepted on data entry steps.
4945	Feature	89	Veeva Form Review nows display Item information when clicking on the header of a repeating Item Group.
4946	Feature	89	Date fields in the Veeva test case editor no longer auto-insert leading zeros or re-case month names as you type — the value you enter is kept and validated against the study date format instead. Checkbox (boolean) values typed in any case are normalised to lowercase when the data is entered.
4947	Feature	89	Veeva test cases can now add an Event Group to a Subject with the new "I add event group" step (with an optional date for unscheduled groups), including an editor helper to pick the event group.
4932	Bug	89	The Veeva Form Review now displays every item's value for Item Group default adds, not just the first item in each repeat.
4933	Feature	89	The TrialGrid draft home page can now show test coverage for Veeva Rules and Comparison Rules.
4935	Feature	89	Automated tests can now link and unlink Veeva forms using the new "I link form ... to form ..." and "I unlink form ... from form ..." steps.
4937	Feature	89	Veeva browser locators and scripts are now stored in the database.
4938	Feature	89	The Veeva Test Case Advisor now generates test cases for rules that use linked-form counts (TrialGrid emits the new link-form steps to set up the required form links).
4939	Feature	89	The Veeva Test Case Advisor now generates test cases for rules that read data on linked forms (TrialGrid enters the linked form's data and links it to the rule's form using the new link-form steps).
4924	Bug	89	Veeva Set Derived Value test cases now emit a 'has value' verification step for multi-line rule expressions, and year-hinted source items are populated with a realistic year.
4928	Feature	89	Added a Veeva test step that marks a form as intentionally left blank.
4915	Bug	89	Veeva 'has value' step screenshot now highlights the value on the specified repeat instance instead of always the first repeat.
4892	System	89	TrialGrid now validates Veeva API responses against typed schemas at the boundary, failing fast with a clear error when a response is missing an expected field.
4893	Bug	89	TrialGrid now navigates to Veeva forms reliably fixing missing screenshots for repeating forms.
4862	Feature	89	The Veeva Test Case generator now supports the @Form.change_reason__v and @Form.form_status__v system attributes; rules using them generate test cases.
4890	Feature	89	Veeva query verification screenshots now highlight the query text for both Datapoint and Event queries, making it easy to see which query was checked.
4891	Bug	89	Item visibility on value steps is now read from the correct repeating itemgroup instance, fixing a spurious "present but not visible" note when the item is shown on the form.
4882	Bug	89	Per-project, per-draft and per-URL permission checks on the Rave and Veeva import/export/download, test-run and URL/Vault registration wizards are now enforced server-side.
4859	Feature	89	The Veeva Test Case generator now supports the @Site system attributes name__v (Study Site Number), oid__v, status__v, principal_investigator__v and locked__v, in addition to the existing timezone__v. Because a site is chosen when the test is run, derivation rules that build a value from a site attribute (for example Concat(@Site.name__v, "-", Text(SUBJNO))) now embed the run-time site value, which is looked up from Veeva and substituted automatically. Rules that compare a site attribute to a fixed value (for example @Site.name__v = '100') generate a scenario with a note describing the site the test must run on.
4860	Feature	89	The Veeva Test Case generator now supports the @StudyCountry system attributes name__v, country_abbreviation__v and country_code__v.
4861	Feature	89	The Veeva Test Case generator now supports the @Casebook.subject_name__v and @Casebook.version__v system attributes.
4881	Feature	89	Added a Veeva test step to re-open a submitted form for edit.
4854	Feature	89	The Veeva Test Case generator now supports rules that use @Form.submit_counter__v, generating scenarios that submit a form enough times to exercise both first-submit and re-submit conditions. Generated scenarios cover submission counts up to 20; rules requiring a higher count report an error so they can be authored manually.
4855	Feature	89	The Veeva Test Case generator now supports rules that reference an item's value via @Item.value__v, treating it as the item's own value. Using value__v on a Date item reports an error, since Veeva requires value_normalized__v there.
4856	Feature	89	The Veeva Test Case generator now supports rules that reference an item's unit via @Item.unit__v, generating scenarios that set the item's unit from its Unit Codelist. Using unit__v on an item with no Unit Codelist reports an error.
4858	Feature	89	The Veeva Test Case generator now supports rules that reference an item's prior value via @Item.previous_submit_value__v, generating scenarios that submit the form twice (the previous value, then the current value).
4974	Bug	88.16	Creating a subject for studies with 'By Site' Subject ID Generation no longer fails when the user account has access to a single study and multiple sites.
4975	Bug	88.16	For studies with 'By Site' Subject ID Generation, a subject created during a test run is renamed by the Vault (from the temporary SCR-#### id to the configured format) once a rule moves it to In Screening. Test runs now detect that rename and continue using the new subject name, so later steps that add events or enter data no longer fail with 'subject not found'.
4869	Bug	88	A Veeva "I should not see the following query" step now correctly passes when the only matching open query differs from the expected text by whitespace or case and the organization does not allow whitespace or case differences in test results. Previously the step incorrectly failed in this situation.
4870	Feature	88	A Veeva "I should not see form" step now captures a screenshot of the form's parent event in review mode, providing evidence of the event's form list when the form is correctly absent.
4871	Feature	88	Veeva event visibility steps now capture a screenshot of the subject in review mode whenever there is no specific event to show — when "I should not see event(s)" passes, and when "I should see event(s)" fails because an expected event is absent — providing evidence of the subject's event schedule.
4872	Bug	88	The Veeva data entry step helper now offers a value dropdown of "true" and "false" for boolean (checkbox) items. The Form column also no longer shows a solitary "." for an incomplete datapoint reference, which previously blocked the column's dropdown search.
4873	Feature	88	When a Veeva test step finds that an Event or Event/Form combination does not exist for the subject, subsequent steps that rely on the same Event/Form now fail immediately ("not found in an earlier step") instead of being re-attempted. A passing step clears this state. This matches the existing Rave behaviour.
4874	Feature	88	Veeva organizations have a new setting "Allow all events to be added" (on by default). When it is off, adding an event that is not Unscheduled in a Veeva test case is a validation error instead of a warning.
4875	Bug	88	Veeva value-check steps (for example "has value") read the value from the API, which does not report visibility. When the item is hidden by form dynamics the field does not appear in the screenshot, so the result text now adds "Item {name} is present but not visible." after checking the loaded form in the browser.
4843	Bug	88	Veeva Test Case generation was failing for a rule with no bindings. The identifier defined in the Rule will be used.
4845	Bug	88	The Veeva Test Case generator was not handling all @PreviousEvent identifiers correctly.
4847	Bug	88	The Veeva Test Case generator showed the coded value instead of the entry label when checking the value of a codelist field. It now uses the label.
4848	Feature	88	The Veeva Test Case generator now supports the GetAllMatches function.
4849	Feature	88	The Veeva Test Case generator now supports the Middle and Substitute functions.
4850	Bug	88	Veeva Test Case generation failed to parse rules referencing OID names that start with a digit or hyphen (e.g. 9HPIN, 6MWT, 9-HPT). These names are now accepted.
4851	Bug	88	The Veeva Test Case generator did not resolve unknown date/time components for MinDate/MaxDate/MinDateTime/MaxDateTime when a Site timezone argument was supplied. This is now handled correctly.
4852	Bug	88	The Veeva Test Case generator now supports the SiteDateTime(date, time) form that combines a Date item and a Time item.
4803	Bug	87	The Veeva Test Case generator was not processing dates and times consistently across timezones.
4804	Feature	87	The Veeva Test Case generator now generates test cases for rules that reference previous or next instances of repeating event groups, events, forms, and item groups via the [-1] / [+1] wildcard identifiers.
4805	Feature	87	The Veeva Test Case generator now surfaces a 'Subject ID must be set' issue in the 'Given I have resolved these issues' placeholder step when a rule writes data to the itemgroup containing the Subject-Identifier item, since the generator cannot pick a value that's unique against existing subjects.
4798	Feature	87	When several rules share the same query text and action target, the Veeva Test Case generator now produces a single combined scenario instead of one per rule.
4801	Feature	87	The Veeva Test Case generator now handles a wider range of rule shapes correctly - "Date of Visit" InWindow rules whose arguments are two event dates (including the bare and Not(InWindow(...)) forms), Max/Min wrappers around wildcard references such as Max($EG.EV[*].FORM.IG.ITEM), IsBlank arguments inside Add Event/Group predicates, attribute references shared across multiple events (for example $TX.D2.event_date__v and $TX.D15.event_date__v), 2-part event identifiers, and Action Targets written in either the "$EG" or "{EG}" form.
4802	Feature	87	The Veeva Test Case generator now sequences Login-block events and data entries in phases driven by the Add Event Group cascade, so gating data is entered before the events it enables; requires every gating value in an Add Event Group predicate to match before keeping per-event data (avoiding "Unique Event Group cannot be found" rejections); uses a single definition of "rule is Active" throughout; and keeps prereq block and datapoint lists paired when collecting isolated prerequisites.
4788	Bug	87	The Veeva test case generator now skips rules that reference linked forms and reports which linked forms are involved. The Veeva API has no endpoint to link forms, so a generated test case for such a rule could not be run, so we skip the rule entirely rather than producing an unrunnable feature file.
4789	Feature	87	The Veeva Test Case generator will switch to using a Background section, creating subjects per scenario, if necessary to test different events.
4790	Feature	87	Veeva Test Case runs will automatically submit an unsubmitted form before checking for a derived value.
4791	Bug	87	The Veeva Test Case generator was producing incorrect year values. This has been corrected.
4792	Bug	87	The Veeva Test Case generator was not respecting numeric formats when checking data values. This has been corrected.
4793	Bug	87	Veeva Test Case generation failed for rules binding a form with commas in its label. This has been corrected.
4794	Bug	87	The Veeva Test Case generator was not generating correct values for some rules with wildcards. This has been corrected.
4795	Feature	87	The Veeva Test Case generator will not now try to create test cases for lab forms.
4783	Bug	87	Veeva Test Case generator now produces date values on different dates (not just different times) when comparing a date/time form item against an event date, and uses date-only strings for event date steps.
4784	Bug	87	Veeva test case generator now computes each event's date from its Event Window (Offset Event + Offset Days) instead of using the base time for every event, so generated 'I add event' steps fall inside the event's accepted date range.
4785	Bug	87	Veeva test case generator now emits the negative scenario before the positive for rules whose action adds an Event Group, Event, or Form — so the negative assertion runs against a clean subject state instead of one that already contains the artefact added by the positive scenario.
4786	Bug	87	The Veeva Test Case generator now detects dynamic forms and add an 'I add form' step before the data-entry table (for repeating forms) or data entry steps to trigger the dynamic add form rule (for non-repeating forms).
4787	Feature	87	There is a new Test Case step 'I add form "X" to event "EG.EV"' which creates an empty form in an existing event, for use only with repeating forms.
4713	Feature	87	There are a default set of Property Sheets for Veeva URLs.
4734	Bug	87	External ID values are now imported correctly for Forms and Item Groups when loading a Study Design Specification.
4735	Bug	87	Fixed an issue where the Veeva Test Case Advisor could place generated queries on the wrong event when an edit check's Action Target field was not on the form bound to the rule's first event.
4736	Feature	87	The Veeva Test Case Advisor now generates 'I update event' and 'I set event ... to did not occur' steps for rules that reference event change reasons or the did-not-occur attribute.
4742	Feature	87	Diagnostic 0180 (Item Name and External ID Reserved Words) now flags lab-prefix Items only when Enable Local Labs is not set to Yes in Study Settings, since TrialGrid auto-creates these Items when local labs are enabled.
4743	Feature	87	Diagnostic 0186 (Veeva ItemGroup Header Visible and Visual Group Selected) now excludes the LBHEADER ItemGroup by default, since TrialGrid auto-creates LBHEADER when local labs are enabled.
4744	Feature	87	Diagnostic 0188 (Veeva Form Radio Button Layout Consistency) now groups Items by Codelist entry count when checking radio orientation consistency, so radio Items with a 2-entry codelist are compared only against other 2-entry codelist Items.
4745	Feature	87	Diagnostic 0190 (Veeva Item Name Length) now excludes TrialGrid-auto-created lab Items by default (LBNRIND_*, LBTEST_*, LBCLSIG_*, LBORRES_*, LBORNRLO_*, LBORNRHI_*, LBOVRDNRLO_*, LBOVRDNRHI_*).
4715	Feature	87	TrialGrid now provides a Veeva diagnostic that flags objects whose External ID does not match their Name, with an autofix that copies the Name into External ID. The list of object types to check is configurable; Form is selected by default.
4716	Feature	87	TrialGrid now provides a Veeva diagnostic that classifies Items as lot numbers, kit numbers, or accession numbers and flags any whose Data Type is not Text. The autofix sets Data Type to Text.
4717	Feature	87	TrialGrid now provides a Veeva diagnostic that flags Concomitant Medications forms which collect Total Daily Dose alongside Dose and Frequency, since these dosing views are mutually exclusive.
4718	Feature	87	EventGroup Event and EventForm custom object definitions are now displayed for Veeva URLs, so their per-relationship properties are visible in lists. On EventGroup Event, Visit Method and Dynamic are surfaced as list columns. Existing Veeva URLs are updated by data migration.
4719	Feature	87	Codelist Entry and Unit Codelist Entry custom object definitions are now displayed for Veeva URLs, so codelist choices are visible in lists. Choice Label is surfaced as a list column on Codelist Entry; Choice Label, Standard, and Conversion are surfaced on Unit Codelist Entry. Existing Veeva URLs are updated by data migration.
4720	Feature	87	Properties on Veeva URLs that store names of other Veeva objects (Codelist and Unit Codelist on Item; Event Group, Event, Form, Item Group, and Item on Casebook Variable, Rule, Repeating Event Group, Review Plan, Safety Form Configuration, and Comparison Rule) are now reference properties pointing at the relevant custom object definitions, enabling dropdown selection and reference validation in place of free-form text. Existing Veeva URLs are converted by data migration; values that match an object in the draft are translated to the object reference, and unmatched names are cleared.
4721	Bug	87	Casebook is no longer part of the Event Group object identifier on Veeva URLs, fixing reference lookups from Casebook Variables, Rules, Comparison Rules, and Repeating Event Groups that store the bare Event Group Name. Existing Veeva URLs are updated by data migration that recomputes Event Group and EventGroup Event identifiers.
4722	Bug	87	Draft Merge was not working for Veeva Drafts. This has been corrected.
4702	Feature	87	TrialGrid now flags Veeva measurement Items (height, weight, vitals, etc.) that do not have an appropriate Unit Codelist.
4703	Feature	87	TrialGrid now flags Veeva measurement Items whose Length, Decimal, or value range is implausible for the kind of measurement they capture.
4704	Feature	87	TrialGrid now flags Veeva Unit Codelists whose conversion formulas do not match the canonical conversion factors for the units they contain, with an autofix that rewrites the formula.
4689	Feature	87	New diagnostic flags Veeva ItemGroups where Header Visible or Visual Group is not set to Yes, with an autofix to enable them and a configurable Item Group Name exclusion list.
4690	Feature	87	New diagnostic flags Veeva Items where the Control Type does not match the codelist size: Picklist is required for codelists with more than 6 entries, and Radio Buttons - Horizontal is unsuitable for codelists with more than 3 entries. The autofix sets the recommended Control Type and an Item Name exclusion list lets users skip specific Items.
4691	Feature	87	New diagnostic flags Veeva Forms with mixed Radio Button orientations: items whose Control Type does not match the Form's majority orientation are reported with an autofix that switches them to the majority (Vertical wins ties). Form Name and Item Name exclusion lists let users skip specific forms or items.
4692	Feature	87	New diagnostic groups Veeva codelists with identical entries (same Choice Codes and Labels regardless of order) and flags Items whose Control Type does not match the most-used valid type within the group, with Picklist beating Vertical beating Horizontal on ties. Codelist Name and Item Name exclusion lists let users skip specific groups or items.
4693	Feature	87	New diagnostic flags Veeva Items whose Item Name is longer than a configurable threshold (default 8 characters). The fix prompts for a replacement name; an Item Name exclusion list lets users skip specific items.
4697	Feature	87	TrialGrid now flags Veeva Date and Date/Time Items whose 'No Future Date' is not set to Yes, with an autofix that sets it to Yes.
4698	Feature	87	TrialGrid now flags Veeva Items whose Length does not match the maximum Choice Code length of their Codelist, with an autofix that sets Length to the correct value.
4699	Feature	87	TrialGrid now flags Veeva data Items that do not have Required set to Yes (skipping Read-only and Derived items), with an autofix that sets Required to Yes.
4700	Feature	87	TrialGrid now flags Veeva Forms whose order relative to other Forms is inconsistent across the Events in which they appear.
4660	Feature	87	When adding a Veeva Vault the roles, labels, custom objects, custom properties, actions and other settings can now be copied from an existing Vault.
4710	Feature	86.2	Subjects can now be created in test cases for studies whose Subject ID Generation Type is set to By Site; TrialGrid drives the Vault UI to create the casebook and the auto-generated subject name is used for downstream steps.
4711	Feature	86.2	Veeva test cases now detect when entering data has caused the Vault to rename the current subject and update TrialGrid to use the new name in subsequent steps.
4683	Bug	86.1	When uploading a Veeva SDS some properties were incorrectly assigned to Events instead of Event Group Events (the Event Group / Event combination in the Schedule). Existing Veeva Drafts will be automatically corrected.
4669	Feature	86.1	There is a new Veeva Test Case step to set visit method, change reason, planned date override and externally owned for Events. Note that existing Veeva drafts will not include the visit method and the SDS must be imported again to pick up the visit method.
4670	Feature	86.1	Veeva 'set event to did not occur' steps can now include a reason.
4672	Bug	86	Screenshots for Veeva forms with item groups with 'Editable grid' display format were not being captured correctly. This has been corrected.
4665	Bug	86	The Veeva 'submit form' test step and item-to-form links in data entry were not passing event group and form repeat numbers to the Veeva API. This has been corrected.
4646	Feature	86	Veeva Object Definitions for Events, Forms, Item Groups, Items, and Codelist entries now have ordinal support. When importing an SDS spreadsheet, the implicit worksheet ordering is preserved as ordinals on the imported objects.
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.
4630	Feature	86	The Veeva Test Case agent now creates Add Event steps where necessary.
4631	Feature	86	The Veeva Test Case agent now has a default value when saving a Test Case.
4626	Feature	86	Standard Rules are now editable in Veeva Library drafts.
4615	Feature	86	Test case run results now show a diff against the closest open query when no exact match is found, display HTML tags in the actual query table so they are visible, and include a text-only diff view that ignores HTML tags to help users spot content differences in TrialGrid.
4608	Feature	86	The Activity tab now shows audited property changes and revert functionality for Veeva core objects, matching the behavior already available for user-managed custom objects.
4601	Feature	86	The Veeva Test Case Run now records the casebook version and build number
4596	Bug	86	The Veeva Test Case Advisor was not processing 2-part (event.form) Action Targets. This has been corrected.
4598	Feature	86	The Veeva Test Case editor helper for 'see value' steps now supports partial datapoint references.
4552	Bug	85	The Veeva and Medidata Test Case agents should have similar workflow and features.
4551	Bug	85	Custom objects in Veeva drafts should be editable.
4535	Feature	85	The Veeva Test Case generator now creates background steps for adding events consistently with other generators.
4536	Bug	85	There was an error generating Test Cases for Veeva rules containing date items with unknown parts. This has been corrected.
4537	Feature	85	The Veeva Test Case generator now supports unknown dates.
4539	Feature	85	Diagnostic V081 'Check text strings for trailing whitespace' is available for Veeva studies.
4540	Feature	85	Diagnostic V179 'Double spaces in Text Fields' is available for Veeva studies.
4542	Feature	85	The Veeva Test Case generator will report an error if a Rule references objects which do not exist.
4527	Bug	85	Veeva Test Cases were not taking screenshots of forms in Log events. This has been corrected.
4528	Bug	85	The Veeva Test Case add event step was incorrectly setting event dates. This has been corrected.
4529	Feature	85	There is a new Veeva Test Case step to verify Event date values.
4530	Feature	85	The Veeva Test Case editor helpers now support repeat numbers.
4438	Feature	85	Veeva Test Case data entry steps can create Item to Form links.
4512	Feature	85	There is a new Veeva Test Case step to submit a form.
4513	Feature	85	There is a new Veeva Test Case step to set an event as did not occur.
4520	Bug	85	The Veeva Test Case Advisor was not adding steps to test subject status for Rules which set the subject status. This has been corrected.
4521	Feature	85	Veeva Test Case event steps will take screenshots.
4522	Feature	85	The Veeva Test Case query steps will show queries in a table and will compare whitespace and case differences using the organization's setting.
4523	Feature	85	The Veeva Test Case query steps now support event date queries.
4524	Bug	85	Veeva Test steps using numeric values were not being compared correctly. This has been corrected.
4526	Bug	85	The Veeva Test Case 'has value' step now returns the error message from the API, for example if an event does not exist in the test subject.
4509	Feature	85	The Veeva Test Case editor helpers will display names and labels to make searching easier.
4506	Bug	85	The Veeva Test Case editor was not reporting some errors correctly. This has been corrected.
4500	Feature	85	Veeva Test Cases support unknown date, time and datetime Items.
4502	Feature	85	If the query is not found the Veeva query test steps will take screenshots of the Form.
4503	Feature	85	The 'enter data' Veeva test step does not now submit data. There is a new 'enter and submit data' step to do this. All existing Veeva test cases have been automatically updated to use 'enter and submit data' for backwards compatibility. The test case generator now defaults to 'enter and submit data'.
4504	Feature	85	The 'enter data' and 'enter and submit data' Veeva test steps now set 'externally_owned' to false so that data can be edited. There is a new 'enter and submit external data' step.
4505	Feature	85	There is a Schedule view showing a grid of Events and Forms.
4485	Feature	85	The Veeva Form review supports Progressive Display.
4488	Feature	85	The Form Review page will display field properties after clicking on a row.
4491	Bug	85	The Draft Name is not being set on uploading a Veeva SDS.
4492	Feature	85	The Veeva Test Case editor View tab will show labels for events and forms.
4493	Bug	85	The Veeva Test Case advisor will use true/false for checkbox/boolean fields.
4494	Feature	85	The Veeva Test Case editor has warnings for invalid checkbox/boolean values.
4495	Feature	85	The Veeva Test Case editor will auto-correct dates to DD-Mon-YYYY format, fixing month capitalization and left-padding single-digit days. [Retired - see issue 4946]
4496	Feature	85	The status (active/inactive) property will be shown in Veeva Rule and Comparison Rule lists.
4497	Feature	85	The 'I wait' step is now available for Veeva Test Cases.
4498	Bug	85	When the Veeva subject status step failed the error message was repeated. This has been corrected.
4499	Bug	85	The 'event date set' message was being repeated in Veeva add event steps. This has been corrected.
4484	Feature	85	There are Test Case editor helpers for the Veeva item visibility steps.
4477	Bug	85	Linked Forms were not being imported from Veeva SDS spreadsheets. This has been corrected.
4481	Feature	85	There are new Veeva Test Case steps to check if Items are visible or not when progressive display is configured.
4476	Feature	85	The Form Review view supports Veeva EDC forms.
4445	Feature	85	There is an Agent to check the progressive display settings on Veeva forms.
4434	Bug	84.1	The Veeva Test Case generator was not resolving @form references correctly when multiple forms were used in a Rule. This has been corrected.
4435	Bug	84.1	Running the Veeva Test Case generator on multiple Rules could lead to inconsistent results. This has been corrected.
4436	Bug	84.1	The Veeva Test Case Generator was not correctly generating additional scenarios for Rules with OR conditions. This has been corrected.
4437	Bug	84.1	The Veeva Test Case Generator sometimes needs to add events before checking if a form exists or not.
4439	Bug	84.1	The Veeva Test Case Generator was not always working for Rules using the InWindow function. This has been corrected.
4402	Feature	84	If a Form is restricted and the user account used to run Test Cases does not have restricted data access then a message will be shown in test step results if the Form is not found.
4390	Feature	84	There is a new Diagnostic for Veeva studies to check if Items are using reserved words.
4391	Feature	84	Veeva query step will display the status of the query in user-friendly text.
4392	Feature	84	There will be a warning the Test Case editor for Veeva test cases if a data entry step could change the subject name and is not followed by a step to select the subject or check the subject name.
4393	Feature	84	There is a new test step for Veeva Test Cases to check value of the subject name.
4394	Feature	84	There is a new step for Veeva Test Cases to check the value of the subject status.
4383	Feature	84	The Veeva Test Case Advisor is available for Comparison Rules.
4382	Bug	83	The Veeva Test Case Advisor was creating add event steps with dates for all event types, including Log events. This has been corrected. Dates can not be set on Log events.
4343	Feature	83	There is a Test Case creator agent for Veeva drafts.
4291	Feature	82	The Veeva Test Case generator now supports the sequence__v system variable.
4292	Feature	82	The Veeva Test Case generator now supports the name__v system variable
4293	Feature	82	The Veeva Test Case generator now supports the count__v system variable.
4289	Feature	82	The Veeva Test Case generator will create additional scenarios for comparison operators.
4288	Feature	82	Users with 'Can manage Vault settings' can view and register Veeva Vaults.
4285	Feature	82	The Test Case generator for Veeva rules will include Units when an Item has a Unit Codelist
4286	Feature	82	Veeva Test Cases can be copied from another draft into the current draft.
4280	Feature	82	There are Test Case editor helpers for all Veeva event steps.
4281	Feature	82	Veeva Test Case event steps now include the event group and event.
4282	Feature	82	There are Test Case editor helpers for Veeva form steps.
4283	Feature	82	There are Test Case editor helpers for Veeva data value steps.
4284	Feature	82	There are Test Case editor helpers for Veeva query steps.
4276	Feature	82	There are tooltips showing the labels for objects in the Test Case editor.
4277	Feature	82	There are tooltips showing the labels for objects in the Test Case run results view.
4271	Feature	82	The Test Case generator for Veeva Rules now supports Add Event actions.
4272	Feature	82	The Test Case generator for Veeva Rules now supports Add Event Group actions.
4273	Feature	82	The Test Case generator for Veeva Rules now supports Add Form actions.
4274	Feature	82	There are new test steps to check if Events do or not exist in Veeva Test Cases.
4268	Feature	82	PDF Reports can be generated for Veeva Test Cases
4269	Feature	82	AI generated summaries are available for Veeva Test Cases and Test Case runs
4262	Feature	82	Screenshots can be captured in Veeva Test Case runs.
4263	Feature	82	Existing test cases can be deleted when generating Veeva test cases
4264	Feature	82	Labels can be applied to test cases when generating Veeva test cases
4265	Feature	82	There is a Test Set Run wizard for Veeva Test Cases
4266	Feature	82	The Veeva test case generator supports the Event event_date__v field
4267	Feature	82	The Veeva test case generator supports the Site timezone__v field
4252	Feature	82	The Test Case view is available for Test Cases in Veeva drafts
4261	Feature	82	The Test Case data view is available for Test Cases in Veeva drafts
4255	Feature	81	When running a Veeva Test Case if the study is not found the Test Case will stop running and display list of studies the user does have access to
4256	Feature	81	When running a Veeva Test Case if the site is not found the Test Case will stop running and display list of sites the user does have access to
4239	Feature	81	The Veeva test case editor has a helper for data entry steps.
4249	Feature	81	Additional properties will be displayed in list views of Veeva draft objects
4250	Feature	81	The 'changes will not be saved' alert should not be displayed for Veeva draft objects
4240	Feature	81	The Test Case Advisor is available for Veeva Rules.
4241	Feature	81	Test Cases can have Veeva Rules as related objects
4199	Feature	81	Veeva Drafts can be uploaded from SDS spreadsheets but cannot be created directly in TrialGrid. Veeva Draft objects can be viewed but cannot be edited in TrialGrid.
4187	Feature	80	Veeva Vault Test Cases can enter data.
4188	Feature	80	Veeva Vault Test Cases can verify entered data values.
4189	Feature	80	Veeva Vault Test Cases can check queries on datapoint.
4186	Feature	80	Veeva Vault Test Cases can check if forms do or do not exist in events.
4175	Feature	80	Organizations with Veeva licences can create Vaults in TrialGrid. Vaults, like URLs, contain Projects and Drafts.
4176	Feature	80	Test Cases can be run on Veeva Vault studies.
4177	Feature	80	Test Cases can create and select subjects in Veeva Vault studies.
4178	Feature	80	Test Cases can add events to subjects in Veeva Vault studies.
4179	Feature	80	Test Cases can be created and edited for Veeva Vault drafts.
4182	Feature	80	Veeva Vault SDS spreadsheets can be uploaded to create drafts in TrialGrid.