Version : 68
Released : 2024-11-03
Changes in this Release
Issue |
Type |
Module(s) |
Description |
---|---|---|---|
3878 |
Bug |
Drafts list API /api/v1/drafts/ ordered data by DraftName which when used with a limit and paging can cause data to be missed because of database ordering on just Draft Name was not stable across requests. It is now ordered by Draft Name and Draft ID which corrects the issue. |
|
3857 |
Feature |
Actions can now be defined for custom objects. |
|
3846 |
Feature |
The new iMedidata home page is supported when running test cases on Medidata Rave EDC URLs. |
|
3847 |
Feature |
The new iMedidata home page is supported when registering Medidata Rave EDC URLs. |
|
3848 |
Feature |
The Medidata 'Protocol ID' is required when running test cases on Rave EDC URLs. |
|
3849 |
Feature |
The Medidata 'Environment Name' is required when running test cases on Rave EDC URLs. |
|
3850 |
Feature |
The Protocol ID will be automatically set to the Study name in the Automated Test Configuration for existing Projects. |
|
3851 |
Feature |
The Environment Name will be automatically set to the corresponding standard Environment in the Automated Test Configuration for existing Projects. |
|
3852 |
Feature |
The Protocol ID will be automatically set to the Study name in the Automated Test Configuration for existing Test Set Runs. |
|
3853 |
Feature |
The Environment Name will be automatically set to the corresponding standard Environment in the Automated Test Configuration for existing Test Set Runs. |
|
3854 |
Feature |
The URL of the TG_UAT subject must be entered in the Automated Test Configuration section for Projects using TG_UAT version 18 or earlier. |
|
3868 |
Bug |
The Add Event Test Case step was not working correctly on some Rave URLs. This has been corrected. |
|
3880 |
Bug |
The Test Case Advisor would fail if there was a derived field in the check steps with an IsEmpty or IsNotEmpty function, and additional scenarios were requested. This has been corrected. |
|
3821 |
Feature |
Diagnostic 48 now allows a standard suffix as well as a standard prefix. |
|
3822 |
Feature |
Diagnostic 168 was added to check that the number of Fields on a Form is not over a limit. |
|
3844 |
Feature |
Labels can now be assigned to custom objects. |
|
3827 |
Feature |
When exporting or importing a Draft using an iMedidata account TrialGrid will prompt for the selection of a Role to access Medidata Rave. |
|
3876 |
Feature |
The Draft Export wizard now supports the new iMedidata home page. |
|
3877 |
Feature |
The Draft Import wizard now supports the new iMedidata home page. |
|
3879 |
Feature |
The option to Push versions to environments and sites when exporting a Draft to Rave with an iMedidata login have been retired and is no longer available. |
|
3863 |
Bug |
When rules for matrices or matrix folders are active for a draft, trying to view the active rules for the draft resulted in an error. This was corrected. |
|
3830 |
Feature |
Comments for a Draft object can now be displayed in draft object lists by clicking on the count of comments for an object. |
|
3831 |
Feature |
Tickets will now be displayed in draft object lists. |
|
3834 |
Feature |
Comments for all objects can now be displayed in draft object lists by clicking on the checkbox next to 'Comments' in the list header. |
|
3835 |
Feature |
Draft objects lists can be filtered to show objects which do, or do not, have comments. |
|
3836 |
Feature |
Draft objects lists can be filtered to show objects which do, or do not, have tickets. |
|
3837 |
Feature |
The 'comments for all objects' selection (see #3834) will be remembered and automatically selected in other draft object lists. |
|
3838 |
Feature |
Clicking on a ticket in a draft object list will open the ticket in a modal |
|
3839 |
Feature |
Comments will be included in exports from draft object lists. |
|
3840 |
Feature |
Tickets will be included in exports from draft object lists. |
|
3865 |
Bug |
On saving form with EproFormat values set, a number of activity records would be recorded for the EproFormat values which did not actually change. This was corrected. |
|
3866 |
Bug |
On the organization and draft home pages the more activities links did not work. This was corrected. |
|
3886 |
Bug |
If duplicate objects were somehow created in a draft, trying to clone the draft would fail with a cryptic error. The error message now explains the duplicate issue so that it can be corrected. |
|
3855 |
Feature |
Custom objects can now be added as related objects to Tickets. |
|
3814 |
Feature |
URLs can be 'pinned', see Pinned Objects. |
|
3815 |
Feature |
Projects can be 'pinned', see Pinned Objects. |
|
3816 |
Feature |
Drafts can be 'pinned', see Pinned Objects. |
|
3817 |
Feature |
Pinned objects will be displayed on the user's home page, see Pinned Objects. |
|
3818 |
Feature |
Pinned Projects will be displayed on the URL home page, see Pinned Objects. |
|
3819 |
Feature |
Pinned Drafts will be displayed on the Project home page, see Pinned Objects. |
|
3820 |
Feature |
Pinned objects can be viewed in a dropdown in the top navigation bar, see Pinned Objects. |
|
3823 |
Feature |
Pinned Drafts will be displayed at the top of the list of Drafts when copying objects. |
|
3824 |
Feature |
Pinned Drafts will be displayed at the top of the list of Drafts when selecting Related Objects in the Ticket editor. |
|
3829 |
Bug |
On the second and subsequent pages of the url team list, changes to user permissions did not register. This was corrected. |
|
3841 |
Feature |
Exports from object listings no longer include columns which have been hidden by the user and the listing control dialog now appears in the center of the screen. |