Skip to main content
Nintex Community Menu Bar
Solved

How to debug SmartForm

  • February 10, 2016
  • 8 replies
  • 59 views
  • Translate

Forum|alt.badge.img+9

Dear K2 friends,

I am wondering if it is possible to debug the K2 Smartform for its functionality , for example, like breakpoint in Visual Studio and know the controls input and output values and variables.

Thank you for your continuous support.

Best answer by Albarghouthy

Hi IPO,

 

Have a look at this:

 

https://help.k2.com/onlinehelp/k2smartforms/userguide/1.0.5/webframe.html#manually_debugging_forms.html

View original
Did this topic help you find an answer to your question?

8 replies

Albarghouthy
Forum|alt.badge.img+16
  • Scholar
  • 741 replies
  • Answer
  • February 10, 2016

Forum|alt.badge.img+9
  • Author
  • 104 replies
  • February 10, 2016

Thank You Mustafa,

 

Great Information which I did not notice. This makes life much easier.

Translate

Forum|alt.badge.img+7
  • 84 replies
  • February 10, 2016

IPO,


 


If you want to know the controls input and output values and variables, you can add datalabels in your views and forms, and transfer data from the controls to the datalabels. I found this useful to figure out what is happening in the background. 


I used the trace statement to figure out what the bool value was looking for. I wrote about it here


 


Trace statements are very basic, and not breakpoints, but they can be very useful depending on the situation. 


 


Chad

Translate

Forum|alt.badge.img+9
  • Author
  • 104 replies
  • February 11, 2016

Thank You Chadg,

Data-label control and transfering the values into data-label is handy to know its values.

Translate

Forum|alt.badge.img+4
  • 18 replies
  • February 11, 2016

Hi IPO,


 


One more way to find which Action is throwing an error and stopping a Form from going forward is to put notifications with different messages after each Rule/Set of Rules so you know after which notification a 'bad' Action is located. This concept of having a maintenance Action was also logged as a feature request. Hope to see it in the future releases of K2 blackpearl.


 


HTH,


Eugene

Translate

Forum|alt.badge.img+3

Is it that difficult to include the rule name, location, or whatever possible rule identifcation in the error section?

 

I mean, I have the unfortunate oportunity of having to support a poorly written K2 application, and, by far, the thing that takes the most time is figuring out where, in sequence of initialize rules spread across the form and it's different views, did the error happen.

 

Seriously, this has just taken the whole day (!) to figure.

 

Either provide where (somehow) in the rules did the error happen (sounds like basic info about an error), or a way to properly search stuff in the rules, and in all of them.

 

The frustration of having spend 6 hours looking for the source rule of a 'Object reference not set..' during form load, only to fix it and find it also happens on a button click (From later experience I'm expecting another 6 hours looking for the offending smart form rule).

 

Also as others pointed out, SmartForms rule break points would be fantastic.

 

(I have literally lost weeks, cumulatively, searching for offending rules)

Translate

Yes K2 is horrible software for developer.

Translate

NigelStratton
Forum|alt.badge.img+5
I know this an old post, but I have written a Chrome extension that greatly improves SmartForm debugging.

SmartForm Assistant
https://chrome.google.com/webstore/detail/smartform-assistant/gofkomdjofigdlgfedgedbibbachbacb

It's not Visual Studio kind of debugging but it makes tracing confusing events MUCH easier. Allows you to look at the data in SmartObjects, edit data labels at run time and much more.
Translate

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings