Journey Manager (JM) The transaction engine for the platform. | Form Builder Platform Developer | 17.10 This feature was introduced in 17.10.
Manager allows you to view messages generated and logged by functions and services written in Groovy, so you can debug and profile them. When a form calls a Transact function, it executes a Groovy script, which can be programmed to write some information into a log file by using a
Logger class, for example,
logger.debug("Variable: " + varaibleValue). In this case, this message is logged into Groovy Service Log and can be viewed in the Groovy Service Log tab.
Messages logged to the Groovy Service Log are stored in the
GroovyServiceLog table, which can grow big, so you need to set up data purging according to your requirements.
All log messages associated with a transaction or PIIPersonally Identifiable Information (PII) is information about an individual that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and any other information that is linked to an individual. In Europe, PII is known as personal data. data are encrypted so you can't search for a part of encrypted text. If you want to search encrypted messages, you need to implement different logging solutions, for example, using the System Event Publisher.
The log can be empty if there is no debugging configured or if the debugging is disabled.
Do not log PIIPersonally Identifiable Information (PII) is information about an individual that can be used to distinguish or trace an individual‘s identity, such as name, social security number, date and place of birth, mother‘s maiden name, or biometric records; and any other information that is linked to an individual. In Europe, PII is known as personal data. data to the service log, for example, to debug a service, as there's a risk of exposing customer's details through the log file.
To view all Groovy service log messages, select Services > Groovy Service Log.
Messages are shown page by page, with the maximum number of records per page configured via the user's preferences.
The Groovy Service Log list displays the following details for each log entry:
To filter or search the Groovy Service Log by one or more criteria, specify the following settings and click Search:
You can't use this functionality to look for a part of encrypted text.
Only services of a selected service type are shown in the dropdown list, if you used the Service Type filter above.
Click Clear to reset the search criteria.
Click Export Data to export the displayed data as a Microsoft Excel (XLS) file.
Alternatively, you can view Groovy Service Log directly from a Transact function's or a service's definition.
To view a Transact function's or a service's Groovy service log:
The memory change value can be negative, but it is the delta value what is important for you to analyze.
Select the Groovy Log tab to see the same logged messages.
To enable Groovy logging, select the Groovy Scripting Enabled checkbox in the Parameters Edit tab.
Next, learn how configure Transact function service definition.