I have a few data tables used for analysis of data that have embedded scripts. These scripts perform analyses that spawn new tables (summaries, model fits from which I create combined data tables, then perform splits, joins, etc.). In these scripts, I often move/rename columns and remove rows/columns, and these scripts are impossible to work on with the debugger.
I need to be able to see how these new tables and reports evolve when trying to debug. With the recent update to JMP16, there was an analysis that yielded a table with columns in a different order than JMP15. I resorted to inserting Throw(); at different points in the script to make ad hoc breakpoints.
An ideal solution would be a debugger that is built into the script editor with breakpoints, like most programming IDEs. The spawning of a separate JMP process for debugging is clunky and prevents straightforward debugging of UI-based analyses.