Not able to navigate to Sub roadmap Steps

[carlin_willams]

Hello All

I have created FPM GAF Application with below steps

Main Step 1 Main Step 2 Substep 2.1 SubStep2.2 and MainStep 3.

Problem is I am unable to navigate subroadmap i.e 2.1.

When I am I am clicking Next button Main Step2 directly going Mainstep 3 it is not going to 2.1 and 2.2

How can I resolve this. Please help.

Thanks & Regards

CW

Edited by: CarlinWilliams on Jun 10, 2011 2:10 PM

[Former Member · Accepted solution]

Hi Carlin,

For the navigation to proceed to the substep from the mainstep, you would need to specifically code to "change the step" from the mainstep to the substep. If such a code were to be incorporated on "click" of next from MainStep2 to substep 2.1, then one would never be able to go to Main3 from Main2 on click of next on Main2, as it would always be rerouted to Substep 2.1.

A better approach would be to include a FPM toolbar button in the Main2 step, the handler for which would contain the code to trigger the "change of step" event. The code can be found as below to achieve this:

Quoting from the FPM cookbook:

Substeps are not visible at startup, but all main steps that are a possible
starting point for substeps are indicated as such on the Roadmap Element at
runtime. Whether a substep is completed or not at runtime, depends on the application context and the user input. Therefore, substeps are statically declared but activated at runtime by the application (via the FPM API).

Adding and Activating Sub-Steps
Procedure
The configuration of substeps is similar to that of main steps. You can add one or
more substeps to a main step and each substep can contain one or more UIBBs.
To add substeps, perform the following steps:
1. In the FPM Configuration Editor, open the Component Configuration
window.
2. In the hierarchy, select the main step to which you want to add a substep.
Choose Add Sub-Step from the action region.
3. In the attribute view, enter the following data:
o SUBSTEP: Enter the Component ID andName. The name will be
shown at runtime beneath the corresponding substep.
o SUBSTEP_UIBB: Enter the Component and Window. In Window enter
the name of the Web Dynpro window of the interface view (not the
name of the Web Dynpro view itself).
After a substep has been configured statically, you may invoke it at runtime via the
FPM API. This is done by raising a special FPM event. Before raising this event, the
event parameters are populated with the corresponding substep ID that you want to
use. This is shown in the sample code below:
Syntax
1. DATA: lo_fpm TYPE REF TO if_fpm,}
2. lr_event TYPE REF TO cl_fpm_event.
3. * get reference to FPM API
4. lo_fpm = cl_fpm_factory=>get_instance( ).
5. * create event
6. lr_event = cl_fpm_event=>create_by_id(
cl_fpm_event=>gc_event_change_step ).
7. * fill event parameters
8. lr_event->mo_event_data-set_value(
9. iv_key = cl_fpm_event=>gc_event_param_mainstep_id
10. iv_value = <ID of Main Step> ).
11. lr_event->mo_event_data->set_value(
12. iv_key = cl_fpm_event=>gc_event_param_substep_id
13. iv_value = <ID of Sub-Step> ).
14. lr_event->mo_event_data->set_value(
15. iv_key = cl_fpm_event=>gc_event_param_subvariant_id
16. iv_value = <ID of Sub-Step variant> ).
17. * now raise event
18. Web Dynpro_this->fpm->raise_event( io_event = lr_event )