Server Actions v App Flows

[CAB_uk]

Hi All,

Sorry if this seems to be a silly question, but - what is the difference between Server Actions and App Flow?

Can’t quite get my head around this, unless I missed something obvious.

Sorry if its a silly question.

B/w
M

[brad]

Not a silly question at all and someone else may be better to answer your question. But I use Page Flows on pages where I may have almost 100 server connects on it but I only want to load certain ones based on a variable. You can also run server connects based on a button click for example. These are just a few examples. I also use the ‘Wait’ element frequently as well.

The only difference between a App Flow and a Page Flow that I can see is that App Flows can be reused on multiple pages and Page Flows are for a given page only.

[htatd]

Server actions are tasks that are executed in the server, and app flows are tasks executed on the client side.

For better performance try to do as much as possible with server actions

[jimed99]

Some insight I got from @ben a while back:

Client-side vs. server-side rendering: why it’s not all black and white

Here’s the context it was shared in:

Dynamic page title from SC

In a layout page I defined in the Template Data a variable called page_title: [image] On a content page using this layout, I defined the page_title in the properties: [image] However the page title is not updated and stays empty. When using a static value, like below, the page title is properly set: [image] The server action I use is returning a value btw, without any errors. Why is this not working with dynamic data from the server action?

[CAB_uk]

Thanks all - that’s really useful, I totally get it now