Back to Ideas
357
Like
Follow Idea
2016-04-21 20-09-55
J.
 
MVP
Comment out logic / Disable tools in action flow
8626Views
103Comments
Implemented
Service Studio
Development Environment 11.0.109.0


Sometime you work on a certain part and are not able to finish certain parts, or want to skip certain parts, like complex queries.

Then it would be great to disable or, comment out certain tools in the action flow. so you don't have to worry about them now.

Perhaps they are not complete yet, or unusable.


With an if-block, it would always follow the true-line, it would skip the for-each etc. etc.


04 May 2010
Copy link to comment

I think this could be a great idea, there is only one thing to think about:

If you validate (true change) the espace, you can't be able to run/ publish the espace, because there are some items disabled. On this way it will be prefented that developers 'forget' to finish the flow later.
06 May 2010
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP

Well, you could flag disabled-items as true-change info's or something like that
08 May 2010
Copy link to comment
Hi Joost,

This is a great idea, and I was just searching for it by "comment" but wasn't able to find it.

I hope you don't mind, but I edited the title of the idea, because it wasn't clear from the title.

Cheers,
Paulo Tavares
20 May 2010
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
I don't mind :)
21 May 2010
Copy link to comment
When you work in a text-based program language like f.i. Java then you have the possibility to place comment markings around your code to deactivate it. 

This is very handy in a test situation where you want to test a new idea but want to keep the existing code.

The workaround in OS on the moment is to use an IF statement but I would like to see a more sophisticated approach : )

Merged from 'De-activate code parts' (idea created on 2010-07-12 10:00:37 by Hans Bruins), on 2010-08-30 15:05:45 by Paulo Tavares
12 Jul 2010
Copy link to comment
Or even when you can't complete the action right away and want to leave it for later, as it is right now you can't compile it and keep working.

Merged from 'De-activate code parts' (idea created on 2010-07-12 10:00:37 by Hans Bruins), on 2010-08-30 15:05:45 by Paulo Tavares
13 Jul 2010
Copy link to comment

It should be possible to comment some code so the operations would be skipped. This way, when testing something, it wouldn't be needed to delete the code :)


Merged from 'Comment Code' (idea created on 2010-08-19 12:30:16 by Miguel Ribeiro), on 2010-08-30 15:06:46 by Paulo Tavares
19 Aug 2010
Copy link to comment
I would prefer that it be thought of as "disable" a piece or section of Action flow, rather than "commenting it out", commenting stuff out is a crutch in traditional systems to compensate for the lack of metadata attached to lines of code. :)

J.Ja

Merged from 'Comment Code' (idea created on 2010-08-19 12:30:16 by Miguel Ribeiro), on 2010-08-30 15:06:46 by Paulo Tavares
23 Aug 2010
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP

same as, if it's disabling you want

https://www.outsystems.com/ideas/57/


Merged from 'Comment Code' (idea created on 2010-08-19 12:30:16 by Miguel Ribeiro), on 2010-08-30 15:06:46 by Paulo Tavares
23 Aug 2010
Copy link to comment
After copying the template there are some features that you may want to keep temporarily but would like to test other changes as you work.  However, outsystems doesn't allow you to publish with errors.  It would be nice to disable these actions with errors so that you can publish.  Then maybe add a warning saying that an action has been disabled.

Merged from 'Ability to mark actions as disabled.' (idea created on 2010-06-24 20:22:33 by Rebecca Hall), on 2010-10-29 17:27:43 by Paulo Tavares
24 Jun 2010
Copy link to comment
It would be a great feature in Service Studio the possibility to comment/disable one or more flow elements.
Sometimes I need to test an action without a part of the flow, and it would be much faster if I could comment the flow elements I want instead of adding some conditions or in the worst case delete them. 

Merged from '[Service Studio] Comment/Disable flow elements' (idea created on 2010-07-01 18:56:45 by Carlos Henriques), on 2010-07-08 16:45:45 by Paulo Tavares

Merged from 'Ability to mark actions as disabled.' (idea created on 2010-06-24 20:22:33 by Rebecca Hall), on 2010-10-29 17:27:43 by Paulo Tavares
01 Jul 2010
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP

similar to this idea: https://www.outsystems.com/ideas/57/


Merged from '[Service Studio] Comment/Disable flow elements' (idea created on 2010-07-01 18:56:45 by Carlos Henriques), on 2010-07-08 16:45:45 by Paulo Tavares

Merged from 'Ability to mark actions as disabled.' (idea created on 2010-06-24 20:22:33 by Rebecca Hall), on 2010-10-29 17:27:43 by Paulo Tavares
07 Jul 2010
Copy link to comment
I love this idea.
Beeing able to disable/comment user actions, screen actions and parts of the business flow is a must.

The true change engine could help the programmers to not forget by issuing a warning. These warnings would be hideable like the others, of course.
09 Feb 2011
Copy link to comment
I would really like to be able to create a comment and associate it to a block of code instead of an action, this way I would be able to accurately say what belongs to that comment.

example:



Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
19 May 2010
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
oh nice idea!

yeah like that.

hmm, come to think of it. something like #region so you can collapse it even?



Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
19 May 2010
Copy link to comment

Lets try just the basic first! :D


Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
19 May 2010
Copy link to comment
Good idea.
The solution I use for this is to "define" an entry point and an exit point of the block I want to comment and then define arrows from the comment to those points.



Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
19 May 2010
Copy link to comment

This would be a great additional to the comment line structures!


Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
20 May 2010
Copy link to comment
Hi Tiago,

You can do that but you lose the description for that action, and I really would like to avoid that.

Cheers


Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
20 May 2010
Copy link to comment
Hello Herminio,
I really don't label the actions "Block Entry Point" and "Block Exit Point". Maybe I should have written "<Block Entry Point>" and "<Block Exit Point>" to make it more clear that those actions just stand as entry and exit points for the block of flow. Hope I made myself clear this time.


Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
20 May 2010
Copy link to comment
It could be like a rectangle we could draw around flow elements, and they would be automatically associated with it. If we drag the container the elements should move with it, and if we delete it, it should delete all elements inside it.
Basically it's like a region and could have a title property, marking the start of a subprocess inside an action.
 
It could have some style options to differentiate from other containers, like background color, or border style.

And a great feature would be comments inside a container, wich would be great for documentation.


Merged from '[Service Studio] Containers inside actions' (idea created on 2010-07-01 19:05:11 by Carlos Henriques), on 2010-07-08 16:13:06 by Paulo Tavares

Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
01 Jul 2010
Copy link to comment
2016-11-21 23-23-05
Gonçalo Borrêga
Hi Carlos,

I like your ideia... but on the other hand... shouldn't this "subprocess within an action" just be moved to a new action? You'll have the comments on the action. If visibility is the concern then, as I see it, a tooltip with an image of the inner action could do the trick

Cheers

Merged from '[Service Studio] Containers inside actions' (idea created on 2010-07-01 19:05:11 by Carlos Henriques), on 2010-07-08 16:13:06 by Paulo Tavares

Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
02 Jul 2010
Copy link to comment
2016-11-21 23-23-05
Gonçalo Borrêga
I use this sometimes:


Being able to move the comment block around with all the inner elements (something like fences)  and being able to collapse them (as #regions) would be great.

Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
02 Jul 2010
Copy link to comment
2016-11-21 23-23-05
Gonçalo Borrêga
I also think this is simliar to https://www.outsystems.com/ideas/157/

Merged from '[Service Studio] Containers inside actions' (idea created on 2010-07-01 19:05:11 by Carlos Henriques), on 2010-07-08 16:13:06 by Paulo Tavares

Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
02 Jul 2010
Copy link to comment
That "subprocess" could be just one or two referenced actions.

In a screen action my flow can start with validations, then get some data I will need after, use some referenced actions that do integration with an external application, do some internal actions, send email, etc.

With all this we can get a big flow, and would be nice if e could use some containers to clearly identify each part of the flow, like:

START
-- start of validation --
- element#1
- element#2
- element#3
----------------------------
-- GET DATA --
- element #4
----------------------------
-- EXTERNAL APP INTEGRATION
- element#5
- element#6
----------------------------

This are basically regions, but could be more than that on Service Studio, with some cool features.

It's close to that idea, although that one focus on comments.
But yes, they could be merged.

Merged from '[Service Studio] Containers inside actions' (idea created on 2010-07-01 19:05:11 by Carlos Henriques), on 2010-07-08 16:13:06 by Paulo Tavares

Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
02 Jul 2010
Copy link to comment
Very nice "workaround" to use  "block comments".

Merged from 'Block Comments instead of Action comment' (idea created on 2010-05-19 10:57:55 by Hermínio Mira), on 2011-03-26 17:39:15 by Rodrigo Castelo
02 Jul 2010
Copy link to comment
Have you ever been messing around with 2 ou 3 solutions for what you want to implement, just to figure out which one is best? Within the ServiceStudio you can only have "active" logic so you aren't able to have all the solutions on the project and to activate them one at a time.

My idea is to give the user ability to disable code, so it won't be processed by the ServiceStudio interpreter and hence not giving all those errors!



Merged from 'Ability to disable logic without deleting it' (idea created on 2011-07-10 12:27:01 by Luís Pedro Fernandes), on 2012-06-19 10:30:06 by Miguel Melo
10 Jul 2011
Copy link to comment
Hi Luis,

I think your idea is this, right?

https://www.outsystems.com/ideas/57/

Merged from 'Ability to disable logic without deleting it' (idea created on 2011-07-10 12:27:01 by Luís Pedro Fernandes), on 2012-06-19 10:30:06 by Miguel Melo
11 Jul 2011
Copy link to comment
Yeah, i searched but didn't find it!

Thanks

Merged from 'Ability to disable logic without deleting it' (idea created on 2011-07-10 12:27:01 by Luís Pedro Fernandes), on 2012-06-19 10:30:06 by Miguel Melo
11 Jul 2011
Copy link to comment
You mean like comment block?


/*

this is a comment block

*/

OR

// this line is a comment


I think this would be great! maybe we can highlight the actions in ServiceStudio, then right click on "disable" and it will grey out all the actions.?

Merged from 'Ability to disable logic without deleting it' (idea created on 2011-07-10 12:27:01 by Luís Pedro Fernandes), on 2012-06-19 10:30:06 by Miguel Melo
15 Jul 2011
Copy link to comment
Yeah, just like that. And the logic wouldn't need to be complete, it would gray out and just sit there until we need it.

It shouldn't also count for the espace SBU's! :P

Merged from 'Ability to disable logic without deleting it' (idea created on 2011-07-10 12:27:01 by Luís Pedro Fernandes), on 2012-06-19 10:30:06 by Miguel Melo
16 Jul 2011
Copy link to comment
(Note: Using Service Studio 5.1)
This also could apply to web screens: There should be a way to disable web screens.

We use test web screens to test not public actions' implementation. When the test screen is not needed anymore instead of beeing deleted it could be disabled, so it doesn't consume Software Units.
The test web screens could be created in a test espace that most of the time would be disabled, but with this solution the actions would necessarily have to be public so that they can be cosumed by the test espace.
03 Dec 2012
Copy link to comment
When programming in .Net or Java you can comment your code to use later.
The idea is to be able to do the same in the Flow Action Editor, so that you don't have to save your logic on another place, or if your logic has an error detected by True Change, you can comment that logic for a while and be able to publish your solution without deleting it.

Merged from 'Comment part of an Action Flow' (idea created on 2012-09-27 15:06:16 by João Costa), on 2013-04-04 16:10:23 by Gonçalo Borrêga
27 Sep 2012
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
Same idea (I agree, it's a very old idea)  as https://www.outsystems.com/ideas/57/

Merged from 'Comment part of an Action Flow' (idea created on 2012-09-27 15:06:16 by João Costa), on 2013-04-04 16:10:23 by Gonçalo Borrêga
28 Sep 2012
Copy link to comment
Thanks!

Merged from 'Comment part of an Action Flow' (idea created on 2012-09-27 15:06:16 by João Costa), on 2013-04-04 16:10:23 by Gonçalo Borrêga
28 Sep 2012
Copy link to comment
2014-04-28 10-19-39
Wayne Hodgson
I would also like to comment out or disable pieces of code because I do not want to remove them and recreate them later.  What about using something like what is used to set a breakpoint in the debugger to flag to ignore an action.  Maybe the platform could add the conditional ifs with out you cluttering up your code. Then list these as information messages when publishing.  I also would not like to see any incompatible or unreferenced resources if these actions are commented out.
11 Feb 2014
Copy link to comment
Has there been movement here in allowing us to mark an action as inactive? 
14 Jul 2014
Copy link to comment
Hello everybody would be able useful to comment objects inside a flow, without having to remove the object from the flow. Sometimes we want to test one situation or another, and we need to hold back in a more immediate and not through version control form. The objects with mark "comment" don't generate any code. Need to comment objects like simple query, advanced and others.

Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
02 Sep 2014
Copy link to comment

I would add that we should know if it will affect something more in the code. See the same warnings and errors as if it had been deleted.

Usually what we do is to put it in the False branch of an invalid condition. That way it isn't deleted, but is also never used. And we don't notice if it is used somewhere because it would still exist.

And if you want to switch between two version of the same object, you have to mark both as comments to switch. You can't have two elements with the same name simoultaneously.

Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
02 Sep 2014
Copy link to comment
Hi Nuno,

Here we are using this alternative too, for comment aour code, and I agree with your point of view, that we have all the benefits of the platform code validations. But I think the Alexandre suggestion is a good idea. As far as I know, when the Outsystems compiler generate the code (Java or C#) all comments are discarded, which gives us a cleaner and take code, minimizing the compiled binary size. Am I right?

Another interesting aspect is that sometimes we have the need to comment a particular code, when there is some incompatibility of a given piece of code, with some components, probably has been updated or deleted. This artifice gives us the possibility to evaluate more easily which made the invalid code.

Cheers,

BN

Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
02 Sep 2014
Copy link to comment
There is at least one other item out there already, this should be merged into it.

J.Ja


Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
02 Sep 2014
Copy link to comment
Hi Nuno I understand your solution,  but I understand that this is a way to circumvent the lack of feature I mentioned.

Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
02 Sep 2014
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
old similar item with tons of discussion :)


https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow/


Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
03 Sep 2014
Copy link to comment
So lets say I am working on a flow in an action and I want to be able to comment out or "skip" an widget in that action.  The action might have an error that I am working on but for whatever reason I want to compile the project and just pretend that that widget is not in the flow without having to completely delete it (think an advanced sql query that I don't want to have to copy/paste or worse lose the sql I have written).  So I could click on that widget in the flow, select "skip" and the line with bend around the widget and the widget would grey out.

Merged from 'ability to "skip" or comment out a widget in an action' (idea created on 2014-09-12 16:42:26 by Jason Herrington), on 2014-09-23 22:45:47 by Gonçalo Borrêga

Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
12 Sep 2014
Copy link to comment
Repeat of an oft-posted idea. :(

J.Ja


Merged from 'ability to "skip" or comment out a widget in an action' (idea created on 2014-09-12 16:42:26 by Jason Herrington), on 2014-09-23 22:45:47 by Gonçalo Borrêga

Merged from 'Able to comment objects: Actions, simple query, advanced query, if and etc.' (idea created on 2014-09-02 14:49:08 by Alexandre Costa), on 2014-09-23 22:47:57 by Gonçalo Borrêga
12 Sep 2014
Copy link to comment
It would be very nice to be able to disable/comment out sections of action work flows. I can't tell you how many times I wish I could do this.
13 May 2015
Copy link to comment
I would love it if I could disconnect a section of a workflow from the main flow and disable/comment it out so my application would still 1 click publish. This is something that developers do all the time when programming and it would be super nice if we could do the same thing with our workflows.
13 May 2015
Copy link to comment
This would be amazing if they did this.  So often I want to "try something else", but don't want to lose the original flow.  If I just pull it out of the main flow, it won't compile of course.  I would love this!
13 May 2015
Copy link to comment
Agree: 1) be able to disable an action and see it grey out. 2) be able to "park" code on a flow that doesn't run e.g. from the scenarios above, I'm trying something else, so I create a disabled flow (greyed and commented of course). 3) code fixing - I don't want to delete the code I've changed, I want to keep it handy in case - could be a temporary fix that needs to be rolled back - as in 2) I want to create a disabled flow and comment appropriately. These fixes would improve efficiency and make long-term maintenance easier. Comment space for a changes log in each action would be useful too. Who, when and what.
12 Sep 2015
Copy link to comment
Another "hack" I found is to create a User Exception that is never called and move my test code under it.
14 Sep 2015
Copy link to comment
2014-08-06 17-57-15
Claudio Lichtenthal
Many times one creates a lot of code but wants it to be disabled and yet not deleted ...
It would be great to be able to disable this code but still keep it in the Action.
Example:
v1 + v2;
When commented out:
/* v1 + v2; */
(Idea on behalf of Burton)


Merged from 'Service Studio: Allow to comment out code' (idea created on 2015-11-23 17:50:03 by Claudio Lichtenthal), on 2015-11-26 09:59:21 by Goncalo Borrega
23 Nov 2015
Copy link to comment
Yes this will help

Merged from 'Service Studio: Allow to comment out code' (idea created on 2015-11-23 17:50:03 by Claudio Lichtenthal), on 2015-11-26 09:59:21 by Goncalo Borrega
24 Nov 2015
Copy link to comment
This idea already exists and has a lot of votes - https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow

Merged from 'Service Studio: Allow to comment out code' (idea created on 2015-11-23 17:50:03 by Claudio Lichtenthal), on 2015-11-26 09:59:21 by Goncalo Borrega
24 Nov 2015
Copy link to comment
My first gripe with this great platform. I would like to disable logic as commenting out is kinda for source and this is Pseudocode, I would like the logic objects icons to change to greyed versions and the generator and TrueChange to simply ignore them.
26 May 2016
Copy link to comment
Can't quite believe this does not exist for a mature product...there must really be some hurdles to implement it by the OS 

Speed developing agile etc how are you meant to do iterative programming quickly generate and deploy to test your changes etc...I am bored already of deleting elements and having to reinstate them...and with out a private ide cheat sheet / Clipboard there is no where you can copy and paste the elements to? Parking the code else where on the canvas hack means the code is still generated which can not be a good thing!


As a Outsystems Developer I would like to within Action Flow Editor I want to be able to select multiple elements on the Content Canvas and right button click and sleect a new option called "Comment Out" from the right context menu which will grey out the selected elements icons and cease to generate the applicable code.

As a Outsystems Developer I would like to within Action Flow Editor I want to be able to select multiple elements on the Content Canvas and right button click and select a new option called "Comment In" from the right context menu which will reinstate any commented out  selected elements.

I seem not to be able to add comments to the previous https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow and fell for adding a lengthy comment a few times and losing the comments, so start another one, shot me.

Merged from 'Comment Out/In Action Flow Elements' (idea created on 2016-07-05 23:33:12 by George Jeffcock), on 2016-07-06 09:03:14 by Goncalo Borrega
05 Jul 2016
Copy link to comment

It's unbelievable that this idea has been posted since 2010 but we still doesn't have a way to comment out things in our logics.

12 Oct 2016
Copy link to comment
13 Oct 2016
Copy link to comment
It would be great to be able to "comment out" parts of an action similar to the way you would when writing code.  

Currently the only way to test without a part of the functionality is either delete it from the code or add a forced if function.

Merged from 'Commenting code in actions' (idea created on 2016-05-20 16:48:40 by Daniel Asserati), on 2016-10-24 17:05:30 by Goncalo Borrega
20 May 2016
Copy link to comment
see https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow

Merged from 'Commenting code in actions' (idea created on 2016-05-20 16:48:40 by Daniel Asserati), on 2016-10-24 17:05:30 by Goncalo Borrega
21 May 2016
Copy link to comment
One of the first Ideas, with 221 Likes!

Merged from 'Commenting code in actions' (idea created on 2016-05-20 16:48:40 by Daniel Asserati), on 2016-10-24 17:05:30 by Goncalo Borrega
24 May 2016
Copy link to comment
Comment values in assignments for quick testings and filters. Use a comment box to put logic inside them to test another ways, without losing the oldest attempts. 


Merged from 'Comment Assignments, Filters and Logic' (idea created on 2016-05-17 11:47:25 by João Cardoso), on 2016-10-24 17:29:16 by Goncalo Borrega
17 May 2016
Copy link to comment
This has been suggested for a long time.  Look at the most liked comments and you'll see it.  It has 219 likes at this time.

Merged from 'Comment Assignments, Filters and Logic' (idea created on 2016-05-17 11:47:25 by João Cardoso), on 2016-10-24 17:29:16 by Goncalo Borrega
17 May 2016
Copy link to comment
Hi,

It would be great to be able to deactivate/disable/comment parts of a process flow while designing the logic of an application. In normal coding, how many of you leave "old code" commented just in case you need it, or even to try a different approach on something, but not losing what you've already done?

If we could select some actions or sections of the process flow and "deactivate" them would allow us to try something and revert to the original "code" by simply reactivating those sections.

Regards,
Paulo


Merged from 'Deactivate/Disable/Comment actions in process flows' (idea created on 2016-02-17 17:49:52 by Paulo Sebastião), on 2016-10-25 08:09:19 by Goncalo Borrega
17 Feb 2016
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP
please search for similar ideas.
 this has been proposed a couple of times

Merged from 'Deactivate/Disable/Comment actions in process flows' (idea created on 2016-02-17 17:49:52 by Paulo Sebastião), on 2016-10-25 08:09:19 by Goncalo Borrega
18 Feb 2016
Copy link to comment
Thanks J.

 Found this : https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow

Merged from 'Deactivate/Disable/Comment actions in process flows' (idea created on 2016-02-17 17:49:52 by Paulo Sebastião), on 2016-10-25 08:09:19 by Goncalo Borrega
18 Feb 2016
Copy link to comment

Comment certain portion of logic instead of deleting it. Suppose if you want to write/update the existing logic, you need to update current one. Instead of that just comment the existing one and create/update with new logic




Merged from 'Comment Portion of code' (idea created on 2017-05-11 03:51:35 by Sunil Mane), on 2017-05-12 10:41:40 by André Vieira
11 May 2017
Copy link to comment

This idea was suggested here -
https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow seven years ago.  Please like that one and maybe on the tenth anniversary it will get implemented.  

<< Not trying to be derogatory but having these popular ideas see no activity for a ridiculous amount of time just irks me >>




Merged from 'Comment Portion of code' (idea created on 2017-05-11 03:51:35 by Sunil Mane), on 2017-05-12 10:41:40 by André Vieira
11 May 2017
Copy link to comment

Currently, we simply use an IF statement  'FALSE'

Can't believe this idea has still NOT been actioned!

31 Oct 2017
Copy link to comment
2016-04-21 20-09-55
J.
 
MVP

well, tbh, I understand why it's hard to implement.. you have to check even more if aggregates can be assigned to listrecords etc..


01 Nov 2017
Copy link to comment

During my project development ,I came across situation where I have remove the action method as it was dependent in different module which was under development .Instead I have to implement a dummy action to test my logic .I don't want to remove the action but since I have to test my application and I cannot publish my module because of error I have to do so. Can't we just disable the action for now or make it some kind of inactive so that its not affecting my current work and allow publishing (even having error but not affecting my current work).




Merged from 'Disabling or making a Server Action inactive to allow publishing of module even having error in it.' (idea created on 2017-11-27 09:09:30 by Being.pandey), on 2017-12-03 08:49:39 by leonardo.fernandes
27 Nov 2017
Copy link to comment

There should be something in Service Studio that should allow developers to disable some of the logic just like we can do in programming languages by commenting that part of the code, that can help in testing and implementing new things much easier.



Merged from 'Disable some part of the Logic similar to commenting out code' (idea created on 2016-11-18 19:00:28 by Gurvinder Singh), on 2018-01-17 16:37:16 by Vasco Pessanha
18 Nov 2016
Copy link to comment

Duplicate of: https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow


J.Ja



Merged from 'Disable some part of the Logic similar to commenting out code' (idea created on 2016-11-18 19:00:28 by Gurvinder Singh), on 2018-01-17 16:37:16 by Vasco Pessanha
19 Nov 2016
Copy link to comment

This would be very useful ..  analogous to the functionality in Knime and Pipeline Pilot. Would make development more expedient.

https://www.knime.com/knime-analytics-platform


27 Feb 2018
Copy link to comment
Merged this idea with 'Block Comments instead of Action comment' (created on 2010-05-19 10:57:55 by Hermínio Mira)
26 Mar 2011
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Frontend
28 Jun 2018
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Service Studio
28 Jun 2018
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Merged this idea with 'Allow Unused Objects in Action Flows' (created on 05 Jul 2018 09:48:38 by Russell Codd)
06 Jul 2018
Copy link to comment

When editing an action flow it would be useful if you were able to mark objects as 'disabled' in some way so that they could still be present in the flow screen without causing errors.

This would allow you to skip over portions of logic, for example, without having to disconnect the connectors.

In addition, when copying actions between flows, it would be useful to be able to place them on the action flow screen in some kind of holding area that would also not generate errors because the pasted flow or action is not connected in correctly. This 'holding area' could even be a tool you drag in to the screen and then place the components inside.

It would perhaps be useful for the Performance Suggestions to show that there are screens with unused components in as well.



Merged from 'Allow Unused Objects in Action Flows' (idea created on 05 Jul 2018 09:48:38 by Russell Codd), on 06 Jul 2018 14:27:11 by Vasco Pessanha
05 Jul 2018
Copy link to comment

Actually, I like this idea.
Not having to delete and reimplement code, or move coding around to test something during development would be a really nice feature.



Merged from 'Allow Unused Objects in Action Flows' (idea created on 05 Jul 2018 09:48:38 by Russell Codd), on 06 Jul 2018 14:27:11 by Vasco Pessanha
05 Jul 2018
Copy link to comment

As a brand new developer to Outsystems, a lot of what I'm currently doing is to copy flows from existing modules and paste it alongside one of my flows - either to compare my flow against another, or to chop in certain bits of what I need.

I hope my idea gave a couple of suggestions as to how it might be implemented from a user perspective so that I can see whether the errors are from my flow or not, and having 'floating/orphaned' components not prevent me from publishing.



Merged from 'Allow Unused Objects in Action Flows' (idea created on 05 Jul 2018 09:48:38 by Russell Codd), on 06 Jul 2018 14:27:11 by Vasco Pessanha
05 Jul 2018
Copy link to comment

To prevent situations like this:


:)


25 Jul 2018
Copy link to comment
Merged this idea with 'Add Enable/Disable for Actions on the flow' (created on 25 Aug 2018 08:07:42 by omid ghanbari)
26 Aug 2018
Copy link to comment

hi there

suppose you designed complex flow behind button click or client action, some times you need to disable some actions on flow but you do not want to disconnect or delete them because you want they stay there but temporary you disabled them for troubleshoot or etc and after that you can enable them again ,now you have to delete them because there is no way to keep and after while you will forget what was actions you want to restore them.

regards,

omid ghanbari



This comment was:
- originally posted on idea 'Add Enable/Disable for Actions on the flow' (created on 25 Aug 2018 by omid ghanbari)
- merged to idea 'Comment out logic / Disable tools in action flow' on 26 Aug 2018 20:23:56 by Justin James
25 Aug 2018
Copy link to comment
Merged this idea with 'Commenting out widgets in logic' (created on 31 Aug 2018 19:06:36 by David Schuler)
03 Sep 2018
Copy link to comment

An attribute could be added to each logic widget that would cause the widget to be ignored at execute time, effectively commenting it out.



This comment was:
- originally posted on idea 'Commenting out widgets in logic' (created on 31 Aug 2018 by David Schuler)
- merged to idea 'Comment out logic / Disable tools in action flow' on 03 Sep 2018 02:31:13 by Justin James
31 Aug 2018
Copy link to comment

It wold be very helpfull! I think this is the first thing anyone realizes when they start developing in OutSystems.

18 Sep 2018
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Changed the status to
Implemented
on 26 Sep 2018

Hey guys,

I'm glad to announce that, with the release of OutSystems 11, you can now disable code with a simple right-click!

As usual, a special thank you to the idea creator, Joost, in our release notes.

Don't forget to check OutSystems 11 what's new to see all the new features that were released:

https://success.outsystems.com/Documentation/11/New_in_OutSystems_11

26 Sep 2018
Copy link to comment

So happy this has been put in, will make a big difference to creating in the IDE :)

27 Sep 2018
Copy link to comment

wow

27 Sep 2018
Copy link to comment
Merged this idea with 'have possibility to have code commented' (created on 09 Oct 2018 12:48:48 by Mykola (Nick) Tkachenko)
01 Jan 2019
Copy link to comment

It would be a big help to have ability to comment some flows. It can be separate flow on action like for exceptions. can be greed out or semitransparent and won't be compiled or under "true change". Just to have possibility to leave some tips or explanations, or alternative code that can be used later or temporary for reference.



This comment was:
- originally posted on idea 'have possibility to have code commented' (created on 09 Oct 2018 by Mykola (Nick) Tkachenko)
- merged to idea 'Comment out logic / Disable tools in action flow' on 01 Jan 2019 18:51:12 by Tiago Leão
09 Oct 2018
Copy link to comment

How is this different from the existing Comment widget? Does it not work in a scenario you need it to?

J.Ja



This comment was:
- originally posted on idea 'have possibility to have code commented' (created on 09 Oct 2018 by Mykola (Nick) Tkachenko)
- merged to idea 'Comment out logic / Disable tools in action flow' on 01 Jan 2019 18:51:12 by Tiago Leão
10 Oct 2018
Copy link to comment
UserImage.jpg
Pedro Sousa

In OutSystems 11 you can now disable elements in a flow.



This comment was:
- originally posted on idea 'have possibility to have code commented' (created on 09 Oct 2018 by Mykola (Nick) Tkachenko)
- merged to idea 'Comment out logic / Disable tools in action flow' on 01 Jan 2019 18:51:12 by Tiago Leão
10 Oct 2018
Copy link to comment

THat is exactly what I was needed :) missed that 11 features list. Thanks! 



This comment was:
- originally posted on idea 'have possibility to have code commented' (created on 09 Oct 2018 by Mykola (Nick) Tkachenko)
- merged to idea 'Comment out logic / Disable tools in action flow' on 01 Jan 2019 18:51:12 by Tiago Leão
10 Oct 2018
Copy link to comment
Merged this idea with 'Add an "Ignore" object (like a traditional comment that can be added to the logic flow)' (created on 28 Aug 2016 11:32:17 by trevor smith)
12 Feb 2019
Copy link to comment

In traditional coding I comment out blocks of code that I don't want but I want to keep just incase I need to revert.  In Outsystems a comment is literally a comment .   I would like to be able to place an Ignore object on the flow diagram ....   you could do it with an end but inserting an end leaves disconnected code which the compiler won't accept.



This comment was:
- originally posted on idea 'Add an "Ignore" object (like a traditional comment that can be added to the logic flow)' (created on 28 Aug 2016 by trevor smith)
- merged to idea 'Comment out logic / Disable tools in action flow' on 12 Feb 2019 12:56:16 by Justin James
28 Aug 2016
Copy link to comment

This idea has been around a long time in various forms.  A quick search shows this one -
https://www.outsystems.com/ideas/57/comment-out-logic-disable-tools-in-action-flow - dating back to 2010.  Add your 'like' to that!



This comment was:
- originally posted on idea 'Add an "Ignore" object (like a traditional comment that can be added to the logic flow)' (created on 28 Aug 2016 by trevor smith)
- merged to idea 'Comment out logic / Disable tools in action flow' on 12 Feb 2019 12:56:16 by Justin James
29 Aug 2016
Copy link to comment

239 Likes, and counting...



This comment was:
- originally posted on idea 'Add an "Ignore" object (like a traditional comment that can be added to the logic flow)' (created on 28 Aug 2016 by trevor smith)
- merged to idea 'Comment out logic / Disable tools in action flow' on 12 Feb 2019 12:56:16 by Justin James
02 Sep 2016
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Merged this idea with 'if custom' (created on 08 Apr 2019 18:33:36 by gyndaniel)
09 Apr 2019
Copy link to comment

Hello guys,
The idea is this:
Thesis:
Usually we have to test a particular function and put a true if. see anexo.jpg.

Idea: allow to place an if in red color so that visualization is easy and to remove such function when it is no longer used. See in the anexo.jpg



This comment was:
- originally posted on idea 'if custom' (created on 08 Apr 2019 by gyndaniel)
- merged to idea 'Comment out logic / Disable tools in action flow' on 09 Apr 2019 10:21:53 by Vasco Pessanha
08 Apr 2019
Copy link to comment

Outsystems 11 allows you to comment out the unused code.



This comment was:
- originally posted on idea 'if custom' (created on 08 Apr 2019 by gyndaniel)
- merged to idea 'Comment out logic / Disable tools in action flow' on 09 Apr 2019 10:21:53 by Vasco Pessanha
08 Apr 2019
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Changed the status to
New

Hi.
Which version are you using? Did you know that in OutSystems 11 you have the ability to disable elements in the flow so that you can test parts of the flow and later on remove them?

This was actually submitted in another community idea:
https://www.outsystems.com/ideas/57/

I'll merge both the ideas.

Thanks a lot for your ideas, keep them coming!



This comment was:
- originally posted on idea 'if custom' (created on 08 Apr 2019 by gyndaniel)
- merged to idea 'Comment out logic / Disable tools in action flow' on 09 Apr 2019 10:21:54 by Vasco Pessanha
09 Apr 2019
Copy link to comment

Hi
I actually did not want to disable just dialing it from another color.
So I can put a red if that means for example a priority stream ...

09 Apr 2019
Copy link to comment