Data Objects are the tables, views, methods, stored procedures, functions and custom SQL made accessible from the Data Sources for reports. This article applies to the Admin Console > Data > Objects settings.

Endpoints for the manipulation of Data Objects (also known as "Entities") in the REST API.

Data Sources establish the connection between Exago and a database or a web service. Although typically only one database is used, Exago can join data from different sources into a single report.

To use the .NET API, the host application must include a reference to these assemblies in its project

There are several properties of the Scheduler Service that must be configured on a per-service level.

User logins must be handled by a security layer in the embedding host application. After a user logs in, the host application should pass identification parameters to the Exago API, which can be used to set permissions on content and data objects within Exago.

Administrators may create additional custom functions using high level coding languages which will be accessible to end-users of the Report Designer.

When updating Exago, consult this guide for potential breaking changes.

Reports can be emailed or scheduled for recurring automated delivery to an email address. The Scheduler Settings are used to configure these services.

This article contains a list of examples for using the .NET API's various features.

This article serves as a glossary of error messages that may be displayed during the configuration or use of Exago BI. A list of potential causes and remedies is also included.

A reference guide that lists the most important enumerated types and lists of constants that are used throughout the API.

This reference guide describes the structure of the base configuration file (typically WebReports.xml), for all nodes outside of the node. Use this guide if you build or edit your config XML directly, without using the Admin Console.