Exago Logo
Search
Generic filters
Exact matches only
Administrators

Custom Context Sensitive Help

Exago is installed with context sensitive help. When a user clicks the Help icon a tab opens to display the appropriate section of the Exago User Guide. The content of this tab can be replaced with custom content managed by the host application. To implement Custom Context Sensitive Help: ...

Customizing Getting Started Content

The Getting Started tab is displayed as a user enters the Exago Web Application user interface. This tab can be customized by customizing HTML in a language definition file. This is done by modifying the language element <GettingStartedContent> in the ...

Displaying User Messages

Some Server Events are designed to display messages to the user based on a return value. For the other server events a user message can be displayed by throwing the WebReports.Api.Common.WrUserMessage(string, wrUSerMessageType) method. Warning This method can be used for all server events ...

Exago Theme Maker

Many components in Exago can be themed and styled. Exago provides a Theme Maker that can create component themes for any color palette. Matching themes can be created for ExpressViews (pre-v2021.1), Express Reports, Charts, GeoCharts, and CrossTabs. The Theme Maker is a JavaScript application ...

Getting Started with Application Themes

In general, we recommend all those intending to make styling changes to do so in a new Application Theme, not in the included Basic theme. Changes made to the Basic theme will be overwritten whenever Exago is updated. In this guide we'll walk through the process of creating a new Application ...

Excel: Grouping on Separate Worksheets

The default behavior when exporting an report to a Microsoft Excel workbook is that all data appears in a single worksheet (tab). If a report contains Group Sections, an Excel export can optionally create a new worksheet for each new instance of the outermost group. The name of each ...

HTML Tag Sanitization

By default, the Web Application and Scheduler Services scan and remove unsafe HTML tags from any user input. User input areas include report cells, report descriptions, filter fields, and so on. This is to protect the application from any potential script injection attacks. Removing unsafe ...

Multi-Language Support

Note The language elements discussed in this article do not include those created by users or administrators such as reports, folders, express report/crosstab themes or Data Field names. To modify Data Field names please see Column Metadata. To modify theme names please see Express Report ...

Remote Execution

Report execution can be balanced across servers to improve performance. As one execution is being processed subsequent report execution calls will be sent to different servers. For each new job, Exago will prioritize the server with the lowest load (according to CPU and memory load) and ratio of running jobs to max jobs allowed.

Report and Folder Storage/Management

This document covers several versions of the application. Use the Viewing content for dropdown to see only the content relevant to a specific application version. Important All legacy content storage mechanisms and the contents of this article were deperecated in Exago v2020.1+. For more ...

Config File XML & API Setting Reference (General Nodes)

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.

Config File XML Reference (All Nodes but General)

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.

Configuring Remote Report Execution Host for Azure App Service Deployments

When Exago is deployed as an Azure App Service, some additional configuration is necessary. At a high level, these configuration steps are: The Exago Scheduler Service must be installed and properly configured on an Azure Virtual Machine. Exago v2019.1.5+ must be installed for both the ...

Considerations When Sizing an Exago System

A quad-core VM with 32GB RAM on a gigabit network running Windows 10 or Linux should support dozens of simultaneous users running average-sized reports. From this most generic specification, there are a number of considerations that should be reviewed in order to strategically expand hardware ...

Storage Management: Custom Implementation

  Recommended Reading The following articles provide background on Exago's Storage Management system. It is highly recommended to review them before writing a custom implementation of Storage Management. Storage Management: Introduction Storage Management: Database ...

Database Aggregation

Exago can aggregate data in memory, but it will attempt to push calculations to the database whenever possible to improve performance. This feature is referred to as Database Aggregation. Aggregating in memory can be under-performant for large sets of data for two reasons: The application ...

Storage Management: Database Schema

Exago's Storage Management implementation defines four tables: Content, Party Type, Content Access and StorageMeta.

Evaluating Exago – Linux

This article will serve as a home base for preparing your environment for an evaluation of Exago BI on a Linux server.

Evaluating Exago – Windows

Welcome to Exago! We're glad to have you here. This article will serve as a home base for preparing your environment for an evaluation of Exago BI. Exago's entire library of documentation is accessible through this Support Site. As the breadth of the product is wide, this article serves to ...

Exago Installation Manifest

When installing the Exago Web Application, the installer will create a new manifest file on your system called ‘ExagoMainfest.txt’. It is very important that this file is never deleted. The manifest file ensures that future installs of Exago do not wipe out the local files that you have ...