How to add a User parameter yes/no within Groups Box parameter that also works in an FME Flow APP?

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!

Hi guys,

Thanks for quick reply!

I’m working with a script that someone else created couple of months ago. What I’m trying to do is to improve the script as much as possible and make it more user friendly for the end users. But I’m afraide I have to change quite a lot in the script. I have many groups and inside these groups I have a bunch of parameters. For example, in the picure below, the Group box “Byggnadsdelar”, I have 8 user parameters connected to that specifik group. With the “Choice” parameter I would have to import the layers from the database(s) in the Choices table right? The thing is that I have like 8 Group box and between 5-12 parameters in each group. 

The end user want to choose which parameters or maybe a whole group it wants to add to the end product. Basically what the user want to do:

1. Draw a polygon on the map in the FME App
2. Choose which of the approximately 50 parameters should be included in the map (reading from different databases)
3. Run the script
4. Download the map with the dwg format.

Please see the attached original fme workspace in this message.

Hi ​@souryana,

I apologize for the confusing user interface. In FME Flow 2024.2, deselecting a group actually does disable parameters within the group, it just isn’t clear until you hover over the checkbox. You can see in my GIF below that it looks like the parameters are still checked and active, but when I hover my mouse over them, it shows that I cannot edit them. In other words, they were successfully disabled. I can only edit the parameters within the group once the group’s parent is set to true.

This is clearer if you deselect the group while one of its child checkboxes is set to false. You can see this has greyed out the checkbox, making it much clearer that this parameter was disabled.

I added a logger to the workspace and after running this job in FME Flow from a Workspace App, both the “Kartografisk text transport” and “Gatunamn” parameters are shown to as “<Unused>” which is consistent with what is shown in FME Form’s translation log. The group’s parent parameter will show a value of “No.”

In contrast, if the group were checked (enabled), the group’s parent parameter will show a value of “Yes” and the child parameters “Kartografisk text transport” and “Gatunamn” would show as “No” and “Yes” respectively in the log. 

In FME Flow 2025, whether or not the parameters have been disabled are much clearer in the Workspace App UI. You can see the checkboxes are greyed out even when they’re still checked instead of remaining fully black.

If you want to move forward with the choice tree to make things clearer for your users, you can speed up choice tree creation by creating a JSON document with all your group and layer names that you can Import to the choice tree.

Example JSON file contents:

{
  "Kartografisk text transport": {
    "Kartografisk text transport": "choice",
    "Gatunamn": "choice"
  },
  "Anläggningar": {
    "Anläggningar linjer": "choice",
    "Bro": "choice",
    "Tunnel": "choice"
  }
}

In your choice parameter, under “Choice Configuration,” select Import/From Dataset… and pick your .json file.

Then, click Next. Import Mode/Import From should be set to “Attribute names,”  then select the JSONFeature.

On the next screen, Select All for Value and Display, and for Import Order choose “Preserve Reader Order.”

The result will look like this in your workspace app:

Also, as an aside, we recommend using the exact same version of FME Form and FME Flow for the best experience.

Regards,

Nia