- Do want to point out the naming convention applied in Service Studio for Client actions with
Reactive web:
In comparison to Traditional web :
Marked both as "Screen actions" in old traditional school.
- And not to be mixed up or confused with the other Client actions for Reactive web which sit under the
Logic Tab:
@Ricardo,
I think Adam is trying to point out that actions on a screen in reactive web (and mobile) are called client actions, and the client actions on logic tab are also called client actions.
On traditional web actions on screen are called screen actions, and actions on logic tab are called server actions.
Personally I don not see a point in defining in the name of an action if it is a server action or client action, the different icon for each type of action already explains this.
@Adam
A better place to discuss this would be in the ideas section: https://www.outsystems.com/ideas/
Regards,
Daniel
Hi Adam,
Naming Convention it is not a topic of right or wrong. You should use the convention that is most comfortable and self-explaining. It simply ensures that all members of the team use the same convection to make it normal.
I, as a rule, use as a convention what action does, what it does and on what basis. If you prefer, you can add "CL" as a suffix if it is a client action and "SE" if it is a server action.Attention, this is just a banal example.
Hope this can help.
Best regards,
Ricardo M Pereira
- Daniel and Ricardo both thanks for your responses!
Indeed Daniel, I just want to bring this under the attention and to be aware of. As this isn't (in my opinion) clearly distinguished and explained in https://www.outsystems.com/learn/lesson/1933/logic-actions As its implementation in Service Studio is somewhat inconsistent (causing to me a bit of confusion at first):