SAC Optimized view mode - load invisible widgets in background?

[axel_]

Hi Folks,

I've got a question about the new optimized view mode for stories.

Is there somewhere a setting that would load all not visible widgets in the background while the user looks at the widgets in the view port?

I understand the concept that the initial load of the story should be as fast as possible by loading only the visible widgets but I don't understand why the story navigation performance is disregarded / not improved by loading all other widgets in the background after initial load.

As enduser I am not impressed that the story is loaded xy secs faster only to wait xy secs when switching pages in the story ...

From my perspective the optimized view mode should give always priority to widgets in view port (initial load, filter driven data change load etc.) but load all other stuff still in background to allow seamless navigation in a story.

But maybe I have just overlooked a setting ...

Best regards,

Axel

[Tunir]

Hi axel0102,

We provide two rendering experiences within Optimized View Mode. By default, as soon as you enable Optimized View Mode, we have Active Viewport Rendering. In this scenario as you described, we render objects that are within the viewport and any objects that are dependent (i.e. Chart Scaling, Axis Alignment, and so on) or not supported. Objects outside the viewport are paused until the user brings them into view.

The Story Designer has the ability to disable Active Viewport Rendering on a per dashboard basis. In this scenario you would be using the same rendering experience that we have in a non-optimized story. In this scenario, we have two distinct behaviors:

Story Open

We will prioritize rendering the Active Viewport. For any objects outside the viewport, we will load all the objects incrementally in the background. Hence, when you scroll, these objects will be either loaded or in the process of loading.

Interactions

For any subsequent story interaction (i.e. filter, linked analysis, etc.) we apply the interaction to the entire dashboard as we have to determine which objects have been impacted.

There are more details on the differences between the two rendering experiences and how you enable it within this detailed blog: https://blogs.sap.com/2021/07/26/the-new-rendering-experience-active-viewport-rendering/

Regards,
Tunir

[axel_]

Are there plans to enhance the optimized view mode with the incremental load in the background both for initial load and change apply?

I understand the target of optimized view mode .... but as stated if it is neglecting the other elements of the story it is sub-optimal.
I believe with outside viewport elements loaded as second priority you would have a really optimized view mode .... otherwise it is just an optimized start mode ...

Best regards
Axel

[arnoldtob]

Hi, this is a good question. It would greatly improve the usability of the new viewmode, that after loading the visible widgets all other widgets would loading in background.

regards

Tobias

[axel_]

So only me not impressed by optimized view mode?

[Henry_Banks]

Hi tunirkapil would you be able to comment here for Axel?

Regards,

H

p.s. FYI larissa_reisinger