Hi,
after sucessfully installing and composing workflows using the existing objects I'm trying to develop own Actions and Workflows.
Whats the suggested way to do some debugging during the development (like watching the content of variables and so on)?
Logging via System.Log(...) is not really satisfying, especially sinc I have to "switch off" all the debug-log-command when deploying on the customers site.
Many thanks in advance!
kind regards,
joerg
Hi Joerg,
If you are looking for debugging steps for watching the contents for a variable, I don't think if that's presently possible without System.log statements. vCO is beneath using Rhino JavaScript for scripting. There's no as such mechanism for debugging apart from the printing statements. You can however try using System.debug which would set the debug threshold.
If you want to debug for the values in the input parameters which are passed to a workflow, that can be done by watching the variables tab in the running/completed/failed workflow token execution.Also, catching the exceptions would also help to debug when some error occurs, the exception can be seen in the variables tab.
Hello
and where can I find the System.Logs of Actions
which are called from a User Interaction of an workflow??
Because in the "Execution Logs" window are only System.Logs
which are direct in the Scripting Task of the workflow.
Kind Regards
klaus
The most effective way for me to debug is to start Orchestrator in command line and adjusting the level of debug to my need. I can then see in real time what is happening in the vCO server. My colleague here use baretail that can be configured to highlight some part of the logs.
Hi!
I prefer to watch the files in \app-server\server\vmo\logs with a tool like mtail
http://ophilipp.free.fr/op_tail.htm
There is a file named script-logs.log which includes all the System.debug-Messages even from your actions.
Cheers,
Joerg
great, that was what I'm looking for!!!
kind regards
klaus