ASSOCIATE-REACTIVE-DEVELOPER practice question 35 of 35

When the user submits data in a Form to the server...

Full set: 262 questions
Answer options
A: a Screen Action runs with the data from the Form as Input parameter.
B: .. the Preparation runs then the Screen Action runs.
C: . the data is stored in the Form's Record implicit variable. Correct answer
D: . the data in the Form is only available in the Preparation.
Correct Answer:
C. . the data is stored in the Form's Record implicit variable.
Explanation

When a Form widget in an Outsystems Reactive Web App is submitted, the data entered by the user into the various Input widgets is automatically aggregated and stored in the variable bound to the Form's Source property. This source variable is typically a local variable of a Structure or Entity data type. The Screen Action triggered by the submission can then access this populated variable to process the data, for example, by saving it to the database. This mechanism simplifies data handling by consolidating all form inputs into a single structured variable.

Why Incorrect

A. a Screen Action runs with the data from the Form as Input parameter. This is incorrect. The data is available to the Screen Action via a screen-level variable (the Form's Source), not as an explicitly passed input parameter to the action itself.
B. .. the Preparation runs then the Screen Action runs. This describes the lifecycle of a Traditional Web App. Reactive Web Apps do not have a Preparation action; they use client-side events like OnInitialize for screen setup.
D. . the data in the Form is only available in the Preparation. This is incorrect because Reactive Web Apps do not have a Preparation action. The submitted data is processed within the Screen Action that handles the form's submission. ---

References

1. Outsystems - Documentation, "Form Widget": This document details the properties of the Form widget in Reactive Web Apps. It explicitly states, "Source: Record or List that holds the data of the form." This confirms that the data is held in a source variable associated with the form.

Reference: Outsystems. (n.d.). Form Widget. Outsystems Documentation. Retrieved from https://success.outsystems.com/documentation/11/developinganapplication/designui/patterns/usingmobileandreactivepatterns/form/ (Under the "Properties" section).

2. Outsystems - Documentation, "Create and validate a reactive form": This tutorial guides developers on handling form data. It shows the creation of a local variable, binding it to the Form's Source property, and then using that variable within the save logic of a Screen Action. This demonstrates that the data is stored in the source variable, not passed as a parameter.

Reference: Outsystems. (n.d.). Create and validate a reactive form. Outsystems Documentation. Retrieved from https://success.outsystems.com/documentation/11/developinganapplication/designui/forms/createandvalidateareactiveform/ (Steps 1 and 4).

3. Outsystems - Documentation, "Screen and Block Lifecycle Events": This document outlines the lifecycle for Reactive screens. It shows that user interactions, like a button click to submit a form, trigger Screen Actions directly. It makes no mention of a "Preparation" action, confirming that options B and D, which reference it, are incorrect for Reactive apps.

Reference: Outsystems. (n.d.). Screen and Block Lifecycle Events. Outsystems Documentation. Retrieved from https://success.outsystems.com/documentation/11/developinganapplication/implementapplicationlogic/screenandblocklifecycleevents/ (Section: "Reactive Web App Screen Lifecycle Events").

Scroll to Top