Module : Veeva
Issue |
Type |
TrialGrid Version |
Description |
|---|---|---|---|
4803 |
Bug |
The Veeva Test Case generator was not processing dates and times consistently across timezones. |
|
4804 |
Feature |
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 |
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 |
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 |
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 |
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 |
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 |
The Veeva Test Case generator will switch to using a Background section, creating subjects per scenario, if necessary to test different events. |
|
4790 |
Feature |
Veeva Test Case runs will automatically submit an unsubmitted form before checking for a derived value. |
|
4791 |
Bug |
The Veeva Test Case generator was producing incorrect year values. This has been corrected. |
|
4792 |
Bug |
The Veeva Test Case generator was not respecting numeric formats when checking data values. This has been corrected. |
|
4793 |
Bug |
Veeva Test Case generation failed for rules binding a form with commas in its label. This has been corrected. |
|
4794 |
Bug |
The Veeva Test Case generator was not generating correct values for some rules with wildcards. This has been corrected. |
|
4795 |
Feature |
The Veeva Test Case generator will not now try to create test cases for lab forms. |
|
4783 |
Bug |
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 |
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 |
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 |
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 |
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 |
There are a default set of Property Sheets for Veeva URLs. |
|
4734 |
Bug |
External ID values are now imported correctly for Forms and Item Groups when loading a Study Design Specification. |
|
4735 |
Bug |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
Draft Merge was not working for Veeva Drafts. This has been corrected. |
|
4702 |
Feature |
TrialGrid now flags Veeva measurement Items (height, weight, vitals, etc.) that do not have an appropriate Unit Codelist. |
|
4703 |
Feature |
TrialGrid now flags Veeva measurement Items whose Length, Decimal, or value range is implausible for the kind of measurement they capture. |
|
4704 |
Feature |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
TrialGrid now flags Veeva Forms whose order relative to other Forms is inconsistent across the Events in which they appear. |
|
4683 |
Bug |
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 |
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 |
Veeva 'set event to did not occur' steps can now include a reason. |
|
4660 |
Feature |
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 |
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 |
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. |
|
4672 |
Bug |
Screenshots for Veeva forms with item groups with 'Editable grid' display format were not being captured correctly. This has been corrected. |
|
4665 |
Bug |
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 |
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 |
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 |
The Veeva Test Case agent now creates Add Event steps where necessary. |
|
4631 |
Feature |
The Veeva Test Case agent now has a default value when saving a Test Case. |
|
4626 |
Feature |
Standard Rules are now editable in Veeva Library drafts. |
|
4615 |
Feature |
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 |
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 |
The Veeva Test Case Run now records the casebook version and build number |
|
4596 |
Bug |
The Veeva Test Case Advisor was not processing 2-part (event.form) Action Targets. This has been corrected. |
|
4598 |
Feature |
The Veeva Test Case editor helper for 'see value' steps now supports partial datapoint references. |
|
4552 |
Bug |
The Veeva and Medidata Test Case agents should have similar workflow and features. |
|
4551 |
Bug |
Custom objects in Veeva drafts should be editable. |
|
4535 |
Feature |
The Veeva Test Case generator now creates background steps for adding events consistently with other generators. |
|
4536 |
Bug |
There was an error generating Test Cases for Veeva rules containing date items with unknown parts. This has been corrected. |
|
4537 |
Feature |
The Veeva Test Case generator now supports unknown dates. |
|
4539 |
Feature |
Diagnostic V081 'Check text strings for trailing whitespace' is available for Veeva studies. |
|
4540 |
Feature |
Diagnostic V179 'Double spaces in Text Fields' is available for Veeva studies. |
|
4542 |
Feature |
The Veeva Test Case generator will report an error if a Rule references objects which do not exist. |
|
4527 |
Bug |
Veeva Test Cases were not taking screenshots of forms in Log events. This has been corrected. |
|
4528 |
Bug |
The Veeva Test Case add event step was incorrectly setting event dates. This has been corrected. |
|
4529 |
Feature |
There is a new Veeva Test Case step to verify Event date values. |
|
4530 |
Feature |
The Veeva Test Case editor helpers now support repeat numbers. |
|
4438 |
Feature |
Veeva Test Case data entry steps can create Item to Form links. |
|
4512 |
Feature |
There is a new Veeva Test Case step to submit a form. |
|
4513 |
Feature |
There is a new Veeva Test Case step to set an event as did not occur. |
|
4520 |
Bug |
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 |
Veeva Test Case event steps will take screenshots. |
|
4522 |
Feature |
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 |
The Veeva Test Case query steps now support event date queries. |
|
4524 |
Bug |
Veeva Test steps using numeric values were not being compared correctly. This has been corrected. |
|
4526 |
Bug |
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 |
The Veeva Test Case editor helpers will display names and labels to make searching easier. |
|
4506 |
Bug |
The Veeva Test Case editor was not reporting some errors correctly. This has been corrected. |
|
4500 |
Feature |
Veeva Test Cases support unknown date, time and datetime Items. |
|
4502 |
Feature |
If the query is not found the Veeva query test steps will take screenshots of the Form. |
|
4503 |
Feature |
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 |
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 |
There is a Schedule view showing a grid of Events and Forms. |
|
4485 |
Feature |
The Veeva Form review supports Progressive Display. |
|
4488 |
Feature |
The Form Review page will display field properties after clicking on a row. |
|
4491 |
Bug |
The Draft Name is not being set on uploading a Veeva SDS. |
|
4492 |
Feature |
The Veeva Test Case editor View tab will show labels for events and forms. |
|
4493 |
Bug |
The Veeva Test Case advisor will use true/false for checkbox/boolean fields. |
|
4494 |
Feature |
The Veeva Test Case editor has warnings for invalid checkbox/boolean values. |
|
4495 |
Feature |
The Veeva Test Case editor will auto-correct dates to DD-Mon-YYYY format, fixing month capitalization and left-padding single-digit days. |
|
4496 |
Feature |
The status (active/inactive) property will be shown in Veeva Rule and Comparison Rule lists. |
|
4497 |
Feature |
The 'I wait' step is now available for Veeva Test Cases. |
|
4498 |
Bug |
When the Veeva subject status step failed the error message was repeated. This has been corrected. |
|
4499 |
Bug |
The 'event date set' message was being repeated in Veeva add event steps. This has been corrected. |
|
4484 |
Feature |
There are Test Case editor helpers for the Veeva item visibility steps. |
|
4477 |
Bug |
Linked Forms were not being imported from Veeva SDS spreadsheets. This has been corrected. |
|
4481 |
Feature |
There are new Veeva Test Case steps to check if Items are visible or not when progressive display is configured. |
|
4476 |
Feature |
The Form Review view supports Veeva EDC forms. |
|
4445 |
Feature |
There is an Agent to check the progressive display settings on Veeva forms. |
|
4434 |
Bug |
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 |
Running the Veeva Test Case generator on multiple Rules could lead to inconsistent results. This has been corrected. |
|
4436 |
Bug |
The Veeva Test Case Generator was not correctly generating additional scenarios for Rules with OR conditions. This has been corrected. |
|
4437 |
Bug |
The Veeva Test Case Generator sometimes needs to add events before checking if a form exists or not. |
|
4439 |
Bug |
The Veeva Test Case Generator was not always working for Rules using the InWindow function. This has been corrected. |
|
4402 |
Feature |
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 |
There is a new Diagnostic for Veeva studies to check if Items are using reserved words. |
|
4391 |
Feature |
Veeva query step will display the status of the query in user-friendly text. |
|
4392 |
Feature |
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 |
There is a new test step for Veeva Test Cases to check value of the subject name. |
|
4394 |
Feature |
There is a new step for Veeva Test Cases to check the value of the subject status. |
|
4383 |
Feature |
The Veeva Test Case Advisor is available for Comparison Rules. |
|
4382 |
Bug |
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 |
There is a Test Case creator agent for Veeva drafts. |
|
4291 |
Feature |
The Veeva Test Case generator now supports the sequence__v system variable. |
|
4292 |
Feature |
The Veeva Test Case generator now supports the name__v system variable |
|
4293 |
Feature |
The Veeva Test Case generator now supports the count__v system variable. |
|
4289 |
Feature |
The Veeva Test Case generator will create additional scenarios for comparison operators. |
|
4288 |
Feature |
Users with 'Can manage Vault settings' can view and register Veeva Vaults. |
|
4285 |
Feature |
The Test Case generator for Veeva rules will include Units when an Item has a Unit Codelist |
|
4286 |
Feature |
Veeva Test Cases can be copied from another draft into the current draft. |
|
4280 |
Feature |
There are Test Case editor helpers for all Veeva event steps. |
|
4281 |
Feature |
Veeva Test Case event steps now include the event group and event. |
|
4282 |
Feature |
There are Test Case editor helpers for Veeva form steps. |
|
4283 |
Feature |
There are Test Case editor helpers for Veeva data value steps. |
|
4284 |
Feature |
There are Test Case editor helpers for Veeva query steps. |
|
4276 |
Feature |
There are tooltips showing the labels for objects in the Test Case editor. |
|
4277 |
Feature |
There are tooltips showing the labels for objects in the Test Case run results view. |
|
4271 |
Feature |
The Test Case generator for Veeva Rules now supports Add Event actions. |
|
4272 |
Feature |
The Test Case generator for Veeva Rules now supports Add Event Group actions. |
|
4273 |
Feature |
The Test Case generator for Veeva Rules now supports Add Form actions. |
|
4274 |
Feature |
There are new test steps to check if Events do or not exist in Veeva Test Cases. |
|
4268 |
Feature |
PDF Reports can be generated for Veeva Test Cases |
|
4269 |
Feature |
AI generated summaries are available for Veeva Test Cases and Test Case runs |
|
4262 |
Feature |
Screenshots can be captured in Veeva Test Case runs. |
|
4263 |
Feature |
Existing test cases can be deleted when generating Veeva test cases |
|
4264 |
Feature |
Labels can be applied to test cases when generating Veeva test cases |
|
4265 |
Feature |
There is a Test Set Run wizard for Veeva Test Cases |
|
4266 |
Feature |
The Veeva test case generator supports the Event event_date__v field |
|
4267 |
Feature |
The Veeva test case generator supports the Site timezone__v field |
|
4252 |
Feature |
The Test Case view is available for Test Cases in Veeva drafts |
|
4261 |
Feature |
The Test Case data view is available for Test Cases in Veeva drafts |
|
4255 |
Feature |
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 |
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 |
The Veeva test case editor has a helper for data entry steps. |
|
4249 |
Feature |
Additional properties will be displayed in list views of Veeva draft objects |
|
4250 |
Feature |
The 'changes will not be saved' alert should not be displayed for Veeva draft objects |
|
4240 |
Feature |
The Test Case Advisor is available for Veeva Rules. |
|
4241 |
Feature |
Test Cases can have Veeva Rules as related objects |
|
4199 |
Feature |
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 |
Veeva Vault Test Cases can enter data. |
|
4188 |
Feature |
Veeva Vault Test Cases can verify entered data values. |
|
4189 |
Feature |
Veeva Vault Test Cases can check queries on datapoint. |
|
4186 |
Feature |
Veeva Vault Test Cases can check if forms do or do not exist in events. |
|
4175 |
Feature |
Organizations with Veeva licences can create Vaults in TrialGrid. Vaults, like URLs, contain Projects and Drafts. |
|
4176 |
Feature |
Test Cases can be run on Veeva Vault studies. |
|
4177 |
Feature |
Test Cases can create and select subjects in Veeva Vault studies. |
|
4178 |
Feature |
Test Cases can add events to subjects in Veeva Vault studies. |
|
4179 |
Feature |
Test Cases can be created and edited for Veeva Vault drafts. |
|
4182 |
Feature |
Veeva Vault SDS spreadsheets can be uploaded to create drafts in TrialGrid. |