That's a pretty cool idea! Being able to create some sort of free-form package structure would greatly improve the structure of an eSpace in ServiceCenter.

The Screen Flows already give me a way of structuring functionality.

It would in a lot of cases come in handy if I could move certain User actions into a screen flow.

E.g. I have an orders screen flow.
I would like to add a GetNewOrdernumber function so I will be able to create ordernumbers through the exact same procedure in the Orders applications as in a Webservice.
(To our company this is and will certainly be a very common way of code reuse)

Moving this action to the Orders screenflow would put it in the 'right place'.
Also being able to move the Webservice to this screenflow would put it in the 'right place'

This is a good way of keeping the structure simple, grouping the functionality and maintaining an overview.
Besides that it helps eliminating the designing the same function twice by different programmers (together with a good naming convention ofcourse)

Yes.

Would be great to have a folder structure for it.
It would be easy to implement and makes life much easier :)

This would be very handy.

On this way it's also possible to give the folder a screen flow name so all the user actions of that screen flow are in that folder.

Organize user actions by folders on SS tree.

Merged from 'Group user actions by folder within SS tree' (idea created on 09:49 (53 minutes ago) by Ricardo Casaca), on 10:42 (just now) by Paulo Tavares

There a lot of actions which are only used in the context of another action, used to arrange and modulate code. These could be attached as sub-actions of that action, providing most needed action organization.

Merged from 'Sub-Actions, or Actions which exist solely on the context of another Action' (idea created on 11 May (Yesterday) by Gonçalo Veiga), on 18:32 (just now) by Paulo Tavares

This could be handled if the organisation of user-actions is implemented

see https://www.outsystems.com/ideas/36(


Merged from 'Sub-Actions, or Actions which exist solely on the context of another Action' (idea created on 11 May (Yesterday) by Gonçalo Veiga), on 18:32 (just now) by Paulo Tavares

Or you depend on action prefixing for organization sake

Merged from 'Subfolders under "Actions" folder' (idea created on 2010-05-21 11:48:58 by Henrique Matos), on 2010-05-28 10:55:00 by Paulo Tavares

similar to https://www.outsystems.com/ideas/36/


Merged from 'Subfolders under "Actions" folder' (idea created on 2010-05-21 11:48:58 by Henrique Matos), on 2010-05-28 10:55:00 by Paulo Tavares

This is a great idea, and would be very handy.

Asked for years for this one! : )

Wonderful Idea, organize the User's Actions in a folder's schema would be great, similar with what happens in Visual Studio.

Yes please....

Yeah!

And while you're at it, why not make it possible to have variables or some way to store data in these folders that would be shared by the actions in them?

Oh wait, that sounds familiar...

Wish granted!

6.0 introduced the ability to create your own folders for user actions and organize them at will.