Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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.


Merged idea

This idea has been merged into another idea. To comment or vote on this idea, please visit IDEAAD-I-29 Improve LotusScript debugger.

Conditional breakpoints for LotusScript Merged

While they are available for Javascript and quite handy I miss them for LotusScript.

It's rather annoying if one wants to debug special cases of an iterative section but has to step through non-interesting cases as well. 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jul 23 2018
  • Investigating
  • Admin
    Thomas Hampel commented
    August 07, 2018 12:10

    Already now you can use an if / then statement to define your case and set your breakpoint within that section

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 07, 2018 12:15

    I know. Which is tedious depending on how many cases you want to catch. I never was a friend of spaghetti code.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 07, 2018 13:43

    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!

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 07, 2018 14:19

    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 :

    1. Add a stop command in the loop at 99 and continue manually
    2. Set breakpoint at the end at the loop and press continue for 99 times.

    Having a conditional breakpoint would allow us to do solution no 1 without editing the code.