18
Views
2
Comments
Solved
lifecycle

What could be a possible sequence of events when requesting a screen:

a. Initialize, Ready, Render, After Fetch, Render, Destroy (of the old screen).

    b. Initialize, Ready, Render, Destroy (of the old screen), After Fetch, Render.

c. Initialize, Ready, Destroy (of the old screen), After Fetch, Render.

d. Initialize, Destroy (of the old screen), Ready, Render.

can someone please explain to me the right order? it confuses me a lot. thanks.

2016-04-22 00-29-45
Nuno Reis
 
MVP
Solution

Hello.

You have all the information on the course: https://learn.outsystems.com/training/journeys/web-developer-662/screen-events/o11/472

B)

Initialize (before there is content)

Ready (after DOM loaded)

Render (second screen is ready to be presented)

Destroy (no need to keep the old any longer)

After Fetch (when the aggregates finished receiving data)

Render (showing aggregates data on screen).

2025-09-25 14-38-22
Lokesh Kumar Yadav
Solution

This PDF will help you 

2.4 - Screens.pdf
2016-04-22 00-29-45
Nuno Reis
 
MVP
Solution

Hello.

You have all the information on the course: https://learn.outsystems.com/training/journeys/web-developer-662/screen-events/o11/472

B)

Initialize (before there is content)

Ready (after DOM loaded)

Render (second screen is ready to be presented)

Destroy (no need to keep the old any longer)

After Fetch (when the aggregates finished receiving data)

Render (showing aggregates data on screen).

2025-09-25 14-38-22
Lokesh Kumar Yadav
Solution

This PDF will help you 

2.4 - Screens.pdf
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.