TeamConnect's logging functionality allows the system to generate logging messages for information or troubleshooting. As a TeamConnect developer, you can specify messages for log levels during customization, design, and production.

For example, when you are writing and testing code, include Debug messages so that you can see what occurs when your code executes. When code is in production, messages with a higher level of severity, such as Warn or Error, indicate less frequent but more critical problems in your code.

Logs capture messages based on the logger levels that system administrators or solution developers define in TeamConnect. TeamConnect only logs messages for the level defined and the levels of higher severity. As a result, if you include a message in your code for a lower level, TeamConnect does not log the message to the logger. For example, loggers with a Warn level include messages with levels of Warn, Error, and Fatal. If your code includes a message for the Info logger level, the message does not log.

Loggers for API Code

TeamConnect has several predefined loggers. Depending on the type of code you are writing, TeamConnect logs messages to the corresponding logger:

•Code for an automated qualifier or action logs messages to the Rule logger.

•Code for a custom screen logs messages to the Custom Blocks logger.

•Code for a custom tool logs messages to the Tools logger.

Logging Messages from the API

Complete the following steps for your custom code to generate log messages:

1.On the Logging page of the Admin Settings, define the logging level for the type of logger associated with the code.

2.Specify logging messages in your code using the CustomItem or Platform logging methods.

3.Add code that checks the logging levels in TeamConnect before running logging methods.