Version : 49

Released : 2023-02-26

Changes in this Release

Issue

Type

Module(s)

Description

3292

Feature

API

A project API call was added which provides a list of all projects in the organization of the requesting user regardless of whether they have access to those projects. Users cannot use these APIs unless they have API access granted by TrialGrid.

3293

Feature

API

A URL API was added which provides a list of all URLs in the organization of the requesting user regardless of whether they have access to those URLs.

3263

Feature

Automated Testing

The Test Case Advisor will now produce better test scenarios for Edit Checks which have a leading 'IsEqualTo' step and multiple IsEmpty/IsNotEmpty 'or' steps, and for Edit Checks which include a Field with a Data Dictionary which has only 1 entry.

3262

Feature

Automated Testing

The Test Case Advisor will remember the options selected by the user.

3261

Bug

Automated Testing

The Test Case editor was not flagging errors if a string used as a placeholder also contained placeholder tags. This has been corrected.

3152

Feature

Automated Testing

The current date and/or time can now be used in Test Cases. See Dates and Times in Test Cases.

3265

Bug

Automated Testing

Pending Test Case runs were displaying with a green background in the Test Case list. This has been corrected.

3287

Bug

Automated Testing

In Test Case runs, TrialGrid would create new log records on Forms with fixed default values. This has been corrected. Draft TG_UAT Version 18 is required for this change. Please contact support@trialgrid.com to obtain this version.

3288

Bug

Automated Testing

In Test Case runs, default values were not always being submitted when the page was saved. This has been corrected.

3289

Feature

Automated Testing

Test Case results will display a table of all queries on a datapoint, including closed ones, when verifying queries on a datapoint.

3285

Feature

Automated Testing

There are new Test Case steps to check for Open, Answered and Closed queries.

3251

Feature

Custom Properties

It is now possible to define custom objects which appear as child objects of Drafts. A custom object can have custom properties defined for it and spreadsheet views. Custom objects can be a convenient way to model simple data that is related to Drafts (IVRS specifications, Report formats etc).

3184

Feature

Diagnostic

Diagnostic 143 was added. This Diagnostic checks if Data Dictionary Entries have Specify = True for customers who do not use Data Dictionary Specify option and prefer to have Specify always False with a separate "Other, Specify" field.

3183

Feature

Diagnostic

Diagnostic 144 was added. This Diagnostic checks if Data Dictionary Entries Coded Data or User Data String contain html or "<string>" values since these block rendering in RaveEDC and in PDF Generator output.

3272

Feature

Diagnostic

Diagnostic 145 was added. This Checks that Form names do not contain individual words which are longer than 25 characters. These form names do not display well in Rave Classic.

3259

Feature

Study build

The Edit Check and Custom Function editors have a new option 'Merge into Rave Draft' in the list of actions in the dropdown next to the Save button. 'Merge into Rave draft' will only be available after a performing an 'Export to Rave' from the Draft home page, and will merge into the Rave Project and Draft selected in the Export to Rave.

3264

Feature

Study build

Small Drafts will be exported without starting a 'one-off' worker, which will make the exports faster.

3245

Feature

Study build

When viewing list of Draft objects (Forms, Folders, etc) an icon will appear in the 'Updated' column if other users are viewing or editing that type of object in the Draft.

3291

Bug

Tickets

Creating a ticket with a title longer than 400 characters would fail with a system error. The system now allows titles up to 1000 characters.

3290

Bug

Tickets

If a ticket had a title longer than 200 characters then the system would fail with an error while trying to create a notification that a user was assigned to the ticket. This was corrected.