So I have a number of Automations that I call in sequence from a parent automation.. Pressing F10 I expect to step OVER the child automation, as I don't want/need to debug those routines. However Visual Studio steps INTO the automation(s) why? Without setting a million breakpoints, how can I ge the F10 Step over to work properly... It does in C#??
F10 really just means "stop on yellow lines". F11 will go to both yellow and blue execution lines. Unfortunately, there's no way to step over an entire automation. Your suggestion of adding breakpoints after the automations you wish to pass by (and clicking F5) is really the only way to do that.
Posted: 4 years ago
Posted: 16 Oct 2019 12:01 EDT
Robert Fleming (RobIsTheName)
Senior Manager, Process Automation
I know that. That's what I'm forced into doing. What sucks is that it leaves with a whole, bunch of break points, I have to clear later. up to 8 clicks to set, jump to/through, remove, disable, etc... And in the end the most important bit of code I'm trying to debug, I miss! Because all the extra reds have confused me to the point that I'm now distracted with always clean up the points I don't need, or trying to step out of an function I didn't want to step into in the first place... UGH!
F10 in any other Microsoft language steps OVER the function, not into... Wish Pega would improve it's debuggering experience.
Posted: 3 years ago
Posted: 24 Jan 2020 10:38 EST
Thomas Sasnett (ThomasSasnett)
Lead Robotics Architect
I know this isn't ideal, but a trick I've found with breakpoints is to simply delete them all in one shot. Make sure all your automations are closed (right-click on any open tab in the interface and select close all documents) and then from the Debug menu is an option to delete all breakpoints. Obviously, this doesn't help if you are wanting to keep them intact, but if you tend to work on one issue at a time, this might be helpful.
I'll certainly mention this to our product team at the next opportunity I have though.