JohnDanter2
VIP Member
Hi folks
With all the new lovely languages we have in Orchestrator, let alone the JET graphs I've posted about before, how do you 'debug' the lines of code we write in the Orchestrator steps?
JET is easy as you do that in JDeveloper and Chrome itself (F10 etc) but how exactly do we debug the lines of code in a Groovy orchestrator step?
All we can see at the moment is values in and values out of the step and it's a kind of black box. I'd like to hit lines of code in the functions or even manipulate output step.
Do you use a third party tools to step line by line, or is this already available in 9.2 and I've missed it
Thanks
John
With all the new lovely languages we have in Orchestrator, let alone the JET graphs I've posted about before, how do you 'debug' the lines of code we write in the Orchestrator steps?
JET is easy as you do that in JDeveloper and Chrome itself (F10 etc) but how exactly do we debug the lines of code in a Groovy orchestrator step?
All we can see at the moment is values in and values out of the step and it's a kind of black box. I'd like to hit lines of code in the functions or even manipulate output step.
Do you use a third party tools to step line by line, or is this already available in 9.2 and I've missed it
Thanks
John