Groovy Service Log

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    Form Builder Platform Developer |  v17.10 This feature was introduced in v17.10.

Manager allows you to view Groovy script logging output so you can debug and profile functions and services that are based on Groovy scripts. When a form calls a Transact function, it executes a Groovy script, which can be programmed to write some information into a log file, for example, logger.debug("Variable: " + varaibleValue). This information is logged and can be viewed in the Groovy Service Log tab. The log can be empty if there is no debugging configured or if the debugging is disabled.

To view a Transact function Groovy service log:

  1. Select Services > Transact Functions.
  2. Locate a Transact function and click Edit.
  3. Click the Groovy Service Log tab to see the list of forms from where functions were invoked with the following details:
    • A function invocation time
    • Duration of the invocation
    • Memory change
    • CPU
    • Number of threads
    • Status
  4. Click a form name to see form details in a form dashboard.
  5. Click Groovy Logger to view the output created during the function invocation.
  6. Note

    Select the Groovy Log tab to see the same logged messages.

  7. Click Submission View to see details of a transaction associated with this function call.
  8. Click Close.

To enable Groovy logging, select the Groovy Scripting Enabled checkbox in the Parameters Edit tab.

To view all Groovy service log messages, select Services > Groovy Service Log.

Next, learn how configure Transact function service definition.