You use the following fields (or combination) to format a command logging device:
Field Name |
Description |
---|---|
{UserName,n} |
The name of the user (User Name) who was logged on when the command was issued. |
{FullName,n} |
The full name of the user (Full Name) who was logged on when the command was issued. |
{Time,n} |
The time (in short format) when the command was issued (hh:mm). |
{TimeLong,n} |
The time (in long format) when the command was issued (hh:mm:ss). |
{Date,n} |
The date (in short format) when the command was issued (dd:mm:yy). |
{DateLong,n} |
The date (in long format) when the command was issued (day month year). |
{DateExt,n} |
The date (in extended format) when the command was issued (dd:mm:yyyy). |
{Page,n} |
The page that was displayed when the command was issued. |
{MsgLog,n} |
The message sent as the Message Log property (of the command record). |
You can use the following fields (in the command field) for Keyboard commands only: |
|
{Arg1,n} |
The first keyboard command argument (if any). |
{Arg2,n} |
The second keyboard command argument (if any). |
. . . |
|
{Arg8,n} |
The eighth keyboard command argument (if any). |
{Native_MsgLog,n} |
The native language version of the message sent as the Message Log property (of the command record). |
Where n specifies the display field size. |
For example, you could have a device configured as follows:
Name |
KeyLog |
Format |
{Date,9} {MsgLog,27} {Arg1,3} by {FullName,11} |
Then a keyboard command (object, page, or system) could be created with the following configuration:
Log Device |
KeyLog |
Key Sequence |
### ENTER |
Log Message |
Density setpoint changed to |
Resulting in an output of the following kind: "01/01/99 Density setpoint changed to 123 by Timothy Lee".