Make the data workbench available on the user interface

The definition of a data workbench should take the context the data workbench is used for into account. There are four major use cases for defining a data workbench:

• The data workbench is available directly from the user profile menu to provide a main data entry capability for an object class.

  Configure the data workbench: You might want to limit the objects in the data workbench to the objects the user can edit.

  Do not use the Alfabet parameter @BASE.

  Add the data workbench to the user profile configuration: Click here for a description of the definition of a user profile menu.

• The data workbench is available in the root node of an explorer to provide editing capability for the root objects in the explorer.

  Configure the data workbench:If you define a data workbench for an explorer root node, the data workbench shall display all objects on the root level of the explorer. If the explorer displays a hierarchy of objects of the same object class, you can define the query of the data workbench to return only objects not having a parent object of the same class.

  A data workbench shall only display application groups not assigned to an application group:

  • SELECT REFSTR
  • FROM APPLICATIONGROUP
  • WHERE BELONGSTO IS NULL

  Add the data workbench to the explorer configuration: This information will be available soon.

• The data workbench is available in a class independent content area to provide information or editing capablities.

  Configure the data workbench: After having defined the data workbench and added it to the class based content area, you can open the Alfabet user interface as an administrative user and define a default layout for the data workbench to display the object class properties, indicators, or roles which are required for the use case the content area is defined for. For example you can add a data workbench to the content area of a business question and display the data that a user might want to change to either enhance the data source of the report to show better results or to edit the data that has been identified to be problematic in the context of the report.

  Do not use the Alfabet parameter @BASE.

  Add the data workbench to the class independent content area: Click here for a description how to add a data workbench to a content area.

• The data workbench is available in a class-based content area to edit objects subordinate to the current object.

  Configure the data workbench: The content in the data workbench must be related with the object the data workbench is displaying data for. Use the Alfabet parameter @BASE to refer to the current object the data workbench is opened for. There are different methods to define a data workbench for a class-based content area:

  • Add a data workbench returning the base object only and providing editability capabilities for a defined data range like roles or indicators. For example to edit the responsibilites for the object, a data workbench can be defined to return the base object only.

    The following query limits the content of the data workbench to the application the user is currently working with in the class-based content area:

    • SELECT REFSTR
    • FROM APPLICATION
    • WHERE APPLICATION.REFSTR = @BASE

    Set the Enable Class Operations attribute of the data workbench to False. Users should not be able to add new objects via this view.

    Add the data workbench to the class-based content area. Log in to the Alfabet user interface as administrative user and create a default data workbench layout that shows one column for each role type. All other data shall be hidden.

  • Add a data workbench returning objects of a sub-ordinate object class related to the base object. You can add a read only data workbench for informational purposes about any kind of related objects. Data workbenches with edit capability can only be added for object classes which have operations referring to the base object class as source object. In the Generic Operations sub-folder of the object class that should be visible in the data workbench, the operations for creating new objects must refer to the object class the class based content area is about:

     

    Define the query for the data workbench to refer to the base object with the Alfabet parameter @BASE

  • The following query limits the content of the data workbench to the local components assigned to the application the user is currently working with:

    • SELECT LOCALCOMPONENT.REFSTR
    • FROM LOCALCOMPONENT
    • WHERE WHERE LOCALCOMPONENT.OWNER = @BASE

    Set the Enable Class Operations attribute of the data workbench to True if users shall be able to add new objects to the view.

  Add the data workbench to the class based content area: Click here for a description of how to add a data workbench to a content area.