We would like to be able to report if a work item is assigned (Yes/No) within the active detail report or add as an option in searches.  This data element isn't tied to productivity but is only on the dimensions that are at a protected at user level.  ... View more

My client (on 23.x) having the following suggestion on the OA. It is suggest to add the function in OA so that the bank holidays defined in the Holiday table can be used: ... View more

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: 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. Inclusion of the User dimension in the Queue reporting object 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. 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. Inclusion of efficiency reporting metrics Key operational performance measures should be available directly within the reporting schema. ... View more

Work ownership for the BusinessArea – WorkType- Queue combination would be helpful, so this can be updated and also made available via Analytics ... View more

Easier and more intuitive reporting capability for individual productivity and performance monitoring. ... View more

We are currently storing a lot of detail around the emails ingested by Capture in the Chorus database (AWD061/62/63) but there is no current mechanism to display this information holistically within the Chorus Portal. This means that the data are currently only available by SQL query (the GetCapturedEmail operation oh the AWD Email Service returns info from those audit tables, but only for a single email at a time). The main use case here would be an indicator of "failed" emails so that remedial action could be taken. I think the view would just need to be a filterable, pageable tabular list of ingested emails. ... View more

An easy way to get data OUT of the tool. I.E. streaming or something of the sort so we can do reporting from a central source outside of AWD as an example ... View more

With the new version of Operational Analytics there is a button that will allow for the export of an page and all reports contained therein to a PDF file. This is functionality that our clients have wanted for a very long time. The downside is that the reports do not dynamically resize to fit the amount of data within the report. If there is a report that you need to scroll to see all of the records it would be exceedingly helpful if when exporting to PDF the report automatically expands to show the entire contents of the report instead of the current behavior which seems to be taking a screenshot of the page.  ... View more

User Administration: User Info – more info via Admin to show when an ID logs in and logs out. This would be particularly useful now that we’re all WFH. ... View more