Standard Reporting Package
Description
LogicNets client installations include the Standard Reporting package, which provides reports that give access to basic user session information such as sessions over time, sessions by application (for when client installations use multiple packages), and usage (minutes) per user. It also provides on-screen and download access to the application logging records for more detailed review.
The Standard Reporting application is based on the LogicNets Reporting framework. This means you can expand the reports to include custom reports. If you have purchased the optional Chart Authoring module (Highcharts), the installation includes additional chart views of the session information.
For access to the Release 7.4 version of Standard Reporting see here. Additionally, LogicNets updated the Standard Reporting application package as part of Release 8.1, and the enhancements include the following:
- LogicNets decoupled the user's choices for filtering and the process of retrieving the data, which speeds data and report return.
- Date formatting now follows the system configuration localization settings for the account.
- For accounts that include Highcharts, enhanced chart labeling shows date range, package selection, and organization (if relevant).
- LogicNets included enhanced data storage and archiving possibilities:
- Changelog data pruning, which is described in System Settings - General.
- Changelog storage options, which are described in Moving changelog Data to Enterprise Database.
General Information
For the sections below, see the referenced numbers in the screenshot at the top of this page. LogicNets breaks the Standard Reporting screen into two sections: search filters on the left (1) and the chart on the right (6).
To interact with the Reporting application, do the following:
- Make one or more selections in the search filters on the left side of the screen, choosing the report, package, organization, and date filters.
- Click Update (5). The system updates the chart on the right based on the selected filters.
Note: When the system starts the application, it inspects source data is inspected for use of organization, user role, user specialty, and reports/filters and removes these parameters when the system does not find that data.
Filters
See 1, 2, 3, and 4 above. The reporting package comes with a set of predefined filters for selecting a subset of reporting data, including the following:
- Report type. See below for report type descriptions.
- Date range filter
- Package filter. This allows you report by application, which can be useful in implementations with multiple "protocols" mapped in LogicNets, as you could review usage stats for each one individually or overall.
- Organization filter. This allows you to filter by organization if it is included in you logging.
Update Button
See 5 above. This button is 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 above. The chart area displays the relevant information from the filters provided. If the filters retrieve no data, the system displays the chart or table in the frame but it will not contain records.
Chart Scope
See 7 above. The system displays below the chart meta data associated with the chart, including the package, organization (when relevant), and installation.
Output Formats (see 8)
See 8 above. LogicNets displays reports on the screen, but you can download the tables. With the Chart Authoring module, you can view reports as graphics and export them 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
- Session Logs
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 filters are only available if your applications add this meta data to the logging during runtime. To include this information in the logging files, use the Add Answer to Log part in your model. For automatic data inclusion note the logging keys below. You can also customize the tables, views, and fields; see Advanced Business Reporting below.- You can log role as application.userRole.
- You can log specialty as application.userSpecialty.
- You can log organization as application.http_headers.accountId.
Data Scope, Archive, and Security
The following features are available as part of Release 8.1+ to improve data security, and archiving and to optimize data analytics performance.
- Set up an automated process to periodically copy data to an alternate database outside of the LogicNets installation.
- Define the data removal timeframe and automatically remove records no longer required for current reporting. You can define this to keep a rolling 12, 18, or 24 months of data, for instance.
By default, the Reporting package recaps application logs for the environment on which it is installed. If your solution involves multiple installations that require aggregating logging data, see Moving changelog Data to Enterprise Database.
Over time, the underlying data table and views contain an increasing amount of data. To ensure the system runs smoothly over multiple years of logging, see Changelog Data Pruning information in System Settings - General.
Advanced Business Reporting
Instead of the LogicNets Standard Reporting, some clients have used the LogicNets Assessment Framework with underlying business tables to create detailed reports. Since the Assessment Framework executes custom modeled logic it 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 for building your reporting suite.