Navigating one OutBound plug to Two Inboung plugs

Hi Friends,
           I developed one application using Radio Buttons. I strucked up at Event Handling. Actually i created one out bound plug and navigated it to two inbound plugs of two diffrent views.
           If i click on one radio button it should navigate it to first view orelse if click on second radio button it should to second view.  
           how can i trigger the particular view based on the radio button i have clicked.
           could you people concern this one and give me a bright answer.

If you use single radio buttons (not RadioButtonGroup):
There is an event RadioButton.onSelect which is triggered when a radio button is selected.
https://media.sdn.sap.com/javadocs/NW04/SPS15/wd/com/sap/tc/webdynpro/clientserver/uielib/standard/api/IWDRadioButton.html
This event has a parameter "key" which contains the key representing the selected radio button.
Assign an action to event "onSelect" and define an action parameter "selectedKey".
Map event parameter "key" to action parameter "selectedKey" e.g. by writing the following code inside wdDoModifyView():
if (firstTime)
  IWDRadioButton radio = (IWDRadioButton) view.getElement("ID-of-radio-button");
  radio.mappingOfOnSelect().addSourceMapping("key", "selectedKey");
The effect is that at runtime, parameter "selectedKey" will contain the key of the selected radio button. In the action handler method you can now use the "selectedKey" parameter to decide which view should be navigated to.
Armin

Similar Messages

  • Web Dynpro: several navigation links connect to one outbound plug of a view

    Hi,
    I have two questions in general Web Dynpro. (I have not found precise answer for the question yet)
    1) What should happen in the following case?
    We have three views in a component. The outbound plug of the first view is connected to the inbound plug of the second and third view via navigation links. Which view should appear, if i fire the outbound plug of the first view?
    Some documentation says, this case is not allowed, some documentation says it is allowed...
    2) If the previous case is allowed, what should happen in the following case?
    In a child component, a window outbound plug is connected to a view inbound plug. Beside this, I implement an inbound plug of the window, where i fire this outbound plug of the window.
    Now, the interface view is embedded into a parent component window. In the parrent component I connect the outbound plug of the interface component to an inbound plug of a parent view (which is also embedded into the window). I also connect an outbound plug of the parent view to the interface view inbound plug.
    What will happen if I fire the parent view outbound plug? Will the parent view or child view appear?

    Hi Huszar,
    I'm a newbie and found your question interesting. So I played a little with this issue and hope I found something to help you.
    But  I wonder in why you want to use such a constellation the first place. What is your purpose? For me the idea itself doesn't make much sense... Did you by chance actually think of one of the following purposes:
    You want two different action elements (e.g. 2 buttons) to fire different conenctions. Then you should use different outbound plugs. Connect the two buttons and the two links to different methods so that the corrsponding plug and button have the same method.
    You want to decide by value or state which view to show. Then you should use two different outbound plugs as well and decide in the button's event handler mehtod which plug to fire , e.g.: if <condition> then <firePlugA> else <firePlugB>.
    Generally, if you connect two views in a window via link you must chose a method to use or create a button. If you chose a method (event handler) the effect in the Java file is that the  method (onActionButtonX()) will call the corresponding firePlugOut-method.
    Unfortunately in the firePlug-method itself there was no hint about the plug's destination. As I connected the same method for button and two plug targets, Web Dypro for no obvious reason always chose the same target. I did not find a possibility to directly chose the target from one outbound plug, so I guess this information is stored somewhere in the background logic.
    Did I get the point or did you think of something completely different? Or maybe you just asked theoretically? In that case I don't seem to get the idea.
    Kind regards,
    Jana

  • View controller active after navigating via outbound plug, is this normal

    Hallo,
    I have two components (comp_a,comp_b).
    comp_a->grid_view_a : fires a event.
    comp_b->grid_view_b : subscribe to the above event.
    My observation is that
    When comp_a->grid_view_a fires a event and comp_b->grid_view_b listen to that event and the Grid is filled accordingly.
    Now i navigate from comp_b->grid_view_b to comp_b->display_view_b  firing a outbound plug.
    Now if i change the selection in comp_a->grid_view_a and it fires a event. I was expecting that nothing happens in comp_b as the subscribed comp_b->grid_view_b is not in the assembly. But to my surprise, the event handler is called and processed while the user still watching/working on the comp_b->display_view_b.
    Has anyone encountered with this problem ?. I was not having this problem a month ago. Could have been introduced in one of our Kernel/Sp updates.
    Your reply is highly appreciated.

    Hallo,
    I have two components (comp_a,comp_b).
    comp_a->grid_view_a : fires a event.
    comp_b->grid_view_b : subscribe to the above event.
    My observation is that
    When comp_a->grid_view_a fires a event and comp_b->grid_view_b listen to that event and the Grid is filled accordingly.
    Now i navigate from comp_b->grid_view_b to comp_b->display_view_b  firing a outbound plug.
    Now if i change the selection in comp_a->grid_view_a and it fires a event. I was expecting that nothing happens in comp_b as the subscribed comp_b->grid_view_b is not in the assembly. But to my surprise, the event handler is called and processed while the user still watching/working on the comp_b->display_view_b.
    Has anyone encountered with this problem ?. I was not having this problem a month ago. Could have been introduced in one of our Kernel/Sp updates.
    Your reply is highly appreciated.

  • Creation of one outbound interface for two diferent senders

    helo.
    i just want to conform ont thing that .
    my scenario is  two diferent files from 2 diferent business systems are sending to one Rfc.
    so i was created only one outbound interface for both senders and one message type bcos the file structure is same for both senders.
    so is there any thing wrong in creating only one datatype,message type,message interface for both senders.
    waiting for your response.
    cheers.
    seeta ram.

    Hi Ram,
    That is perfectly correct when you have two senders and one receiver Scenario and <b>Business Service is different</b>. Then you can use the same Interface.
    Just keep in mind that the key for XI to recognise the Right interface is combination of these 3 parameters:
    Sender Service, Sender Interface and Namespace. These cannot be duplicated.
    When the Message type is same in the sender input data then you can create just one Message Type and One Data type and RFC is anyhow the imported RFC which you need not have to worry.
    In Configuration Scenario you need to configure separately the RD, ID, CC and Agreements for the Interfaces.
    Hope this answers your query. Let us know if you need anymore clarification
    Thanks
    Srini

  • OutBound Plug

    Hi To all,
                Can we connect one Outbound plug to more than two views in WebDynpro? if yes than how? please give code also

    Hi Kapil,
    We cant connect one outbound plug to 2 views.  To navigate from one view(ex:FirstView) to another view(ex:SecondView), FromView should have one outbound plug, SecondView should have one inbound plug. If u need to go to ThirdView from FirstView, then again FirstView should have one more outbound plug and ThirdView should have Inbound plug. Totally FirstView have 2 outbound plugs to each view and other views have their own inbound plugs.
    (However We can create separate links for outbound plug to 2 views. But we can connect to only one view which we have linked first)
    Hope this clears ur doubt.
    Regards,
    Kalai.

  • Outbound plug, confusing error message: no navigational link attached

    Hello,
    I just finished the WebDynpro Quiz tutorial and deployed the application. Unfortunately when pressing the start button the application dumps and I get a stack trace
       com.sap.tc.webdynpro.services.exceptions.WDRuntimeException:
    Cannot navigate via outbound plug StartQuizOut of view WelcomeView
    because there is no navigational link attached to it
        at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:349)
    indicating that there was no navigational link attached to my plug StartQuizOut. However the link is definitly there.
    As sources are not provided I cannot debug into the class named in the trace.
    Could someone please give me a hint. I think I did everything according to the tutorial, but I am stuck now.
    Regards,
    Sebastian Kamp
    P.S. I searched this forum for "no navigational link attached"; there are some threads with a similar problem description, but no solution is provided.

    Hi Zita,
    thanks for your answer. I kind of solved the problem. When following the Tutorial I ended up for some reason with two versions of/references on (?) the WelcomeView - one was embedded in the QuizViewSet, the other directly in the Quiz-Window - don't ask me how that happend. Anyway, both were identical except the navigation links. The embedded view had all the navigation links required, the other didn't. So eventually in despair I deleted this view.. and now it works fine.
    Regards,
    Sebastian

  • How to pass parameters of outbound plug of one view to other view...

    Hello All,
    i have a scenario like this.
    1) i have two views(View1, View2) and iam calling View2 using View1 Outbound plug which is having one parameter(Par1). iam filling this parameter in lead_select method using
    "wd_this->fire_op_to_display_plg (
    par1           =   itab-name1
    In the debugging iam able to see Par1 is filled with value.
    2) In View2 iam calling View1 using Inbound plug with no parameters.
    3) I have to pass this Par1 which i got in View1 to View2 so that i can use this for displaying the output(this parameter is mandatory in processing the data of View2.
    Could any one suggest how can i approach to solve this problem step by step.
    Thanks,
    Sree.

    go to the the method of inbound plug in methods tab of view 2
    and add the same parameter with same name and with the same type and directly access in the method..
    see the picture  test is the inbound plug
    http://flickr.com/photos/28584284@N04/2845020873/
    Abhi

  • I have a Cisco/Linksys WRT-54G wireless router and 2 Airport Extremes (the small ones that plug directly into the wall). Is it possible to extend the network from the router using these two AEs? I have a DVD player and Ext HD plugged into the router too..

    I have a Cisco/Linksys WRT-54G wireless router and 2 Airport Extremes (the small ones that plug directly into the wall). Is it possible to extend the network from the router using these two AEs? I have a DVD player and Ext HD plugged into the router too. Any ideas? I'm guessing the only way is to do what I've seen in these community pages which states that it can be done but it will drop the bandwidth by 50%. Thoughts?? Thanks!

    The Cisco/Linksys WRT-54G was one of the very few routers said to be compatible with Apple's implementation of WDS (Wireless Distribution System) settings.
    The info that I have on file indicates that only the WRT-54G versions 4 and under were compatible, so that would be one bridge to cross.
    Even if you find that your Cisco/Linksys might be the right version, Apple never published instructions on how to configure the Express devices with other manufactures, so users were left to their own devices to try to figure out how to get things working. Apple's instructions to connect to other Apple devices are in the link below:
    WDS network
    If you were hoping to use 2 Express devices in this type of configuration...even if it works...the bandwidth penalties will be extremely severe.
    The first Express drops the bandwidth (and speed) on the entire network in half and the second halves everything again. So, the result, in effect would be a "g" wireless network running at 25% speed. Few users would consider installing this type of network.
    At this point, it becomes one of those things where the fact that you might be able to do something does not mean that there would be much value in doing so. But, it is your decision to decide if you want to try to proceed.

  • Is it possible to Create dynamic outbound plug and it's navigation link?

    Hi,
    i am trying to create an outbound plug in runtime dynamically, is it possible?
    I have found out how to create the outbound plug in wdDoModifyView: "<b>view.getViewInfo().createOutboundPlug()</b>"
    but the problem is how do i set the plug name, and how do i create it's navigation link to bind him to an inbound plug in another view.
    Thanks,
    Carmit

    Hi Carmit,
    the following code snippet creates a link between a newly created outbound plug (outbound plug name is not really necessary) and an already existing inbound plug:
    /* targetViewInfo is the IWDAbstractViewInfo of navigation target
       srcViewInfo is the IWDAbstractViewInfo of navigation source
       Find inbound plug, must exist */
    IWDInboundPlugInfo targetPlug = targetViewInfo.findInInboundPlugs(inboundPlugName);
    /* Create outbound plug with "automatic" name */
    IWDOutboundPlugInfo srcPlug = srcViewInfo.createOutboundPlug();
    /* Create link from out to in */
    IWDNavigationTargetReferenceInfo targetReferenceInfo =
      srcViewUsage.createNavigationTarget(srcPlug.getName(), targetViewUsage, targetPlug.getName());
    /* Fire srcPlug somewhere...*/
    Hope that helps.
    Regards
    Stefan

  • Multiple inbound and outbound plugs

    Hi Experts,
    Can anybody give an example scenario where we compulsorily need multiple inbound and outbound plugs for a view??

    Hi snakar rao  ,
                           Suppose we have three views, a , b, c. Suppose we have a requirement like we need a button move_to_b on a, a button back in b which will move back to a, a button move_to_c on b and a button move_to_initial screen on c.
    in this case
    we need one out bound plug in a which will be connected to inbound of b
    one out bound plug in b which will be connected to inbound of c.
    in this case a needs two inbound plugs, one is for navigating from b and the other is for navigating from c
    if there is a requirement like we need to navigate from a to c directly also, in this case c need one more inbound plug thats to connect the inbound plug from a.
    Regards
    Sarath

  • Fire outbound plug of interface view controller?

    Hello Experts-
        In my WD project I have two apps A and B.
        I need to navigate from app A to app B.
        In the interface view controller of app A, I have created an outbound plug called GotoB.
        I determine the URL of app B using the WDURLGenerator and store that value in a string.
        In a view of the app A I have the code:
    <code>
    wdThis.wdGetAInterfaceViewController().wdFirePlugGoToB("URLtoB");
    </code>
        For some reason nothing seems to be happening when the event triggers in the view of app A that runs the above code. The view of app A just seems to refresh. The one thing that does happen is that on the refreshed view of app A if I click on the button to trigger this event again I get an 'app A has expired' WAS error.
        What am I missing here? How can I make the navigation from app A to app B work?
    Thank you,
    - Vik.

    Hi,
    well step by step:
    1) Create component Component1 (package="com.sap.sdn", window name = "Component1CW", View name="Conponent1CV")
    2) Create component Component2 (package="com.sap.sdn", window name = "Component2CW", View name="Conponent2CV")
    3) Create application "App1" (package="com.sap.sdn", Web Dynpro component="Component2", the rest - by default)
    4) In Component1CWInterfaceView create outbound plug "GoToComp2"
    5) In Conponent1CV add Component1CWInterfaceView as required controller
    6) In Conponent1CV add button and in action handler put following:
      public void onActionGoToComp2(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
        //@@begin onActionGoToComp2(ServerEvent)
        wdThis.wdGetConponent1CWInterfaceViewController().wdFirePlugGoToComp2();
        //@@end
    7) In component Component2 add Component1 as Used Web Dynpto Component (name="Component1CU")
    8) In Component2CW embed view (Component1CWInterfaceView) as Embed Interface View of a Component Interface, and set this view as default.
    9) In Component2CV add inbound plug "FromComponent1"
    10) In Component2CW link embedded View Component1CU.Conponent1CWInterfaceView.GoToComp2 with Component2CV.FromComponent1
    11) Build-deploy-run. Click on button. It should work.
    Regards, Maxim R.

  • ABAP webdynpro app not redirecting using Outbound plug in portal

    Scenario-
    There is one Abap webdynpro application APP1 calling another abap webdynpro component Comp 2 through outbound plug on a button click. This is working fine if service is tested independantly.
    SAP ECC system is having a webispatcher and the application should be accessed using webdipatcher only i.e. ECC should not be called directly.
    SSL has been configured b/w ECC and webdipatcher.
    The Abap webdynpro application APP1 is integrated into portal using Abap webdynpro iview.
    Setting in Portal system are reffering to Webdipatcher for ECC system instead of ECC system directly.
    Issue-
    App1 is loading successfully into portal and all the data is coming properly but when trying to navigate to second component on button click it is not navigating. iview is getting refreshed but not redirecting to required component and is still on the same application.
    Please suggest the reasons and solutions if anyone has clue about it.
    Regards
    Deepak

    Hi,
    Please refer to these links -
    How to secure WDA over an external facing portal
    WebDynpro ABAP and Portal Navigation
    WebDynpro ABAP and Portal Navigation problem
    Please check for the portal eventing between the applications.
    Regards,
    Lekha

  • Why do we use inbound and outbound plugs in abap webdynpro?

    hi all,
    why do we use inbound and outbound plugs in abap webdynpro?
    Thanks

    Actually we have 2 types of plugs
    1.View plugs
    2.Window plugs/Interface Plugs
    plugs are for navigating one view to the other and also you can pass the parameters along with the plugs.
    Outbound plug is to navigate from one view to other view,also we can pass parameters along with the plug.
    Inbound plug is like event handler/receiver of the outbound plug.
    Using window plugs we can call other Web Dynpro applications.for more information check this link.
    http://help.sap.com/SAPHELP_NW04S/helpdata/EN/45/19bf8c16f25d7ae10000000a11466f/frameset.htm
    Thanks
    Suman

  • Help Needed-Doubt in Outbound Plug Delegation

    Hi Experts,
    We had a requirement to create a view for displaying opportunities and provide navigation to the same from the view.
    We were getting exceptions for incorrect implement and we solved it using the delegation concept.
    Doubt:
    In our Z component window we have Outbound Plugs namely navigate_display,navigate_create and navigate_edit.
    But in our component usage we are using BT111M_OPPT component which has an OP DOCFLOW that need to be delegated as well for proper navigations to happen. The OPs of  BT111M_OPPT navigate_display and navigate_create has been delegated to OPs navigate_display and navigate_create of our Z component window respectively.
    Since we do not have a DOCFLOW OP in our Z component, is it correct if we delegate it to an available OP(say,navigate_display -  this has been currently done and it is working fine now) or should we create an OP and den fire DOCFLOW OP within the same in our z component window?
    Any pointers would be highly appreciated.

    Hi,
    Thanks for the reply.
    My doubt is now about the flow of the firing.
    While using navigational link concept,it just finds source and target as defined and navigates accordingly...but in this case
    i am unable to arrive at such a conclusion.
    My Z component had OPs in window : A,B,C.
    I embedd a std. component in my z component. Std. component has window OP D.
    I delegate the window OP of the std. component(D) to my Z component window OP(A).
    Which OPs should be triggered within D and A(param iv_outbound_plug value to be passed to the fire method)?
    So what would be the flow of the firing in two cases : 1. If i am navigating to the embedded view ?
    2. If i navigate back to z component view?
    Like i am not clear about the basic flow concept on the firing of OP of window and so i am confused about the usage.
    Please help if you knwo any link where i can get an idea about the same.
    I searched sdn but not to much avail.
    Thanks
    Swapna

  • How to fire outbound plugs of a window?

    I have a component which I want to re-use in applications. The component should have 2 outbound (interface) plugs which can be wired into parent applications. When the user clicks buttonA in the component it should fire outboundPlugA, likewise for buttonB we have outboundPlugB. My problem is that I can only seem to fire outbound plugs of the view and not of the window.
    Until now, we've solved this by firing interface events of the component controllers but it seems plugs would be more elegant.
    How does one fire outbound plugs of the window?

    OK, I've done what you said and have the following in the event handler (action of a button) in my view:
      DATA:l_ref_test TYPE REF TO ig_comp1_window.
      l_ref_test = wd_this->get_comp1_window_CTR( ).
    The compiler error message is:
    Method "GET_COMP1_WINDOW_CTR" is unknown or PROTECTED or PRIVATE.
    This method does not exist as far as I can see.

Maybe you are looking for

  • Photo storing app won't open after update.

    This is kind of embarrassing. I downloaded the app Private Photo Vault on my jailbroken iOS 7.1.2 iPhone 4. I used this app to lock away some inappropriate pictures I didn't need other people seeing in my library. It had worked perfect until the upda

  • PNG or GIF?

    Pretty sure this is a simple one - the PNG version of the company logo I'm using is around 250Kb, whereas the GIF file is about 20Kb. I keep reading in various places that using PNG for graphics files is preferable to GIF. Certainly so for designing

  • SGD, inventory management & asset tracking functions

    Is anyone using an app that allows scheduling of the servers within the database & displaying in with the main body @ single sign-on using the current UI? If so, please point me in the direction - I've pieced together a few apps that do what I need &

  • Cuic : SCHEDULED REPORT EXECUTION FAILED

    Hey. Every time i try to schedule a report to being send with an email and pdf i only get an email saying SCHEDULED REPORT EXECUTION FAILED The email has no subject or anything. If im scheduling it to send it as xls og html i works fine - but fails o

  • Modify target value in contract to be more than 1 000 000 000 LE

    I am working in ECC6, MM module, i want ask some quistions, 1-modify target value in contract to be more than 1 000 000 000 LE. 2-printing all un released documents. 3-all available reports detailed in MM. 4-modify percentage in fields to be 3 digits