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.
If you have ArcGIS Pro installed on your machine then you have access to the arcpy.geocoding module with its Locator class, which can be serverless. This puts geocoding in the hands of anyone with (say) a file-based locator.
using a shift or control (any key combination with left click-drag) to “turn off” autosnap to transformer ports, connection lines, etc while moving one or more transformers into an area where there may be one or more connection lines right where you want to place the new transformer.
Please add Import from Feature Cache (Similar to AttributeFilter) where you can populate the right side or the left side from values. It would also be great to have some multi row copy/paste (drag drop) to be able to easily adjust the mappings withing the mapping editor.
Hi,Right now it’s impossible to dynamically push a different Headers to the HTTPCaller. You need to already set all the Header names prior to using it.That will be awesome to be able to use, like a Json to push the Headers you want to use, like the Body section.
Currently there is not a connection, transformer or writer that connects FME directly to Azure Key Vault or other key vaults. This would be needed to access sensitive information such as Client IDs and Secrets for Web Connections (to Portal, ACC etc), stored on Key Vault, that we could then incorporate directly into our workbenches. As a company, security is becoming ever more important and this connection would greatly help us to manage sensitive data in line with corporate requirements. We recognise that the existing web connections have decent encryption in place, however there is a general push to have a more standardised approach to storing ids/secrets at a company level.
With libraries like DuckDB in your Python environment, as is the case where you either have ArcGIS Pro or Enterprise on your FME machine, or you’re using ArcGIS Data Interoperability, then it is easy to retrieve potentially millions of features from an S3-API compliant object store or other web source in seconds, but it’s a bottleneck to send them on into the workspace one by one.I would like to see performance like reading CSV files brought to PythonCreator.There is a possibly related existing idea Introduce a Python Dataframe Creator/Transformer but I don’t want to confound using dataframes with this idea, which is fundamentally about performance.Dataframes might be how this idea is implemented, but my guess is that would be a heavy lift for Safe, another way might be a way to output an aggregate feature.
When we create a Web or FME Server connection in a workbench it automatically gets prefixed with myname. And then when published to Flow we get the same…. is it possible to create these connections with a more generic name, I’m not connecting as “robert.mcpherson” and it doesn’t seem to matter but this is an enterprise system and I will be for ever named in the system. I guess it doesn’t matter but it doesn’t seem a very “enterprise” thing
It would be really useful to have the option to install FME Flow with no pre-installed workspaces, no inactive automations/schedules, no topics/publishers/subscribers, and no AR App. Just the bare minimum: the Admin user and the default roles (fmesuperuser/fmeadmin/fmeauthor/fmeuser).All the other utilities and example content could instead be made available through FME Hub for download as Flow projects when needed.On a related note, I also question the usefulness of the default “Temp” resource connection, since it isn’t required by the system and isn’t automatically cleaned up. For new users especially, its presence can be confusing.
To my surprise, there is no option to add headers to an HTTP request in Automations. We need this option. In the meantime, I'll go back to Workbench :(
Currently the JSONValidator only validates syntax, whereas the XMLValidator allows for Syntax only or Syntax and Schema.The Schema can defined as per http://json-schema.org/documentation.html
It is really handy to set multiple presets in 2019 and this makes life a lot easier but i'm missing the ability to share these settings/presets with my colleagues. I would really love to see an export/import button or even a linked button so when changing some of the settings in the given preset it also changes everywhere else.
I need a method for ensuring workflows that include a single workspace being run multiple times triggered by the output of an automations writer are run consecutively not in parallel.In a similar way to how the Workspace Runner in FME Form ‘Wait for job to complete’ option works.I don’t want to simply assign these to a queue with a single engine as I want the first job to pick the first available engine.
It would be nice to format the font (i.e. increase size, bold, etc.) in FME Flow Automation annotations. I understand that font size is somewhat controlled via browser settings and/or monitor resolution, etc. However, it would be nice to be able set bold for text elements or underline headers, etc. If it could mimic the functionality in FME Form, great, if not, a few font/text formatting options for annotation would be helpful.
The usage of deployment parameters greatly simplifies switching between test and production environments.When workspaces are used in automations, which reference deployment parameters in transformers, it is not possible to get the information from the corresponding “Run a Workspace” action whether deployment parameters are used and what values they have. The workspaces must first be downloaded and opened in FME Form to see, if deployment parameters are referenced in FME elements.Is it possible to use a symbol in the action to indicate that deployment parameters are being used and to include an overview of the parameters with values in the “Parameters” tab ins the action details (for example like in my sketch)?Thank you very much.
I would propose a switch in the backend to show or hide the geometry definition input field.My users are all over the place, some of them understand that they have to set a point on the map and are confused thereafter when a whole GeoJSON syntax shows up instead of coordinates they expect, others think they should write a street address in the input field (mistaking the input field for a geolocator), etc…I can leave a message for them but hey, how many will read it...
Currently, FME Flow Apps and Gallery Apps are either always enabled or always disabled. There are times when it would be useful for this to be managed in the app settings for example: If we need to restrict access to specific timeframes, such as during business hours. Having to manually enable and disable apps is frustrating. For apps with a defined start and end date for their availability, it would be much easier if we could automate them being switched on/off. It would be epic if we had a scheduling feature for FME Flow Apps that allows us to define periods of availability, similar to that for Schedules for Workspaces, where we can set when and how often an app is availableBeing able to configure an app to be automatically enabled or disabled based on a recurring schedule (e.g. weekdays from 8am to 6pm) Setting a specific start/end date and time after which the app becomes available/unavailable.
It would be great to have an 'undo' function for automations that are deleted.
Could you please add an “Export to CSV” option (download button) on the Jobs page in FME Flow (Completed / Running / Queued tables)? Admins frequently need to analyze job metadata dashboards. While the REST API supports retrieving job history, a one‑click CSV export from the UI would make this far easier for day‑to‑day administration and reporting.Why this matters:1. Reduces time and friction compared to building API queries/workspaces for each export.2. Aligns with existing Jobs table filters/column customizations (export what is visible).3. Common admin use case: ad‑hoc analysis, audits, troubleshooting, capacity/performance reporting.Notes:1. The current Jobs page allows filtering and viewing details/logs, but there’s no built‑in “export/download” for the visible rows.2. Adding a native export would complement the REST API V4.
FME courses and examples for the new Data Virtualization feature include lessons on how to create GET and POST endpoints in FME Flow and Form but there are no examples of how to use create a PUT (update) request in Flow and build a workspace which updates a data source. I’m working through this myself but I’m surprised that PUT and DELETE endpoints are not covered (but especially PUT) in the Data Virtualization course which I took a few weeks ago. The POST example in the course has been useful but is not enough in my opinion.
Hi, please, let's add automatic pre-loading of parameters before launching the automation app, similar to the workspace app. After all, even before launching the automation app, it is necessary to know the current values of dynamically changing domains in the background, for example in company databases.Anyway, solution for workspace app is brilliant! https://support.safe.com/hc/en-us/articles/40509829569805-Dynamic-Parameter-Configurations-in-FME-Flow-Apps
I use the Mark Location tool (via righthand mouse click) all the time in FME Data Inspector when building processes and I am then constantly zooming to the marked location via the mouse wheel. It would be great if the ‘Locate’ button in the Marked Location dialog box could be added to the standard toolbar in the FME Data Inspector so as soon as it loads I could click the Locate button and zoom to what I am interested in. Thanks!
It would be useful if there was a way to validate all database and web connections on an FME FLow instance. This could be used to check whether an install or network change has introduced errors.If this could be done via the API it would also allow automated, periodic checking.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.