Hi, I'm currently extending a existing Ivy application. I face the problem of being unable to debug (trace) Ivy script. Is there some tooling? maybe some trick to output directly into the "runtime log" of the designer? I've already hack the logger to display SQL and such. I'm familiar with web development, java, tomcat and most of the ecosystem. I just have hard time tracing the logic in process. I currently have a bug with Ivy add on, I replace all parameter values one by one with hardcoded values to see what is going on. I've figure out which variable is erroneous but can't figure out what's in it. asked 14.11.2016 at 20:41 RemiMorin |
You can use the 'ivy.log' API to write logs into the runtimeLog. E.g. There is no way to really debug ivyScript. But you can always factor out ivyScript code and wrap it in a JavaClass. Java code can be debugged as described here: http://answers.axonivy.com/questions/21/how-can-i-debug-my-java-class-in-the-designer answered 15.11.2016 at 09:20 Reguel Werme... ♦♦ |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 14.11.2016 at 20:41
Seen: 17,673 times
Last updated: 15.11.2016 at 09:21