| Article ID: | 267 |
| Last updated: | November 02, 2006 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
This article explains how to supress the logging of a particular element data variable, such as an account number or PIN.
SYMPTOMS
Developer is creating a secure application in which sensitive information should not be logged.
RESOLUTION
To prevent the logging of an element data variable for an element:
1) Select the element.
2) In the Element Configuration pane, click on the Data tab.
3) Specify that element data should be created with the same name as the variable you would like to supress, and that it should be created after the element is visited. Set the value of this variable to its previous value, using substitution. Ensure that the 'Store this in log' checkbox is unchecked (see diagram below for example).

Diagram: Configuring an element to supress logging of its 'value' element data variable
4) Ensure that the logging cache size used for your application's activity logger is set to a large enough value to ensure that logging never occurs in the middle of an element. A cache value of 100k or higher is adequate for most applications, but if your elements produce particularly verbose logging use a higher value. This setting can be found in your activity logger's configuration file, in AUDIUM_HOME/applications/APP_NAME/data/application. Here is an example of this setting:
NOTE: Many voice elements will still log interaction data (e.g. user utterances, interpretations, etc.) even when the steps in this article are followed. Change your application's logging level to "moderate" or "minimal" (in CS 3.4.x / 3.5) or modify your custom loggers (in CS 3.6) to prevent this additional information from being logged.
|