Problem:
With the v2.1 version of Signals Clinical (SC), the screen does not display any Data Connections (of any types; FTP or Rave) until at least one Study exists in the system, even when Data Connections actually exist in the system's database. This defect can lead to several scenarios. The Revvity Signals R&D Team intends to resolve this defect in a future release.
Details:
The Administrator creates a new Rave Data Connection, per instructions in the Quick Start Guide. It successfully gets created in the database; however, due to the above-noted defect, the Administrator does not see it on-screen. When the Administrator user does not see their new connection, they assume it failed, and then they try creating it again, with the same name. At this point they get a fairly unhelpful popup message in red: "Failed to create connection". The Revvity Signals R&D Team intends to improve this error handling and diagnose-ability in a future release, so that when errors do occur, then on-screen messages will indicate possible root causes to fix.
Note that with Signals Clinical, the integration to Medidata Rave (Rave Data Connection) is a different use case than with the classic Clinical product. The Signals Clinical product does not replace the Rave Connector in Spotfire, but it is a separate use case. The Line Listing Review (LLR) feature with Signals Clinical does not use a Spotfire-based Rave data connection; rather it resides within Signals Clinical and uses the Rave product's Biostats Adapter. The Connection for Medidata Rave Spotfire add-in uses the ODM Adapter instead.
Note that when creating a new Data Connection (of any type) the user interface (UI) requires that the user click a Test Connection button, which then enables the Save button (if the test passes). Also with this same version (v2.1), further modifying and testing the new connection in the same UI session sometimes fails. The Revvity Signals R&D Team intends to improve this error handling and diagnose-ability in a future release.
Solution:
For now, with v2.1 version of Signals Clinical (SC), the best approach is to create at least one study in your system, before creating any Data Connections.