Interpreting User Actions from Usage Pattern Tracking Data
This topic describes how user actions are recorded in the UPT logs.
This task is a step in Process of Setting Up Usage Pattern Tracking.
User actions are captured in the UPT log as uaseq1, uaseq2, and so on, and are recorded under UPT Details. The following template is an example of how
user actions are structured in the UPT log file, and the following
table explains some of the log information:
<UPT Details>
<uaseq1>
<EUA>
<ParentRN>
<CurrentRN>
<OT>
<Value>
</EUA>
</uaseq1>
<uaseq2>
<OUA>
<ParentRN>
<Type>
<Operation>
</OUA>
</uaseq2>
</UPT Details>
The following table explains some of the log information:
| Log Information | Description |
|---|---|
uaseq1 |
All user actions are captured in the order in which the user rns actions in the application. The user actions are recorded sequentially, uaseq1, uaseq2, and so on. |
EUA |
This is an explicit user action with user input. |
ParentRN |
The repository name. |
CurrentRN |
The repository name of the current interface control on which the user is performing an action. |
OT |
The object type in which the user is performing the action. |
Value |
The value entered by the user. |
OUA |
Other User Action. |
Type |
This is a type of action where user input is required. |
Operation |
This is a user action such as a mouse click, or a keyboard shortcut. |
The following is an example of UPT log data. In this example, the log file contains a record of a user updating the Location field in an Account applet:
@0`0`5`0`EUA`3``ParentRN`SIS Account List Applet`CurrentRN`Location`OT`JText`Value`San Francisco`rowid`4`Also in this example, the following five user pattern tracking properties and the respective values are recorded:
ParentRN: SIS Account List Applet
CurrentRN: Location
OT: JText
Value: San Francisco
rowid: 2