Hello ​@souryana , 

I think you maybe want to try a different parameter type. 

Maybe try the “Choice” type and build a choice tree which would allow you to select and unselect groups. See below. 

This is how your parameter choice would look. 

This is how it would look in your app. 

Yeah - I’ve been able to confirm this. Not great. In general I tend to avoid grouping for the most part if I’m planning on have a workspace run on FME Flow - there are just several cases where it can be a bit buggy as you’ve found.

Perhaps an alternative for you to use could be using the Choice type parameter - You can configure it so the UI work in a similar way. This also works as expected on FME Server. 

 

You will need to change your process though to handle the new values coming from the parameter. In the end it’s just one parameter with <sapce> or <comma> separated values for the choice. I’m not sure if this still makes sense for your workflow.

Hello ​@souryana , 

I think you maybe want to try a different parameter type. 

 

Maybe try the “Choice” type and build a choice tree which would allow you to select and unselect groups. See below. 

 

This is how your parameter choice would look. 

 

 

 

Ha! well two suggestions of the same thing has to be good advice!