Which behavior does not apply to forms?

The behavior described in choice B does not accurately reflect the functionality of forms within OutSystems. Forms in OutSystems are indeed meant to gather input data from users, but they do not have a "Source" property specifically designated for user-sent values. Instead, forms typically have properties that bind data to input fields, allowing for data submission, but they do not directly derive from a source property in the manner described.

In contrast, forms clearly have the role of grouping input widgets for data viewing and editing, as indicated in choice A. This means that multiple input fields can be organized within a single form for user interaction, which enhances data capture and organization.

Choices C and D highlight important functionalities of forms. Forms can indeed include a variety of widgets such as links and buttons, which provide navigation and actions for the user, confirming their interactive nature. Furthermore, forms play a critical role in validating user input—indicating whether the data entered meets the required criteria before submission, which is confirmed by choice D.

Thus, choice B stands out as the correct response since it misrepresents the fundamental attributes associated with forms.