Call new URL in same Browser

[jrgen_bauer]

Hi @ all,

I try to call another WD4A-Application with:

lr_window = lr_window_manager->create_external_window( url = lv_url ).

The system create a new browser window, but I want to start it in the same browser window (or close the parent window).

Have somebody an idea to solve this?

thanks

Jürgen

[thomas_szcs]

Hi Jürgen,

by starting a new application in the same browser window, the current application has to stop. Hence, there are two methods of achieving what you want. The first one is to use an exit plug and to specify the new URL there. The second option is to use the suspend/resume functionality. For the latter, my suggestion is to consult the online documentation, because it's a huge topic by itself with quite some pitfalls along the way.

Best regards,

Thomas

[jrgen_bauer]

Hi Thomas,

thanks for answer.

The suspend/resume functionality sounds good. But I can't find any documentations.

Colud you give me a hint or an example?

Tanks

Jürgen

[thomas_szcs]

Hello Jürgen,

please try these links:

WDA help

Suspend/resume

Best regards,

Thomas

[jrgen_bauer]

Hello Thomas,

I tried to implement coding from help file

method ONACTIONGO_SUSPENDING .

data: L_REF_MAIN_WINDOW type ref to IG_MAIN_WINDOW .

L_REF_MAIN_WINDOW = WD_THIS->GET_MAIN_WINDOW_CTR( ).

L_REF_MAIN_WINDOW->FIRE_GO_SUSPENDING_PLG(

URL = 'http://…………/webdynpro/sap/my_secondary_wda' ).

endmethod..

I got a syntax-error: IG_MAIN_WINDOW doesn't exist. Have you any idea?

regards Jürgen

[thomas_szcs]

Hello Jürgen,

just replace main_window with the name of your window. So if you window is called FOO, the name will be IG_FOO.

Best regards,

Thomas

[jrgen_bauer]

Hello Thomas,

thanks, now it works well.

DATA:

l_ref_window TYPE REF TO ig_main. "main: Name of window

l_ref_window = wd_this->get_main_ctr( ).

l_ref_window->fire_op_to_url_suspend_plg(

url = 'http://www.sap.com' ). "op_to_url_suspend: Name of Outbund-Plug Suspend

regards Jürgen

[Former Member]

Hi,

l_ref_main_window->fire_w_suspend_plg( link = lv_url ).

When i tried in the same way, i got the exception like "URL parameters specified for an exit or suspend plug, but no URL specified ". ( Defined the plug as Suspend and added a parameter named link and passed the value. )

[thomas_jung]

Are you running in the Portal? Suspend and Resume plugs aren't supported in the portal and this is generally the error message you receive when you try to use them within the Portal.

http://help.sap.com/saphelp_nw70ehp1/helpdata/en/45/19bf8c16f25d7ae10000000a11466f/frameset.htm

[Former Member]

Dear Thomas,

As i got that error, i even tried with the Exit plug. And moreover this application is executed directly i.e. from se80 not from portal.

[thomas_jung]

Are you sure your URL is properly structured? Can you capture the URL value in the debugger and post it here?

[carsten_schoen-schmidt]

Hi Thomas,

can you clarifiy please how it comes to the general statement "Suspend & Resume is not supported in Portal environment"? Since it is posted in the SAP Help, is it really meant principally or are there some exceptions?

I am trying to implement a similar scenario on customer site with Floorplans, and I know that the Floorplan components are handling the Portal client for suspend/resume navigation. Also I received some information that the scenario should work, even with Portal.

I also have seen that OBN supports suspend/resume on URL parameter basis in 701 and from 702 on even when utilizing Launchpad configuration. And OBN must definitely be Portal, right ?

Talking about Launchpad, if you look in the Launchpad classes, the Portal related implementation of the launcher class (CL_APB_LPD_START_APPLICATIONS) considers the suspend call as well.

So, given this information, how is the general statement in the 701 Help document meant?

Unfortunately, my resume action doesn't work either yet, I suppose I have a problem with resume URL as well. For this reasin I came over this thread.

Thanks

Carsten

[thomas_jung]

>can you clarifiy please how it comes to the general statement

I don't have any details I can share. If development makes such a statement, they must have encountered some incompatibilites that cause they not to support this technology within the Portal.

Here is some additional detail from the 7.02 online help:

http://help.sap.com/saphelp_nw70ehp2/helpdata/en/43/6b972329d23d33e10000000a11466f/frameset.htm

For every interface view, you can flag exactly one inbound plug as a resume plug. When navigating in the portal, the existence of a resume plug results in the following behavior: If the Portal Navigation recognizes such a plug in the running application, the latter is not exited when navigating away but is instead transferred to a suspend mode. The session ID and contents of the context are retained and a new application is started. If a user then goes back to the original application via the navigation menu of the portal, it can be processed in exactly the same state in which it was left. Note the following:

If an application features a resume plug, the corresponding session is retained when navigating away in the portal. However, in many cases it may be sensible or even absolutely necessary to close the application completely. In such cases, you must not implement a resume plug for the interface view.

...

While your applications are running within a portal, the portal navigation takes care of the suspend step without you having to implement it at design time. The mere existence of a resume plug ensures that an application is only interrupted and not exited in the case of a portal navigation. However, this does not take place if the application is not running in the portal and can thus not make use of the portal navigation mechanism.

...

If an outbound plug is flagged as a suspend flag in a Web Dynpro ABAP application, this can lead to errors when the application is executed in the portal. If you are not completely sure that your application is executed solely outside a portal, you should avoid the use of suspend plugs.

[Former Member]

hi jugen..

in that case you can go for linktourl ui element which opens the link automatically, specified by you.

---regards,

alex b justin

[jrgen_bauer]

Hello,

thanks for your answer, but I want to start the side (URL) from an action/methods.

Have you any other idea?

regards

Jürgen