HowTo: Enable Log for GXflow runtime

Official Content
This documentation is valid for:

This document explains how to enable logging for Workflow Tables impact, reorganizations, and access to GXflow database information when using the GeneXus IDE.

Sometimes when you need to reorganize Workflow Tables or make an impact analysis, or when a Workflow process isn't working correctly, an error occurs showing no specific details. This may happen when a new Upgrade of GeneXus is installed. In this case, it is useful to enable logging and look for errors in the .log file created, as shown below:

Enabling logging in the GeneXus IDE (for GXflow impact)

It only implies enabling the Generator's logging. The logging properties can be found under Preferences by clicking on the corresponding Generator node.
For example, for a .NET Framework environment:

LogExample

The properties to be set for all the Generators are as follows:

  • Log level property defines how much detail has to be added to the log at runtime.
  • User log level property details the writing level of the Log when using the Log API programmatically.
  • Log output property indicates the output for the Log level property.
  • Log file property defines the name of the Log Output file when the Log Output Property is set to File.

Java has some unique properties:

  • Log JDBC Activity allows knowing what happens in the JDBC connections to the databases. If you set this property to Yes, the following properties will appear.
  • Use unique names property defines whether you want to automatically generate a log file or use a fixed name.
  • JDBC Log File property completes the path to a log file.
  • Detail property indicates the JDBC log’s detail level.
  • Enable buffering property allows indicating whether the buffer is activated when generating the activity log.

To apply changes made by these properties, Build any object.

After setting the properties, execute the reorganization or impact analysis, and the log will be created. The actions that you do in GXflow Client will be registered in this log.

If the path is not defined, the log will be created by default in the following files according to your generator:

  • .Net Framework <kb_path>\CSharpModel\web
  • .NET  <kb_path>\NetModel\web\bin
  • Java <webapp_path>\logs\

If the log is working correctly, it should have a line similar to this one when you are signing in GXflow:

2022-06-15 10:41:49,002 34 DEBUG GeneXus.Data.ADO.GxCommand - ExecuteReader: Parameters @AV40WFUsrCod='WFADMINISTRATOR'

Note: If you are generating with .Net or Java, another client.log will be created in <kb_path>\Model\web\bin and <kb_path>\Model\web\logs, respectively. It will only have information about the creation or reorganization of the database when you do a Build/Rebuild.

See Also

HowTo: Enable Log for GXflow BPDeployer
HowTo: Generate log for GXflow license manager