Skip to main content

Processed export definitions

Suggest edit Updated on October 22, 2021

Create a custom desktop analytics report by using the data in the processed export. For example you could use this data to create custom dashboard reports on utilization, such as screen usage, to measure adoption of a new application or process.

The following list defines each field in the processed export:

operation_id
Unique identifier of the row (a primary key value).

Data type: VARCHAR

parent_operation_id
operation_id of the parent event. You can match screen events with application events. For example, you can match event_name = 'FormLostFocus' (screen event) with rows where event_name = 'AppLostFocus' (app event).

Data type: VARCHAR

session_id
The Robot Runtime session that generated the events. Every time that the data collector starts, the system generates a unique session_id and all the events that occur during that session are assigned the same session_id.

Data type: VARCHAR

shift_date
The shift day for the associate.

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

network_id
The domain account of the associate who generated the event. You can use the values in this field to join with the network_id in other default exports.

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 an associate's team.

Data type: INTEGER

level_1_name
The label that is assigned to level_1_id. This value is typically the team name of the associate.

Data type: VARCHAR

event_name
Name of the event. Examples of event_name values include AppLostFocus, FormLostFocus, PageLostFocus, Copy, Cut, Paste, IdleStopped, WebPageLoadEnded, and ProcessWaitEnded.

Data type: VARCHAR

category
Category of the application used in the event. Note: The Pega Workforce Intelligence administrator defines the application categories.

Data type: VARCHAR

domain
Domain of the web application, such as www.pega.com.

Data type: VARCHAR

exe_name
Name of the executable file of a Windows application, such as notepad.exe, or the browser name for a web application event, such as chrome.exe.

Data type: VARCHAR

app_value
Application name, which is typically the exe_name for a Windows application executable file, or the domain name for a web browser application.

Data type: VARCHAR

app_alias
Alias that the Workforce Intelligence administrator assigns to the application.

Data type: VARCHAR

screen_text
Screen name or title of an application.

Data type: VARCHAR(MAX)

screen_alias
Display name that is defined by screen rules and applied to the screen_text, url, or url_title. An administrator creates screen rules in Workforce Intelligence.

Data type: VARCHAR(MAX)

url
URL of a web application. Note: For Windows applications, this field contains the NULL value.

Data type: VARCHAR(MAX)

url_path
Path portion of the URL for a web application.Note: For Windows applications, this field contains the NULL value.

Data type: VARCHAR(MAX)

url_title
HTML title tag in a web application. Note: For Windows applications, this field contains the NULL value.

Data type: VARCHAR(MAX)

process_id
Unique ID that the Windows operating system assigns to an application when the application launches. The Details tab of the Windows Task Manager utility displays this same integer.

Data type: INTEGER

start_time
The time when the event began.

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

end_time
The time when the event ended.

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

duration_ms
Number of milliseconds that the event lasted. The duration is calculated by using the difference between the end_time and start_time values.

Data type: BIGINT

process_total_wait_time_ms
Number of milliseconds that an application was unresponsive, typically waiting for an internal operation to complete. Associates might experience this as a frozen application.

Data type: INTEGER

in_focus_duration_ms
Number of milliseconds that the associate stayed in an application that was waiting.

Data type: INTEGER

out_of_focus_duration_ms
Number of milliseconds that an application continued to wait after the associate left the application.

Data type: INTEGER

cut_count
Number of Ctrl+X key presses during the event.

Data type: INTEGER

copy_count
Number of Ctrl+C key presses during the event.

Data type: INTEGER

paste_count
Number of Ctrl+V key presses during the event.

Data type: INTEGER

keypress_count
Number of keys pressed during the event. This integer includes the key presses for any cut, copy, paste, and error keys.

Data type: INTEGER

errorkeypress_count
Number of Delete key and Backspace key presses during the event.

Data type: INTEGER

mouseclick_count
Number of mouse or wheel button clicks. For mice that have two buttons, both the left and right mouse button are included in this count.

Data type: INTEGER

mousewheel_count
Number of spins of the wheel on a mouse. Note: Mouse wheel behavior is different from application to application. Most applications implement a type of screen scrolling behavior, but some applications implement the mouse wheel for zoom control.

Data type: INTEGER

scroll_count
Number of scrolls in an application. Scrolling typically means that the associate wanted to see something that was not visible in the current size of the window application frame or screen frame.

Data type: INTEGER

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

Data type: INTEGER

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

Data type: DECIMAL

day
The day on which Workforce Intelligence received the event.

Data type: VARCHAR in the format of YYYYMMDD

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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