Question
AIG
US
Last activity: 19 Apr 2016 11:06 EDT
Understanding History Table in Pega ?
1) What is the significance of the below columns in the History Table (pc_history_work)?
PXASSIGNMENTELAPSEDTIME,
PXTASKELAPSEDTIME,
PYPERFORMACTIONTIME,
PYPERFORMASSIGNMENTTIME,
PYPERFORMTASKTIME
2) What is the difference between the above columns?
I have currently looked into my POC environment, and the values are same for the above columns.
3) How are the values computed internally for the above columns?
Accepted Solution
Pegasystems Inc.
US
Not sure if you have checked the online help:
Quoted here:
Standard properties in the History-Work- class |
The standard properties in the History-Work- class support the work item history display from the History button (
).
This table identifies several of these, in alphabetical order, ignoring the first two characters of the name. Many properties are present only in work history records of specific types. Properties marked (
) are computed by standard rules. Do not set values for these properties in your application rules, except in unusual situations where you intend to override the default computation.
Not sure if you have checked the online help:
Quoted here:
Standard properties in the History-Work- class |
The standard properties in the History-Work- class support the work item history display from the History button ().
This table identifies several of these, in alphabetical order, ignoring the first two characters of the name. Many properties are present only in work history records of specific types. Properties marked () are computed by standard rules. Do not set values for these properties in your application rules, except in unusual situations where you intend to override the default computation.
Property |
Purpose |
More |
| pxAssignment ElapsedTime |
Duration in seconds of all operator time spent on this assignment. For pyHistoryType "F" only.
|
|
| pyHistoryType | A single letter indicating the event that caused this history instance to be created. For example, F indicates that a connector flow action was completed, and M indicates that a memo was added.
|
history type |
| pyPerformer | Operator ID or "system, for history instances created by an agent.
|
|
| pyPerformActionTime | Elapsed time in seconds that the Perform user form was presented when a user processed the most recent (connector or local) flow action. ForpyHistoryType F and L only.
|
Assignment statistics |
| pyPerformAssignmentTime | Elapsed time in seconds spent by the current user on one or more flow actions this assignment. Sum of one or more time intervals from the initial presentation of a Perform user form until it is closed or another appears. If this operator has completed three local actions and then finally completed a connector action, this is be the sum of four times. Time spent on this assignment by other users is not included. For pyHistoryType F only.
|
Assignment statistics |
| pyPerformTaskTime | Similar to pyPerformAssignmentTime but not reset upon reassign. Sum of pyPerformAssignmentTimevalues for all users who worked on the assignment, in seconds. For pyHistoryType "F" only.
|
Assignment statistics |
| pyWorkClass | Work type of the work item. In some applications, a work item's work type may change during processing (to another type within the same work pool.)
|
work type |
AIG
US
This process is going to be time consuming, and this would going to be my back-up plan. I am looking for insights from some one who has done this analysis before.
Accepted Solution
Pegasystems Inc.
US
Not sure if you have checked the online help:
Quoted here:
Standard properties in the History-Work- class |
The standard properties in the History-Work- class support the work item history display from the History button ().
This table identifies several of these, in alphabetical order, ignoring the first two characters of the name. Many properties are present only in work history records of specific types. Properties marked () are computed by standard rules. Do not set values for these properties in your application rules, except in unusual situations where you intend to override the default computation.
Not sure if you have checked the online help:
Quoted here:
Standard properties in the History-Work- class |
The standard properties in the History-Work- class support the work item history display from the History button ().
This table identifies several of these, in alphabetical order, ignoring the first two characters of the name. Many properties are present only in work history records of specific types. Properties marked () are computed by standard rules. Do not set values for these properties in your application rules, except in unusual situations where you intend to override the default computation.
Property |
Purpose |
More |
| pxAssignment ElapsedTime |
Duration in seconds of all operator time spent on this assignment. For pyHistoryType "F" only.
|
|
| pyHistoryType | A single letter indicating the event that caused this history instance to be created. For example, F indicates that a connector flow action was completed, and M indicates that a memo was added.
|
history type |
| pyPerformer | Operator ID or "system, for history instances created by an agent.
|
|
| pyPerformActionTime | Elapsed time in seconds that the Perform user form was presented when a user processed the most recent (connector or local) flow action. ForpyHistoryType F and L only.
|
Assignment statistics |
| pyPerformAssignmentTime | Elapsed time in seconds spent by the current user on one or more flow actions this assignment. Sum of one or more time intervals from the initial presentation of a Perform user form until it is closed or another appears. If this operator has completed three local actions and then finally completed a connector action, this is be the sum of four times. Time spent on this assignment by other users is not included. For pyHistoryType F only.
|
Assignment statistics |
| pyPerformTaskTime | Similar to pyPerformAssignmentTime but not reset upon reassign. Sum of pyPerformAssignmentTimevalues for all users who worked on the assignment, in seconds. For pyHistoryType "F" only.
|
Assignment statistics |
| pyWorkClass | Work type of the work item. In some applications, a work item's work type may change during processing (to another type within the same work pool.)
|
work type |
AIG
US
Yeah. I have checked the Help File. The verbage is confusing when you put multiple attributes into context.
I am looking for an explanation or an article which demonstrates a typical workflow along with the values for each of these attributes. It's something like below. The only part that's missing in the below explanation is on the entries in the History Table, i.e. whether there is one entry per transaction or one entry for all the transactions.
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
Action |
ActionTime |
AssignmentTime |
TaskTime |
|
8 |
8 |
8 |
|
24 |
32 |
32 |
Yeah. I have checked the Help File. The verbage is confusing when you put multiple attributes into context.
I am looking for an explanation or an article which demonstrates a typical workflow along with the values for each of these attributes. It's something like below. The only part that's missing in the below explanation is on the entries in the History Table, i.e. whether there is one entry per transaction or one entry for all the transactions.
https://community.pega.com/sites/default/files/help_v717/procomhelpmain.htm
Action |
ActionTime |
AssignmentTime |
TaskTime |
|
8 |
8 |
8 |
|
24 |
32 |
32 |
|
6 |
38 |
38 |
|
4 |
4 |
42 |
|
20 |
20 |
62 |
|
18 |
42 |
80 |
These timings are set to zero for assignments completed through bulk processing. This value indicates that the assignment was processed automatically.