Using the Default Widgets

The Platform offers several components out of the box, as listed in Section Understanding Widgets.

As described in Section Understanding the Management Views, a configurable widget can be a part of a:

  • Custom View, in which case it will be the only widget visible on the page, or placed on a

  • Custom Dashboard, with other widgets, where they can be resized and moved.

Widgets reflect real time data from the current scenario, which can be filtered depending on the visualization purpose. For more details, please refer to Section Understanding Widget Context.

Some of them allow comparing data between scenarios. For more details, please refer to Section Understanding Scenario Comparison.

For each created widget, a configurator allows indicating the entities and attributes to display. Users can also indicate nested entities, i.e. entities used as attributes in other entities, which are tagged with an icon in the configurator. A preset configuration can also be applied to some widgets using custom controllers. For more details, please refer to Chapter Customizing the Default Widgets.

To quickly display the capabilities of the application, the Sample Widget, Sample Map Widget and Sample Parameter Widget can be created without further configuration.

Finally, users can also implement their own custom widgets. For more details, please refer to Section Creating Custom Widgets.

Note:

Note that "internal entities", not defined in the data model, are generated by the application. For more details, please refer to Chapter Generating the Application Structure.

  • GeneSchemaIssue is used by the system to store issues detected by the schema checkers according to the model definition in the JDL while GeneIssue can be used by projects to store issues associated to a scenario according to project specific logic. For more details, please refer to Section Understanding the Data Service Checkers.

  • GeneParameter can be used to store in each scenario project specific parameters in order to manipulate for further customization. For more details, please refer to Chapter Understanding the Data Object Model (DOM).

  • In the Data Explorer widget, internal entities are hidden by default and, when displayed, they may contain rows referring to other scenarios than the one currently selected. In this case, they cannot be edited until said scenario is selected. For more details, please refer to Section Using the Data Explorer Widget.