simpleType AveragesMeasureType

namespace | http://base.api.ec.n2.tibco.com
type | restriction of xs:string
properties |
base | xs:string
used by |
element | ProcessDurationMeasureEntry/type
facets |
Kind | Value | Annotation
enumeration | PROCESS_TOTAL |
documentation
Total number of processes started for this duration
enumeration | PROCESS_TOTAL_TIME |
enumeration | PROCESS_AVERAGE_TIME |
enumeration | WORKITEM_TOTAL |
enumeration | WORKITEM_ACTIVE_AVERAGE_TIME |
documentation
User Task Instance Active Duration (Average) All AMX BPM tasks will emit a READY and COMPLETE event. The time interval between the emission of these events will determine the Task Instance Active duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st offer / allocate (firstOfferTime) and workItem completion (completionTime) disregarding any intermediate states.
enumeration | WORKITEM_ACTIVE_TOTAL_TIME |
documentation
User Task Instance Active Duration (Total) All AMX BPM tasks will emit a READY and COMPLETE event. The time interval between the emission of these events will determine the Task Instance Active duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st offer / allocate (firstOfferTime) and workItem completion (completionTime) disregarding any intermediate states.
enumeration | WORKITEM_WAIT_TOTAL_TIME |
documentation
User Task Instance Wait Duration (Total) All AMX BPM tasks will emit a READY and OPEN event. The time interval between the emission of these events will determine the Task Instance Wait duration. The Process Duration will be calculated when the task's (first) OPEN audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Offer / Allocate (firstOfferTime)and 1st Open (firstOpenTime)
enumeration | WORKITEM_WAIT_AVERAGE_TIME |
documentation
User Task Instance Wait Duration (Average) All AMX BPM tasks will emit a READY and OPEN event. The time interval between the emission of these events will determine the Task Instance Wait duration. The Process Duration will be calculated when the task's (first) OPEN audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Offer / Allocate (firstOfferTime)and 1st Open (firstOpenTime)
enumeration | WORKITEM_ACTION_TOTAL_TIME |
documentation
User Task Instance Action Duration (Total) All AMX BPM tasks will emit an OPEN and COMPLETE event. The time interval between the emission of (the first OPEN of) these events will determine the Task Instance Action duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Open (firstOpenTime) and form submission (completionTime)
enumeration | WORKITEM_ACTION_AVERAGE_TIME |
documentation
User Task Instance Action Duration (Average) All AMX BPM tasks will emit an OPEN and COMPLETE event. The time interval between the emission of (the first OPEN of) these events will determine the Task Instance Action duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Open (firstOpenTime) and form submission (completionTime)
enumeration | WORKITEM_WORKINGTIME_TOTAL_TIME |
documentation
User Task Instance Working Time Duration (Total) All AMX BPM tasks will emit an OPEN and various user interaction end events, namely CLOSE, PEND, CANCEL and COMPLETE events. The User Task Instance Working Time Duration will be incremented by the time interval between each OPEN and work item end event pairing, each time one of these event pairings completes. Thus giving a total working time for a task instance, regardless of the number of times it is opened/closed and by how many different users. We interpret this as we need to calculate the cumulative time for between first and last (form submission) activities.
enumeration | WORKITEM_WORKINGTIME_AVERAGE_TIME |
documentation
User Task Instance Working Time Duration (Average) All AMX BPM tasks will emit an OPEN and various user interaction end events, namely CLOSE, PEND, CANCEL and COMPLETE events. The User Task Instance Working Time Duration will be incremented by the time interval between each OPEN and work item end event pairing, each time one of these event pairings completes. Thus giving a total working time for a task instance, regardless of the number of times it is opened/closed and by how many different users. We interpret this as we need to calculate the cumulative time for between first and last (form submission) activities.
annotation |
documentation
Enumerated value defining the type of an AverageMeasure. One of the following: - PROCESS_TOTAL: Total number of instances of this process template started during this ProcessDurationMeasurePeriod. - PROCESS_TOTAL_TIME: Total time that instances of this process template were active during this ProcessDurationMeasurePeriod. - PROCESS_AVERAGE_TIME: Average time that an instance of this process template was active during this ProcessDurationMeasurePeriod. - WORKITEM_TOTAL: Total number of work items generated by this process template that were active during this ProcessDurationMeasurePeriod. - WORKITEM_ACTIVE_AVERAGE_TIME: Average time that a work item generated by this process template was active during this ProcessDurationMeasurePeriod. A work item is defined as being active between the time of the event when it first entered the OFFERED state and the time of the event that it entered the COMPLETED state, disregarding any intermediate states. - WORKITEM_ACTIVE_TOTAL_TIME: Total time that work items generated by this process template were active during this ProcessDurationMeasurePeriod. A work item is defined as being active between the time of the event when it first entered the OFFERED state and the time of the event that it entered the COMPLETED state, disregarding any intermediate states. - WORKITEM_WAIT_TOTAL_TIME: Total time that work items generated by this process template were waiting during this ProcessDurationMeasurePeriod. A work item is defined as waiting between the time of the event when it first entered the OFFERED state and the time of the event when it first entered the OPENED state. - WORKITEM_WAIT_AVERAGE_TIME: Average time that a work item generated by this process template was waiting during this ProcessDurationMeasurePeriod. A work item is defined as waiting between the time of the event when it first entered the OFFERED state and the time of the event when it first entered the OPENED state. - WORKITEM_ACTION_TOTAL_TIME: Total time that work items generated by this process template were being actioned during this ProcessDurationMeasurePeriod. A work item is defined as being actioned between the time of the event when it first entered the OPENED state and the time of the event that it entered the COMPLETED state - that is, when the user submitted the form. - WORKITEM_ACTION_AVERAGE_TIME: Average time that a work item generated by this process template during this ProcessDurationMeasurePeriod. A work item is defined as being actioned between the time of the event when it first entered the OPENED state and the time of the event that it entered the COMPLETED state - that is, when the user submitted the form. - WORKITEM_WORKINGTIME_TOTAL_TIME: Total time that users spent processing work items generated by this process template during this ProcessDurationMeasurePeriod. A work item is defined as being worked on between the accumulated time between each event when it entered the OPENED state and the time of the paired event when it entered a PENDED, SUSPENDED, CANCELLED or COMPLETED state. - WORKITEM_WORKINGTIME_AVERAGE_TIME: Average time that a work item generated by this process template was worked on by users during this ProcessDurationMeasurePeriod. A work item is defined as being worked on between the accumulated time between each event when it entered the OPENED state and the time of the paired event when it entered a PENDED, SUSPENDED, CANCELLED or COMPLETED state.
source | <xs:simpleType name="AveragesMeasureType"> <xs:annotation> <xs:documentation>Enumerated value defining the type of an AverageMeasure. One of the following: - PROCESS_TOTAL: Total number of instances of this process template started during this ProcessDurationMeasurePeriod. - PROCESS_TOTAL_TIME: Total time that instances of this process template were active during this ProcessDurationMeasurePeriod. - PROCESS_AVERAGE_TIME: Average time that an instance of this process template was active during this ProcessDurationMeasurePeriod. - WORKITEM_TOTAL: Total number of work items generated by this process template that were active during this ProcessDurationMeasurePeriod. - WORKITEM_ACTIVE_AVERAGE_TIME: Average time that a work item generated by this process template was active during this ProcessDurationMeasurePeriod. A work item is defined as being active between the time of the event when it first entered the OFFERED state and the time of the event that it entered the COMPLETED state, disregarding any intermediate states. - WORKITEM_ACTIVE_TOTAL_TIME: Total time that work items generated by this process template were active during this ProcessDurationMeasurePeriod. A work item is defined as being active between the time of the event when it first entered the OFFERED state and the time of the event that it entered the COMPLETED state, disregarding any intermediate states. - WORKITEM_WAIT_TOTAL_TIME: Total time that work items generated by this process template were waiting during this ProcessDurationMeasurePeriod. A work item is defined as waiting between the time of the event when it first entered the OFFERED state and the time of the event when it first entered the OPENED state. - WORKITEM_WAIT_AVERAGE_TIME: Average time that a work item generated by this process template was waiting during this ProcessDurationMeasurePeriod. A work item is defined as waiting between the time of the event when it first entered the OFFERED state and the time of the event when it first entered the OPENED state. - WORKITEM_ACTION_TOTAL_TIME: Total time that work items generated by this process template were being actioned during this ProcessDurationMeasurePeriod. A work item is defined as being actioned between the time of the event when it first entered the OPENED state and the time of the event that it entered the COMPLETED state - that is, when the user submitted the form. - WORKITEM_ACTION_AVERAGE_TIME: Average time that a work item generated by this process template during this ProcessDurationMeasurePeriod. A work item is defined as being actioned between the time of the event when it first entered the OPENED state and the time of the event that it entered the COMPLETED state - that is, when the user submitted the form. - WORKITEM_WORKINGTIME_TOTAL_TIME: Total time that users spent processing work items generated by this process template during this ProcessDurationMeasurePeriod. A work item is defined as being worked on between the accumulated time between each event when it entered the OPENED state and the time of the paired event when it entered a PENDED, SUSPENDED, CANCELLED or COMPLETED state. - WORKITEM_WORKINGTIME_AVERAGE_TIME: Average time that a work item generated by this process template was worked on by users during this ProcessDurationMeasurePeriod. A work item is defined as being worked on between the accumulated time between each event when it entered the OPENED state and the time of the paired event when it entered a PENDED, SUSPENDED, CANCELLED or COMPLETED state. </xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:enumeration value="PROCESS_TOTAL"> <xs:annotation> <xs:documentation>Total number of processes started for this duration</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="PROCESS_TOTAL_TIME"/> <xs:enumeration value="PROCESS_AVERAGE_TIME"/> <xs:enumeration value="WORKITEM_TOTAL"/> <xs:enumeration value="WORKITEM_ACTIVE_AVERAGE_TIME"> <xs:annotation> <xs:documentation>User Task Instance Active Duration (Average) All AMX BPM tasks will emit a READY and COMPLETE event. The time interval between the emission of these events will determine the Task Instance Active duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st offer / allocate (firstOfferTime) and workItem completion (completionTime) disregarding any intermediate states. </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_ACTIVE_TOTAL_TIME"> <xs:annotation> <xs:documentation>User Task Instance Active Duration (Total) All AMX BPM tasks will emit a READY and COMPLETE event. The time interval between the emission of these events will determine the Task Instance Active duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st offer / allocate (firstOfferTime) and workItem completion (completionTime) disregarding any intermediate states. </xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_WAIT_TOTAL_TIME"> <xs:annotation> <xs:documentation>User Task Instance Wait Duration (Total) All AMX BPM tasks will emit a READY and OPEN event. The time interval between the emission of these events will determine the Task Instance Wait duration. The Process Duration will be calculated when the task's (first) OPEN audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Offer / Allocate (firstOfferTime)and 1st Open (firstOpenTime)</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_WAIT_AVERAGE_TIME"> <xs:annotation> <xs:documentation>User Task Instance Wait Duration (Average) All AMX BPM tasks will emit a READY and OPEN event. The time interval between the emission of these events will determine the Task Instance Wait duration. The Process Duration will be calculated when the task's (first) OPEN audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Offer / Allocate (firstOfferTime)and 1st Open (firstOpenTime)</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_ACTION_TOTAL_TIME"> <xs:annotation> <xs:documentation>User Task Instance Action Duration (Total) All AMX BPM tasks will emit an OPEN and COMPLETE event. The time interval between the emission of (the first OPEN of) these events will determine the Task Instance Action duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Open (firstOpenTime) and form submission (completionTime)</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_ACTION_AVERAGE_TIME"> <xs:annotation> <xs:documentation>User Task Instance Action Duration (Average) All AMX BPM tasks will emit an OPEN and COMPLETE event. The time interval between the emission of (the first OPEN of) these events will determine the Task Instance Action duration. The Process Duration will be calculated when the task's COMPLETE audit event is received and written to the Audit trail for the process instance. We interpret this as we need to calculate the time between 1st Open (firstOpenTime) and form submission (completionTime)</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_WORKINGTIME_TOTAL_TIME"> <xs:annotation> <xs:documentation>User Task Instance Working Time Duration (Total) All AMX BPM tasks will emit an OPEN and various user interaction end events, namely CLOSE, PEND, CANCEL and COMPLETE events. The User Task Instance Working Time Duration will be incremented by the time interval between each OPEN and work item end event pairing, each time one of these event pairings completes. Thus giving a total working time for a task instance, regardless of the number of times it is opened/closed and by how many different users. We interpret this as we need to calculate the cumulative time for between first and last (form submission) activities.</xs:documentation> </xs:annotation> </xs:enumeration> <xs:enumeration value="WORKITEM_WORKINGTIME_AVERAGE_TIME"> <xs:annotation> <xs:documentation>User Task Instance Working Time Duration (Average) All AMX BPM tasks will emit an OPEN and various user interaction end events, namely CLOSE, PEND, CANCEL and COMPLETE events. The User Task Instance Working Time Duration will be incremented by the time interval between each OPEN and work item end event pairing, each time one of these event pairings completes. Thus giving a total working time for a task instance, regardless of the number of times it is opened/closed and by how many different users. We interpret this as we need to calculate the cumulative time for between first and last (form submission) activities.</xs:documentation> </xs:annotation> </xs:enumeration> </xs:restriction> </xs:simpleType>

XML Schema documentation generated by XMLSpy Schema Editor http://www.altova.com/xmlspy