ASSOCIATE-REACTIVE-DEVELOPER practice question 11 of 35

Ending a Screen Action with an End element or a Destination to the '(Current Screen)' yields the same result.

Full set: 262 questions
Answer options
A: TRUE Correct answer
B: FALSE
Correct Answer:
F; A. TRUE; L; S; E
Explanation

The statement is false. Ending a Screen Action with an End element versus a Destination to the (Current Screen) produces fundamentally different results in an OutSystems Reactive Web Application. End Element: When a Screen Action terminates with an End element, it completes the server-side logic and sends an asynchronous (AJAX) response back to the client. The browser does not perform a full page reload. Instead, only the parts of the screen bound to data that was changed during the action are updated. This preserves the current state of the screen, such as scroll position and the values of client-side local variables. Destination to '(Current Screen)': Using a Destination element to navigate to the (Current Screen) explicitly instructs the server to perform a full navigation. This causes the browser to reload the entire page. As a result, the screen's state is reset, all its Aggregates and Data Actions are re-executed, and the screen lifecycle events (On Initialize, On Ready, On Render) are triggered again. Therefore, an End element results in a partial AJAX refresh, while a Destination to the current screen results in a full page reload.

Why Incorrect

The statement is presented as a "TRUE OR FALSE" question. The "True" option is incorrect because, as explained above, the two methods have distinct technical behaviors and result in different user experiences. One preserves the screen state through an AJAX update, while the other resets the screen state through a full navigation and page reload.

References

1. OutSystems Official Documentation - End Element: "The End element ends the execution of an action flow. When modeling a screen action, the End element sends the updated values of the screen variables to the browser to update the screen." This describes the AJAX-based update mechanism without mentioning a page reload.

Source: OutSystems Success Center, "Toolbox > End".

2. OutSystems Official Documentation - Destination Element: "The Destination element allows you to navigate to a Screen in your application... When you end a flow with a Destination, you are redirecting the end-user to a new screen." Navigating to the current screen is a specific case of this, which forces a re-initialization and rendering of that screen, equivalent to a page refresh.

Source: OutSystems Success Center, "Toolbox > Destination".

3. OutSystems Official Documentation - Reactive Screen Lifecycle: The documentation on the screen lifecycle events (OnInitialize, OnReady, OnRender) and the behavior of Aggregates and Data Actions clarifies that these are re-executed upon navigation to a screen. A Destination to the (Current Screen) triggers this full lifecycle, whereas an End node in a Screen Action does not.

Source: OutSystems Success Center, "Reactive Web > Screen and Block Lifecycle Events".

Scroll to Top