Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Let me give an example of what I think the author is referring to. Let's say you are using a loop to run a process and and the end of a loop generate a document. There is a runtime error and 100 document is generated so you are guessing that the 101st process encounter some sort of undefined data. Right now, the only way to test this hypothesis is either :
Having a conditional breakpoint would allow us to do solution no 1 without editing the code.
Thomas, what you are referring to is a condition in your script. The author most likely means within the debugger! Most (other) debuggers have this feature, and it’s very useful!
I know. Which is tedious depending on how many cases you want to catch. I never was a friend of spaghetti code.
Already now you can use an if / then statement to define your case and set your breakpoint within that section