Hiding FPM "Close" button in Portal/NWBC

Hello,
First some background, when you launch a WDA FPM application in the portal on of the standard buttons that it shows is the "Close" button. This button allows for the closing of the current browser window, When the FPM application is displayed inplace in the portal, this sort of behaviour is not very useful!
There was a thread : Re: Disable 'Close' button in Standard billing FPM Application in which Thomas Jung gave a detailed explanation of why this button was appearing and a very good suggestion on how to stop it.
I understand how I can hide this button - albeit a long winded process when the element is not available for personalisation unless you launch the application from NWBC or a portal (and with our dev portal not by default pointing to our configuration master client...) sigh...
I also understand that the WDA application is completely unaware that it is in an external portal window, or displayed inplace in the portal (although if it calls a new portal URL it can specify whether it should be displayed inplace or external).
What I don't understand is why this is the case - The portal has an API - Class AbstractNavigationConnectorNode method getShowType which returns whether the window is external or inplace, surely the WDA handler for the portal could query this and expose it to the WDA frameworkn through the interface IF_WD_PORTAL_INTEGRATION. Then it would be simple to hide the close button for inplace windows and show it for external windows.
Given that the portal allows users to launch whichever pages they want externally (although I tend to always turn off this option) it is very hard (i.e. not possible) for us to know for sure if the application will be launched inplace or externally - so "hard coding" the visibility of the close button by personalising the application is not a great solution.
WDJ is aware of the inplace/external nature of the portal window that it is running in and applications do code to support this. It seems to me an omission that WDA does not have this same level or knowledge of the portal environment that it is running in.
Are there any plans to extend the IF_WD_PORTAL_INTEGRATION interface to support this? Or are WDA applications destined to a less informed life than their WDJ cousins.
Sorry for the rant like nature of this post - but I hope that someone from SAP might be able to help me understand this problem.
Cheers,
Chris

Hi Chris,
Sorry about the late reaction. I think that is because of the nature of the question and the person who is asking. You are one of the expert people who are in SDN to help people. If you ask such questions then it is mostly stay not answered :).
I have encountered this problem earlier this year and also we have had several emails between Thomas Jung. We are not coming further than to follow Thomas suggestion to Disable the close button in Portal.
regards
Senthivel

Similar Messages

How to Hide FPM Close button

Hi,
I have created one FPM application. When that application is called from portal, an aditional button 'CLOSE' is appearing.
I did not put that button to FPM application and when I test the application from R/3, the button is not appearing. But it appears on portal. How hide this close button ?
(I have also posted the same message to FPM Forum.)
Thanks in advance..
Vikrant

Hi,
1 Open WDC FPM_GAF_COMPONENT.
2 Go to Web Dynpro Application -> <Application> -> Applic. Configurations.
3 Copy <Aplication config> to some u2018Zu2019 Application Configuration name and save as local object.
4 Open that application in admin mode and copy the URL.
5 Add that copied URL to some role so that it can be displayed in Portal or NWBC by taking care of parameter u2018sap-config- mode=Xu2019 must be in URL.
6 Open that application in Portal or in NWBC.
7 Right click in Contextual navigation area.
8 Select u2018Setting for Current Configurationu2019.
9 Here set the u2018Closeu2019 button visibility as u2018INVISIBLEu2019

Another Issue of ClOSE button in portal environment

If I have dirty data detected in my FPM based WD app and I click the close button on toolbar, it warns me a message box to ask me continue or not, If I continue, it stops on the original window rather than close window without saving.
But the close fork on the right-top of the widnow works normally.
I think they should behavior the same.
regards Bill

Hello Bill,
if you have dirty data on the screen it should always be asked if you would like to exit the application without saving it. I don't know exactly how the behaviour of the portal is when closing the application by pressing the 'X' on the upper right corner of the browser - but you are right, it should behave in the same way.
The best thing would be to open a message to our queue so we can decide internally which components are involved.
When doing this please give us very detailed information about:
1) a scenario description where you have found issues (information about the use case, names of involved FPM application(s) and component configurations, your package)
2) the environment where the issue came up (link to portal and a user/password to recreate the scenario, the appropriate backend system with logon data so we can also have a look into your configuration, explanation how to navigate to your application on portal side).
Thanks and best regards,
Julia

Disabling the Close Button of JFrame or Frame

Dear Friends,
can anybody please help out to solve the problem i am having in disabling the close button of Jframe . Or try for hiding the close button from the screen
thanks kalyan

to disable the close button
myFrame.setDefaultCloseOperation(WindowConstants.DO_NOTHING_ON_CLOSE)

Hiding Close Button

Hi,
I have created one FPM application. When that application is called from portal, an aditional button 'CLOSE' is appearing.
I did not put that button to FPM application and when I test the application from R/3, the button is not appearing. But it appears on portal. How hide this close button ?
Thanks in advance..
Vikrant

Hi,
1 Open WDC FPM_GAF_COMPONENT.
2 Go to Web Dynpro Application -> <Application> -> Applic. Configurations.
3 Copy <Aplication config> to some u2018Zu2019 Application Configuration name and save as local object.
4 Open that application in admin mode and copy the URL.
5 Add that copied URL to some role so that it can be displayed in Portal or NWBC by taking care of parameter u2018sap-config- mode=Xu2019 must be in URL.
6 Open that application in Portal or in NWBC.
7 Right click in Contextual navigation area.
8 Select u2018Setting for Current Configurationu2019.
9 Here set the u2018Closeu2019 button visibility as u2018INVISIBLEu2019

Close button - FPM WebDynpro - not working after upgrade NW 7.01/SP10

Hi,
I have developed a form using FPM Webdynpro. When click on a workitem in UWL, it launches the form which I have developed.
One of the standard buttons on the form is "CLOSE" button (Which automatically appears). This was useful to close the window and was working fine all these days.
Over the weekend our basis team upgraded the system to Basis patch SP10 and NW 7.01 SP10 patch for Portal.
Since then when I click on "CLOSE" button, it doesn't close the window and message on the window is "Application was terminated; you can close the window".
Please let me know how to resolve this issue. Thanks.
Regards,
Vijay.

This is to do with web browser we use. When you press close button the window.close script is called. However the browser checks if window.opener is filled or not. If it is empty you get warning message to confirm your action.
please read it here how logoff is working
[http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/6af21301a907bee10000000a42189d/content.htm|http://help.sap.com/saphelp_nw70ehp1/helpdata/en/48/6af21301a907bee10000000a42189d/content.htm]

NWBC - hiding/greying out buttons and OBN errors

Hi,
I'm working with Environment, Health & Safety via NWBC, but having great trouble influencing the NWBC screens.
I am backend security proficient enough, however I cannot seems to figure out how the buttons on the NWBC side are controlled,
hidden or greyed out. They don't always match with the ACTVT fields that you have in your backend authorization roles.
Things such as Work Centres, the left side-panel/navigation menu I can control, that is not too difficult. What I want to know
is why sometimes buttons are greyed out in certain forms or screens and how I can authorization trace that. Almost nothing of
what is going on in NWBC or in dynamically created POWL screens leave any traces on SU53 authorization error reports.
Who has some good pointers on how to get more grip on NWBC behavior of mostly
- buttons (hiding, greying out)
- how to find the correct missing services
and
- other OBN errors ?

Usually it is the application specific POWL feeders which define what actions are available. POWL will automatically disable buttons where the action isn't listed as support. In other words this is a application specific problem, not a NWBC one.

Finder close button missing

Hi All,
Upgraded to Yosemite, now the finder red, yellow and green close/ minimise buttons are missing.
I can still close this by clicking where they should be.
Is this me or have Apple gave us another dud OS?

Hello Mathias,
for the close-button we are using a WD ABAP API to determine
whether to activate the close button or not.
The note #1234843 has been published by WD ABAP to classify in
which situation the close functionality should be available and
when not. The change that has been made with the last transports to the
EhP4 systems - the only change with the close functionality is that
the close button won't be displayed in FPM standalone-applications
anymore.
They have done this because of negative side effects in standalone mode when closing the window.
Best regars,
Julia

Close Button for Web Dynpro in an iView launched from UWL

Hi All, this sounds like such a simple thing but its really got me thinking.
Have a web dynpro application launching form the UWL into an iView (using the IViewLauncher, I'm using this so I can change some visual effects of the application with the iView). The application is the LeaveApprover application.
Need a close button on the confirmation screen. Have tried the following code called from a Close button:
     try {
          String url = WDURLGenerator.getWebResourceURL(wdComponentAPI.getDeployableObjectPart(),"closepage.html");
          TaskBinder.getCurrentTask().getClient().sendRedirect(url, 0);
     } catch (Exception e) {
          e.printStackTrace();
The closepage >>
function closeWindow()
{var currWindow = window.top;
currWindow.opener = window.top;
currWindow.close();
onload run the closeWindow function
This is a test file to close the window....
This works if I use the standard UWL launch but DOES NOT WORK with the iViewLauncher.
Also tried creating an exit plug in the interface view and calling it from my close button, but no luck with either.
Please help. Thanks Brian
Edited by: Brian Carter on Dec 8, 2009 11:54 AM
Edited by: Brian Carter on Dec 8, 2009 11:55 AM
Edited by: Brian Carter on Dec 8, 2009 11:58 AM
Edited by: Brian Carter on Dec 8, 2009 11:59 AM
Edited by: Brian Carter on Dec 8, 2009 11:59 AM

Hi Brian,
we had a similar problem in the past. We wanted to call a normal Button placed on the WebDynpro View and the close script was saved in the km content in portal.
We solved it with an own project in NWDS including the html Files.
Follow the link and you find our solution. Hope it helps.
Re: Portal navigation problem

Browser close button / unload event

Hi,
In Ie8 session is carrying when i close the browser using X button. Is there any way to capture this browser close button or any portal unload event.
Thanks
Manu

There is no clean way to do this. The only way i know of is to have a private global javascript variable true/false (true = show the popup, false = show popup) where the default value is true. On every click of link / form submit where you need the popup to be suppressed , set the value as false. (you can do this using a js library which can attach events to onsubmit, onclick of all links)
However the behavior you are proposing is really , really annoying (as a user), consider your interface before implementing something like this. Valid usecases are prompting the user to save changes before leaving the page, not you are leaving the website (Thats why i typed something or closed the browser)

Close Button in OIF is missing

Hello
Unfortunately we don't see any CLOSE button in an OIF application. Our test applications don't define the parameter FPM_HIDE_CLOSE. Therefore we don't have a glue why the close button is not displayed. Did something change within FPM?
Regards,
Mathias

Hello Mathias,
for the close-button we are using a WD ABAP API to determine
whether to activate the close button or not.
The note #1234843 has been published by WD ABAP to classify in
which situation the close functionality should be available and
when not. The change that has been made with the last transports to the
EhP4 systems - the only change with the close functionality is that
the close button won't be displayed in FPM standalone-applications
anymore.
They have done this because of negative side effects in standalone mode when closing the window.
Best regars,
Julia

Disabling default close button in JFrame

hi,
in JFrame there are by default 'minimize', 'maximize' and 'close' button. is it possible to disable or not to show the 'close' button'
regards,
tom

If you want to control the closing of the frame you can use
frame.setDefaultCloseOperation(JFrame.DO_NOTHING_ON_CLOSE)If you are interested in listening whether this button was clicked (for example as an alternative to a "Close" button you can register a WindowListener and handle the windowClosing(...) event
About disabling/hiding - maybe you will have to subclass the frame header UI class, which is L&F specific.
HTH
Mike

How to avoid the "Save As" dialog when using "Close Button"

Hello All,
I am facing a problem while closing a pdf file.
I am using the following code to Open a pdf file.
CAcroApp objAcroApp = new AcroAppClass();
CAcroAVDoc objAVDoc = new AcroAVDoc();
objAVDoc.Open(C:\\new.pdf,Sample);
objAcroApp.Show();
After opening the document I am **** some changes (adding markup) in the file.
Then I am closing the file using the Close Button and in YES for the save confirmation dialog.
Here is the problem.
After giving YES, I am getting a Save As dialog with "Sample.pdf" in the FileName box.
I am getting this only in Acrobat 9.0.
When I tried the same in Acrobat 8.0 I didnt get Save As dialog. It saved with out "Save As" dialog in "C:\\new.pdf".
I need to give the same behavior in both Acrobat 9.0 and 8.0.
Please help me out to fix this issue. Thanks in advance.
Regards,
Mohd Mustafa SK

In what you have posted, there is no reason it shouldn't work the same way in Acrobat 9. I would recommend that you submit your complete application to developer support.

How to suppress Save As dialog when using the Close button on an editable pdf

Environment: Windows 7, SDK 9, Adobe Acrobat Pro X, Visual Studio 2010 Professional
Summary: when a document is opened for editing using automation, edited, then closed using the "Close" button, the confirmation dialog appears, "yes" is selected and then the "Save As" dialog appears. It should save without the "Save As" dialog in the same way it does were the document opened from Adobe Acrobat directly. My question is, is there any flag to set which governs whether the "Save As" dialog appears as part of the close document process. It is behaving as if the document is read-only upon close. (it isn't)
This is how the document is opened from C++:
if(SUCCEEDED(hr = ::CoCreateInstance(__uuidof(Adobe9::Acrobat::CAcroAVDoc), 0, CLSCTX_ALL, IID_IUnknown, (void**)&pUnk))){
hr = OleRun(pUnk);
if (SUCCEEDED(hr)){
if (SUCCEEDED(hr = pUnk->QueryInterface(&pAVDoc))){
hr = pAVDoc->Open((BSTR)CComBSTR(strPath), strDocName, &bRet);
Even when the plugin is removed from the plug_ins\AcrobatSDK directory, the behaviour is the same.
Another reproduction is running the BasicIacVC sample, commenting out all lines from gAcroPdDoc->Close(); in InitInstance() and returning TRUE. If an editable document is opened using the sample, edited then closed using the "X" button, the confirmation dialog is followed by a "Save As" dialog as if it were a read-only document which it is not.
Any suggestions would be appreciated.
Regards,
Evan

Yes, it does. (as long as the pdf has been opened via a COM interface)

Not able to get the minimize maximized and close button and its running with full screen mode.

Hi
My Thunderbird is running with ubuntu OS and while using some shortcut key my thunderbird mailbox switched to full screen mode. now i am not able to resize it's view and also not able to see minimize, maximize and close buttons on top left corner.
Please help me out.
Thanks

I'm also running Ubuntu. Not sure how you got there, but you can try a Control-Q to quit. Then restart it and hope in comes back normal.

Hiding FPM "Close" button in Portal/NWBC

Similar Messages

Maybe you are looking for