BIApplicationFrame Refresh

[BenPatterson]

Hi,

When using the recommended WDA BIApplicationFrame Element, the contents

(the Web Template) is refreshed on any action performed by the user

outside of the BIApplicationFrame Element.

For example if the user presses a button or even right clicks on the

application outside of the BIApplicationFrame Element, the entire

BIApplicationFrame is re-freshed causing a disruption to the flow of

the user interface.

Does anyone know how the BIApplicationFrame Element can be used so that the WDA Application logic determines when the Element is refreshed, preventing

the refresh from occurring on any (or all) user actions?

Kind regards,

Ben.

[thomas_szcs · Accepted solution]

Hi Ben,

That's caused by the browser. The browser reloads the complete page including the iframe in which the BI report resides. You can experiment with stateful and stateless BI to minimize the impact. An alternate solution is to integrate WD and BI using the portal. Both would then reside in different iViews and updates would be decoupled.

Best regards,

Thomas

[BenPatterson · Accepted solution]

Hi Thomas,

Thank you for your reply.

I am not using an IFrame as this is deprecated so I am using the supported BIApplicationFrame, surely this is based on better technology than a simple html IFrame.

Are you able to elaborate further on what you mean by stateful/stateless BI?

When using the portal we have issues with using visual composer (it forces a click to activate the components before they can be interacted with) and we can't decouple it using iViews as we are using the WD components to control the variables via the context.

Kind regards,

Ben.

[thomas_szcs · Accepted solution]

Hello Ben,

In the browser, the Web Dynpro ui element BIApplicationFrame is rendered as a simple html iframe with some script around it for session handling with BI. There is some kind of "communication channel" from the BI content to the WD framework around it. This is one of the reasons why ppl should use the BIApplicationFrame rather than the IFrame ui element, which is deprecated due to the missing session handling support when it comes to integrate external content.

Stateful BI means that the BI system keeps the state of your BI application inside of the BI system for some time. When the a request is triggered from the browser to the BI system, the BI systen does not have to recreate everything. Stateless means that the BI system has to recreate everything with each roundtrip. There are pros and cons for both approaches. Stateless is useful for "display one time" reports or if the sessions of all users logged into the system would increase memory usage beyond system boundaries. Stateful is useful for interactive scenarios.

Best regards,

Thomas