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's gravatar image

accept rate: 50%

You can use the 'ivy.log' API to write logs into the runtimeLog. E.g. ivy.log.info("this is my parameter:"+ strInput); The logger is also available in plain Java via Ivy.log().info("hello logger");

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%20Wermelinger's gravatar image

Reguel Werme... ♦♦
accept rate: 70%

edited 15.11.2016 at 09:21

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: 14.11.2016 at 20:41

Seen: 17,268 times

Last updated: 15.11.2016 at 09:21