I’m wondering whether it is possible to log messages inside “Invoke code” activity in the same manner as the “Log message” activity does? Is there for example a particular namespace that contains the logging methods so that I could use them inside “Invoke code” activity? This would be useful so that I could get more fine-tuned information about what happens inside the “Invoke code” activity.
Thank you for your reply. I have been using Console.WriteLine method so far but the problem with this is that log messages don’t appear in Orchestrator even though I specify the log level as Trace.
Thank you! This seems to do the trick. Using this approach I managed to get the logging working with the following piece of code:
Dim logMessage As UiPath.Core.Activities.LogMessage = New UiPath.Core.Activities.LogMessage()
logMessage.Level = UiPath.Core.Activities.CurentLogLevel.Error
logMessage.Message = "Hello World!"
Dim logInvoker As WorkflowInvoker = New WorkflowInvoker(logMessage)
logInvoker.Invoke()
I am creating a Custom Activity and use Console.writeline so far I watch the value from output panel in studio but I can not see in the Orchestrator log.
I was trying to find how to log messages from invoke codes and I came across this thread.
Unfortunately, I believe this no longer works on newer versions of UiPath. Could you provide the current solution or reopen the following thread?
I was trying to call this activity as per you suggested, though I got the Object Null exception.
I have attached the workflow and the screenshot I am getting while executing the workflow.
Need your help.
Im re-taking it time to time and its becoming one of the top ranked hour-wasted topics in my team… Still no idea about which Object we have to send here…
Overcoming the issue with the InArgument /Conversion we can do:
Code:
Dim wl As System.Activities.Statements.WriteLine = New System.Activities.Statements.WriteLine()
wl.Text = New InArgument(Of String)("Hello From WriteLine")
Dim res As IDictionary(Of String, Object) = WorkflowInvoker.Invoke(wl)
Unfortunatly the same was not working on the first hit with logMessage. But the LogMessage Activity was created with the Input Arguments for LogLevel and Message in the same way and looked ok for this part