Tracking View Usage Through Statistics

Starting from Aptify Web release 6.1 and above, administrator have the ability to track the usage of all the views in the system. This functionality enables administrator to make decisions regarding unused views depending on the tracked usage patterns. Usage statistics are available on both ‘per view’ basis or can be analyzed based on a dataset.

Details Available in Usage Statistics:

• View ID
• View name
• Last run by user ID
• Last run by Username
• Last run-on date
• Dependent area (where the view was opened)
• Run count (number of times view was used on that area)
• View owner name
• View creation date

Whenever a user accesses a view from any control, such as forms, dashboards, other views, shared views, process flows, event handler, ServiceDatatObjectParameter, the above-mentioned details are populated in the ‘View Statistics’ table. The details in View Statistics table servers as a point of reference for administrators to assess which views can be discarded and which should be retained.

Views that cannot be tracked via view tracking as a result of view execution, are listed separately to inform administrators. Despite not being directly executed, these views are integral to the system's functionality and cannot be deleted. 

All the views that are used by the application internally are marked as ‘Is System View’ by the installer. Aptify setup process takes care of marking all such existing views as system views. Administrators are restricted from deleting views marked as system views to prevent accidental removal and avoid functionality disruption. This includes views utilized in process flows, event handlers, etc. 

The following new appSettings entry was introduced for the application config files with the 6.2 release.

Aptify.Services.Views.EnableCaptureViewStatistics

• Purpose: Aptify 6.1 introduced a dependency on a config file attribute EnableCaptureViewStatistics, as a part of the View Statistics feature implementation. This config file attribute is placed under the appsetting entries, however, is not automatically added to AptifyAsyncProcessor.exe.config or AptifyCreateProcessFlowRun.exe.config as part of the service pack installer. Due to this application server feature does not work correctly when this setting is not available in the application server config files. Hence, they need to be updated in the AptifyAsyncProcessor.exe.config and AptifyCreateProcessFlowRun.exe.config files.
  
  
• Prior Behavior: Without this attribute, the Application Server fails to process jobs.
  New Behavior: When this setting value is true, the application server successfully processes the jobs scheduled.
  
  
• Default Value: True
  
  
• Action Needed: This attribute is available by default in the application config files but not automatically added in AptifyAsyncProcessor.exe.config or AptifyCreateProcessFlowRun.exe.config for application server features. Hence, this will now be available with default value true.