Workflow system must support the complete cycle of business process automation.
Simple and Powerful
You can compose complex reports and statistics based on the process data via some simple clicks. You don‘t need SQL knowledge and there is no need to learn another query language to use the Reporting Component of @enterprise: Simply select the fields you want to display, determine sorting and aggregation attributes and finally create your conditions using the @enterprise report definition interface.
You can refer to all the data in your workflow database, including forms and documents. Typical process data are task processing time, idle time, process start time, process and task status, current an previous agents. The report definitions can be stored in the database for later execution. The Reporting Component is integrated into the @enterprise permission system, therefore you can define who may execute or edit which report.
More powerful than SQL
The sophisticated query engine of the @enterprise Reporting Component allows the execution of reports, which can not be defined in plain SQL alone. For example, the computation of time spans can rely on customized calendars defining holidays, weekends, or working hours. Data compression and different visualizations based on the raw data tops off the functionality of the Reporting Component.
Report definitions can contain parameters. At execution time the values for the parameters are specified or taken from the execution 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.
In addition to the tabular output the reports can be shown graphically or exported to MS Excel. Because of the open architecture of the @enterprise Reporting Component you can access the data via an API and therefore integrate it in your applications.