Hide Previous and Next default buttons in GAF?

[Former Member]

Hello to all,

I'm using GAF and I want to implement my own navigation logic. To be able to do that I need to hide/deactivate/remove the default 'Previous' and 'Next' buttons that come with GAF. How can I do that?

I've read this post: http://scn.sap.com/thread/1120913 and I found this:

Hi Julia,
I just found that it is indeed possible to hide the default buttons (Previous and Next) buttons that come with GAF. In the component configuration, choose View: 'Web Dynpro Built-In' from the top menu bar. Expand the element CNR_VIEW -> TOOLBAR_TOP, and set the visibility attribute to 'Invisible'. This would hide the default buttons, and you can use your own buttons to raise the FPM events 'Next' or 'Previous' to navigate between the views.
Kamal

but the solution they porpose does not work for me. In the "View:  'Web Dynpro Built-In' from the top menu bar " there is nothing, it is empty.

Of course, I've implemented the Interface IF_FPM_UI_BUILDING_BLOCK. Any ideas?

Thank you very much in advance!

[Former Member]

Thank you all,

@Harshith Reddy I don't know how to access to the screen you showed me. When I double-click  in the component configuration (sorry for the German )

I only get this screen

Could you please tell me how to get there? Maybe it depends on the version? I think we have a new one.

@Julia Bender I try to explain it a little better. What I want to do is:

Being at the first mainstep, I want to jump to the first substep when I click Next (Weiter - standard button). The problem comes becouse when I click directly with the mouse in the second mainstep, I jump down too, becouse the event for the button Next and clicking in any button is the same. I've tried to differenciate them in all possible manners, but I couldn't, there is always a point in that you really don't know if you clicked Next or the second mainstep. If I could hide these buttons, I could do an identical Next button, but with a different associated event.

Sorry for my English, I hope you get what I mean.

Best Regards!

[julia_bender]

Hello Daniel,

thanks for the detailed scenario description.

The standard behaviour of the Next button is that it is generally navigating to the next available mainstep. What we recommend when navigating to a substep is, having a button next to the Next step button which is responsible for navigating to the substep!

This navigation behaviour is the most understandable one for the user. It would be very irritating if the next step button one time navigates to a mainstep and the other time to a substep.

So my recommendation is to add another button next to the Next step button with the label e.g. "Navigate to substep xyz" or with the name of the action of the substep, e.g. "Maintain xyz data".

After you have implemented the additional button with a certain Event-ID, e.g. NAVIGATE_TO_SUBSTEP_1_1. This event you handle in PROCESS_EVENT of your UIBB or AppCC and fire another FPM-Event, which navigates you to this substep. The coding looks like this:

DATA: lo_fpm TYPE REF TO if_fpm,

            lr_event TYPE REF TO cl_fpm_event.

* get reference to FPM API

     lo_fpm = cl_fpm_factory=>get_instance( ).

* create event

     lr_event = cl_fpm_event=>create_by_id( cl_fpm_event=>gc_event_change_step ).

* fill event parameters

     lr_event->mo_event_data-set_value(

               iv_key = cl_fpm_event=>gc_event_param_mainstep_id

               iv_value = <ID of Main Step> ).

     lr_event->mo_event_data->set_value(

               iv_key = cl_fpm_event=>gc_event_param_substep_id

               iv_value = <ID of Sub-Step> ).

     lr_event->mo_event_data->set_value(

               iv_key = cl_fpm_event=>gc_event_param_subvariant_id

               iv_value = <ID of Sub-Step variant> ).

* now raise event

     wd_this->fpm->raise_event( io_event = lr_event ).

Best regards,

Julia

[Former Member]

I just want to do a comment to your answer, maybe it may be helpuf for anybody else the way I define the button to go into a substep.

I just define it into the Interface like as can be seen in the screenshot (sorry again for the German, but I think it is perfecly understandable)

I think it is easier when you can introduce the parameters direcly into the interface.

[julia_bender]

Hi Daniel,

the so called implicit personalization (tab Web-Dynpro-Built In) you can reach via the Admin-Mode. Just start your application and add parameter &sap-config-mode=X to your application.

Then open the context menu via right-mouse click and choose "Settings for current configuration".

Be aware that the settings you are doing here are valid just for the current client! So I would prefer the solution I already gave above.

Best regards,

Julia

[julia_bender]

Hello Daniel,

what interests me the most at the moment is: Why do you need a break-out scenario besides the next and previous buttons?

What is your navigation alternative? Please describe it in more detail.

Probably another and easier solution can be found if we understand what you would like to reach...

Thanks for your answer in advance and best regards,

Julia

[Former Member]

Hi Daniel,

Check this image.

In the TOOLBAR_TOP you have the container holding buttons.From here you can make those buttons invisible.