Hi, is important create a folder tree in Logic tab.

Within ServiceStudio we can create folders within for instance Server Actions to create logical units within an eSpace. This is limited to a depth of one; To keep everything cleaner and organized, I would like more depth...

For instance:

Now:  

Server Actions -> Cache -> ......

Would like: 

Server Actions -> Cache -> Read -> ..

Also on the UX part this would create a cleaner list

Simulair idea:

https://www.outsystems.com/ideas/1000/sandbox-sub-folder-in-actions-folder

When working on a project, the implementation paradigm of OutSystems leads to one of two implementations.

  1.  The big ball of string Server Action, aka one Server Action that has all the required logic to do everything with no reuse of common operations.

  2.  Death by a thousand cuts, aka in an attempt for reuse, functionality is broken down into Server actions with a McCabes complexity of 7 or less.  This lead to a hug list of  Server Actions that are only organized by Name.

Server Actions should be allowed to be

1.  Grouped by an arbitray folder, similar to built to the display that of the OutSystem built in functions.

     MyApp

         Conversion Server Actions

              Entity1ToEntity2 Server Action

              Entity1ToEntity2 Server Action

              Structure1ListToEntity1 Server Action

      Structure Server Actions

               LookUpStructure1

               LookupStructure2

      Lookups

           Lookup Entity1 by Secondardy Key Server Action

           Lookup Structure1 by Primary Key

2.  Allow for ServerActions to have a parent child/relationship at the metadata presentation level or perhaps the even the physical level.

       BigBallOfString ServerAction

               Validate Inputs ServerAction

                Caluculate Outcome ServerAction

                Business Rule 1 Server Action

                Business Rule 2 Server Action

                Save Output Sub Server Action

3.  Automatically create Folders to contain Server Actions for Entities, Structures (interface or .net extension method based of the given Entity/Structure)

                 Structure 1

                    LookupEntityFromStructueKey

                 Entity 1

                    ConvertEntity1ToCustomerAStructure

On Service Studio, add Subfolders to Actions Folders for a better organization of the code.

Would be a nice to have.

Luis

Mmm... I'm not entirely sure that wouldn't quickly lead to 12-level deep nested actions, knowing the knack for organizing most programmers have, but yeah, sometimes a 2nd level is useful :).

Before adding subfolders (which I don't think should be more than 1 level), I would see folders added to images and structures first:

https://www.outsystems.com/ideas/1048/create-folders-inside-images-and-resources

Yes, that too :)

In Service Studio, the actions are sorted alphabetically within a folder. Sometimes, and for readability reasons, it is handy to be able to place related actions next to each other within the same folder. It would be nice if we could do this in the same way that we can reorder individual assignment statements within an assignment.

Right now, we are "forced" to tweak the name of the action to achieve this.

Even though I understand it perhaps, what is the real advantage?

you can create more folders to group them.

furthermore, would you have it per user or global?

Hi Joost, we could indeed create more folders to group them but then we end up with the same problem as the order of the folders can also not be changed. We would have tweak with folder names to get the result desired.

In summary, in service studio we have one single level of categorization for actions, by using folders. If we want to create more levels of categorization, we have to play around with how we name folders and actions. If we could create folders within folders, that would help. Nonetheless, I’m still convinced that being able to set the order would improve readability.

With respect to your second question, I would say that the order would be global and not user dependent but I’m open for arguments in favor of user specific order. 

Hi Pedro,

Indeed I agree with you regarding the problem being having "one single level of categorization for actions".

Actually, this is not a problem specific to actions as you can see the same thing regarding resources, images ou structures.

What we should have (and want in the future) is having folders in more elements in the platform. We collecting and merging all this feedback in this idea:
https://www.outsystems.com/ideas/784/servicestudio-folders-for-entity-and-structure

I'll also merge this one ok?

Cheers

Also, found one related with subfolders:
https://www.outsystems.com/ideas/2694/service-studio-add-subfolders-to-the-actions-section-for-a-better-organization

Hi Vasco, no problem in merging the idea as long as changing the order of actions within a folder and the order of folders within folders is also taken into account ;)

Would be nice if we could create a hierarchy to our taste inside the Server Actions folder. Right now you can only create top level folders and that's already very nice for atomic or core entities, but something like this example would be really useful when you want to organize code for orchestration:

Operation

|---- CRUDS

|---- Calculations

|-----|-----Movements

|-----|-----Customers

This is a duplicate of a highly liked idea.

J.Ja

Hi Folks,

Right now we can add only one level folder inside a folder (in Logic tab), not able to add a folder in web screen(Interface, Data Tabs) 

It's good to have multiple folders inside the folder OR web screen it improve readability and maintainability of the big application.

Pls have a look in the screenshot:

If we are able to add folders inside the folder then we can handle better the big applications where ate 40 OR 50 actions are there.

Hi,

I think it would be interesting for the organization of the actions, the creation of several folders within others, in at least one layer.

No, I would like this functionality to exist in the service studio logics

I request you to add the functionality to create sub folders in DATA component, this may useful to segregate the items and to find easily. For example: in my session variable folder i created many variables for different screens. when i would like to find the desired variable it takes me some time. If I create sub-folders then I can segregate variables according to the screens by creating sub-folders with the screen names.

Hi,

I am not against grouping of stuff in SS, but I am more worried about your use-case.

It's now very wise to have many session-variables. this will hurt your performance.

I like this idea and this is not difficult to do

Rather than having a folder structure, where you have to visually find your component, i would prefer to have a filter where I can type. Same like when you add a server action and start typing and all matching actions show up.

I would think this has been implemented in P11?

I would like to be able to create folder structures with more than one level within the object tree, as this would make it possible to create applications with objects that are better organized and easier to read.

The entire community could benefit from this possibility, mainly using conventions that already exist in other technologies.

At present we can have only 1 level folders to group various actions. Think of adding folder inside floder- nested folders in the service studio

This will help more maintainability