ASSOCIATE-REACTIVE-DEVELOPER practice question 32 of 35

Using an Ajax Refresh in the flow of a Screen Action allows refreshing a specific widget, but for it to work ...

Full set: 262 questions
Answer options
A: The widget needs to be a Table Records and the Screen Action must be executed with Ajax Submit.
B: The widget must have a Name and the Screen Action must be executed with Ajax Submit. Correct answer
C: The widget must have a Name and the Screen Action must be executed with Submit.
D: The widget must have a Name and the Screen Action must be executed with Navigate.
Correct Answer:
B. The widget must have a Name and the Screen Action must be executed with Ajax Submit.
Explanation

In OutSystems Reactive Web Apps, the Ajax Refresh tool is used within a Client Action to update a specific part of the screen without a full page reload. For the Ajax Refresh tool to target a widget, that widget must have its Name property defined, making it identifiable in the action's scope. The Client Action itself must be triggered asynchronously, for example, by a Button or Link's On Click event. The term "Ajax Submit," while specific to Traditional Web, correctly describes this asynchronous behavior, which is essential for a partial screen update.

Why Incorrect

A. The "Table Records" widget is from Traditional Web Applications. Reactive Web Apps use the Table or List widgets for displaying tabular data.
C. A full Submit causes a complete page reload, which defeats the purpose of using Ajax Refresh for partial, asynchronous screen updates.
D. A Navigate action is used to direct the user to a different screen or URL, not to refresh a component on the current screen.

References

1. OutSystems - Documentation, "Ajax Refresh Tool": "The Ajax Refresh tool refreshes a specific widget on the screen. To be refreshed, a widget must have a name." This directly supports the first condition in the correct answer.

Source: OutSystems. (n.d.). Tools in a Client Action. OutSystems Documentation. Retrieved from https://success.outsystems.com/documentation/11/reference/servicestudioreference/logictab/clientactionsfolder/clientaction/toolsinaclientaction/ (Under the "Ajax Refresh" section).

2. OutSystems - Documentation, "Triggering a Screen Action": In Reactive apps, Screen Actions (Client Actions) are triggered by events, such as a button's On Click. This process is inherently asynchronous (AJAX-based). The documentation on button properties states the On Click event defines the "Client Action to execute when the user clicks the button." This aligns with the "Ajax Submit" concept of an asynchronous request.

Source: OutSystems. (n.d.). Button Widget. OutSystems Documentation. Retrieved from https://success.outsystems.com/documentation/11/reference/outsystemslanguage/designingui/widgets/buttonwidget/ (Under the "Events" section).

3. OutSystems - Guided Path, "Reactive Web Developer": The "Reactive UI Development" module explains that to refresh a widget, it must be named. It also demonstrates that the refresh logic is placed inside a Client Action, which is executed asynchronously upon a user interaction, preventing a full page load.

Source: OutSystems. (n.d.). Becoming a Reactive Web Developer Guided Path. OutSystems Training. (Specifically, the sections covering UI design and client-side logic).

Scroll to Top