4
 Followers
342
 Likes

Comment out logic / Disable tools in action flow

Service Studio
On our radar


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.


Created on 4 May 2010
Comments (80)

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.

Well, you could flag disabled-items as true-change info's or something like that
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
I don't mind :)
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
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

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
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

same as, if it's disabling you want

http://www.outsystems.com/wisdomofthecrowds/IdeaComment_List.aspx?IdeaId=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
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.
Merged this idea with 'Block Comments instead of Action comment' (created on 2010-05-19 10:57:55 by Hermínio Mira)
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
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

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
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

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
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
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
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
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
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
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
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
I also think this is simliar to http://www.outsystems.com/WisdomOfTheCrowds/IdeaComment_List.aspx?IdeaId=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
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
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

similar to this idea: http://www.outsystems.com/wisdomofthecrowds/IdeaComment_List.aspx?IdeaId=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
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
Hi Luis,

I think your idea is this, right?

http://www.outsystems.com/wisdomofthecrowds/IdeaComment_List.aspx?IdeaId=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
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
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
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
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
Same idea (I agree, it's a very old idea)  as http://www.outsystems.com/wisdomofthecrowds/IdeaComment_List.aspx?IdeaId=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
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
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

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
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
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
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
old similar item with tons of discussion :)


http://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
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
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
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
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
This idea already exists and has a lot of votes - http://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
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
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
Thanks J.

 Found this : http://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
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
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
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
see http://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
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
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

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

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

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

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

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

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

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

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
(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.
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.