Standard Reporting Package

  • updated 2 wk ago


The Standard Reporting package is included in client installations to give access to basic user session information such as sessions over time, sessions by application (for when client installations use multiple packages), usage (minutes) per user, etc. It also provides on screen and download access to the application logging records for more detailed review as necessary.

When the installation includes the optional Chart Authoring module (Highcharts), then additional chart views of the session information are available.

This application is based on the LogicNets Reporting framework, and can therefore be expanded on to include a custom set of reports in addition to those provided as a courtesy.

This package has been updated for Release 8.1 on. For access to the Release 7.4 version of Standard Reporting see here. The additional enhancements in Release 8.1 include:

  • decoupling the user's choices for filtering and the process of fetching the data, which leads to faster data retrieval 
  • date formatting that follows the system configuration localization settings for the account
  • enhanced labelling on the charts (for accounts that include the Highcharts license) to show date range, package selection and organization (if relevant)
  • enhanced data storage and archiving possibilities:

General Notes

(reference numbers in graphic above)

The screen is broken out into two sections: the search filters on the left (1) and the chart on the right (6). 

To interact with the Reporting module you should:

  • Make one or more selections in the search filters on the left, to choose the report, package, organization (where relevant) and date filters
  • Click the UPDATE button (5) to update the chart on the right, based on filters selected.

During the application start up, the source data is inspected for use of organization, user role, user specialty, and reports/filters including these parameters are removed when no data is found.

Filters (see 1, 2, 3, 4)

This package comes with a set of predefined filters for selecting a subset of reporting data, as follows:

  • Report type (see below for descriptions)
  • Date range filter
  • Package filter, which allows you to drill down to reporting by application. This can be useful in implementations where there are multiple "protocols" mapped in LogicNets, as you could review usage stats for each one individually or overall
  • Organization filter (where organization is included in the logging) - not shown

Update Button (see 5)

This button will become active when there is a change in any of the filters. You may change one or more filters prior to updating the chart. This mechanism is in place for performance reasons, in case of large installations that may take several seconds to retrieve the relevant data.

Chart Area (see 6)

The chart area will show the relevant information from the filters provided. (Note that if the filters retrieve no data, the chart or table will show in frame, but will not contain any bars and/or records).

Chart Scope (see 7)

Below the chart, you will find meta data associated with the chart, including the package, organization (when relevant) and installation. This information is included in chart images (for when pasted into reports).

Output Formats (see 8)

Reports are generated on screen, and tables are downloadable.

With the Chart Authoring module, reports can be viewed as graphics, and exported as PDF, image files or CSV format by clicking on the "hamburger" icon in the top right of the chart.


Report Types

Always Available

  • Session Overview table

  • Session Logs table

Available with Chart Authoring Module

  • Sessions per Day, per Hour, per Month, per Package, per User

  • Total and Average Usage per User (minutes)

  • Users per package, per role, per specialty

    Logging for Role, Specialty, Organization
    Note that per role and per specialty reports and organization filter are only available if this meta data is added to the logging during runtime. In order to include this information in the logging files, use the Add Answer to Log part in your model. For automatic inclusion note the logging keys below. Otherwise, the tables, views and fields can be customized per use  - see Advanced Business Reporting below.
    • role can be logged as application.userRole
    • specialty can be logged as application.userSpecialty
    • organization can be logged as application.http_headers.accountId

Data Scope, Archive & Security

The following features are available as part of Release 8.1 on to improve data security, archiving and keep data analytics performance optimal. 

  1. set up an automated process to periodically copy over the data to an alternate database outside of the LogicNets installation.
  2. define the data removal timeframe and automatically clear out records no longer required for current reporting.
    You can define this to keep a rolling 12, 18 or 24 months of data, for instance

The Reporting package will recap application logs for the environment it is installed on, by default.  In the event that your solution involves multiple installations that require aggregation of logging data, feature 1 below will be useful. See Moving changelog Data to Enterprise Database.

Over time, the underlying data table and views contain an increasing amount of data. To insure the system runs smoothly over multiple years of logging, feature 2 is useful. See Changelog Data Pruning (described as part of the System Settings - General article).

Advanced Business Reporting 

Note that some clients have utilized the LogicNets Assessment framework with underlying business tables instead, as an alternative to this framework. The Assessment framework executes custom modelled logic, and is suitable for detailed business reporting where a wide range of filters might be required.  Speak to your LogicNets Project Manager about the best approach to building your reporting suite.

Reply Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
Like Follow
  • 1 mth agoLast active
  • 17Views
  • 2 Following