Hi All,
I just wanted to know the order in which the screen/block event will get triggered when we have added a web block in a web screen. I added log logic to see the order and this is what i got.
On Initialize (Screen)->On Ready (Screen)->On Initialize (Block)->On Ready (Block)->On Render (Screen)->On Render(Block)
Please let me know the correct order .
nope,
for a simple example of a block being on a screen unconditionally, it is
screen initialize > block initialize > block ready > block render > screen ready > screen render
each waiting for the previous handler to finish.
use console.log instead
Dorine
I agree with @Dorine Boudry . This is what I get
I have used JS script to log the events - console.log(`[${new Date().toISOString()}]`, $parameters.In1);
Hi @Siya ,
I could have pasted almost exactly the same screenprint :-)
A tip if you often use console log in Chrome to time stuff, you can leave out the first part of your log, and just ask the browser to give you the timestamp when things happen
@Dorine Boudry : Thanks for the tip :)
Hi,
You can refer the document. Outsystems given the official document so you can know the correct flow for the screen and block lifecycle.
Thanks,
Sriyamini J
Hi Sriyamini,
I have referred this document before .It explains the event order for a particular screen or a web block. My question is for the order when we have added a web block within a screen. Which events will be triggered first, web block or web screen.
Thanks Dorine Boudry & Siya , I got my answer
> screen initialize
> block initialize
> block ready
> block render
> screen ready
> screen render
> screen destroy
> block destroy