Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In the new parameter manager it is not possible anymore to edit the type of a parameter. It makes it troublesome when you create a parameter in a transformer and want to improve it later. Could this be set up the old way?
In the new published parameter manager dialog in FME 2021, would be great to have an option to change the parameter type, e.g. from text to choice, or text to database connection, etc. Right now it seems the only way to do this is to delete and recreate the parameter.
Following up on this question: https://community.safe.com/s/question/0D54Q00008vYVCFSA4/apply-border-style-only-on-bottom-with-exelstylerGive the possibility to apply a border on individual sides of the cell. It is already possible to select the border Style, but not the side to which it should apply.
I've looked at the currenlty FMEDesktop 2018beta. And there's an very cool feature for Excel Styling. New transformer ExcelStyler.What I like to see is some more flexibility on styling Cell borders. See image what I want and like to see.
Add support for reading and writing Esri representation geometry.
When using FME server apps I would like to give the user a feedback message directly into the browser when the job is complete. This Idea is closely related to virtualcitymatt's but applies in a broader sense to info messages regardless of job's status (failure or success).
Include junctions in the disabled connections or transformers list or create a new list to show disabled junctions. These can be hard to find if they have been made disabled in large workspaces.
Currently (2021.1.1.0 (20210730 - Build 21619 - WIN64)) disabled junctions can not be found in the navigator, like disabled transformers and connections. It would be nice if these could be added to the "Disabled Transformers" group.The workaround is to search for "junction" in the workspace search, this will display all junctions and mark the disabled junctions grey.
Ok, so perhaps this is trivial, but every time I update an important workspace and add a version to the Workspace Properties I click on the History tab and enter the 'user' and a 'comment' and then click to add the date and expect to get a date picker pop up. It doesn't, and I always think, I must ask for that! Well now I am.
The history panel in the Workspace Description is a great way of documenting changes but unfortunately the lines don't wrap:This makes it very hard to read longer comments (and let's face it, sometimes you need them, you can't always condense a large number of changes to just a few words). So I think it would be very useful if that comment line would wrap and/or accept newlines, like this:
Would it be possible to add a dropdownlist for users in the Workspace Parameters Description under Workspace Parameters Description | Name | History?We work together with multiple people on workspaces, it would be great to have a dropdownlist with usernames, in stead of writing the names ourselves.
***Note from Migration:*** Original Title was: Resize textbox when long comment is added in Workspace Parameters Description history To get a better overview of the 'comments' under the history tab in the Workspace Parameters Description it is useful that the textbox automatically resizes according to the text-length. At the moment you cannot read the full text, you have to scroll to the right to read it completely. Another functionality would be to add a calender view, to select a date, under the 'date' attribute,
Consider changing the FME Lizard icon in the Community Forums seasonally. Example: Around Christmas time, put a Santa hat on FME Lizard; In Winter, put a festive scarf around FME Lizard’s neck; For Summer, put FME Lizard in a hawaiian shirt, shorts, and sandals, maybe have him reclining on the beach in a lounge chair wearing sunglasses,
In the installation wizard of FME Flow(2023.0, and still in 2023.2.1), you are prompted the default database username “fmeflow”, but in the installation script’s for the SQL server database, the default username is “fmeserver”. I suggest there would be nice with an alignment here.
Adding on the idea by @egomm I would suggest opening the list of aliases for transformers.This could be in the FME Options menu.Being able to add aliases would allow for language specific aliases.Not all foreign customers are familiar with the English geospatial terminology.
I'm sure I'm not alone in having blank spots with regards to some transformer names. What would be great is if a user could add custom keywords which would result in additional transformer suggestions.e.g. If I could add the keyword trim to the snipper transformer, it would mean that would be suggested as an option if I type trim, as in my mind I think of this as a line trimmer and can often not remember that it is snip and nothing related to cut or trim!It could be similar to how the depreciated transformers are currently shown
***Note from Migration:*** Original Title was: Aliases for FME transformers near like the names used in OGC or SQL for similar functions Hi guys, I have a collegue that uses QGIS and Postgis a lot and FME Workbench a little. Every time he asks me “Hey, I’m looking for some function that does this, where is it in FME?”Of course he should use FME Workbench a lot more often, be he came up with the idea to generate aliases for transformers that are near like the names used in OGC or SQL for the same function. Is that something where you could do something about?
It would be great if you could add the ability to submit transformer keyword suggestions through the Workbench interface, these could then be vetted and added in by Safe. For example when a MapInfo user comes to FME for the first time and wants to break apart multi-part polygons, they search for "dissaggregate" a CAD user searches for "explode". Neither search even when using the specific key word search yields the 'Deaggregator' transformer.I repeatedly hear this as a frustration from new users that the system language they are used to using is often very different in FME and that ironically they could do with a keyword translator!
I have a suggestion for organizing transformers in terms of help and searching and naming. It would be helpful to have a 'user favourite' transformer folder that a user can drag transformers into. This way, Safe can attempt (as they have done with the 2017 release) to organize transformers into groups and categories but this would allow users to drop the one's that they know and use into a bucket for frequently used transformers. Also, it would be good to put tags in the help files that describe the transformer in different terms then the geekly-nerdy-programmery language that is used to name transformers. It is hard to search for a trasnformer using their names only - because what is a TOE-MATO for someone is a TAH-MATO for others. Users could suggest alternate names or tags via the ideas page or a SAFE sponsored 'alternate naming event' or even a card at the FME UC saying "If you could rename a transformer to a different name which transformer would it be and what would be the new name ...?". Just some ideas to enhance the search-find-discover capabilities of FME. Thanks.
***Note from Migration:*** Original Title was: Typing a transformer name on canvas should search transformers using contains - rather than begins with. The workspace behaviour when searching for a transfomer on the canvas should change. When searching for AttributeManager, I have to type 'AttributeM' before it finds the transformer. Typing the whole word Attribute is cumbersome. It should be able to find the AttributeManager when someone searches for 'AttMan' or 'Manager'. This would speed up the search when there are many transfomers starting with the same word.
If I had a penny for every time I've miss typed "attributemanager" on workbench, well I'd have a lot of pennies, but I think FME should figure out what "attriutemanger" is for me.
How do you duplicate a feature? Of all the aliases for Transformer names out there, I think that the Cloner needs an alias 'Duplicator'.Hands up, every one!
There are several ideas around improving the functionality available in Annotations, but why not go the whole hog and (as per Leaflet popups for example) have each annotation being its own HTML page - capable of displaying images, tables, even video if required.As a slightly lesser alternative, annotations could be created using Markdown.
Have an advanced text editor option for annotations in workbench that uses html tags for more control over annotations. There is already the font editor dialog, but I would like to be able to type out my formatting while I am writing the annotation.The font editor also doesn't persist when text is changed, it reverts back to the default formatting. This can be avoided by using tags.
Regexp support on FME Server Directory Watcher. Add option to only notify if "attribute" = regexp - ie if filename contains *badf*.dw*
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.
