Debug

You can debug AVEVA Work Tasks. The various methods implemented to debug include:

• Setting the Debug Level

• Logger Message Categories

Debug AVEVA Work Tasks

• Access the Central Configuration URL (for example, https://worktasks.connect.aveva.com/CC123456789). and navigate to WTLogger Console.

  The WTLogger Console window appears.

  The events are displayed in the WTLogger Console when AVEVA Work Tasks is running. The WTLogger Console displays events using three types of log categories. These log categories are used to identify the type of information.

The following debug levels are available:

• Level 1: This level shows minimal information in the Logger Console. The Logger console displays information related to the start and end of a workflow. Error messages are also shown in this mode.

• Level 2: This level provides detailed information of background activities. It will show all the messages logged from the actions.

• Level 3: This level displays messages indicating whether an action is executed.

All error messages logged in the Logger Console will be sent to the user e-mail ID. This e-mail ID is picked up from the SMTP node in the configuration file.

Logger Message Categories

There are three categories of messages logged in the log files.

• Information (i): This type of message is preceded by a lower case 'i'. It indicates messages containing general information about the events being logged. Each message of this type has four parts:

  • the event information

  • the module generating the event

  • the machine on which the event took place and

  • the date and time of the event

• Warning (?): This type of message is preceded by a question mark '?'. These messages are warning notes to the users about the events being logged. The messages of this type have a structure similar to the 'Information' messages with the same four parts as mentioned earlier.

• Error (!): This type of message is preceded by an exclamation mark '!'. It indicates error messages with details specific to the error. Messages of this type can be further classified into four parts similar to the other two messages. In addition, it has the 'Exception Stack Trace', which occurs before the machine name and date/time. It can be identified by the keyword 'Source' and it can be used to trace the source of the error.

Logger Activity

The Logger Activity can be used to log custom messages like information, warnings, and errors which should be logged to the Log Console from the workflow.

BAM Report

This report presents details related to failed workflows.