Running reports

Workforce Performance reports can be run on-demand, scheduled with predefined parameters, or displayed as burst reports using Launch Pads. Users can run simple reports with a few parameters on an ad-hoc basis because they require less performance overhead. However, in larger environments where the volume of report requests is greater and more complex, you should schedule reports to run during off-peak hours to avoid system performance bottlenecks.

Consider these points when deciding whether to schedule reports or execute the reports on-demand:

  • The number of variations of a single report required

    For example, you may need a weekly report sent to supervisors across 100 stores parameterized by teams. This report requires significant processing time and is best scheduled during off-peak hours. In addition, it would probably benefit from bursting, which enables the production of reports with user-specific content that is based on a common report definition.

  • The volume of data produced by a report

    Some reports require aggregated data from a large number of tables in the database. These reports usually require greater processing overhead and time. The less complex the report, the less data is required.

  • The use of real-time information versus historical information

    For example, you might want an Employee Overtime report from the past week only. This report should be scheduled.