How is data fetched by an Aggregate bound to a Table or a List widget?

The correct answer is rooted in how OutSystems handles data binding between Aggregates and UI components, specifically Table or List widgets. When you set the Source property of a widget to the output of an Aggregate, you establish a direct link between the data fetched by that Aggregate and the display logic of the widget. This allows the widget to represent the data dynamically, responding to any changes in the underlying data set that the Aggregate fetches.

This method facilitates ease of use and maintains clean code architecture since developers can focus on using the widget's properties and the data model provided by the Aggregate without needing any additional configuration or manual efforts to fetch or bind data. Consequently, changes in the Aggregate's data will automatically reflect in the UI, simplifying both the development process and maintenance of the application.

The other choices, while they touch upon different aspects of working with data in OutSystems, do not accurately describe the standard process for binding an Aggregate's output directly to a widget's Source property. For instance, automatic binding based on scope might suggest a level of implicit connection that does not provide the clarity or control expected in a professional coding environment. Similarly, expressions and programmatic assignments introduce unnecessary complexity and can lead to harder-to-maintain code. Thus, by setting the Source