Warn/Error Logging Level show debug information in bg-ca.log

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When the Process Engine Persistence Logging is set to Warn or Error, there are more messages in bg-ca.log than in Info level.

Steps to Reproduce:

1. Create a new Process with just one action, which executes a custom script. Script contents:

<gel:script xmlns:gel="jelly:com.niku.union.gel.GELTagLibrary" xmlns:j="jelly:core" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <gel:log level="INFO">This is a log message on Level Info</gel:log>"/>
</gel:script>

2. Go to Logs > Edit Configuration. Set the Process Engine Persistence Logging to "Info".
3. Run the process.

Actual Results: Once the process completes, there is an Info message with the process log output, and no entry in bg-ca.log.

4. Go to Logs > Edit Configuration. Set the Process Engine Persistence Logging to "Warn" or "Error".
5. Re-run the process.

Expected Results: Once the process completes, there is no Info message with the log output, and no entry in bg-ca.log.

Actual Results: Once the process completes, there is no Info message with the log output, but there is now DEBUG information of this process in bg-ca.log:

SYS   2022-10-05 06:50:40,797 [Custom script execution pool-16-thread-1] utilities.BpmErrors (clarity:x:x:none) 

Begin Information:
  Step Action Id: xxxxxxx
  Process Instance Id: xxxxxxx
  Step Instance Id: xxxxxxx
  Code: bpm.customScriptDone
End Information

Environment

Release : 16.0.3

Component : Clarity Process Management

Cause

DE66871

Resolution

This issue is fixed in Clarity 16.1.1.

From this version, in order to see process information in the bg-ca.log when a GEL script completes after this change, the com.niku.bpm.utilities.BpmErrors logger category must be enabled in the logger.xml and it must use level DEBUG or INFO.