Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
How about merging these items?Run > Enable All BreakpointsRun > Disable All BreakpointstoRun > Enable/Disable All Breakpointscf.Readers > Enable/Disable Feature TypesTransformers > Enable/Disable TransformersTransformers > Enable/Disable InspectorsWriters > Enable/Disable Feature Types
Highlight all canvas objects for whom an updated version is available in the current FME release. Then provide a way to upgrade each one, one at a time, to engage the latest functionality while allowing any parameter/port changes to be dealt with. (Readers and writers updatability can be voted on over here: https://knowledge.safe.com/content/idea/18878/versioning-of-readers-and-writers.html
Just today FME 2015.1.3.1 build 15573 has been available. Users who have registered in the download page received a notification mail, but others may not know yet. Since the update could contain some important hot-fixes, I think it should be informed to every user.How about checking for updates automatically whenever the user opened Workbench and other components of FME Desktop?- check for updates automatically when opened by default,- show a message box to prompt update if a newer version has been available,- the user can stop/start the automatic checking optionally. e.g. check a checkbox in the message box to stop; stop/start by a setting in the About dialog or FME Options.- manual checking can also be used (current menu: Help > Check for Updates).It may also be good if the user could choose the frequency of the automatic checking for updates. Once per Day, Once per Week, None, and so on.
1. In WorkspaceRunner, it is better if we have option to disable the reader or writer, it will be better. Disabling writer/reader should be done with the help of input itself.2. We are passing the parameters to workspacerunner with the help of csv/xls file. For each parameter even the format of attributes from coming in are same still we have to select manually. Automatic mapping of attributes with parameters will also help even better
***Note from Migration:*** Original Title was: Oracle SDO Writer to use calculated CS extents when creating sdo_geom_metadata entry When an Oracle spatial table is written, a metadata entry in user_sdo_geom_metadata is created with layer CS extents (Max X Coord, Min X Coord ....) in DIMINFO column taken from "Format Parameters" setting of the Writer Property menu. I think it will be helpful if FME allows CS extent settings on the "Format Parameters" tab to be OPTIONAL, in which case FME automatically calculate the extents from the source data for use in the created metadata entry.
The default behavior of the ListExploder in 2015+ is different from 2014 and earlier. Many users expect that the transformer behaves with "Use Incoming List" mode (it's equivalent to the default in 2014), but the current default is "Use Original" in fact. In the Community Answers, I have seen several questions caused by the conflict, and I myself often forget to check this setting too.The default itself is not an issue. It's the issue that the "Attribute Accumulation" parameters group is not expanded by default.Hope that the parameters group will be expanded (shown) by default.
***Note from Migration:*** Original Title was: Contrast enhancing transformer for rasters with various contrast enhancement algorithms A contrast enhancing transformer for rasters with various contrast enhancement algorithms.Technically a user can achieve this themselves, but the maths to do so is probably beyond most users (certainly is me).
I'd like to have an transformer to update data (e.g. ESRI File Geodatabase) for an ArcGIS Server Service. So the transformer should manage to stop the service, then update the data and last to start the service again...
For Workspace Runner, it would be nice if when you right click on the transformer, you can "Open workspace in new FME instance".Similar to the "Open destination folder" business.
Provide an Admin user an interface to create a custom SHARED RESOURCE FOLDER that is parallel to the default Data folder (ex. not under the default Data folder).The Admin user can then create subfolders in the custom SHARED RESOURCE FOLDER and have control over each subfolder's access by roles/users.Support Instance Reference ID: C108149
To be able to run the workspace from a compiled executable. A valid FME Desktop installation would be required.
Export and import your history (to a certain level?. This way you can continue some different testing paths without having to save multiple versions of your workbench.
Change the current "view 1" etc to the workbench name so that when multiple inspection windows are open it is easier to tell which is which
If I want to expose the list with PythonCaller,I must expose elements of list. eg._listField{}.name,_listField{}.typeIf can add "Lists to Expose" to Advanced Parameters,expose list will be easy better.
The Regular Expression Editor has been newly introduced in FME 2016 beta. It's a great enhancement, welcome.In my observation, the Test String which the user entered will not be preserved once the editor has been closed. The editor restores the default string "Enter a string to test here..." whenever the user opens it.The usability would be further better if the field could preserve the user entered test string for each transformer.
Allow for more projection systems in the webmaptiler. Some people need/want their web services in local projection systems. British National Gird would be very useful. Also give it more options for pyrmid prodduciton.
Sometimes I just want to trace the follow of features through the Workspace when debugging. I have to define a Breakpoint somewhere after one of the Feature Types - and make an educated guess for the first one, or maybe I've disabled a Reader/Feature Type.However it would be nice to be able to 'Run with Breakpoint' without one defined and popup a confirmation that says none found but would you like to use the first feature read to start the Breakpoint process. Clearly you couldn't 'Continue to next breakpoint' but could 'Step to next connection'. A very quick way of tracing a flow especially with multiple readers/feature types.
It would be nice to have the option to add the 'Redirect to Inspector' to your Translation Parameter Dialog. This could either be done to add it as a parameter (this way you can define to show or not to show it in the Translation Paramaters Dialog) or to add it standard to the Translation Parameters Dialog (but sometimes you don't want to show it there).
It's possible to define a condition to filter a breakpoint (right click the breakpoint > Edit Breakpoint). It can use the condition builder to define a test to trigger the breakpoint. If I have multiple breakpoints across a Workspace and trying to debug a feature with a given identifier, I'd like to specify that identifier value at runtime as a Parameter and fetch it into the condition builder. All breakpoints would then only trigger for that specific feature. You could use the operator 'like' for multiple.
***Note from Migration:*** Original Title was: Allow Selecting Multiple List Elements for Old (Input) Attribute Column in AttributeRenamer Updated: 2016-02-06In FME 2016.0, the ability to rename list attributes has been added to the AttributeRenamer. Instead, the List Element Selection dialog has been retired, and now you will have to edit the "Input Attribute" column manually if you need to rename individual elements of the list. e.g. change "_list{}" to "_list{0}". I feel a bit inconvenience.It might be better if the dialog would be restored with some enhancements:The user can choose "Rename List" or "Rename List Elements" in the dialog.If "Rename List" is chosen, the list name (e.g. "_list{}") will be set to the column.If "Rename List Elements" is chosen, the user can select one or more elements (indices), and then the element(s) (e.g. "_list{0}") will be set to the column.The column still can be edited directly.=====Original Idea:The "List Element Selection" dialog for the AttributeRenamer only allows a single element selection currently.If it would allow selecting multiple elements and insert rows into the Old Attribute column automatically, could reduce user's effort to enter multiple elements one by one, in the case where the user needs to rename multiple elements at once.
The XMLUpdater has two input ports - Document and Update, and at least one Update feature is always required even if the update operations don't require any Update feature. For example, this simple Rename operation also requires a useless Update feature input.I think it would be better that the user can omit inputting Update features if the update operations don't require them.The JSONUpdater may also be so.
Add a Python/Tcl function which defines a global variable with initial value, so that the user can call the function in Startup Python/Tcl script.
I have been tinkering around with some of the new transformers in FME 2016. I think the AttributeValidator and AttributeManager transformers are a fantastic addition but I would like to make one recommendation. When dealing with large data, I think its acceptable not to know what is in every field. Therefore I think it would be very useful if, as well as the field headings, it loaded the first line from the table. That way you get a snapshot of the data while filling in the parameters in these transformers.
AttributeCreator: If you create a series of attributes in the AttributeCreator, it is not possible to reference to an attribute that you created previously on the same AttributeCreator. Would it be possible to create a mechanism that makes it possible to call an attribute that is created in the same AttributeCreator.
***Note from Migration:*** Original Title was: Add Parameters to Control Decimal Places to GeometryExtractor and GMLFeatureComposer Hope decimal places will be controllable, similar to the Maximum/Minimum Decimal Places parameters of the GML writer.
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
