Logging tab of the Activity Property panel

In addition to the default information that is collected in the processes.log when you execute a process, you can specify information to be logged for each activity in the process. When you test the process in the  Development Studio application, the log entries for the activity are written to the console window and to the processes.log file on the computer where  Development Studio is installed. When the process is executed on the grid, the entries are written to the processes.log file on the peer that executes the process.

By default, when the  product runs a process on the grid, it logs only process starting and ending information. However, you can use the Logging tab to configure logging for additional information about each activity in the process.

The following figure shows the Logging tab for the Call Adapter activity.

The Logging tab enables you to configure process log messages to write before, after, or before and after the activity executes. The log message can include static text as well as the value of one or more designated context items at the time of the activity's execution.

When processes are run on the grid, the log levels indicate the priority, or urgency, of the message. The logging levels, in ascending order of priority are:

  • debug
  • info
  • warn
  • error

The activity's log messages are written to the log only when the activity log level priority is greater than or equal to the logging level set for the grid where the process is executed. For example, if you set an activity's log level to info, the message will be written to the executing peer's processes.log file if the grid's logging level is set to debug or info, but not if the grid's logging level is set to warn or error. 

Logging Level

Description

DEBUG

(default for processes.log) The most detailed logging level; logs low-level messages, normal execution, recoverable erroneous conditions, and nonrecoverable erroneous conditions

INFO

Logs normal execution, recoverable erroneous conditions, and nonrecoverable erroneous conditions

WARN

Logs recoverable erroneous conditions and nonrecoverable erroneous conditions

ERROR

The least detailed logging level; logs only error conditions that are not usually recoverable

When processes are tested in  Development Studio, all configured log messages are written to the console window and to the processes.log on the computer where  Development Studio is running.

Recommendation

While developing a workflow, log the following items to assist with troubleshooting:

  • adapter requests
  • adapter responses
  • the value of context items before and after they are changed
  • the results of any complicated transform

This section contains the following topic:

Was this page helpful? Yes No Submitting... Thank you

Comments