Version : 66

Released : 2024-08-31

Changes in this Release

Issue	Type	Module(s)	Description
3788	Feature	API	Compliance fingerprints are now included in the api for exported draft objects and standards compliance.
3782	Feature	Actions	It is now possible to run Actions from object editors.
3762	Feature	Automated Testing	There are new Test Case steps to check if a query is open, or not open, for a specified Marking Group. These steps are only available when using TG_UAT version 21 or higher.
3755	Feature	Automated Testing	When entering data on landscape Forms data will be entered in one transaction for all records (standard and log) which exist on the form. Data for log records which do not already exist will be entered in separate transactions. This feature is only applicable when using TG_UAT version 21 or higher.
3787	Bug	Automated Testing	The Test Case Advisor could fail if an Edit Check contained static values for a text field and static values for a date or time field. This has been corrected.
3786	Bug	Automated Testing	Tags and line breaks in Test Case data table values could cause errors in PDF generation. This has been corrected.
3798	Bug	Automated Testing	Test Cases were not running on Medidata Rave Classic URLs when using iMedidata logins. This has been corrected.
3750	Feature	Custom Properties	When creating a custom object it is now possible to choose from the available icons.
3752	Feature	Custom Properties	When creating or updating a custom object it is now possible to choose the separator for the parts of the custom object identifier.
3757	Feature	Custom Properties	It is now possible to choose which custom properties are concatenated to create the identifier for an instance of a custom object. These identifiers are used in standards compliance matching to library objects.
3783	Feature	Property Sheets	Labels may now be shown, read only, in property sheets for Edit Checks and Folders.
3726	Feature	Standard Rules	It is now possible to create standard rules for custom objects.
3727	Feature	Standards	Custom objects now take part in standards compliance.
3728	Feature	Standards	It is now possible to switch off standards compliance reporting for custom object types from the URL editor page. Objects continue to have compliance calculated but excluded custom object types do not appear in compliance reports.
3784	Bug	Study build	When copying Data Dictionary entries between data dictionaries via the compare dialog, Data Dictionary Ordinals were not recalculated. This was found to be a problem also for Form Field Ordinals and Ordinals of Unit Dictionary Entries This was corrected with incorrect ordinals updated.
3785	Bug	Study build	It was possible to paste Data Dictionary Entry values with trailing spaces into the Data Dictionary editor and save the Dictionary, preserving the spaces. This was corrected, leaving existing values unchanged for compliance reasons.