Assignment statistics

PRPC computes elapsed-time statistics when a user form based on a harness named Perform is presented. These statistics report on human use of application facilities and can be useful in understanding the operation. The system saves these statistics in instances of work item history, as properties in the History-Work- class.

Reports in the Analyze Performance area of the Monitor Activity work space summarize these statistics.

Properties

The values of these properties are in whole seconds.

• pyPerformActionTime — Elapsed time that the Perform user form was presented to a user, when the user was processing the most recent (connector or local) flow action.
• pyPerformAssignmentTime — Elapsed time spent by the current user on one or more flow actions for this assignment.  The time is the sum of the time intervals from the initial presentation of a Perform user form until the form is closed or another form opens. For example, if this operator completes three local actions, and then completes a connector action, the elapsed time is the sum of the four times. Time spent on this assignment by other users is not included.
• pyPerformTaskTime — Sum of pyPerformAssignmentTime values for all the users who worked on the assignment.

Work history instances are created only when users complete the form.

Example

An assignment in a workbasket allows users of the application to choose the Resolve flow action, which completes the assignment. Alternatively, users can choose any of three local flow actions. These do not complete the assignment.

• Save — to save data entered so far
• RequestInfo — to generate correspondence
• Transfer — to move the assignment to another operator's worklist

The following table shows the statistics maintained in history records as users Harry and Bobbie work on this assignment.

Action	ActionTime	AssignmentTime	TaskTime
1. Harry chooses Save, enters data and clicks  Submit  .	8	8	8
2. Harry chooses RequestInfo, enters data and clicks  Submit  .	24	32	32
3. Harry chooses Transfer, and transfers the assignment to Bobbie.	6	38	38
4. Bobbie chooses Save, enters data and clicks  Submit  .	4	4	42
5. Bobbies chooses RequestInfo, enters data and clicks  Submit  .	20	20	62
6. Bobbies chooses Resolve, completes the form and clicks  Submit  . Bobbie's first two submit operations fail because of invalid data. The third submit is accepted; three tries take 18 seconds total.	18	42	80

These timings are set to zero for assignments completed through bulk processing. This value indicates that the assignment was processed automatically.

	assignment, bulk processing, harness, history type, local flow action, perform
	Atlas — Standard properties in the Work-History- class Atlas — Standard Report Definitions — Work Analysis

Definitions