Managing the Application Data

The way data is managed by the application can be tailored to the project requirements in many ways before its deployment. For more details, please refer to Section Deploying the Application. These customizations are described in greater details in the other Parts of this documentation, Understanding, Customizing, and Securing.

The data that the application allows to manage is contained in "scenarios". A scenario file is a file that contains data for a set of:

  • tables called "entities", which contain

  • columns called "attributes" or "fields", which themselves contain

  • "values" pertaining only to the scenario file, whereas entities and attributes are predefined for the whole data model.

The relationships between entities are defined in the .jdl file(s) describing the data model. For more details, please refer to Chapter Defining the Data Model.

The scenarios are processed by the application through the Scenario Service. For more details, please refer to Chapter Understanding the Scenario Service.

Scenarios are associated to workspaces, over which users have permissions. For more details, please refer to Chapter Setting Permissions.

From the web client, users can access the workspaces and scenarios over which they have permissions using specific menus. For more details, please refer to Sections Understanding the Sidenav Workspace Selector and Understanding the Scenario Selector.

Users can also display more details on the workspaces and scenarios over which they have permissions using dedicated widgets. For more details, please refer to Sections Using the Workspace List Widget and Using the Scenario List Widget.

Note:

Scenario links can be created from the Scenario list widget using the option Create link.

  • Creating a scenario link to a scenario adds said scenario to a workspace accessible to users that cannot access the current Workspace.

  • Editing a scenario in a workspace also impacts its corresponding scenario links, even when they are in other workspaces.

  • Deleting a scenario link does not delete the linked scenario. However, deleting a scenario does delete all related links.

  • In a composite data model application, when adding a scenario that references other scenarios, it is possible to select a scenario link or a normal scenario. Once the scenario is added, a permission rule is also created to make the referenced scenario accessible to everyone. This is required, in case it is moved into another workspace for instance, to prevent losing ACCESS to the new scenario which, itself, also requires ACCESS to the referenced scenario. For more details, please refer to Section Understanding Operations.

Finally, users can edit the content of a scenario either by: