I'm new to OutSystems and I've noticed a confusing point: the terms "Screen Action" and "Client Action" seem to be used interchangeably.
The training materials clearly differentiate between Screen, Client, and Server Actions.
UNTIL this point it is completely clear.
However, in the platform and community discussions (exams, forums, blog posts), everything seems to be labeled as "Client Actions."
This is a Screen Action
Screen Action creation
Below is a REAL Client Action
This creates confusion, especially for newcomers.
Are we talking about a Screen Action or a Client Action?
For clarity, I suggest consistently naming Screen Actions as "Screen Actions" across the platform. This would help avoid mix-ups and make learning easier.
Has anyone else faced this issue? Thoughts on this suggested change?
Hi,
It ain't that difficult, "ever seagul is a bird, but not every bird is a seaqul".
A screen action is an client action but not every client action is a screen action.
A screen action is a client action within the scope of a screen, it can only be referenced and executed in the scope of a screen.
A client action, that is not a screen action, is defined on the logic tab, and can be called from screen actions. So client actions on the logic tab are the more reusable actions in your application.
Regards,
Daniel
I completely understood that. Also for example, Screen Aggregates are nothing but a data action with a aggregate tightly coupled with it. But in Outsystems, they have wrapped it in name of Screen Aggregates and this is very useful for the thinking, communication and solution.
Similarly, I suggest the term "Screen Action" to be used in the screen client action area inside outsystems. Makes everyone life easier.
Alright, I don't see the confusion, but maybe others do like you.
You would be better off then posting this as an Idea on https://www.outsystems.com/ideas
as the community itself cannot implement your request.