##### Compile

# Trace Options

All trace files are for support use only.

## Runtime Trace Options

Trace files will be stored in the WebServer's application directory for the Web App.

### Trace Level

There are 5 levels supported (0 - 4), which are described below. Each incremental level also traces the data of the previous level(s).

Priority Order | Description
0 - None | No log events are traced.
1 - Errors | The default. Only error conditions are traced.
2 - Warning | Warning messages are traced.
3 - Basic Trace | The normal tracing level, provides information as to code flow, and so on.
4 - Detailed Trace | Shows all possible traces, including input/output data.

### Maximum number of Trace Files

Number of Trace Files and Size of Trace files. Allows the amount of trace data to be collected to be modified.

### Maximum Size of Trace Files (in KB)

Maximum size of trace files in Kilobytes.

### Base Trace Files Name

Allows trace file names to be customized. Default is WWGRT. Default file names will have the form WWGRTxxxxx.log where xxxxx is a sequence number.

### Organize Trace Files By...

Allows you to determine how trace files are to be saved. Each user should have their own set of trace files, and the identity of the user can be different depending on the environment. The choices are IP Address, Cookie ID (Genesys Agent Scripting stores a unique cookie ID on each user's machine), and Host name.

## Editor Trace Options

Click the Enable Editor Tracing check box if you want to trace operations through the Genesys Agent Scripting editor. When this option is selected, the files are stored in the Genesys Agent Scripting Application directory. Two files are created, WWGEditor.log, and WWGEditor.log.bak. The file WWGEditor.log contains trace messages indicating what forms have been loaded, and which buttons or menu items the user has selected. This is valid for the current or most recent session. There is no limit on size. The file WWGEditor.log.bak contains the data from the previous Editor session.