Aging and Exceptions

The Aging and Exceptions dashboard displays information about the age of the requests that are currently open as well as the request exceptions (such as the number of requests escalated, pushed back, and blocked) for those requests.

This information provides a means to focus on overall workflow velocity with a visual representation of the age distribution of open requests as well as exceptions that have occurred so far. If exceptions are happening unexpectedly often and delaying request completion, action may be taken to reduce those exception types and speed the process.

For details on the actions that you can take in the dashboard panels, see Working with Dashboard Panels. Exceptions to these actions are described in the sections for each dashboard panel, below.

Open Requests by Age and Status

The Open Requests by Age and Status dashboard shows a breakdown of the ages of open requests as well as their current statuses.

The data elements in this chart cannot be drilled across or applied to the current filter. You can use the Actions menu to view and download the request activity in the visualization. See Working with Dashboard Panels.

Request Exceptions by (Application or View)

The Request Exceptions by (Application or View) dashboard shows the open requests that have had exceptions, grouped by application, dimension (if one application is selected in your filter), view, or viewpoint (if one view is selected in your filter).

The request exceptions that are displayed include the number of requests that were escalated, recalled, pushed back, future dated, or blocked at least once in their workflow. The Failed Auto-Submit column displays the number of requests that had subscriptions that were configured to be submitted automatically but that were prevented from doing so by validation issues.

Note:

The exception numbers in the chart do not indicate the number of requests that are currently blocked, or pushed back, etc. They just indicate that at some point during the request workflow, an exception was encountered.

Also, a single request could have encountered more than one exception type during its workflow. For example, a request might have been escalated and then recalled. So the number of exceptions listed in the chart may not always add up to the total number of open requests in the first column.

For each element in the chart, you can drill down to view the request activity, drill across to view the requests in another visualization, or apply the specifics of that element to the page filter. You can also use the Actions menu to view and download the request activity in the visualization. See Working with Dashboard Panels.