Navigation between FPM OIF, GAF and vice- versa

[Former Member]

Hi

Is it possible to navigate between OIF and GAF??

Scenario:

I have a component built using OIF FPM, in the component i have a Button and on click of button is it possible to completely hide OIF FPM and call a new component that executed GAF.

Also after completing GIF steps, is it possible on click of button i land back to same position of OIF FPM where i started?

Regards,

SJ

[Former Member]

thanks for all the replyes

[ChrisPaine]

Basically, can you do a suspend - resume with FPM applications?...

Well, not that I know of. You could write your FPM app in such a way that you could store its state at a given point and resume it again. But not really just navigate away to another app and comeback with everything still the same.

The main reason I do not think it would be possible without explicitly coding "save of current state, reload of state" functionality is that the FPM is by definition only allowed to be defined once within any given memory space - as although the FPM is an instance - you can only have one of these at a time as the attribute go_instance of CL_FPM is a static attribute.

This is also why you can't embed a GAF inside a OIF FPM and vice-versa.

[Former Member]

Yes, Basically, can suspend - resume with FPM applications be possible?...

If not navigate away to another app and comeback to old OIF with everything still with same state....

Is it possible to replace complete OIF (O1) window with other GAF (G1) Window and proceed with other OIF (O2) window....

I have 5 tabs created using OIF, and each tab will call other specific GAF component.

So is this scenario possible and on call of GAF from one tab, is it possible to complete overwrite (hide) all the OIF tabs, including hiding IDR?

Many Thanks,

SJ

[ChrisPaine]

Sorry, I don't think so.

You couldn't launch into the current window, and then swap back.

This is because of the issue I've already mentioned - the FPM instance is singleton -only one can exist in any given memory space.

so you could build your components/applications such that:

OIF app saves current state - potentially in singleton/static class attribute

launches GAF app replacing current OIF app

GAF app completes - relaunches OIF app

OIF app checks for previously saved state - if one exists - reloads OIF app in that state.

Save/resume would be a pretty cool thing for the FPM to have. I'm really not sure why SAP have made the FPM singleton - in WDJ it wasn't - the reference to the FPM instance was passed to each component through an "onInit" method - but nothing like this exists in WDA, instead we just have the static get_instance method.

Perhaps later versions of the FPM will allow us to have multiple FPM instances at the same time, but currently, we can't do it.

[Former Member]

Little confused with the below two lines..

You couldn't launch into the current window, and then swap back. 

launches GAF app replacing current OIF app

So GAF is launched in same window or separate window.....if in same window it means it's able to replace whole OIF window with GAF?

So i do a final conclusion based on what i understand, ignoring saving current state is....

It's possible to navigate from OIF to GAF in same window (ignoring saving of current state part), just navigation in same window.

[ChrisPaine]

> confused

Sorry, let me try to be a little clearer!

You would have to completely launch a new application which would completely replace the current application. This would not be in the same "window" in WDA terminology - but in the same browser window, portal page, etc.

NB the FPM has a very handy interface IF_FPM_NAVIGATE_TO which you can get from the IF_FPM~GET_NAVIGATE_TO method.

It might be worth pointing out that it is possible to suspend and resume a FPM application - but not to launch another FPM app...

see the section in the [Floorplan Manager Developer Guide:|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/90f3cfd2-46d0-2b10-b3ab-eabf3452cc50]

>The Suspend and Resume feature enables an FPM application to remain in a

>suspended state when a user navigates to a URL. When the user navigates back to the

>FPM application, the Suspend and Resume feature allows the application to be

>resumed in the exact state it was before navigation occurred.

However, it is important to note:

>Suspend and Resume is currently limited to URL navigation.