Users can compose complex reports and statistics based on process data through a simple point-and-click interface in the reporting component of @enterprise. No knowledge of SQL or any other query language is required: users can simply select the fields they want to display, determine sorting and aggregation attributes, and create their conditions using the @enterprise report definition interface. 

Reports can refer to any data in the workflow database, including forms and documents. Typical process data might include task processing time, idle time, process start time, process and task status, current and previous agents. The report definitions can be stored in the database for later execution. The reporting component is integrated into the @enterprise user access control  system, enabling administrators to define who has the right to execute or edit each report. 

More powerful than SQL 

The sophisticated query engine of the @enterprise reporting component enables the execution of reports which could not be defined in SQL alone. For example, users can compute process-timespans based on customized calendars that use an organisation’s definitions of holidays, weekends, or working hours. The reporting component also features data compression and enables a variety of data visualisations. 

Highly flexible 

Report definitions can contain parameters that are updated at execution according to the context (current date, user). Reports can be executed by a scheduler and the results can be exported regularly to other systems, for example to create up-to-date monthly performance reports. 

Multiple presentation formats 

In addition to the standard tabular output, reports can be shown graphically or exported to Excel. The open architecture of the @enterprise reporting component enables access to data via APIs for direct integration into applications.