Debug several eSpaces
1401
Views
25
Comments
On our RadarOn our Radar
Debugger

If we are in Debug mode and the action references some action / page from an external eSpace we should be able to continue debugging (at least if we had the 2 eSpaces opened in Service Studio)

That is already possible.

For the referenced eSpace:
- Open it in service studio,
- Set a breadpoint,
- Click debugger and select 'select entry eSpace',
- Click debugging in public area

Now you can call the action from the public property of the selected entry espace and you action will be debugged.
Yeah, but that's not very user friendly, and often it fails for some reason.

It indeed can be more user friendly :).

For me it works every time...

2023-02-10 19-42-59
João Melo
 
MVP
Guys, when I click 'Select entry eSpace', the only option I get is '(this eSpace)'.

What can I do??
João,
You must do that step in the referenced eSpace.
Sometimes you don't see them because the consumers aren't published after publishing the consumer. But such a question should really be in a separate forum thread, not on this idea!
2023-02-10 19-42-59
João Melo
 
MVP
I don't know why, but it worked today... Thanks folks..
It would be better to just turn on the debugger than selecting entry espace.  Its difficult getting debugger to catch.
2023-02-10 19-42-59
João Melo
 
MVP
Totally agree with Rebecca... So it is still an idea!
Also agree with Rebecca, very flaky behaviour, sometimes it works, sometimes it doesn't, depends on how I hold my tongue when starting the debugger I think :)

Few people actually know how the Select Entry Module works. I frequently see people complaining that the breakpoint is not stopping, without realizing they were attached to the wrong module. But it's not their fault, this information is hidden, and the Select Entry Module dialog doesn't provide any help on how to use it:

A few ideas on how to improve it:

- Make 'step into' work even for consumed objects. For example, when stepping into a referenced action, Service Studio would ask for download the producer, set the breakpoint at the start of the action, and attach the debugger to the correct module, before actually stepping into the action. Likewise, 'step out' would need to work consistently across modules.

- Document how to debug producers in the help file. Really.

- Have a more concrete text in the Select Entry Module dialog, helping to choose the correct module, referring to scenarios like debugging a consumed web block, or a consumed action, debugging timers and web services...



Merged from 'Simple debugging of producers' (idea created on 2017-07-27 04:40:45 by Leonardo Fernandes), on 2017-07-28 13:27:59 by Leonardo Fernandes

I would like to just turn on the debugger and then have it stop on breakpoints for espaces I have open.  This is one of the biggest hangups for new developers too.



Merged from 'Simple debugging of producers' (idea created on 2017-07-27 04:40:45 by Leonardo Fernandes), on 2017-07-28 13:27:59 by Leonardo Fernandes
2014-02-07 17-02-43
Vasco Pessanha

Totally makes sense (add another Like) ;)

Also related to this one:
https://www.outsystems.com/ideas/1033/debug-several-espaces


Cheers,



Merged from 'Simple debugging of producers' (idea created on 2017-07-27 04:40:45 by Leonardo Fernandes), on 2017-07-28 13:27:59 by Leonardo Fernandes

You CANNOT get rid of the "Select Entry Espace" step without completely changing the way publishing a producer works. Why? Because each deployed Espace is a separate application in IIS, WAR in JBoss, to attach the debugger to. The system shouldn't attach to ALL deployed applications on the server, that would be nuts.

J.Ja

Merged this idea with 'Simple debugging of producers' (created on 2017-07-27 04:40:45 by leonardo.fernandes)
2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Debugger
Merged this idea with 'Smarter Debugger - Multiple Modules Fast Traveling' (created on 25 Jul 2019 16:49:16 by André Painha)

So, just had a really simple idea.

After having to debug logic divided through several modules, having to set every debugger individually, sellecting each entry module etc, I was thinking... How is this not automated?
So, the idea would be:

If debugging a module and an action gets called from another module, would it be possible for a "Quick-Debug" option (Another F key) that would enter the new module and start the debugging for us, being already on context?


I'm not even sure if that is possible but... Would be great if it were!



This comment was:
- originally posted on idea 'Smarter Debugger - Multiple Modules Fast Traveling' (created on 25 Jul 2019 by André Painha)
- merged to idea 'Debug several eSpaces' on 18 Oct 2019 08:56:34 by Kilian Hekhuis
Changed the category to
Debugger


This comment was:
- originally posted on idea 'Smarter Debugger - Multiple Modules Fast Traveling' (created on 25 Jul 2019 by André Painha)
- merged to idea 'Debug several eSpaces' on 18 Oct 2019 08:56:34 by Kilian Hekhuis

I think this idea was submitted many times before.



This comment was:
- originally posted on idea 'Smarter Debugger - Multiple Modules Fast Traveling' (created on 25 Jul 2019 by André Painha)
- merged to idea 'Debug several eSpaces' on 18 Oct 2019 08:56:34 by Kilian Hekhuis

Hi Rebecca,


I've tried looking for it before posting, and I didn't get any exact match. Maybe I didn't spend enough time doing that. If that is so, apologies, still, if several people asked for it... It's probably worth implementing!


Cheers



This comment was:
- originally posted on idea 'Smarter Debugger - Multiple Modules Fast Traveling' (created on 25 Jul 2019 by André Painha)
- merged to idea 'Debug several eSpaces' on 18 Oct 2019 08:56:34 by Kilian Hekhuis

It's a good Idea. +1



This comment was:
- originally posted on idea 'Smarter Debugger - Multiple Modules Fast Traveling' (created on 25 Jul 2019 by André Painha)
- merged to idea 'Debug several eSpaces' on 18 Oct 2019 08:56:34 by Kilian Hekhuis

+1

Maybe it's a good option to just upvote it instead of making a comment with only +1

I suppose everyone posting a +1 is also upvoting it, would be a bit silly otherwise :).