To monitor business activity where a particular value exceeds a specific level, you can define "thresholds" to specify the target value. The pre-configured objects in the Thresholds project monitor the number of workflows or work items that exceed specified threshold values for idle time, processing time, and total processing time, and list the items that exceed each threshold in a separate report. In addition, an alert is automatically generated when items exceed the threshold.
To examine this project, import the Thresholds project into FileNet Application Workbench. See BAM example - Rejected orders with Amount greater than 5000 (threshold) for an end-to-end demonstration of setting up threshold objects.
NOTE If the resulting list of items exceeding the threshold is expected to be greater than a few hundred items, the system could experience response issues or ultimately an out-of-memory error since this list is completely maintained in memory.
The following table lists the Thresholds dashboard objects for work items and workflows.
Objects related to work items | Objects related to workflows | |
---|---|---|
Dashboards: | Active work items with threshold monitor | Active workflows with threshold monitoring |
Dashboard objects: | Number of work items with processing time exceeding |
Number of workflows with processing time exceeding Workflows with processing time exceeds threshold |
In FileNet Business Activity Monitor (BAM) , the following objects gather and assemble the business data for display in BAM dashboard objects:
The following table lists the Thresholds FileNet Application Workbench objects for work items and workflows.
Objects related to work items | Objects related to workflows | |
---|---|---|
Views and events:
|
Work Item Idle Time Threshold Detail View Work Item Idle Time Threshold Event |
Workflow Processing Time Threshold Detail View Workflow Processing Time Threshold Event |
Contexts and dimensions: See Contexts and dimensions for more information. |
Queue_Context/Queue_Dimension UserName_Context/UserName_Dimension Workflow_Context/Workflow_Dimension WorkflowDefinition_Context/WorkflowDefinition_Dimension |
|
Business activities | Work item processing time | Workflow processing time |
Scenarios | Processing time exceeds threshold | Processing time exceeds threshold |
Rules | Number of work items with idle time > 3 days exceeds threshold Number of work items with processing time > 3 days exceeds threshold Number of work items with total processing time > 3 days exceeds threshold |
Number of workflows with processing time exceeding |
Alerts | Idle time exceeding Total time exceeding Work items with processing time > 3 days exceeds threshold |
Workflow processing time exceeding (alert) |
Reportlets | List of work items with idle time exceeding 3 days List of work items with processing time exceeds threshold List of work items with total processing time exceeds threshold |
List of workflows with processing time exceeding |
The objects related to each set of threshold objects (idle time, processing time, and total processing time) are very similar. This section details the Work Item Total Processing Time Threshold Event. (Use FileNet Application Workbench to view the details of the other events.) This event allows you to monitor the number of active work items whose total processing time (actual processing time plus idle time) exceeds a specified threshold, in this case, three days (4,320 minutes). In addition, you can view a list of the specific work items that exceed the threshold.
The Work Item Total Processing Time Threshold Event uses the following query to retrieve information from the Process Analyzer F_DMWIP table, with additional reference information retrieved from the Process Analyzer D_DMWorkItem table.
select top 500 f.DMWorkItem_key,
w.WobNum,
1 as TotalTimeExceed
from F_DMWIP f, D_DMWorkItem w
where (WaitCurrentMinutes+ProcCurrentMinutes+IsInWaitStatus*MinutesSinceLastEvent+IsInProcStatus*MinutesSinceLastEvent) > 4320
and f.DMWorkItem_key=w.DMWorkItem_key
Notice that the query retrieves both WobNum (the unique identifier for a work item) and TotalTimeExceed. The Work Item Total Processing Time Threshold View uses TotalTimeExceed to determine whether a threshold has been exceeded. The Work Item Total Processing Time Threshold Detail View uses WobNum when displaying the list of the specific work items that exceed the threshold. Only the top 500 work items exceeding the threshold are returned.
The Workflow Processing Time Threshold Event allows you to monitor the number of active workflows whose total processing time (actual processing time plus idle time) exceeds a specified threshold, in this case, three days (4,320 minutes). In addition, you can view a list of the specific workflows that exceed the threshold.
The Workflow Processing Time Threshold Event uses the following query to retrieve information from the Process Analyzer F_DMWorkflowWIP table, with additional reference information retrieved from the Process Analyzer D_DMWorkflow table.
select top 500 f.Workflow_key,
w.WobNum,
1 as ProcTimeExceed
from F_DMWorkflowWIP f, D_DMWorkflow w
where MinutesSinceCreation > 4320
and f.Workflow_key = w.Workflow_key
As above, the query retrieves both WobNum and ProcTimeExceed. The Workflow Processing Time Threshold View uses ProcTimeExceed to determine whether a threshold has been exceeded. The Workflow Processing Time Threshold Detail View uses WobNum when displaying the list of the specific workflows that exceed the threshold. Only the top 500 workflows exceeding the threshold are returned.