Unlike system log files, that store information about system events, object modifications, and login counts for basic security and operational auditing, presentation usage tracking captures navigation workflows for usage analytics. It provides information about, for example, which views, cockpits, or reports were opened, in what sequence, and how long rendering took. The data is written directly to the ALFA_PRES_USAGE_TRACKING database table.
Data privacy and security
By default, the tracking data is not exposed to general end-users.
In the preconfigured Alfabet IT Transformation Server solution, usage tracking is used to provide each user information about which objects the user recently accessed in the Recent Assets functionality.
Raw data is only available to system administrators with direct database access. In addition, customers can provide defined users access to the data via configured reports in customer configured administrative user profiles. The information from activity tracking can help to improve the solution configuration and to identify performance issues.
Data protection rule compliance
You can any time deactivate presentation usage tracking completely or run it in anonymized mode. In anonymized mode, the user ID is not tracked and the corresponding data is left blank. Navigation and performance data, like the rendering time, are still logged anonymously.
The standard Recent Objects menu item added to new user profiles as well as the Recent Assets view in the preconfigured Alfabet IT Transformation Server solution require activated presentation usage tracking with user ID tracking to provide data.
Local labot laws, privacy regulations like GDPR, and internal workers council agreements vary across regions and organizations. You should review the data scope and functionality of presentation usage tracking with your data protection officer to ensure alignment with legal requirements and internal privacy policies.