cancel
Showing results for 
Search instead for 
Did you mean: 

How to optimize initial loading of an application

Former Member
0 Kudos

Hi Experts,

could you pelase advise us how we could optimize the loading of an application in the following case:

we have an OVP application with page master. In the master we have a list and depending on its selection, in the details we show/hide dynamically different sections. The whole application consists of 39 UIBBs and we noticed that the method call_uibb_pbo is called for all of them. This causes some delay when starting the application. Actually on the initial loading we show only some of those UIBBs and processing all of them is not necessary. Just asking if there is a way to mark some of the UIBBs not to be loaded when starting the application.

Thank you in advance!

Kind Regards,

Miroslava

Accepted Solutions (0)

Answers (2)

Answers (2)

simon_hoeg
Advisor
Advisor
0 Kudos

Hi Miroslava,

a quite similar problem has been discussed here.

So you may use the asynchronous capabilities of FPM.

Best regards,

Simon

ulrich_miller
Active Participant
0 Kudos

Hi Miroslava,
did you already try the option "lazy load"? This is available for OVP floorplan, I think since 7.31. You can activate it in the general settings of the OVP configuration. However this might not work in case there is wiring active for the UIBBs.

Then if lazy load does not work for you: You could check via OVP API whether the panels are collapsed, and if so, you do not need to fetch data of course.

Even better: Is it really necessary to have 39 UIBBs on the screen? An alternative could be: In OVP configuration you could make e. g. 10 UIBBs visible and the rest move to personalization, so that each user could make them visible when necessary via personalization.

Kind regards,
Ulrich

Former Member
0 Kudos

Hi Ulrich,

thanks a lot for the reply.

Actually we have:

Collapsed UIBB Proc Mode: Defer Participation(in FPM event loop) ( lazy Loading).

Your suggestion to add the UIBBs to personalization will not work, because in the page

master tree we have 5 diffrenet groups of selection. Depending on the record selected(to which group it belongs to ), we should show some sections and hide others. There is a requirement what to see and what - not. It could not be personalized.

What we plan is to make all of the sections collapsed by default and on lead selection to expand them.

Just wanted to ask if there is another option which we could not think of.

Thanks,
Miroslava