249
Views
5
Comments
Solved
Screen Lifecycle
Question

Hi,

By initialize de application, immediately the Aggregates an Data actions are defined at the screen level are triggered, Witch one triggered at first? Aggregates? Or Data actions?

Thank you!

2020-11-13 07-48-15
Khuong Truong
Solution

Hi @Mehdi Hadjian Hosseinabadi ,

I'm adding this document, you can take a look to get more clearer understanding about screen and block life circle: https://success.outsystems.com/Documentation/11/Developing_an_Application/Implement_Application_Logic/Screen_and_Block_Lifecycle_Events

The document does mentions: 

Regards,

Khuong

2020-06-08 06-48-23
Divyanshu Pathak

Hi Mehdi,

Data Actions and client-side Aggregates concurrently start to fetch data after the Screen loads. 

Would suggest you to read documentation.

https://success.outsystems.com/Documentation/11/Reference/OutSystems_Language/Interfaces/Adding_Data_and_Logic/Data_Action

Regards,

Divyanshu

2022-08-22 10-07-00
Mehdi Hadjian Hosseinabadi

Thank you Divyanshu,

2023-10-21 19-42-11
Tousif Khan
Champion

Hello

Both the Aggregate and data action run parallel, 

There is video available in course with a good explanation

have a look at it 

https://www.outsystems.com/training/lesson/1947/displaying-data-on-screens?LearningPathId=18

Best Regards

Tousif Khan

2020-11-13 07-48-15
Khuong Truong
Solution

Hi @Mehdi Hadjian Hosseinabadi ,

I'm adding this document, you can take a look to get more clearer understanding about screen and block life circle: https://success.outsystems.com/Documentation/11/Developing_an_Application/Implement_Application_Logic/Screen_and_Block_Lifecycle_Events

The document does mentions: 

Regards,

Khuong

2023-07-17 14-07-32
Jobbe Maas

Hi @Mehdi,

I think the answers above gave a clear answer to your question, but i have 1 addition:

Each Aggregate or Data Action that is configured to run at start will start async, and will start and end independent of each other. 

But there's an exception!
When you have dependencies between Aggregates or Data Actions the system automatically chains the requests. 
For example: if you use the result of an Aggregate inside a Data Action (or the other way around), the second request will only be executed after the first request is completed.

Hope this helps you further.

Kind regards,

Jobbe Maas

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