In this lab, Nick explains how we can use HTML and Action Events to take interactivity on report output to the next level.

Certain items in the Report Designers can trigger Action Events to take certain actions outside of the default ExagoBI behavior.

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.

Sessions are the means by which REST persists changes through multiple API calls. A REST session allows for you to easily encapsulate a group of user-specific changes.

The Report Designer is the main editor for Advanced and CrossTab Reports. A full suite of reporting and design tools with a spreadsheet-like interface is available.

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

Client Integration Manager Nick Cortina demonstrates how to download the code sample, write a custom Storage Management implementation and how to build a "Favorites" folder in to the Report Tree using the new Storage Management enhancement in v2020.1 of our product.

A list of supported operating systems, server software, .NET and mono versions and web browsers.

A video demonstration of making an Action Event to launch a custom context aware dialog when attached to a cell in a report

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

The Settings endpoint allows access to many for the current configuration and session.

The Design Grid is main interaction point of the Advanced Report Designer. Use the Design Grid to define the layout of the report by adding, altering and deleting rows, columns, and sections to it; and to define the content of the report by entering data fields, text, labels, formulas, images, charts, CrossTabs and maps to it.

The Feature/UI settings allow administrators to hide various features in the user interface.

When building configuration files without the Admin Console, or to change settings in the API, use this reference to map Admin Console General settings to the relevant config file node or API key.