|
This topic describes the traditional WorkManager portal introduced in V5.1. As a best practice in new applications, use a portal based on the composite Manager portal (introduced in V5.5), rather than the traditional WorkManager portal.
Reports in the Analyze Performance group of the Monitor Activity workspace cover resolved work objects and selected flow rules. Reports cover work objects processed by the currently selected application
From the WorkUser portal, click the Monitor Activity
bar to enter the Monitor Activity workspace. Locate the
Analyze Performance area. Click the Browse Category
button (
) to list the reports in
this category.
Select a link and review the status line of the browser window to learn the name of the associated summary view or list view report.
Select a flow name (in
the lower left corner of this space and click the View Flow icon
(
) to
see the flow diagram with overlays at each assignment that has an
associated service level rule PROJ- 583 heat maps The overlay
shows the number of assignments in the workbasket or worklist that
are:
These reports are based on summary view rules.
Link |
Description |
|
Action Analysis History-Work-. |
Presents a tabular report identifying the percentage of time, for each assignment, that users selected each connector flow action. You can compare these actual results with the expected percentages (known as likelihoods) presented on the flow diagram itself. This report may help identify which flow actions take the longest to complete, and which are used more often or less often, than expected. Detail rows show the average duration and counts. |
| Action Performance
History-Work-. ActionAnalysisby FlowTaskPerson |
Drill down summary by flow listing the count, processing time, idle time, and duration. |
Action Processing Time
History-Work-. ActionPerformanceTime |
Reports on the average time, in hours, for a flow action to be completed. KARAF 5/2006 BUG-193 5.2SP1 |
| Performance Detail
History-Work-. PerformanceDetail |
Presents a summary report of number of tasks, average time tasks spend in processing, and idle time. Data are grouped by flow name, assignment, action, and the performer.KARAF 5/2006 A special activity computes idle time as NATAA 9/27/06 the average of this difference: (pxAssignmentElapsedTime - pyPerformActionTime) |
|
Task Duration History-Work-. |
Presents a pie chart and summary statistics for completed assignments, by selected connector flow action. Identifies the flow actions that require users the most time to complete. Columns identify the total time (in hours, minutes, and seconds) and count for each connector flow action. Click a row to see the supporting details. |
| Task Performance
History-Work-.TaskPerformance |
Presents a bar chart and summary counts of how much time — in hours — tasks are in processing and in idle mode as well the total time that a task takes to complete. KARAF 5/2006 |
|
Timeliness by Task |
Presents a bar chart and summary counts of completed assignments in the selected flow or flow, by selected connector flow action. Columns identify how many were completed within the goal time associated with the assignment, beyond the goal by within the deadline time, past deadline, and totals. Click a row to see supporting detail, including the task duration in seconds. |
These reports may fail or may operate
with poor performance if the system saves instances of the work
history classes in your system in a table that does not have
appropriate columns exposed. Use the table
pr_history_work (or another table with similar exposed
columns) for work object history, not the pr_history or
pr_other table. To confirm correct mapping of work
history:
|
deadline, goal, history type, likelihood |
|
WorkManager portal — Working in the Monitor Activity workspace |
|
Atlas — Standard properties in the History-Work- class |
WorkManager portal — Monitor Activity
workspace
Basics
Portals in applications