Chorus Reporting Enhancements

[andrewparish]

As a Chorus report writer, I need to report on the events within a process and the time taken to complete each event. We also need to report on the Line‑of‑Business (LOB) fields for each event, enable filtering of SYSTEM events where required, and support reporting on both in‑flight and completed work.

It is currently difficult to meet these and other reporting requirements using the existing Chorus dimensional reporting schema. We would therefore like to request the following enhancements:

1. Access to LOB history across all reporting objects
   At present, the Work reporting object is the only object that holds LOB history (CURRENT = 0). We require access to LOB history in all relevant reporting objects.

2. Inclusion of the User dimension in the Queue reporting object

3. A reporting object to distinguish assigned vs. unassigned work
   We frequently need to report on work volumes by assignment status. Currently, the only workable solutions involve AppStudio or HOLD files, which is not efficient or scalable.

4. Availability of Workstep Names and Process Model information
   Information such as process names, versions, and workstep names should be included in the reporting layer. Their absence makes it extremely challenging to move beyond basic Queue/Status‑based reporting.

5. Inclusion of efficiency reporting metrics
   Key operational performance measures should be available directly within the reporting schema.