Version : 40
Released : 2022-04-18
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
2806 |
Bug |
When requesting full details of lists via the API, performance was slow. Performance has been improved by reducing the number of database queries, and by removing 'text_description' from the Edit Checks detail. |
|
2832 |
Bug |
The API was returning Folder, Form and Field ids in Check Steps, Check Actions and Derivation Steps, instead of OIDs. This has been corrected. |
|
2846 |
Feature |
In Action preconditions the function compliance_status_is(ALLOWED_CHANGES) returns True if the object has only allowed changes or passed rules. The new function only_allowed_changes() returns True if state is ALLOWED_CHANGES and the count of allowed changes is greater than 0 and the count of rules passed is 0. That is, there are ONLY allowed changes type changes. |
|
2847 |
Feature |
In Action preconditions the function compliance_status_is(ALLOWED_CHANGES) returns True if the object has only allowed changes or passed rules. The new function only_rules_passed() returns True if state is ALLOWED_CHANGES and the count of rules passed > 0 and the count of allowed changes is 0. That is, there are ONLY standard rules passed type changes. |
|
2852 |
Feature |
In Action preconditions the new function matches_copy_source() returns True if the object is in a draft linked to a library and has been copied from some other object (e.g. another draft) and matches that object precisely (by fingerprint). Otherwise it returns False. |
|
2828 |
Bug |
The "I add folder" test steps were creating additional parent folders when adding child folders to parent folders. This has been corrected. A new version of the TG_UAT draft, version 12, is required. |
|
2829 |
Feature |
The Test Case editor will display a warning for steps which reference nested folders or parent/child folders and which do not use an absolute folder reference. |
|
2830 |
Feature |
The Test Case editor will display a warning if the 'folder exists' step is used with parent/child folders. An 'add folder' step should be used. |
|
2835 |
Feature |
The Test Case Advisor will now insert the Parent Folder OID for any Folders which have a Parent Folder. |
|
2835 |
Feature |
The Test Case Advisor will now insert the Parent Folder OID for any Folders which have a Parent. |
|
2836 |
Feature |
The Test Case Advisor will now create 'I add folder' steps for Folders which have a Parent. |
|
2839 |
Feature |
When saving a Test Case Template, TrialGrid will check all Test Cases in the Draft to see if they import or include that Template, and will update them if so. |
|
2841 |
Feature |
Before deleting a Test Case Template, a confirmation message will be displayed asking the user to confirm that the Test Case Template should be deleted. |
|
2849 |
Feature |
When deleting a Test Case Template, TrialGrid will check all Test Cases in the Draft to see if they import or include that Template, and will update them if so. |
|
2842 |
Feature |
When a new Test Case Template is created, TrialGrid will check all Test Cases in the Draft to see if they import or include that Template, and will update them if so. |
|
2843 |
Feature |
The Test Case 'Is Template' property is now included in Draft exports and imports. |
|
2844 |
Feature |
When copying Test Cases into a Draft, Test Case Templates will be copied first. |
|
2845 |
Feature |
Test Case Templates cannot include or import another Template. |
|
2850 |
Feature |
When saving a Test Case Template, there will not be an error message if the Template has no Scenarios. |
|
2851 |
Feature |
When editing a Test Case Template, the View, Data and Run History tabs will not be displayed. |
|
2860 |
Feature |
A new 'healthcheck' has been added to alert TrialGrid Ltd if any Test Case runs have stalled. |
|
2861 |
Feature |
Stalled Test Case runs will be automatically set to a state of Failed by TrialGrid. |
|
2864 |
Feature |
The Test Case Excel report now includes the email of the user who created the Test Case, when it was created, and the email of the user who last updated it and when. |
|
2870 |
Feature |
Invalid Test Cases will not be included in Test Case PDFs or Test Case Excel reports. |
|
2871 |
Feature |
The number of scenarios in each Test Case is displayed in the Test Case list |
|
2872 |
Bug |
Test Case results were not including screenshots for all forms if the form was inside a nested folder (a folder with a parent folder) and there were multiple instances of the parent folder. Test Case results were not being verified correctly for Forms inside nested folders. These issues have been corrected. |
|
2873 |
Feature |
The Test Case editor will display an error, and the Test Case will be invalid, if there is no login step in the Test Case. |
|
2874 |
Feature |
The Test Case editor will display an error, and the Test Case will be invalid, if there is no create or select subject step in the Test Case. |
|
2875 |
Feature |
The Test Case editor will display an error, and the Test Case will be invalid, if the Background line has been accidentally deleted. |
|
2876 |
Feature |
The Test Case editor now displays a count of the number of scenarios, and a count of the number of test steps. |
|
2878 |
Feature |
The Test Case results will report if the same query is open more than once on a datapoint. The step will still pass. |
|
2881 |
Feature |
A new Test Case step will check if a Form exists in the specified Folder in the Rave subject and if it does not, then TrialGrid will ignore it and will not attempt to enter data into that Form. See Automated Testing Step Reference |
|
2744 |
Bug |
In a Test Case with an included Template, the helper icons would not always be positioned on the correct line. This has been corrected. |
|
2892 |
Bug |
The Test Case Advisor would fail for Edit Checks referencing an integer Field using StandardValue and UserValue. This has been corrected. |
|
2893 |
Bug |
Test Cases would not run when testing Rave EDC studies if the Site Number was different from the Study Site Number. This has been corrected. The Site Number should be entered and TrialGrid will look up the Study Site Number and use that to navigate in Rave EDC. |
|
2895 |
Bug |
Test Case results were incorrectly reporting fields as being entry restricted. This has been corrected. |
|
2878 |
Feature |
The Test Case results will report if the same query is open more than once on a datapoint. The step will still pass. |
|
2900 |
Bug |
When running multiple Test Cases at the same time against Rave EDC, some calls to Rave custom functions could fail. This has been corrected. |
|
2889 |
Bug |
If a Derivation is inactive, it will not be included in the Test Case generated for an Edit Check which references the Field which is the target of the Derivation. |
|
2816 |
Feature |
Diagnostic 0033 now has an 'ignore inactive' setting, and will report on Fields which are not visible. |
|
2808 |
Feature |
Diagnostic 0134 will report text Fields with a format of $200 or longer which do not have query non-conformance set. |
|
2809 |
Feature |
Diagnostic 0135 will report Forms which are set to be EPRO Forms. |
|
2810 |
Feature |
Diagnostic 0016 has a new setting 'All Checks'. When this is set, the Diagnostic will report all Edit Checks which do not have Bypass During Migration set. |
|
2817 |
Feature |
Diagnostic 0016 has a new setting 'Ignore Inactive'. |
|
2866 |
Feature |
The default for Diagnostic Import Settings is now Overwrite. |
|
2867 |
Feature |
The Activity Record for Diagnostic Import Settings now includes whether it was an Overwrite or Merge. |
|
2868 |
Feature |
Diagnostic 0047 has new settings. Coded Data can be checked case-sensitively only, and User Strings can be excluded from checking for duplicate entries. |
|
2869 |
Bug |
Merging Diagnostic Settings into a Project could lead to duplicate setting values. This has been corrected. |
|
2753 |
Feature |
Diagnostic 00136 will check if more than a maximum number of Review Groups are set in Field properties. |
|
2753 |
Feature |
Diagnostic 00137 will check if more than a maximum number of Marking Groups are set in Check Actions. |
|
2889 |
Feature |
Diagnostic 00138 will check if any Field OIDs start with a number. |
|
2691 |
Feature |
Diagnostic 00139 will check that Forms with Lab Analyte Fields also have a Field which sets the Observation date (record or datapage date). |
|
2890 |
Feature |
Diagnostic 00140 checks that standards fields are positioned before log fields (with the exception of derived and label fields). |
|
2882 |
Feature |
Diagnostic 00141 finds inactive Forms, Fields, Checks and Derivations. The auto-fix will remove the inactive objects. |
|
2888 |
System |
It is now possible to export all projects, drafts and content for an Organization in one TrialGrid environment and import into another TrialGrid environment. Contact support@trialgrid.com if you would like to do this. |
|
2834 |
Feature |
When a user is invited and their email address domain is linked to an SSO provider, the user activates their account by logging in via SSO. |
|
2838 |
Feature |
When a user logs in via SSO the provider may send over additional attributes of the user such as last name and first name. If the system detects attributes which could be translated as "firstname" or "lastname" by removing spaces and underscores and putting identifier to lower case then these attributes of the user profile will also be updated on login. |
|
2811 |
Feature |
Draft Upload/Import will not warn if a Derivation or Edit Check has no steps. |
|
2812 |
Feature |
Draft Upload/Import was renumbering Derivation Step Ordinals if they did not start at 1 or were not in sequential order. This caused issues with merging Drafts back into Rave and so StepOrdinals will not now be renumbered on Upload or Import. |
|
2348 |
Feature |
Duplicate Derivation Steps were being created in Medidata Rave after a draft merge from TrialGrid. This was due to the renumbering of Derivation Step Ordinals. TrialGrid will not renumber Derivation Step Ordinals on import of a Draft, but if a Derivation is updated in TrialGrid the Ordinals might change, and this may cause issues when merging back to Rave. |
|
2813 |
Feature |
Draft Upload/Import will fail with an error if an object which should have an ordinal does not have one. |
|
2814 |
Feature |
Draft Upload/Import will display the identifier of a row if there is a warning message about that row. |
|
2822 |
Feature |
When an organization is linked to a Single Sign On provider, users cannot change their own passwords, this is the responsibility of the Single Sign on system. |
|
2823 |
Feature |
When an organization is linked to a Single Sign On provider, users cannot activate Two-factor authentication in the system. This is the responsibility of the Single Sign on provider. |
|
2825 |
Feature |
When an organization is linked to a Single Sign On provider, users cannot login via the normal login page. When they try they are offered a link to login via the Single Sign on provider. |
|
2826 |
Feature |
Once I have logged into the system via SSO, when I visit the login page again I see a link to the last SSO I used. |
|
2827 |
Feature |
When a user is linked to an SSO provider, I can log in to the system from the SSO portal (assuming I am logged into the SSO portal). |
|
2831 |
Feature |
When a user is linked to a Single Sign On provider they cannot request a password reset link from the "forgot password" page. |
|
2855 |
Feature |
In the create draft from library dialog when there are warnings about unset Project properties the link now takes the user direct to the metadata tab |
|
2854 |
Bug |
When a draft object is linked to a library other than the default library and this other library is soft-deleted, the list of objects cannot be displayed. An error occurs. |
|
2859 |
Feature |
Projects now have an option to switch off all Standards Notification emails. |
|
2833 |
Bug |
When editing Draft Lab Variable Mappings, if a Form was selected, and then no Form was selected, a javascript error was displayed. This has been corrected. |
|
2853 |
Feature |
In Draft Compares it is now possible to change the short names of drafts (A/B) for different names such as Source/Target or Old/New. |
|
2856 |
Bug |
When a label name has two spaces in it, e.g. "Test: One" lists of objects could not be filtered by that label. This was corrected. |
|
2853 |
Feature |
In Draft Compares it is now possible to change the short names of drafts (A/B) |
|
2857 |
Bug |
When a Form is copied into a Draft, TrialGrid will look for invalid Edit Checks which refer to the Form OID, or the FieldOID of a Field in the Form. These Edit Checks will be updated with references to the Form/Field(s). TrialGrid was not looking at Check Actions with missing objects. This has been corrected. Copying Folders will also update Check Actions now. |
|
2858 |
Bug |
If an Edit Check Action refers to a Folder, Form or Field which does not exist in the Draft, TrialGrid was not marking the Edit Check as invalid. This has been corrected. |
|
2862 |
Bug |
The validation of settings for Check Actions 'UpdateFolderName' and 'UpdateFormName' in CQL and Quickedit was wrong and has been corrected. |
|
2863 |
Feature |
The Custom Function list can now be searched by Source Code. |
|
108 |
Feature |
The Custom Function list now displays the name Custom Functions which are called by other Custom Functions, in the Actions column. |
|
2865 |
Feature |
The Custom Function list now has a columns 'Actions' which displays the actions performed by the custom function. see Custom Function List. |
|
2884 |
Bug |
Draft Lab Settings could not be saved if the Lab configuration variable names were not in upper case. This has been corrected. |
|
2885 |
Feature |
When viewing a comparison of Edit Checks, the quickedit will have the same order of steps as in the quickedit editor. |
|
2879 |
Feature |
From the Draft Compare Dialog it is now possible to copy objects that don't exist in one draft to the other. |
|
2886 |
Feature |
When copying an Edit Check or Derivation, if the Variable OID of a Field is different in the target draft, then it will be updated to match the Field in the target draft. |
|
2828 |
Bug |
The "I add folder" test steps were creating additional parent folders when adding child folders to parent folders. This has been corrected. A new version of the TG_UAT draft, version 12, is required. |
|
3989 |
Feature |
Version 12 of the TG_UAT draft has been released. This issue has been added retrospectively for documentation. |