Endless flickering/blinking/refreshing on URL iView load

[Former Member]

Hello All,

I'm facing the following problem:

An URL iView, that is based on Web Application Designer template is included in a portal role. When the iView is previewed alone (from its design) it work fine - opens in separate windows, ask for variables, shows the result, charts, etc.

But when it is launched via detailed navigation menu of the role it doesn't load, instead the busy sign appears and start blinking as if the page is constantly refreshed. I try with including the iView in a separate page and the the result in the preview mode is the same. Only preview of the iView itself works. It seems there is any issue with the iframe/iframes generated by the portal when the role navigation is launched.

There are some other iViews, based on different intranet sites (not parts from the EP itself) which work fine alone and from a role.

We use NW 7.3 and the components are at SP 0. Should I expect resolving of this issue if upgrade to SP 7.

There is not such a problem in another our system for tests wich is NW 7.0 based.

Has anybody faced such a problem?

A lot of similar issues are described, but not exactly as this one and no solution is described.

[Former Member · Accepted solution]

Dear Colleagues,

Thank you for your replies. The flickering is still there, even after sp7 upgrade. But another workaround is applicable - the iView is created not as URL type (using its url address) and as type BEx Web Application iView and then published directly to the portal with Publish command in Web Application Designer.

That works for now.

Thank you again,

Regards

[Former Member]

Hi Georgy,

I would recommend that you upgrade to the latest SP for 7.3. SP0 could very easily contain a bug. That would be the first thing I would try if I were you.

Also you could use HTTP Watch or Firebug to try to see what the HTTP traffic looks like during the issue - that might give you more clues as to what is going on.

Cheers,

Simon

[hofmann]

Endless flickering also appears on older versions of the portal. The problem is the portal framework, the EPCF Proxy and - of course - Javascript. Some can check if it appears for all browsers, use Firebug, but the problem is to trace it down and then, to get rid of the problem.

You can use the iFrame iView to integrate the application or create a HTML file with an iFrame inside it.

[SandipAgarwalla]

Greorgy

What is the isolation mode of the iview in the page?

[Former Member]

Sandip,

the isolation mode/method of the iView itself and of the page in wich it is included is "URL".