Allow copy/cut + paste of Exceptions

By Justin James on 17 Aug 2015
Since we can't have public Exceptions, would be good to be able to copy/cut + paste Exceptions from one eSpace to another. Even with public Exceptions, this would still be helpful.

J.Ja
João Melo29 Aug 2015
Sometimes I have to refactory my application and move some logic between espaces. But I can't do the same with the user exceptions.

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
Justin James29 Aug 2015
I had this same need a few weeks ago :)

http://www.outsystems.com/ideas/2109/allow-copy-cut-paste-of-exceptions

J.Ja


Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
João Melo29 Aug 2015
Cool.. The ideas must be merged. Can we do this?

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
J.31 Aug 2015
Not us, but the grandmasters!

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
Kilian Hekhuis31 Aug 2015
Well, an exception is only a name and nothing else, so I figure OS just thinks "copy/paste the name already and be done with it" :)

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
João Melo31 Aug 2015
Killian, and when I want to copy 10 (or more) exceptions? Wouldn't it be nice if I could do that at once?

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
Kilian Hekhuis1 Sep 2015
Joao,

10 copies still needs ten copy/pastes. Also, it'd be better imho if exceptions could be public, in which case all this copy/pasting wouldn't be needed. Note that I did Like the idea, as I think everything should be copy/pastable, but the use case is better handled by allowing them to be public.


Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
João Melo1 Sep 2015
Sorry, but I disagree. Think about a refactoring... I need to move 10 actions between espaces to maintain cohesion. Why should I place exceptions in a different one?

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
Kilian Hekhuis1 Sep 2015
Hi João,

Sorry, I misread your previous comment. You are right, if you need to move 10 different exceptions from one eSpace to another, copy/paste would be a time saver. 


Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
Justin James1 Sep 2015
Copy/paste of the name isn't good enough, because when you move the Actions, they are looking for Exceptions that do not exist. You need to go find every error in the destination eSpace, look up the Action in the original eSpace, and see what Exception it was looking for. What a big pain in the neck!

J.Ja


Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis
Kilian Hekhuis1 Sep 2015
That would call for a TrueChange healing...

Merged from 'Move exceptions between espaces' (idea created on 2015-08-29 00:14:41 by João Melo), on 2017-10-18 12:00:26 by Kilian Hekhuis