Hide/Remove GAF Mainstep in a standard FPM application

[Former Member]

Hi,

I need to Hide/Remove a GAF Mainstep in a standard FPM application

It is a FPM CAF application with 5 roadmap steps

1 - 2 - 3 - 4 - 5

Now I want to completely remove step 4. Not disable.

The 4th step is just a review screen. Since the items can be reviewed in the previous item edit screen in step 3 my client want to remove the review screen. Step 4 completely.

Should be simple I thought.

First I went the configuration path which looked very promising.

With a custom Floorplan manager configuration I could just delete the step. I thought.

However that broke the application logic somehow.

Then I tried the dynamic way via FPM_OVERRIDE_EVENT_GAF

I added a post exit and called the IF_FPM_ GAF->HIDE_MAINSTEP

Technically that worked just perfect. The step went away and at a first glance the problem was solved.

But customers can't easily be fooled

My CAF now look like this

1 - 2 - 3 - 5

Urgh! I want it to be

1 - 2 - 3 - 4 (...of course ...)

Can I change the last step number sequence somehow.

Not the step description but the actual Step sequence number in the box

Or how can I solve this?

Best Regards!

Mikael

[Former Member]

Hi Mikael,

You can create another variant and than put only 4 UIBBs (Skip the one you dont want).

However even you hide the step, the code in the process event of that step still run. so you may need to incorporate the logic written in the undesired step into one of the existing step.

Try this.

Thanks & Regards,

Arvind

[Former Member]

Hello

I'm thankful for your suggestion however my problem is not about hiding individual UIBBs in a GAF mainstep

I want to hide an entire GAF Mainstep(roadmap step).

The hiding could be solved in the override exit but it had the consequense that the sequense numbering in the GAF was broken.

Before hide

1-2-3-4-5

After hide

1-2-3-5

My only problem is that I want the number in the last GAF main step box to be 4 instead of 5.

Any suggestion? There is probably a very easy fix for this. But I cannot find it.

Best Regards!

/Mikael

[Former Member]

Hi

As arvind already said. Create a new variant with only 4 steps . On FPM start event, set the vriant to your new Variant.

I think this is the simple way you are looking for.

regards

Senthivel

[Former Member]

Hi Senthivel

I ever used the way you have suggested, but I have a new problem. Although I have set a new variant id on the FPM

START event, but how could I restart my current fpm application?

You know my variant-switching button is in the main step 1 of Variant 1, and my idea is to click this button and then my application navigate to Variant 2 (which has fewer mainsteps ) .

Thanks.

Best Regards,

Alex

[Former Member]

Hi Alex

You can fire the event to start over onece again.

data: lo_fpm type ref to if_fpm,

lo_event type ref to cl_fpm_event.

lo_fpm = cl_fpm=>get_instance( ).

lo_event = cl_fpm_event=>create_by_id( cl_fpm_event=>gc_event_start_over ).

lo_fpm->raise_event( lo_event ).