Skip to Content (Press Enter)
Back to Ideas
40
Like
Follow Idea
Warning when quering data in viewstate
856Views
9Comments
On our RadarOn our Radar
Frontend (App Interfaces)

Hi,


I would like to suggest that it might be helpful if Service Studio alerts when using preparation data on screen actions, which increases hugely the view state and it would be aligned with the performance best practices.

10 Oct 2018
Copy link to comment

Perhaps using preparation data in screen actions should be prevented altogether?

11 Oct 2018
Copy link to comment

You're right, Hanno.


In the description I elaborated but forgot to update the title.

12 Oct 2018
Copy link to comment
2014-02-07 17-02-43
Vasco Pessanha
Changed the category to
Frontend
16 Oct 2018
Copy link to comment

I don't think it should be prevented. But a warning would be a good idea.

18 Oct 2018
Copy link to comment

Agree with Marcelo 

24 Oct 2018
Copy link to comment

Use but don't abuse it. A warning in service studio and better viewstate size monitoring tool in service center (right now we need to extract that info from an excel file)

24 Oct 2018
Copy link to comment

@Rui  you can also use Outsystems Launcher to check the viewstate size

24 Oct 2018
Copy link to comment

It is also possible to use service center reports to evaluate the size of viewstate of each page but a warning would help developers to pay attention and senior developers to review the quality of the code. 

24 Oct 2018
Copy link to comment
Changed the status to
On our RadarOn our radar

Hi João,

That's a good idea. In fact we already have some warnings in place (e.g. when doing a foreach of an aggregregate that is used on a tablerecords, we give a warning to set the start index and maximum iterations, but that warning is often ignored), but I guess we could have more.

We're currently working so that new web applications would not use viewstate at all (similar to mobile apps), which should be even better, but I'll leave this  as "on our radar" and see if we keep getting feedback on this after that.

Cheers,

Tiago Simões



12 Apr 2019
Copy link to comment