Design views for the user interface

Different types of views are accessible in the Alfabet user interface:

• Data workbenches provide editing capabilities for objects of a specific object class. Objects are listed in a table and the user can directly edit the objects in the table. In addition, users can create own graphic visualizations about the data in the data workbench and add them to content areas.

  Users can access data workbenches either from the left-side navigation, from an explorer node, or from a content area which contains the data workbench as embedded view.

• Content areas provide a collection of content items in one or multiple content pages. Content items embed views, like data workbenches, cards, or configured reports. You can define class independent content areas which serve as an entry page to the Alfabet application or as a collection of data to analyse a specific context. You can also define class-based content areas for object classes. The class-based content area provides ReadWrite or ReadOnly access to data about an object. Users with edit permissions can edit data directly in the content items of the content area or via an editor or guided data view.

  Users can access class independent content areas from the left-side navigation and class-based content areas via navigation to an object, for example from a data workbench or configured report, or on click on an explorer node.

• Business Functions/Explorers provide either access to a view or an explorer. Standard business functions cannot be edited. In addition to standard business functions, you can create custom business functions listing objects in an explorer.

  Users can access business functions from the left-side navigation or from a content area which contains the business function as embedded view.

• Configured Reports provide either a tabular view or a graphic view based on a customer defined query. You can define own reports based on a number of templates.

  Users can access configured reports from the left-side navigation, or from a content area which contains the configured report as embedded view.

• Graphic Views are standard tabular or graphic views provided with the Alfabet meta-model. Graphic views can provide the ability to edit data or to analyse data in reports. You cannot change graphic views.

  Users can access graphic views from the left-side navigation, from an explorer node, or from a content area which contains the configured report as embedded view.

• Cards display a number in a prominent way. Cards showing indicator values can be defined by administrative users for evaluation types and indicator types. Users working in a data workbench can create cards showing a number derived from the data in the data workbench and add this card to a content area.

  Users can view cards in a content area.

• Guided data views consist of a number of embedded views and a panel listing all embedded views. In the panel, users can see which data in which embedded view requires attention because data quality is not as expected. The number of data quality violations for each data quality severity level is listed beneath each view caption. The user can click the caption to scroll down to the respective embedded view.

  Users can access guided data views via a button in a content area or an editor.

• Editors open when a user creates or edits an object via button interaction. A standard editor consist of editable fields in one or multiple tabs. Standard editor tabs cannot be changed, but you can add a new tab to the standard editor to edit custom data. The concept of editors is still available in Alfabet, but will be deprecated in the future. Editing capabilities are provided by data workbenches, class-based content areas and guided data views.

  Users can access editors via buttons for editing or creating objects.

• Wizards guide the user through creating or editing of an object. A wizard consists of a number of editors and views which are accessible one after the other. Wizards are still available in Alfabet for backwards compatibility reasons. They should be substituted with guided data views.

  Users can access editors via buttons for editing or creating objects.