Module : Rave Integration
Issue |
Type |
TrialGrid Version |
Description |
---|---|---|---|
3917 |
Bug |
71 |
When uploading a draft from the filesysytem the upload would report that there were warnings even if there were no actual warnings. This has been corrected. |
3955 |
Bug |
70 |
Medidata Rave Lab Configuration files could not be loaded if a Lab had an empty Description. This has been corrected. |
296 |
Feature |
70 |
It is now possible to upload Drafts in Excel 2007-365 (.xlsx) format. |
2296 |
Feature |
70 |
If an attempted Draft upload is in Excel 97-2004 Workbook (.xls) format, an error message will be displayed. |
3908 |
Feature |
70 |
It is now possible to export Drafts in Excel 2007-365 (.xlsx) format. |
3891 |
Feature |
69 |
The Draft Download wizard will not now display icons next to each object type. |
3915 |
Bug |
68.9 |
iMedidata two factor authentication was not being processed properly causing failures in draft import and export and test case runs. This has been corrected. |
3876 |
Feature |
68 |
The Draft Export wizard now supports the new iMedidata home page. |
3877 |
Feature |
68 |
The Draft Import wizard now supports the new iMedidata home page. |
3879 |
Feature |
68 |
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. |
3827 |
Feature |
68 |
When exporting or importing a Draft using an iMedidata account TrialGrid will prompt for the selection of a Role to access Medidata Rave. |
3801 |
Bug |
66.1 |
Loading an ALS draft into TrialGrid is sometimes failing for one customer. An administrative configuration setting has been added to TrialGrid to allow for a longer duration to upload the file. |
3719 |
Bug |
64 |
When using different wizards to export or import drafts from Medidata Rave or to run Test Cases, TrialGrid caches values entered in the wizards and could use inappropriate values from one wizard in another wizard. This has been corrected. |
3554 |
Bug |
58.1 |
When a Draft was imported from Rave the QuickEdit generated for display and editing was set to the TrialGrid preferred format which can re-order AND/OR steps and modify static value lengths (e.g. "Y" $3 -> "Y" $1). This has been corrected and the display/edit QuickEdit is set to reflect the values of steps exactly as in the ALS. |
3525 |
Bug |
57.2 |
Users were unable to use an iMedidata login to import or export Drafts. This has been corrected. |
3529 |
Feature |
57.2 |
An error message will be displayed if an iMedidata user account which has been switched to the new Medidata home page is used to import or export Drafts. The new Medidata home page is not yet supported by TrialGrid. Support for the new Medidata home page will be added in a future TrialGrid release. |
3490 |
Bug |
55.2 |
Draft exports to Rave were failing with Chrome browser errors. This hotfix will update Chrome to the latest version. |
3420 |
Bug |
53 |
When exporting/importing drafts using an iMedidata login, it was sometimes necessary to enter the two factor code and then restart the login wizard. This has been corrected. |
3170 |
Feature |
46.5 |
The Draft Import/Export wizard has been updated to support the new iMedidata login page. |
3084 |
Feature |
45 |
When exporting/importing a draft from Rave using an iMedidata login with two factor authentication, a message will be displayed if the password is about to expire and must be changed. |
3104 |
Bug |
44.2 |
Exporting or importing Drafts using an iMedidata account using SMS authentication would sometimes fail. This has been fixed. |
3001 |
Bug |
44.2 |
As part of the fix for issue #3104, email and voice two factor authentication are now supported. |
3104 |
Bug |
44.1 |
When exporting or importing Drafts using an iMedidata account, iMedidata two factor authentication was not working. This has been fixed. |
3084 |
Feature |
43.2 |
When exporting/importing a draft from Rave using an iMedidata login with two factor authentication, a message will be displayed if the password is about to expire and must be changed. |
2992 |
Feature |
43 |
When posting a draft to Rave and publishing it via the export wizard, any warnings that appear in the More Info section of the Rave screen are now shown in the export task progress messages or in the export dialog if the export fails. |
2949 |
Feature |
42 |
When posting a draft to Rave, a new 'worker' will be created. This will avoid the task being killed if the general worker is re-started as part of daily routines. |
2946 |
Bug |
41.1 |
Deviation Classes containing a comma were causing an error loading a Core Configuration. This was corrected. |
2811 |
Feature |
40 |
Draft Upload/Import will not warn if a Derivation or Edit Check has no steps. |
2812 |
Feature |
40 |
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 |
40 |
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 |
40 |
Draft Upload/Import will fail with an error if an object which should have an ordinal does not have one. |
2814 |
Feature |
40 |
Draft Upload/Import will display the identifier of a row if there is a warning message about that row. |
2789 |
Bug |
39 |
When exporting a Draft, the order of Check Actions will be the order in which they were created, e.g. the same order as in Medidata Rave. |
2786 |
Bug |
39 |
When importing a Draft from Rave, the warning messages were not being grouped into summary rows. This has been corrected. |
2760 |
Feature |
37 |
When uploading or importing a Draft, warning messages if there are missing values in the ALS spreadsheet columns will be not be initially displayed if there are more than 5 warnings. A summary message will be displayed and the details can optionally be viewed. |
2748 |
Feature |
37 |
When uploading or importing a Draft, warning messages will be displayed if there are Fields with Analytes which do not exist in the Lab Configuration for the URL in TrialGrid. |
2738 |
Feature |
37 |
TrialGrid does not support logging into iMedidata using email for two-factor authentication, e.g. when importing or exporting drafts. A message will be displayed if the iMedidata account is configured to use email for two-factor authentication. Please consider changing your iMedidata account to use the Okta app or SMS. |
2709 |
Bug |
35 |
When downloading a Draft from TrialGrid the filename inside the zip archive had an extension of 'xlsx'. This has been changed to 'xls', so that the file will open in Excel. |
2707 |
Feature |
35 |
When downloading a Draft from TrialGrid the spreadsheet file will now be compressed in a zip archive. |
2693 |
Feature |
35 |
When uploading and importing Drafts and Version from Medidata Rave, TrialGrid will display warnings if the Draft contains Marking Groups, Review Groups, EDC Roles, Deviation Classes and Codes or Subject Statuses which do not exist in the Core Configuration in TrialGrid. There is a new configuration option for each URL in TrialGrid which will prevent missing Core Configuration settings from being loaded into TrialGrid. Contact support@trialgrid.com if you would like this to be configured for you. |
2686 |
Bug |
35 |
When saving or validating Custom Functions containing unicode characters the Custom Function validation would fail with an error. This has been corrected. |
2642 |
Bug |
34 |
Some users could not import Drafts using iMedidata logins. |
215 |
Feature |
34 |
Draft Downloads and Direct Draft Exports will display a list of object types which can be included in the download or export. |
1674 |
Feature |
34 |
Drafts and versions can be imported from Rave Global Libraries. |
2555 |
Feature |
34 |
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 |
34 |
Drafts can be exported to Rave Global Libraries. |
2581 |
Feature |
34 |
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. |
2600 |
Bug |
34 |
Derivations using the function 'Space' were not uploaded correctly. This has been fixed. |
2525 |
Bug |
34 |
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. |
2482 |
Feature |
33 |
Direct Draft Exports to Rave now have an option to Overwrite the latest CRF Version (Publish-in-Place) in Rave. |
2511 |
Feature |
33 |
There is a new 'wizard' to export and import Drafts to and from Rave, which will guide you through the login steps (direct to Rave or via iMedidata) and export/import steps. |
2515 |
Feature |
33 |
When exporting a Draft to Rave, TrialGrid will stop checking the export progress after 3 hours if Rave has not finished importing the Draft. This timeout setting is configurable, please contact TrialGrid support if you have a Draft which needs longer than 3 hours to upload into Rave. |
1215 |
Feature |
33 |
The Draft export/import wizard will display an error if your iMedidata password has expired. |
2464 |
Bug |
31 |
Direct Draft imports from Rave would fail if the Draft Name contained HTML tags. This has been corrected. |
2409 |
Bug |
30 |
When pushing a Draft to Rave via an iMedidata login, the connection to Rave would terminate after 30 minutes due to iMedidata timeout. This was corrected. |
2126 |
Bug |
21 |
When a user had access to both a Rave Global Library Volume and a Rave Project with the same name the Rave Direct Import process would try to import the Rave Global Library Volume version and would fail if it was read-only to that user. This was corrected. |
559 |
Feature |
16 |
When exporting an ALS file, custom TG_ tabs are placed at the end of the ALS file generated i.e. the last tabs in the spreadsheet. |
1351 |
Bug |
14 |
Rave 2019.1.0 changed the way publish in place is reported. This affected the "Publish in Place" functionality of direct-Rave exports (causing it to fail). This was corrected. |