The Logger object writes to the Test Result window before the script is live (committed). After the script is committed, the logger writes to a rolling log file (similar to drm.log). The log file currently in use is called customobjects.log. When the current log file is rolled over, the Platform appends a number to the file extension: customobjects.log1.
The Logs button in the View and manage custom objects page allows you to download this log file. Another button, Purge Logs, allows you to delete all OLD log files. The log file currently in use is NOT deleted.
Note: The results for custom objects run from the Test page of the Custom Object wizard do NOT appear in the custom object log file. The results for custom objects run from the Test page appear in the Test Result window only.
Your Platform administrator can configure the location on the file system and the format of the logger using a properties file.
The following attributes are available for the Logger object:
o logger.info()
o logger.debug()
o logger.error()
Refer to the following examples to see how you might use this object and its attributes:
o Custom Object Example: Alarm Object Logger
o Custom Object Example: Event Logger
o Custom Object Example: Registration Logger