Forge

Now you can run your actions only when you are sure that a certain DOM element is already present on the page. No more strange behaviors caused by an action trying to access a part of the page that was not yet rendered.

This asset serves as a visual and interactive guide to demonstrate the communication process between a block and its parent (in this case, a screen) in the OutSystems development environment. It provides a step-by-step walkthrough, essentially debugging the intricacies of this interaction with a straightforward example.

The goal is to enhance developers' understanding of how events are triggered, handled, and communicated within the application. By incorporating a simplified and visually engaging representation, the asset offers a clear and illustrative journey, making it easier for developers to comprehend the flow of information from a block to its parent screen.

Through a simple example, developers can witness the real-time flow of events, triggers, and handles, gaining insights into the behind-the-scenes mechanisms of their OutSystems application.