If presentation usage tracking is activated in the server alias of the Alfabet Web Application, information about all user activity will be written to the ALFA_PRES_USAGE_TRACKING class table of the Alfabet database. All time information is returned in database time, which means the time at the database server host location.

This table is not visible in Meta-Model tab of Alfabet Expand. Nevertheless, configured reports based on native SQL can be defined to read the data.

The ALFA_PRES_USAGE_TRACKING table has the following columns:

  • TRACK_ID: A unique ID for this tracking information.
  • PRESENTATION_TYPE: The type of view the user is working with. For example, DataWorkbench for a data workbench, BusinessFunction for a functionality, or Wizard for a wizard. If a user opens a content area, the content area is not added to the tracking data. Only the content items the user is working with are tracked.
  • PRESENTATION_NAME: The name of the view the user is working with.
  • ENTRYPOINT_TYPE: The entry point can have the following values:
  • ENTRYPOINT_NAME: For access via bookmarks, the name of the bookmark is stored. For access via an external link, the accessed view is stored. If the ENTRYPOINT_TYPE is MainMenu, this column is empty.
  • NAVIGATION_SOURCE_TRACKID: The navigation source track ID is identical for all objects that have been opened simultanously. If a user accesses an object cockpit, all configured reports that are embedded in the object cockpit and are therefore visible to the user will be tracked. The object cockpit and the configured reports will have the same navigation source track ID. If a user is accessing a view multiple times, the navigation track ID is different.
  • NAVIGATION_SOURCE_TYPE: The type of view the user was opening this view from. For example, ObjectCockpit for an object cockpit or BusinessFunction for a functionality.
  • NAVIGATION_SOURCE_NAME: The name of the view the user was opening this view from.
  • BASEOBJECT_ID: The REFSTR of the base object the user is currently working with.
  • BASEOBJECT_NAME: The name of the base object the user is currently working with.
  • BASEOBJECT_CLASS: The name of object class of the base object the user is currently working with.
  • SESSIONS_ID: The session ID of the user session. If the user logs out and logs in again, the session ID will change. The session ID does not inform about the user that logged in.
  • SUBSESSION_ID: The sub-session ID of the user session. A new sub-session ID is provided if a view is opened in a new tab such as when opening a diagram in the Alfabet Diagram Designer.
  • USER_ID: If the Track User ID checkbox in the server settings of the Alfabet Web Application is set, the REFSTR of the user accessing the view will be tracked. Otherwise this column is empty.
  • USER_PROFILE: The name of the user profile the user is logged in with.
  • START_TIME: The time when the user accesses the view.
  • END_TIME: The time when the user leaves the view.
  • PREPARE_TIME: This column stores the time when data preparation is finished and rendering of the view is started.
  • PREPARE_DURATION: This column returns the time period between the time the user requested the view and the time data preparation has finished. This information can be used to identify performance problems with for example configured reports that are due to query execution. Customers can build configured reports vizualising view preparation performance according to their requirements.

The following columns are not used. They are reserved for future functionality on our product roadmap and are currently not populated or exposed anywhere in the application. They were implemented to store the following information , but never used because a valid use case was not identified and tracking was limited to information for current use cases only to enhance data privacy and security:

  • CONTEXT_INFO: This column was intended to store filter settings of views, but is currently not used because it is sensitive user data and no use case requiring the data was identified so far. Do not use this field to enter data manually or via batch import.
  • DETAILS: This field was intended to store customer comments about the presentation usage. It is not filled by the system and no feature was implemented around it. You can optionally use it to enter comments for further analysis.
  • POLICY_ID: This field was added for a proposed feature storing the policy ID of the ITPolicy class. The feature was not implemented because of a lack of demand. Do not use this field to enter data manually or via batch import.