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.
Duration in seconds of all operator time spent on this assignment. For pyHistoryType "F" only.
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.
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.
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.