Shape the future of FME with your ideas
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
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.
FME Flow APP with dynamicParameterData is great!However, I have installed the FME flow APP on my PC, and I would prefer to open the installed APP directly instead of a new web page. The progressive web application (PWA)) APP gives a better integration / look and feel.
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.
Sometimes you only realize after a while that you need some followup action after a writer. This results in deleting the writer and inserting all the necessary information into a new FeatureWriter.I think it would be helpful if you could convert a normal Reader or Writer to a FeatureReader/ FeatureWriter.
Idea: cancelling a job will rollback the whole transaction of all features for Snowflake WriterObserved behavior: cancelling a job in FME Flow will stop additional features from being written, but features that have already been written to Snowflake are already committed without any rollback of the transaction. There is inconsistency between “Features Written’ as recorded in the job log and actual features written according to Snowflake logs. The job log records zero features written while there have been many features written to Snowflake despite job being cancelled.Desired behavior: cancelling a job in FME Flow will stop additional features from being written and rollback any partial changes the job has just done. Outcome: improved management of jobs.
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.
[A Message from Product Management at Safe Software] This idea has been refined from its initial posting. The original description is preserved below for reference.The built-in “admin” user account in FME Flow lacks support for modern multi-factor authentication (MFA), including 2FA or passkey-based login. This poses a security risk, especially in environments where organizations rely on local accounts as a fallback when identity providers like Microsoft Entra ID (formerly Azure AD) are unavailable.This idea proposes adding support for MFA/2FA/Passkeys to FME Flow’s local system accounts. This is critical for scenarios where SAML, LDAP, or Entra ID integrations fail or are temporarily offline, leaving only the local admin account as an option for access. Dear All,I would like to see FME Flow provide native built-in feature to allow users to run FME Schedule or default Dashboards -→ JobHistoryStatisticsGathering.fmw use Microsoft Entra SSO (FME) SAML-based admin accounts.We purposefully disable local “admin” users, since FME Flow doesn't provide 2FA/MFA option for local users but set it up to use Microsoft Entra SSO (SAML) with mandatory 2FA.Your support is appreciated :)Cheers,Reno
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.
In an Automation email action, we would like to use deployment parameters to set the following parameters:SMTP Server SMTP Server Port SMTP Account SMTP Password Connection security (less important)Motivation: we have clients with an important number of automations that use the “Email (send)” external action. When the smtp server settings change, e.g. between DEV and PROD environments, it’s a significant amount of manual and error-prone work to change these settings consistently in all the automations. It would be a big help if these settings could be set using deployment parameters:
It would be great to have an 'undo' function for automations that are deleted.
An integration with monday.com api would be nice!
All the grids in FME servers are not sortable by users, sorting is the very basic function expected by all users from any software these days.Please allow users to click on any column header to sort ascending/descending/removing sort for a given column. The user should be able to hold the shift or control key to choose multiple columns to sort. The sort function should work for all supported data types in the column, e.g. Number, text, date, user, etc.
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!
Currently, when a Database Connection is created from the FME Flow interface, there is no visual check that confirms the connection has been successfully established. It is possible to enter incorrect credentials, and FME Flow will still allow the database connection to be saved without showing any error.As an improvement, it would be very helpful to include a visual indicator, for example, an icon, that immediately confirms whether the database connection was successful. This would help avoid configuration mistakes and make it easier to detect access issues early.
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.
When you publish a workspace from FME Form, you can specify Flow topics to be notified on success or failure. And you can view this setting via Workspaces > [Repo] > [Workspace] > Advanced. Unfortunately it is read-only.We should be able to change the setting here. That way one can have a different topic per environment. Re-publishing via FME Form is not an option when using Projects for repeatable deployments.
Good morning. As an FME Flow admin I have to review the job logs manually for several projects due to the fact that users have not added a notification topics when they publish the forms. This is a problem as most of the time, workspace authors don’t even know that jobs have failed unless they review the logs themselves. I am trying to anticipate this scenario and inform the workspace authors as soon as jobs fail. Can we make the advance parameters editable for a selected workspace in FME Flow--see attached picture-- otherwise users will need to republish the workspaces that don't have a topic. I know that I need to educate the workspace authors to add the topics when publishing instead of fixing thins on the back end. This would just make the job much easier.
When inspecting feature attributes in the Visual Preview, there is an under appreciated option to select Columns in the Table view.Large schema's such as Esri's UN model have so many columns, that if you select only a few columns, it can help you quickly identify issues in the values. For example with Dates, filtering for columns with names that include date, you can more easily inspect and find dates that maybe in different/inconsistent formats. I'm asking to add a Preset/Save button, that remembers a preset or last selection of columns.Attribute Table > preset save as my attribute selection list
The problem The documentation for FeatureMerger mentions a "Suppliers First" mode that can reportedly be very beneficial to performance (and, I would imagine, crucial for Streams), but comes with the constraint that all suppliers must have arrived before the first requestor comes in. To my knowledge, there is currently no way in FME of upholding that guarantee in a reliable manner. The timing between Readers, Creators, FeatureReaders and SQLExecutors is not something I can claim to understand, and the completion order can change based on whether caching is turned on or not. This is already troublesome when editing workbenches, but it can be expecially problematic inside custom transformers, where you don't have control over the delivery order of features in your input ports. This isn't merely an issue with FeatureMerger; it's going to be a problem at any time where you rely on input ordering for a transformer to work properly, with specific attention given to Streams and Feature tables. If I have a PythonCaller that configures itself based on data coming from TransformerA before it's ready to accept data from TransformerB, there isn't a lot of options for reliably dealing with out-of-order input. Holding onto features is illegal when bulk mode support is advertized, so the PythonCaller must either opt out of it (which hurts downstream performance) to accumulate any features it's not ready to process until the configuration features have come in. Even then, it can't know when TransformerA has closed, so unless it only expects one configuration feature, it's dangerous to start processing before close() has been called. This might be clearer when considering the attached screenshot: Python_MapAttributes needs the output line from JsonTemplater in order to work with the data coming from MappedInputLines. If MappedInputLines starts sending features first, the PythonCaller can't do anything yet, and can only crash (undesirable) or start buffering features (illegal in Bulk mode). The solution The idea would be to have some sort of Semaphore transformer, something like a FeatureHolder, but with (at least?) two input ports: a "Priority" port, which lets features through normally, and a "Held" port which buffers features until the other port has closed and no more features can go through it. This would ensure that no feature from the "Priority" side can ever arrive before a "Held" feature, thus allowing workflow and transformer designers to guarantee feature ordering downstream without breaking bulk mode. Other relevent use cases One might also consider having a Terminator node which should stop the translation when an assertion or a join fail in some unexpected way, but should wait until every faulty feature has arrived to give proper context instead of immediately stopping at the first one. Bad features could be sent through the priority port and then the priority port routed to a terminator, so that no feature can be passed to the next step until it has been verified that none exist that would trip the Terminator. This would also allow the Terminator to be changed to wait for all features to have arrived before stopping the translation, instead of aborting at the first one (which currently makes sense, as the more you wait, the more you risk that downstream writers will have already started to write incomplete data).
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.
