SC folder actions

[JonL]

Same as we have global actions, but for folders.

The action steps added to the account folder json file (api/account/folder.json) would be inserted (if it exists) after globals and before any of the individual files.

Global SC -> Folder SC -> File SC
/modules/global.json -> /account/folder.json -> /account/getUser.json

[George]

We did had the same idea some time ago, but there were some disadvantages:

Do we really need to Server Restrict every single Server Action we want to protect?

We did introduce the global action that always run first. So common logic you can put in there. Similar idea is also to have common action per folder indeed. But should it execute for server actions directly under this folder or any children even nested ones. Although it does sounds great when we consider it, it does have some disadvantages. Most important one is that you loose any overview of which actions ran automatically before the current one. People already have trouble with single glo…

[JonL]

I think that could be solved in the UI.

At the beginning of the file workflow you could add two contracted nodes(global and folder) that are expandable and contain the steps. These steps would not be editable. Visually you could make them a bit traslucid by lowering alpha or something similar.

Double clicking on the nodes would open global.json and folder.json SC flows.

It would also improve the UX in the data pickers as right now global bindings seem to come out of nowhere.