For a Screen or Client or Server action
creating 10 inputs separately like this
or creating a structure first with 10 attributes and then add only one input to the action with type structure
which one is best practice? in accordance with both maintainability and performance wise?
Hello @Priya Naveen,
I’d go with using a structure. Imagine a scenario where you need to pass pagination data like page number, page size, along with some filtering options. If you define all of these as separate input parameters in an action, then any change, like adding a new filter or modifying an existing one, will impact every place where that action is used. You’d end up having to update multiple consumers and also spend time tracking where the action is being called.
On the other hand, using a structure gives you a centralized place to manage all these inputs. You can extend it by adding new attributes without changing the action signature itself, which makes the system easier to maintain and scale. It also makes the intent clearer, since all related data is grouped into a single contract instead of being scattered across multiple parameters.
As for performance, the choice between individual parameters and structures has no measurable impact either way. In case of reusability struct can be beneficial.
Hope that brings some clarity. Check this one as well: https://www.outsystems.com/forums/discussion/53751/structures-as-input-parameter-of-a-screen/#Post201538