Workflow Soluiton

 View Only
  • 1.  Process Manager Logging Problems

    Posted Feb 13, 2014 11:02 AM

    We have been having some problems in our Production environment with getting Process Manager logging to work consistently. We have multiple workflows in the same environment with some having no issues with logging, but others are not logging at all. Looking through the Log Viewer I see an error:

    "Global data 'ProcessName' is null"

    The error is under the LogicBase.Components.Ensemble.Reporting.LogMessageProcessComponent Logging category.

    Has anyone else experienced similar issues with Process Manager logging being inconsistent between workflows, or has anyone seen the error message I am getting? I'm simply confused as to why some workflows would be logging correctly and others would not if they are in the same environment.

    Thanks for your help!

     



  • 2.  RE: Process Manager Logging Problems

    Posted Feb 17, 2014 11:10 AM

    Is the Global Data option ProcessName set to anything?  Open the workflow, on the navigation pane, click the top-most option (process name), click the Global Data tab and see if there is a default value for ProcessName.   If not set it.   If there is something set, maybe it's being cleared somewhere in the workflow?



  • 3.  RE: Process Manager Logging Problems

    Posted Feb 17, 2014 12:37 PM

    Hi Justin,

    Thanks for the suggestion. I went ahead and looked at the ProcessName field, but found that it was populated for the workflows in question:

     

    Untitled.png

    I don't believe that we are clearing the ProcessName in the workflow at all, simply because we would have no reason to. I wonder if this issue could possibly be caused by something outside of the workflow, possibly in the Local Machine settings in the Task Tray tool?



  • 4.  RE: Process Manager Logging Problems

    Posted Feb 17, 2014 02:40 PM

    I don't think its anything that would be in the LME.   Try setting a value for the Global.ProcessName variable from within the workflow itself and see if that does anything.