Exago keeps a text log of when certain tasks are performed. For example each time a page or report is loaded, each time an error occurs or when various phases of execution happen.

An Api object should be the first thing that is created to interact with the Exago .NET API.

There are a number of precautions that should be taken before running Exago in a production environment.

This article logs changes made in the REST Web Service API.

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

In order to decrease the amount of resources needed to handle the configuration information, especially in situations where a large number of complex database objects are present, the option to implement a static configuration has been introduced.

As a highly-configurable environment, Exago consists of many components. This article will describe these components, where they are located, why they need to be part of the implementation strategy, and how they should be propagated from system to system.

Microsoft Azure is a cloud infrastructure for hosting files, databases, virtual machines, and web applications. Exago supports various forms of integration with Azure.

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

Custom Filter Functions provide the ability to make functions that will dynamically calculate a value for a filter using high level code.