A video demonstration of the use cases for the Scheduler Service beyond scheduling and emailing.

Exago's Scheduler Service is used to regularly execute and deliver reports in an automated fashion. It can also be used to turn a machine into a "remote execution" engine to add additional execution resources to Exago. In Step 3 of the Getting Started Guide, we review installing and configuring this service.

The toolbar contains the buttons and menus used to modify the report. Modifications can include aesthetic formatting, inserting formulas and images, linking reports, and much more. This article applies to versions released before v2021.1.

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

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.

The Scheduler Queue is a custom-built application library that sits between the Exago core application and any number of Scheduler Service instances and handles how schedule traffic is managed. The Scheduler Queue is completely optional, but configurations with multiple scheduler instances for which load balancing is a priority are ideally suited to making use of this feature.

A video demonstration of application themes, customizing the Getting Started page, translating the user interface and setting data object metadata amongst other customization topics.

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.

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.

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

Roles are created to specify how a user or group of users interfaces with Exago. Roles can restrict access to folders or data objects. Roles can also override the General Settings.