ASSOCIATE-REACTIVE-DEVELOPER practice question 34 of 35

When using a Popup_Editor, consider that you implement a Screen Action in the Popup Screen that requires Source Screen to be refreshed. How would you implement that Screen Action?

Full set: 262 questions
Answer options
A: You use the Popup_Editor_Close to close the Popup, followed by the Ajax Refresh to refresh the Source Screen.
B: You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen, followed by the Popup_Editor_ ... the Popup
C: You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen and close the Popup. Correct answer
D: You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen, followed by the Popup_Editor__... the Popup and an Ajax Refresh to refresh the Source Screen.
Correct Answer:
C. You use the Popup_Editor_Notify for the Popup Screen to notify the Source Screen and close the Popup.
Explanation

The correct implementation pattern for a popup to communicate back to its source screen in Outsystems Traditional Web involves the PopupEditorNotify action. This action triggers an OnNotify event on the source screen. The developer then implements a Screen Action on the source screen to handle this event, which is where the Ajax Refresh should be placed. The action within the popup screen is responsible for sending the notification and then closing the popup, typically using PopupEditorClose. Option C best encapsulates this two-part responsibility of the popup's action: notifying the source screen and closing itself.

Why Incorrect

A. You cannot directly call an Ajax Refresh on a widget in the source screen from an action running inside the popup screen.
B. This option describes the correct sequence of actions (Notify followed by Close), but it is incomplete ("...") and less descriptive of the overall pattern than option C.
D. The Ajax Refresh is misplaced. It must be executed in the OnNotify handler on the source screen, not in the popup's action flow.

References

1. Outsystems Official Documentation (Traditional Web): "Use Pop-ups". This document details the communication pattern between a popup and its parent screen. Under the section "Pass Information from a Pop-up to the Source Screen," it states: "In the Screen Action that closes the pop-up, add a PopupEditorNotify Action to send a message to the Source Screen... In the OnNotify Action of the Source Screen, add the logic to refresh the Screen..." This confirms that the notification is sent from the popup, and the refresh happens in the parent's OnNotify handler.

2. Outsystems Training Material (Traditional Web): In the "Becoming a Traditional Web Developer" guided path, the lesson on "Pop-ups" demonstrates this exact pattern. The example "Save" action within a popup screen contains the sequence: PopupEditorNotify followed by PopupEditorClose. The OnNotify action on the parent screen then contains the Ajax Refresh. Option C describes the purpose of this implementation from the popup's perspective.

3. Outsystems Official Documentation (Reactive Web): While the question refers to a Traditional Web widget (PopupEditor), the modern equivalent in Reactive Web uses events. The documentation on "Triggering Screen and Block Events" explains the analogous pattern: a Block (or Popup content) triggers an event, and the parent Screen has a handler action that executes logic, such as refreshing data. This highlights the separation of concerns, which is consistent with the Notify pattern.

Scroll to Top