Installing and working with use cases in Exchange
- Borja Moro Moreno
About use cases
Combinations of components designed to tackle specific situations, covering both data reception and usage.
They consist of a data injector (synthetic data) and a data receptor (a data handler available in Exchange, normally an Activeboard, an Application or an Alert pack). As with Content packs, all components inside a use case exist individually in Exchange, and are installed and accessible upon installation of the use case.
The injector and receptor in a use case also exist in Exchange as standalone items so launching the use case will install the receptor and launch the injector individually. Even though you can install them separately, it is much more convenient to install the use case.
Despite serving a particular purpose, this kind of content is very versatile in the sense that they can be designed for a variety of contexts.
Included content
Under the Included contents section of the Overview tab, you can see the injector and receptor the use case is composed of and access each of them by clicking on their names. If the receptor is already installed, it displays the Installed green sign.
Launch and stop
The button to install use cases is called Launch. After launching the use case, the receptor will display the Installed green sign and the injector will display the Running green sign while data is being injected (see Installing and working with synthetic data more info).
You can Stop use case using the button at the top right of its card or access the Manage installed content area. The data will stop being injected but the receptor will remain installed unless you manually uninstall it by accessing its separate content card.
Open and navigate
You can click the Open button to access the receptor in a new browser tab so that you can keep your current session while you work with it.
If the receptor is an Activeboard, you will open it and see the widgets displaying the injected data.
If the receptor is an alert, you will open the alert management area and see the alert definition, which you can use to access the data table with the injected data. For this type of cases where the receptor is an alert, the injected data must be continuous, otherwise there will not be data available for the alert to trigger.
Â