Web Blocks are reusable screen parts that have a private scope. When a screen uses a web block it can only send information through input parameters, and can't access directly any variables or actions of the web block.

But sometimes you need to send information from the web block to the page where it is running.

An example is when you have a form encapsulated on a web block. When the end-user submits the form, the web block needs to let its parent screen know about the change. The screen can then react to this change, for instance by updating the header, menu, or title.

To make a web block communicate to its parent, and notify that something meaningful has happened, use the Notify action.

In this example the:

  1. End-user fills the form and clicks the Save button;
  2. Save action from the web block runs. We use the Notify action, to notify the parent screen of this change;
  3. Page where the screen block is instantiated receives the notification;
  4. Update Screen action runs to handle the notification;

Finally the Update Screen action ends, and the web block Save action continues to run.

See Also

About Web Blocks | Notify Action