Regarding interface views inside a view.

Hi,
We have a screen in which a view uses interface views of two other components.
Depending on the link clicked anyone of the interface view should be displayed in the bottom of this main view.
I am using view container UI element for this requirement. Are there any ways of switching the interface view in a single view container element.. instead of creating two of them, each for one interface view.?
regards
Bharathwaj

Bharathwaj,
Yes, it is possible.
Create 2 outbound plugs in outer view, link them to corresponding inbound plugs of interface views.
Now on action fire one forementioned plugs.
Valery Silaev
EPAM Systems
http://www.NetWeaverTeam.com

Similar Messages

Regarding navigation from Interface View

Hi All,
i am trying to pass data from one component to other component via exposing the interface view controller of second component to 1st component via Used Webdynpro Component concept.
I am able to navigate from one component view to 2nd component view with the action of fireplug from 1st to 2nd. but i am not able to do
vise versa.
What i got, after embedding the 2nd view in the 1st component window, inbound plug is created automatically. If in the same view(embedded interface view) i try to place out bound plug i m not able to do. how to get this navigation from 2nd view to 1st view.
Please help me out.
Regards,
Deepak

Hi deepak,
I didnt work on it but giving just an idea....
till now you did....
i am trying to pass data from one component to other component via exposing the interface view controller of second component to 1st component via Used Webdynpro Component concept.
I am able to navigate from one component view to 2nd component view with the action of fireplug from 1st to 2nd. but i am not able to do
vise versa.
What i got, after embedding the 2nd view in the 1st component window, inbound plug is created automatically. If in the same view(embedded interface view) i try to place out bound plug i m not able to do. how to get this navigation from 2nd view to 1st view.
now to do vis versa you have to do all this things for other component. I mean expose 2nd component via Used WD component concept. now embed 1st view in 2nd component window. just reverse of what you did till now.
and take a view set where in first view area show the first navigation, and in the second view area of view set show the second navigation.
Am I clear?
PraDeep

Change Button for Interface View is Inactive

Hi,
I have created a Web Dynpro ABAP component & application.
Now I want to add URL parameters to it.
I went to interface view, I can see "change" button in menu but its not clickable.
Any idea why this is happening?
Thanks and regards,
Amey

Hi Amey,
IF you dont have any interface attributes or methods, there is nothing you can change in Interface View.
For Adding Parameters, goto your Application to add application parameters in Parameters tab.
You can chooose from existing set of parameters or Create a new parameter such as TEST1 & any default value like 1 or A etc .
Now goto your Window method HANDLEDEFAULT & frmo here you can access what value you are getting from the URL Parameter TEST1 by using below code...
data lv_configid type string.
lv_configid = wdr_task=>client_window->get_parameter( TEST1' ).
now IF for your application say zph_test02, if you are running URL as http://xxxxxx.xx/sap/bc/webdynpro/sap/zph_test02?sap-language=EN&TEST1=2
The value lv_configid will have value 2 now when application is launched with that url & parameter TEST1=2.
Thanks,
Phani Mullapudi

Help on Interface views

Hi,
I am aware that there is a 1:1 relationship with Interface view and a window.
1) But I am not sure for the purpose of the inbound plug "Default". What is the significance.
2) What does the plug type - startup / Resume/ Standard refer to ?
I am also aware that if a window has 'n' number of views and the user want to see a particular view on the startup, we have to enable the default option as 'True' in the view properties. There is only one view which can be made to have dafault as 'True'
Any suggestions to help me get clear would be welcome.
Regards
Gandolf

Hi Gandolf,
Please refer the following links which will help you in getting a fair idea about the navigational links and plugs.
Resume and Suspend Plugs:
http://help.sap.com/saphelp_nw04s/helpdata/en/68/3aee42c4257176e10000000a1550b0/frameset.htm
Inbound and Outbound Plugs:
http://help.sap.com/saphelp_nw04s/helpdata/en/47/455c6980f81962e10000000a114a6b/frameset.htm
Hope it helps.
Cheers,
Manoj

Required to Initialize interface view

Hello guys,
I am facing a strange issue while using viewsets in web dynpro java. The view set (Grid Layout)contains two columns, where the left side view contains the list of orders. when i click an order i navigate to the interface view of another component to display the details of the order. I ll also navigate to other views in the window of the interface view.
Now when i again click the order number on the left side to view the order details, the first view in the interface is not displayed. it only shows the current view which is active in that window. how can i resolve this issue.?
Kindly give me a solution..
Regards,
Karthikeyan R

Hi,
Please check whether the default property of the Interafce View is set to true.
Open the Window Editor -->right click on Interface View -->Check Default.
Thanks and regards

Component Usage / Interface Views

Hi Experts,
I have added two fields in CPGOE_DETAILS/ovefdetails view through AET.
Now I want to attach search help to those fields through compoent usage.
So I have created component usage of BP_HIER in the CPGOE_DETAILS.
I am able to call the search help view : SearchHelpNodesVs because it is default view in Interfave view SearchHelp for the first field.
for the second field i want to call the view : SearchHelpVS which is also available in interface view SearchHelp.
Please suggest the solution.

Hi Naresh,
the window SearchHelp has two different inbound plugs which you have to use.
- IP_SEARCH_NODES opens BP_HIER/SearchHelpNodesVS
- IP_SEARCH_TREES opens BP_HIER/SearchHelpVS
Just use the correct inbound plug to get the search you want.
Best regards
Matthias

How to make a view created using enhancement framework as Interface View

Dear Experts.
I Created A new View and window by using Enhancement Framework for a standard webdynpro comp. Now i want to use the same window as a UIBB in FPM , since in window properties interface view check box is unchecked it's not allowing me to use a UIBB in FPM.
Kindly answer for the following.
1) Is there any way to make a view a interface ( whcih is by default in nature but while creating from Enhancement framework behaivng Strangly).
2) If there is no way then how to use enhanced (additional View Created in Standard WDA comp) further like in FPM ( UIBB ).
thanks in Advance.
Best Regards,
Kranthikumar Palle

>
kranthi9121 wrote:
> Dear Experts.
>
> I Created A new View and window by using Enhancement Framework for a standard webdynpro comp. Now i want to use the same window as a UIBB in FPM , since in window properties interface view check box is unchecked it's not allowing me to use a UIBB in FPM.
>
> Kindly answer for the following.
>
> 1) Is there any way to make a view a interface ( whcih is by default in nature but while creating from Enhancement framework behaivng Strangly).
>
> 2) If there is no way then how to use enhanced (additional View Created in Standard WDA comp) further like in FPM ( UIBB ).
>
>
> thanks in Advance.
>
> Best Regards,
> Kranthikumar Palle
Hi,
Please see [https://cw.sdn.sap.com/cw/docs/DOC-21546|https://cw.sdn.sap.com/cw/docs/DOC-21546]
windows created through enhancement are local to component and hence they are not visible outside.
You need to find other way to provide your interface view to UIBB.

Firing the Suspend Plug of Interface View Controller of1 DC from another DC

Hi Experts,
Can you please let me know if it is possible to fire a suspend plug from a Component Controller?
I've been tried it before from View controller on some event and was able to fire the plug successfully but when I am trying to fire the same from the init method of the Component Controller or init method of the view controller, it gives me the below error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Instance of interface view controller XXXXCompInterfaceView does not exist.
I believe that it is not possible to fire the suspend plug from the Init method of either Component Controller or View Controller.
So, is it possible to fire the suspend plug in one custom method of a component controller if the custom method is called from some another component?
Please let me know.
Thanks & Regards,
Anurag

Hi Prashant,
When I am trying to fire the Suspend plug from my view on click of a button, I am getting the following error:
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Cannot suspend embedded component via outbound plug <Plug Name> of view <Interface View Name>
    at com.sap.tc.webdynpro.progmodel.view.ViewManager.fireSuspendPlug(ViewManager.java:209)
    at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:533)
    at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
Earlier, when I used to fire the plug from my DC; it used to work fine but now my DC is being used as a used DC in another component and since then I am facing this issue.
Currently, my DC is being used as used DC. I am not sure if I use any used DC, it would work or not.
Please respond if anybody has any suggestions.
Regards,
Anurag

How to call a view from Interface view

Folks,
How to call a view from interface view (onPlugDefault method) . I was trying to set context of controller but it is not working . What is the work around.
Manish

Hi Manish,
An interface view is created for each window that you have, which in-turn has views embedded, one of which is default. If you want to pass data which you have in your interface view, do the following
- Add your component controller in your interface view properties
- In the onPlugDefault method(I assume this is where you have the data available through URL parameters),set the component controller context variables like
wdThis.wdGetComContr.wdGetContext().currentContextElement().setName("John");
-Access these context variables in your view as well by adding the component controller as the required controller
Your default view will appear automatically when you call the application.
Regards,
LM

Fireing outbound plug of interface view from within component

Hi all,
is there a better way of firing an outbound plug of an wd component interface view than from within the interface view controller itself?
The problem is, that you easly get a cyclic reference if you evaluate inbound component plugs in the interface controller (usage from int view ctrl --> int ctrl needed) and then try to fire an outbound plug from this interface controller (usage comp int --> comp int view usage needed).
One workaround is to use some custom controller with usage of the interface view, but this doesn't seem to be a nice solution.
So is it possible to fire outbound comp plugs from, lets say the component controller - without any usage releation to the comp int view - instead, maybe via wdComponentAPI? If yes, could you provide a code snippet?
Thanks you and best regards,
Christian

Hi Christian,
this is not possible by using the public API only, i'm afraid. It is of course possible, if you decide to forget about the possible drawbacks of using methods and classes reserved for internal use. But you have to use it at your own risk. I hacked this together some weeks ago, don't know whether it still works
* Fires an outbound plug of an interface view with parameters.
* @param wdComponentAPI Component API "owning" the interface view.
* @param windowName Name of window
* @param plugName Name of outbound plug
* @param callerParameterMap optional Map of plug parameters.
public static final void fireOutboundPlug(
IWDComponent wdComponentAPI,
String windowName,
String plugName,
Map callerParameterMap)
throws WDRuntimeException {
// Find window requested
IWDWindowInfo windowInfo = wdComponentAPI.getComponent().getComponentInfo().findInWindows(windowName);
if (windowInfo == null) {
    throw new WDRuntimeException(
      "Can't find window: " + windowName + " in component: " + wdComponentAPI.getQualifiedName());
// Get info of interface view
IWDInterfaceViewInfo ifViewInfo = windowInfo.getInterfaceView();
if (ifViewInfo == null) {
    throw new WDRuntimeException("Window: " + windowName + ", no interface view info found");
// Find outbound plug
IWDOutboundPlugInfo outboundPlug = ifViewInfo.findInOutboundPlugs(plugName);
if (outboundPlug == null) {
    throw new WDRuntimeException(
      "The interface view: " + ifViewInfo.getName() + " has no outbound plug: " + plugName);
// Parameter passing
Collection plugParameters = outboundPlug.getParameters();
// TODO make check optional, check caller map parameter keys against existing
if (plugParameters == null || plugParameters.isEmpty()) {
    // No caller parameters allowed.
    if (callerParameterMap != null && !callerParameterMap.isEmpty()) {
      throw new WDRuntimeException(
        "The outbound plug: " + plugName + " has no parameters, callerParams must be empty/null.");
// TODO This is a hack, use of internal WD runtime classes and methods (don't use productive).
InterfaceView ifViewController =
    (InterfaceView) ((Component) wdComponentAPI.getComponent()).getController(ifViewInfo.getName());
ifViewController.navigate(outboundPlug.getName(), callerParameterMap);
Please remember, that not everything which is technically possible, makes sense
Regards
Stefan

Fire outbound plug from view in a DC to the interface view.

I have a DC1 which has a view.From this View I fire a outbound plug with a string parameter to an interface View's inboundplug with the string parameter.This view is in another DC2 and used DC in DC1.
Now when I try to Build the DC1,I get build error with the error log saying that the plug parameters arent compatible.But both the parameters are of same type.

Hallo Kent,
as long as your Comp A component keeps alive it also keeps it state when leaving it via navigation. By setting its lifecycle property as "manual" you can manage the lifecycly of Comp A on your own. This means the Web Dynpro Java Runtime will not destroy this component instance when leaving it via navigation.
To navigate back you can apply the cross-component navigation technique I described within my tutorial on https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/webcontent/uuid/751d003a-0b01-0010-8996-afbaa3fd5339">cross-component [original link is broken] [original link is broken].
Regards, Bertram

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.

How to define exit plug for interface view?

hi experts,
I am trying to define exit plug for interface view , but i am not able to make interface view into change mode. it doesnt allow me. what should be done/
Thanks,
saurin shah.

Hi ,
Check the Interface in the Window this will reflected in the Interface Window
Regards
Vikranth

Difference between interface view and interface controller

Hi,
What is the difference between interface controller and interface view?
When we will use interface controller and when we will use interface view?
How do we create an interface view?
How do we attach this interface view to a view in another component
Regards
MQ

Hi
Interface View Controllers
A) Implement event handlers which are called when ..
-starting (start-up plugs) Web Dypro applications
-a component is reached via navigation (inbound plugs)
B) Allow fireing outbound plugs (navigation)
C) Allow firing exit plug
D) Have no own context, public methods or events
Interface Controller of a Component
The interface controller of a Web Dynpro component contains all context nodes, events and methods of the component controller to which you assigned the Interface addition in the Controller Editor. These parts can be displayed in the interface controller view, although you cannot edit them here.
Interface Controller of a Component Interface
A Web Dynpro component interface can be created independently and defined so that it can be implemented later in any components (see working with Web Dynpro Component Interfaces in the Programming Manual of this documentation). That is why in this case you can define the context nodes, methods and events you require in the interface controller view. The relevant implementation then takes place in the component controller of the implementing component.
Check this links and work on it.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#13 [original link is broken]
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c87806865f26?rid=/library/uuid/49f2ea90-0201-0010-ce8e-de18b94aee2d#12 [original link is broken]
Interface view and interface controller
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f727d100-0801-0010-4cbd-b0ad5c161945
Difference between custom controller and interface component
Thanks and Regards,
Tulasi Palnati

What is the purposeof interface view property?

what is the purposeof interface view property?

Hi Rafi,
Interface View means Communication between two views in diff Contrallers.
http://help.sap.com/search/highlightContent.jsp
Regards
Vijay Kalluri

Regarding interface views inside a view.

Similar Messages

Maybe you are looking for