Call a URL which is a Javascript

[Former Member]

Hi All.

I know we CANNOT call javascript in Web dynpro abap.

I also know we can call a URL via calling external window and passing the URL.

We needed a functionality which requires a small piece of javascript code to be executed on click of any button. I have placed a javascript code in the portal server.

I was wondering if there could be a way to call a URL WITHOUT the external window - this would mean that I call my javascript URL whenever I want.

Thanks in adv for your patience.

[Former Member]

Hmm, have to find other forum where i could say my honest opinion then...

Customers pays quite a lot of using SAP products...Somebody have to speak up sometimes

It is not any personal!

Back to issue then. How i open another web page via office control?

"Use OfficeControl or InteractiveForm for Office and PDF documents"

KK

[thomas_jung]

>

> Hmm, have to find other forum where i could say my honest opinion then...
> Customers pays quite a lot of  using SAP products...Somebody have to speak up sometimes 
> It is not any personal!
> Back to issue then. How i open another web page via office control?
> "Use OfficeControl or InteractiveForm for Office and PDF documents"
> KK

Did I ever say you can't express your opinion? I said you must remain civil. Saying that SAP doesn't have "common sence" is not being civil. You can claim that there is no use of Adobe PDF online (which I don't agree with at all), but don't insult our developers/product designers.

Who said you should be able to open another web page via office control. As stated in the help OfficeControl is for opening Office documents. InteractiveForm is for opening PDF documents. We never said anything about opening just any web page via these UI elements. We are just stating that if you have office or PDF documents you don't use the iFrame to open them - you should use their respective UI elements.

If you want to open another web page, the recommended solution is another iView within a Portal or NetWeaver Business Client page. This way the two technologies are clear separated and there is less expectation that all parts should meet the same standards for theming, accessibility, personalization, etc. You can still communicate events between the two iViews using Portal eventing if necessary.