Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Workflow export definitions

Updated on October 22, 2021

Obtain high-level metrics for workflow types, find outliers, and understand each instance by basing custom analysis on the exported workflow file. All of the fields in this export are arranged by workflow instance.

The following list defines each field in the workflow export:

workflow_instance_id
The specific instance of a workflow (a primary key value).

Data type: VARCHAR

path_id
Represents the ordered steps of an instance. If two instances share the same path_id, you can describe the two instances as having identical steps in the same order of appearance.

Data type: VARCHAR

workflow_id
Workflow name of the instance.

Data type: VARCHAR

workflow_name
Name of the workflow of the instance.

Data type: VARCHAR

workflow_type
Type of workflow, which is either TAG or TASK.

Data type: VARCHAR

shift_date
The shift day on which the instance was captured.

Data type: DATE in the format of YYYY/MM/DD

network_id
Domain account of the associate who performed the workflow instance step.

Data type: VARCHAR

level_1_id
Unique identifier of the next level up from the associate level. This value is typically the unique ID of the associate's team.

Data type: INTEGER

level_1_name
Label that is assigned to level_1_id. This value is typically the name of the associate's team.

Data type: VARCHAR

start_time
The time when the instance began. This value is the same as the start_time value of the first step of an instance.

Data type: UTC TIMESTAMP in the format of YYYY/MM/DD hh:mm:ss

end_time
A UTC time stamp that represents the time when the event ended. This value is the same as the end_time value of the last step of an instance.

Data type: UTC TIMESTAMP in the format of YYYY/MM/DD hh:mm:ss

duration_ms
Number of milliseconds that the instance lasted. This value is the difference between the end_time value of the last step and the start_time value of the first step.

Data type: BIGINT

productive_duration_ms
Number of milliseconds that the associate spent in all productive applications in the instance.

Data type: BIGINT

idle_duration_ms
Number of milliseconds that were idle in the instance.

Data type: BIGINT

non_work_duration_ms
Number of milliseconds that the associate spent in all non-work applications in the instance.

Data type: BIGINT

unknown_duration_ms
Number of milliseconds that the associate spent in all unknown applications in the instance.

Data type: BIGINT

wait_duration_ms
Number of milliseconds that the associate spent waiting in any application that reported wait time during the instance.

Data type: BIGINT

waste_duration_ms
Number of milliseconds that the associate spent idle or in any non-work or unknown application during the instance.

Data type: BIGINT

occ_duration_ms
Number of milliseconds of that the associate spent idle and where the associate identified the idle time by using an off computer code (OCC). You can capture this information only if you enable the OCC feature.

Data type: BIGINT

num_steps
Number of steps in the workflow instance.

Data type: INTEGER

cutcopy_count
Total number of times that the associate pressed Ctrl+X and Ctrl+C during the workflow instance.

Data type: INTEGER

paste_count
Total number of times that the associate pressed Ctrl+V during the workflow instance.

Data type: INTEGER

keypress_count
Total number of key presses by the associate during the workflow instance. This number includes the key presses for any cut, copy, paste, and error keys.

Data type: INTEGER

errorkeypress_count
Total number of times that the associate pressed the Delete key and the Backspace key during the workflow instance.

Data type: INTEGER

mouseclick_count
Number of mouse and wheel button clicks during the workflow instance. Note: If a mouse has two buttons, this number includes both the left and right button.

Data type: INTEGER

mousewheel_count
Number of spins of the mouse wheel during the workflow instance. Note: Mouse wheel spin behavior differs between applications. Most applications implement scrolling, but some applications implement zooming.

Data type: INTEGER

scroll_count
An integer that represents the number of scrolls of the associate during the workflow instance. Scrolling generally means that the associate wanted to view something that was not visible in the current size of the window.

Data type: INTEGER

windowmovesize_count
Number of times that an associate moved or resized the window of an application on the screen during the workflow instance.

Data type: INTEGER

friction_score
A score that indicates the amount of interaction that is required to complete the workflow based on the number of steps, key presses, clicks, and scrolls in a workflow.

Data type: DECIMAL

efficiency_score
A score that indicates the amount of waste in a workflow by comparing production and other work time to total time.

Data type: DECIMAL

complexity_score
A score that indicates the variability that is required to complete a workflow, including total applications and screens, unique applications and screens, and number of steps in a workflow.

Data type: DECIMAL

overall_score
A score that indicates the overall health of the workflow, based on the efficiency, complexity, and friction scores of all paths in the workflow along with other criteria. This score is a weighted average that helps analysts determine which workflows might require more analysis.

Data type: DECIMAL

instance_cost
Duration (in hours) of the event multiplied by the cost (hourly rate). Note: The Workforce Intelligence administrator defines the hourly rate on the Application Administration page.

Data type: DECIMAL

day
The day in which the associate completed the instance.

Data type: VARCHAR in the format of YYYYMMDD

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us