Create folder tree

By Eduardo Caetano on 18 Apr 2016
Hi, is important create a folder tree in Logic tab.


J.18 Apr 2016
it's so important you can already do it?

Kilian Hekhuis20 Apr 2016
Well, no, you can add a single folder. Sometimes you'd like more than one level (though having more than two would be questionable). That said, I'm pretty sure this is a duplicate, and there are also many about specific parts (also on data tab).
Justin James23 Apr 2016
This is very much so a duplicate.

J.Ja

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



Merged from '[ServiceStudio] Add more folder depth' (idea created on 2017-05-30 14:18:22 by Patrick Baanvinger), on 2017-08-28 02:58:35 by Justin James

Simulair idea:

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




Merged from '[ServiceStudio] Add more folder depth' (idea created on 2017-05-30 14:18:22 by Patrick Baanvinger), on 2017-08-28 02:58:35 by Justin James
erik berg27 Aug

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



Merged from 'Support for a hierarchy of Server Actions' (idea created on 2017-08-27 18:08:56 by erik berg), on 2017-08-28 02:57:02 by Justin James

Merged from '[ServiceStudio] Add more folder depth' (idea created on 2017-05-30 14:18:22 by Patrick Baanvinger), on 2017-08-28 02:58:35 by Justin James