Version : 34
Released : 2021-10-24
Changes in this Release
Issue |
Type |
Module(s) |
Description |
|---|---|---|---|
2536 |
Bug |
Actions |
Actions on object listings will sometimes temporarily remove custom property values already shown in the object list. This was corrected. |
2543 |
Feature |
Actions |
Before actions are executed the action dialog now shows how many objects out of the selected will actually be affected (e.g. 10 selected / 5 applicable) |
2544 |
Feature |
Actions |
The action dialog now shows the pre-condition for the action to help users understand why an object cannot have the action applied. |
2585 |
Bug |
Actions |
When actions are used to collect custom property values the values are not initially set (i.e. only updates were working). This was corrected. |
2582 |
Feature |
Actions |
The compliance status of objects (e.g. Matched, Different, Not Found etc) can now be checked in Action preconditions. |
2571 |
Feature |
Actions |
To make it easier to understand why an object did not meet Action preconditions the Action dialog now displays the parts of the precondition logic with either a check (tick) or a cross to show whether that part of the precondition was evaluated and what its return value was (check=True, cross=False). |
2598 |
Feature |
Actions |
Actions can now be set as auto-run. This means the action runs automatically on all objects of this type when they are saved, labelled or otherwise changed. |
2612 |
Feature |
Actions |
Actions now have an ordinal which affects their display order and the order in which auto-actions run. |
2633 |
Feature |
Actions |
Actions cannot be created with duplicated or conflicting add/remove label operations. |
2636 |
Bug |
Actions |
When auto-actions were triggered by user actions, the auto-action did not see new labels applied to the object which could then affect its logic. This was corrected. |
2635 |
Feature |
Actions |
Action preconditions do not recognize “Smart quotes”. The system now warns if a precondition contains smart quotes. In addition, examples containing smart quotes were removed from the online help. |
2521 |
Feature |
Automated Testing |
The Test Case results will display a message if a Rave EDC user does not have permission to execute the test step, for example if their Rave EDC Role does not have data entry permission. |
2524 |
Feature |
Automated Testing |
The Test Case results will display a message if a subject is required for a test step and one has not been created or selected in the previous steps. |
2542 |
Bug |
Automated Testing |
Test Cases without screenshots were not running against Rave EDC. This has been corrected. |
2552 |
Feature |
Automated Testing |
Test Case results will now include a message if non-ascii characters are present in expected or actual query text. |
2554 |
Bug |
Automated Testing |
TrialGrid would sometimes incorrectly check Queries when running Test Cases. This has been corrected. |
2541 |
Bug |
Automated Testing |
Long Draft names were overflowing the table border in the Test Case pdf report. This has been corrected. |
2583 |
Bug |
Automated Testing |
Test Case runs against Rave EDC are sometimes failing with an error 'Folder not found' or 'Form not found'. Additional logging and error handling has been added. |
2591 |
Feature |
Automated Testing |
When text cannot be highlighted in a Test Case screenshot a message is added to the Test Case log. This message now has a level of 'info'. |
2592 |
Feature |
Automated Testing |
If TrialGrid receives a '500 Internal Server Error' from Rave when entering Test Case data, a message will be added to the results to explain that this might be caused by a Custom Function error. |
2615 |
Feature |
Automated Testing |
There is a new 'Data' view for a Test Case which displays the data entered in each test scenario in a table. The table is read-only. |
2616 |
Feature |
Automated Testing |
The Test Case view will remember which tab was selected and display that tab the next time a Test Case is opened. |
2537 |
Feature |
Automated Testing |
The Test Case Advisor has a new option to create test scenarios using the Rave unknown date formats, UN, UNK, UNKN for days, months and years. |
2620 |
Feature |
Automated Testing |
The Test Case Advisor has a new option to create additional test scenarios such that each Field is tested with at least 2 different values. |
2634 |
Feature |
Automated Testing |
The Test Case Advisor will attempt to use the same value (0 for unchecked, 1 for checked) for all checkbox Fields if there are multiple checkbox Fields in an Edit Check. |
2605 |
Feature |
Automated Testing |
A default for the data entry step used by the Test Case Advisor can be set for each URL in TrialGrid. Contact support@trialgrid.com if you would like this to be configured for you. |
2590 |
Feature |
Automated Testing |
The Test Case Advisor will now create separate steps to select values from Dynamic Search List fields. |
2607 |
Feature |
Automated Testing |
The Test Case Advisor will now add references to Dynamic Search List custom functions |
2608 |
Feature |
Automated Testing |
A default for the content of new Test Cases can be set for each URL in TrialGrid. |
2609 |
Feature |
Automated Testing |
It is now possible to import or include the content of one Test Case inside another Test Case. |
2521 |
Feature |
Automated Testing |
The Test Case results will display a message if a Rave EDC user does not have permission to save a form in Rave EDC. |
2646 |
Bug |
Automated Testing |
Test Cases were not saving when using Internet Explorer. This has been fixed. |
2646 |
Bug |
Automated Testing |
Test Cases were not saving when using Internet Explorer. This has been fixed. |
2648 |
Feature |
Automated Testing |
Importing or exporting a Draft to Medidata Rave via iMedidata now supports two factor authentication using the Okta system recommended by Medidata. |
2640 |
Feature |
Collaboration |
In the Object Editors activity list you can now filter to see only comments or only activities or both. |
2597 |
Bug |
Document Templates |
Some document templates cannot be saved or edited without encountering an error stating that "The following variables are undefined ..". A solution for this issue was documented in the tips and tricks section of the document template help. |
2639 |
System |
Infrastructure / System |
All failed login attempts are now logged so that TrialGrid personnel can be informed of persistent failed login attempts. |
2525 |
Bug |
Rave Integration |
If a AddMatrix action is loaded from an ALS without a True/False set in the ActionScript column then the resulting matrix cannot be loaded to Rave. This value is now set to False by default. |
2600 |
Bug |
Rave Integration |
Derivations using the function 'Space' were not uploaded correctly. This has been fixed. |
215 |
Feature |
Rave Integration |
Draft Downloads and Direct Draft Exports will display a list of object types which can be included in the download or export. |
1674 |
Feature |
Rave Integration |
Drafts and versions can be imported from Rave Global Libraries. |
2555 |
Feature |
Rave Integration |
Draft Downloads and Direct Draft Exports to Rave will display warnings if the Draft has issues which might prevent it being loaded into Rave, or published after loading. Not all upload issues will be flagged yet. |
2578 |
Feature |
Rave Integration |
Drafts can be exported to Rave Global Libraries. |
2581 |
Feature |
Rave Integration |
It is now possible to Publish and Push new versions in Rave during a Direct Draft Export. This option is only supported when using an iMedidata login. |
2642 |
Bug |
Rave Integration |
Some users could not import Drafts using iMedidata logins. |
2519 |
Feature |
Standard Rules |
Wildcards can now be entered as object identifiers in Standards Rules. This allows Rules to be written that are applied to all objects that match the Wildcard. Wildcards use regular expressions to match objects by name as explained in the help. |
2523 |
Feature |
Standard Rules |
Object Identifier selections (including wildcards) can now be tested from the Rule Editor dialog. This allows you to see which objects from the library draft would be selected by this identifier. |
2593 |
Bug |
Standards |
When an object had been approved by a standards manager, the approval was reverted if a user added a comment to the approved object. This was corrected so that adding a comment does not change the compliance approval. |
2596 |
Bug |
Standards |
Standards compliance approval requests were being sent to users with inactive accounts. This was corrected. |
2570 |
Bug |
Study build |
The Draft compare results were sometimes showing Custom Functions as being different when they had no differences other than whitespace. This has been corrected. |
2594 |
Feature |
Study build |
When deleting a Form, a dialog now shows the effect of removing that form such as the Edit Checks which will be deleted as a result of the delete. Previously Forms "in use" were blocked from deletion. |
2599 |
Bug |
Study build |
When an object is deleted which is linked to a Ticket as a related object an error occurred and the object was not deleted, This was corrected. |
2606 |
Bug |
Study build |
Saving a Library form causes recalculation of related objects compliance state to happen twice. This was corrected. |
2601 |
Bug |
Study build |
When creating a new Derivation using quickedit, an error message will be if there is already a Derivation of that name. |
2603 |
Bug |
Study build |
When creating a new Edit Check using quickedit, an error message will be if there is already an Edit Check of that name. |
2602 |
Bug |
Study build |
An error occurred when copying a Derivation which had invalid cql. This has been corrected. |
2618 |
Bug |
Study build |
Data Dictionary Entries with & in them were being encoded to & when displayed (similarly, < to < and > to >). This was corrected. |
2619 |
Bug |
Study build |
Data Dictionaries could be saved with no changes made and this added new activity records. This was corrected. |
2627 |
Feature |
Study build |
Data Dictionary entries with < > and & in their user values were not being displayed correctly in the form preview. This was corrected. |
2622 |
Bug |
Study build |
View and Entry restrictions with & in their names were being shown as "not in the Core Configuration" in the Form Editor. This was corrected. |
2632 |
Feature |
Study build |
The Form preview for date fields with formats DD- or MMM- now shows UN or UNK to make it clearer that these are partial dates. |
2586 |
Feature |
Study build |
The Edit Check list now displays Bypass during migration, and can be filtered by Bypass during migration. |
2638 |
Feature |
Study build |
All Activities for objects now appear in their own tab in the object editor. Previously the activity list was found in the side-bar. |
2557 |
Feature |
Tickets |
The New Ticket page now has the same appearance as the Edit Ticket page. Previously the New Ticket page was a simplified page allowing entry of only Title, body and a due date. |
2558 |
Feature |
Tickets |
Tickets may now be created directly from object editors (e.g. when editing a Form). The ticket created this way is automatically associated with the object being edited. |
2335 |
Feature |
Tickets |
Duplicate of #2558. |
859 |
Feature |
Tickets |
Duplicate of #2558. |
2559 |
Feature |
Tickets |
Tickets related to objects may now be edited directly from the editor for that object. e.g. When editing a Form, tickets related to the Form can be edited in a pop-up window. |
2564 |
Feature |
Tickets |
Tickets and comments use Markdown syntax to display plain text with formatting such as bold or to create headings and tables. Our Markdown syntax removed newlines from content. Newlines are now preserved in Tickets and Comments. |
2565 |
Feature |
Tickets |
The "Edit Ticket" button which initiates editing of the heading or body of a ticket has now been changed to a pencil icon which comments also use |
2566 |
Feature |
Tickets |
When opening a ticket from the Object Editors, or creating a new Ticket the pop-up window had a Close button to make it clear how to dismiss the window. |
2641 |
Feature |
Tickets |
In the Object Editor and Ticket activity lists you can sort by latest activity last (the default) or latest activity first. |
2526 |
Bug |
UX |
When filtering check list by CheckAction, closing the filter area did not remove the CheckAction filter. This was corrected. |