Reports¶

A report in AcuGIS Report Server is a published JasperReports definition (JRXML or compiled .jasper) plus catalog metadata: key, display name, type, datasource, thumbnail, folder placement, and access rules.

Reports are the primary unit of work for most users. You publish them from Report Designer (or the CLI/API), organize them in folders, grant access, supply parameters, and run them to PDF, Excel, HTML, and other formats.

What is a report?¶

Aspect	Description
Definition	JRXML / `.jasper` executed by the JasperReports engine on Report Server
Catalog key	Stable identifier used by the viewer and automation (for example `Invoice`)
Metadata	Name, type, datasource binding, thumbnail, access groups
Storage	Files under the server JRXML directory; metadata in the application database

How reports are organized¶

Reports live in the catalog, browsed from the portal at / and opened in the viewer at /reports/{key}.

You organize them with folders. Folder ACLs and report access groups together control who can see and run each report. See Permissions.

Publish and edit forms are available in the Reports hub in the web UI.

Report types¶

Type	Notes
Jasper report	Both packages
Map Report	Professional package with a valid license

Embedded Maps are map elements inside a standard report layout (rendered at fill time), not a separate report type. See Embedded Maps and Map Reports.

Execution¶

From the viewer, choose a format and supply parameters, then run the report. Output is generated by the Jasper engine and returned as a binary (PDF, spreadsheet, HTML, and so on).

Details: Report execution and Output formats.

Parameters¶

JRXML parameters become viewer inputs and automation arguments. Keep names stable for anyone who runs the report from the UI, CLI, or integrations.

Details: Parameters.

Permissions¶

Visibility combines:

Folder ACL (inherit or explicit)
Report access_groups set at publish/update
Your user and group memberships

API Tokens and browser sessions use the same ACL evaluation. Details: Permissions.

Scheduling¶

Scheduled delivery (email / jobs) is configured in the administration UI for operators who have rights to schedules and recipients. Scheduling is not the same as on-demand execution from the viewer.

For Developers¶

Implementation details live in the Developer Guide and Reference — not in this user-facing page.

Integration path	Go here
REST API	REST API overview · REST reference
CLI	CLI overview · Running reports
SDK	SDK overview