18.2 What Can Be Logged

The Workflow Administration Console allows you to log any workflow functionality, and actions, such as granting permissions and making external service calls. The log level for these features is controlled by configuring logging for the packages they use. You can change log levels from the Logging page.

The Workflow Administration Console functionality that executes on a client and does not directly execute in context of the web server cannot be logged in the same way. For example, most of the form processing that occurs in the client. The action scripts defined on the form control’s onLoad, onChange, or custom events execute in the browser of the user’s client computer and not in the workflow web server. Therefore, errors that occur while rendering the form or processing an action script, cannot be directly logged. However, workflow queries issued from a form or Start Activity can be logged to troubleshoot the workflow features. You can view the Workflow Administration Console errors and informational messages in the Client Browser Developer Tool. Click either the Console tab or the Network tab. It contains HTTP response codes for both successful and failed requests. The workflow application allow you to record the outcome of a user’s request and response.

The Workflow Administration Console allows you to log the state of a user’s request and response at the following locations in the data flow:

  • Between the browser and the application server

  • Between the application server and the application database

  • Between the application server and the external service

You can configure the log files to include entries for the following events:

  • Configuration

  • Events processed by application components such as authentication, role assignment, and resource access

  • Error conditions

The log files help you determine the reason for a request failure. For example, if the browser did not send the required information.