Suppress Workunit Logging in Sup Process but not Parent Process?

andy

Anyone know if it's possible to suppress Workunit logging in a Sub Process if it's enabled in the Parent Process? It seems like the Parent's logging setting takes precedence even if logging isn't enabled on the Sub Process; I'm guessing because the Sub Process runs under the same Workunit as the Parent Process, i.e. it's merged into the Parent Process.

The only solution I've found so far is disabling Workunit logging in both and adding a logger function to explicitly log in the Parent Process. Any thoughts?

balkenhol

It makes sense that the sub process is taking on what the original process flow is using since I've heard behind the code it's just copying those nodes over in place of the sub process node.  During the last IPA Interactive Briefing, I asked it was possible to implement custom logging and still get to the neat usage statistics at the end of the flow.  The answer was, no, there was no functionality to do this - however one could technically turn logging on for the PfiFlowDefinition right at the end of the work unit and it would capture these.

I haven't tested that, but you may try putting a Landmark Transaction at the beginning of your sub process that detects the logging level of the main PfiFlowDefinition and toggles it off if it was already on, go through normal processing, and toggle it back on at the end of the sub process. It seems odd to me that the work unit would keep track of things as they change on flow definition rather than using some cached value.  You may have to add a wait node in there to force it to wait (clear the cache) and check the flow definition as it starts back up.

Without knowing anything about your problem and use case, this seems like a lot of effort that probably would be just as easy to implement custom logging.  Plus, there's the audit log that would show the logging being toggled twice per work unit.