Product Info: Configuring the Report Repository

InetSoft's reporting software gives administrators the ability to configure the report repository in order to meet specific organizational needs. View the information below to learn more about the Style Intelligence solution.

The definitions of all Viewsheets are stored in the registry file named asset.dat. To add a Viewsheet to the Repository, use the Visual Composer to save the Viewsheet into a global scope. See Viewsheet for more details.

To modify setting for a particular Viewsheet, click the desired Viewsheet in the Repository tree. This opens the 'Viewsheet Definition' page, which consists of three tabs on the bottom of the page.

These are Viewsheet, Materialized View, and Security. The next sections provide additional details about the available settings.

#1 Ranking: Read how InetSoft was rated #1 for user adoption in G2's user survey-based index Read More

Click the Viewsheet tab at the bottom of the screen to access the Viewsheet definition page. The following options are available.


Field

Description

Name

The name under which the Viewsheet should be listed in the Repository. Certain characters (e.g., “/”) are not permitted in names.

Alias

The Viewsheet name displayed to the user in the Portal.

Description

A brief description to be displayed as a tooltip when the user hovers the mouse over the Viewsheet in the Portal or Visual Composer Repository trees.

Click the Materialized View tab at the bottom of the screen to access options related to materialization for the Viewsheet.

Click the Security tab at the bottom of the screen to manage Viewsheet permissions. By default, a Viewsheet is set to inherit security permissions from its parent, which is the folder it resides in. This default behavior can be modified and a Viewsheet may have its own security information setup, independent of its parent. Once set up, the security permissions for the Viewsheet override those of the Viewsheet's parent. Setting up security for a Viewsheet is very similar to setting up security for any other component.

why select InetSoft
“We evaluated many reporting vendors and were most impressed at the speed with which the proof of concept could be developed. We found InetSoft to be the best option to meet our business requirements and integrate with our own technology.”
- John White, Senior Director, Information Technology at Livingston International

What Assets Are Contained in InetSoft's Report Repository?

InetSoft's report repository contains various assets essential for report management, collaboration, and deployment within the reporting platform. While the specifics may vary based on the version and configuration of the software, here are the common assets you will find in InetSoft's report repository:

  1. Report Definitions: The core assets in the repository are the report definitions themselves. These definitions include metadata such as report name, description, parameters, data sources, and the layout of the report (e.g., tables, charts, graphs). Report definitions specify how data should be queried, aggregated, and displayed to users when the report is executed.

  2. Data Sources: InetSoft's report repository contains configurations for connecting to various data sources, including relational databases, OLAP cubes, web services, flat files, and more. These configurations typically include connection details, credentials, and other settings necessary for accessing and querying data for report generation.

  3. Query Definitions: Within the repository, there are saved query definitions or SQL queries used to retrieve data from underlying data sources. These queries can be reusable components that are incorporated into multiple reports or data models.

  4. Data Models: InetSoft's reporting platform supports the creation and management of data models or data sets that encapsulate the structure and relationships of underlying data sources. Data models can simplify report development by abstracting the complexity of underlying data schemas and providing a unified view for reporting purposes.

  5. Report Templates: The repository contains predefined report templates or layout templates that define the visual styling, formatting, and branding of reports. Templates allow organizations to enforce consistency in report design and presentation across the enterprise.

  6. Parameters and Filters: InetSoft's report repository stores predefined parameters and filters used in reports to enable interactivity and customization. Parameters allow users to input values at runtime to control the data displayed in the report, while filters enable dynamic data filtering based on predefined criteria.

  7. Scheduled Jobs: The repository contains configurations for scheduled report generation jobs. Organizations can schedule reports to be executed at specific times or intervals and distribute the output to predefined recipients via email, file servers, or other channels.

  8. Security Policies: InetSoft's report repository includes security policies and access control settings governing who can access, view, modify, or execute reports and other assets within the platform. Role-based access control (RBAC) mechanisms ensure that sensitive data and reports are protected from unauthorized access.

  9. Audit Logs and History: Some versions of InetSoft's reporting platform store audit logs and version history for reports and other assets. Audit logs track user activities such as report execution, modification, or deletion, providing accountability and traceability for administrative purposes.

  10. Custom Extensions and Scripts: Depending on the platform's extensibility features, the repository contains custom extensions, scripts, or plugins developed by users or third-party developers to extend the functionality of the reporting platform, integrate with external systems, or automate tasks.

Previous: Report Parameters and Security