It would be great if you could generate a richer Parameters Prompt when using the Prompt and Run mode. For example, you could have different parameters depending on the value of one of them, or group them, or have possible values depending on others, etc. Maybe having subsequent dialogs could be a way of doing it. See:
http://gis.stackexchange.com/questions/97762/fme-c...
Merged Ideas:
User Parameters with conditional values by fgiron on January 8, 2016
If I want to set a private parameter dependent on a published one, I have to use a "script" parameter type. It would be nice to be able to choose a "conditional" type directly. Now you can only use conditional values in user parameters when setting them from transformers that have the Conditional Value option (https://knowledge.safe.com/questions/3477/published-parameter-with-conditional-values.html).
Custom Transformer UI Generation by fmelizard on October 29, 2015
Allow richer layout (grouping, etc) within custom transformer parameter UIs
Dynamic published parameters by tlabs on April 18, 2019
It would be nice to have Published Parameters auto-populate based on another published parameter.
Example:
There are 2 published parameters
1. Type: Text. Name: Airport Code. Input: CAB5
2. Type: Coordinate System Name. Name: Coordinate System. Input: WGS84-ABBOTSFORD-CAB5
User inputs Airport Code CAB5, and the Coordinate System would automatically select the above listed Coord Sys because there is only 1 coordinate system associated with that Airport Code.
Allow User Parameters to be grouped into sections. by sam.mcdonald on October 25, 2020
I believe it would be beneficial for end users if groups or sections could be created for User Parameters, which would segregate them into logical groups in the Server UI and Desktop Translation Parameters popup. Examples could be input files and output folders sections, and so on.
Please refer to the Layers.png image for a quick edit I did of the Server UI to demonstrate this.
Collapsable public parameter by todd_davis on October 17, 2017
In a number of situations there can be public parameter in either a workbench/custom transformer that may only need to be changed on the rare occasion (e.g. the default value will likely be used). I have instances where a transformer/workbench, may have over 10 parameters because of what a client wants in terms of options, and in most occasions they will really be dealing with say 4. The extra parameters can lead to confusion, or users not updating the correct parameters because of the crowded interface.
I am hoping that an extra checkbox could be added next to the "optional" and "published" in the parameter definition. Ticking this checkbox would mean that when a run/transformer dialog was shown that the parameters would be found in a collapsed "Advanced" section.
It would certain tidy up the interface, but still allow as many options as people wanted.
Ability to set parameter relationships by 1spatialdave on February 8, 2016
Occasionally when creating parameters to control a workspace it would be nice to be able to create a relationship between parameters to make it clear to the user running the process which parameters to set. For example if a user selects from a choice parameter that they would like to do a proximity search against restaurants, two additional parameters that were by default greyed out should then become available so that the user can enter a parameter value for the maximum number of results to be returned and enter the search radius. Its the kind of detail that could be applied when the parameter is created, like, 'set parameter as primary' and then you could add 'child' parameters to that primary.
Allow group the parameters by taojunabc on October 27, 2016
For a complex workspace, the user may have many parameters, the current FME does not allow the user to group parameters, but when many of the parameters, the parameter input dialog will be relatively messy. Hope to be able to allow the user to group parameters.
Conditional parameters by chrisw84 on May 31, 2017
I've had an internal client ask if FME/server could include parameters that appear/disappear or even change selectable values based upon parameters selected ahead of them. We have the ability to make parameters optional already, so can this be toggled dynamically?
