Debugging: match console output to specific workflow activities
If I add the debug=true parameter to a viewer URL, a lot of useful information about which activities are run is logged to the browser's console.
Some activities can easily be identified, such as CreateValue, which logs the name of the variable, e.g. --> gcx:wf:core::CreateValue ($myVariable) . For other activities only a number is logged, e.g. --> gcx:wf:core::If (374) .
Is there an easy way to match a debug statement to an activity in the workflow (other than going through the entire workflow process step by step)?
-
Hi @Berend Veldkamp? ,
You could assign an id to the specific "If" activity instance that you are interested in. By default, the Workflow Designer only creates an ID for activities that have outputs. Otherwise we assume you don't need its name.
The number you see in the log is the underlying numeric value that all activities have behind the scenes. Those values are not shown anywhere in the user interface.
0 -
Hi Ken,
Thanks, that makes sense.
It would be nice though if we could search for that number in the designer, like we could in the workflow 4 designer. Are there any plans to build such a feature?
0 -
Hi Berend,
I've considered this before but I don't really think we could make it a priority. The underlying ids are a bit more low-level than we'd like to go. For the most part, adding text ids via the designer achieves the same thing.
Feel free to add it to the ideas page if you like. If there turns out to be a demand for it I can reconsider.
0 -
Yes, I'll do that (here).
Adding ID's to all activities will clutter up the list of variables that's in the code completion (which in many cases is too long already), and I'd really like to avoid that.
If searching by ID in the designer isn't feasible, maybe the name or description of the activity could be logged to the console?
0
Please sign in to leave a comment.
Comments
4 comments