Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
An integration with monday.com api would be nice!
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
In FME Flow, Flow App users can trigger a workspace with a Run button, but they can also submit hundreds or thousands of jobs, intentionally or by mistake. This can easily overload the system.Job Queues and Routing Rules help organize jobs, but they don’t limit how many jobs a user can submit.Feature request: Add a configurable per-user job limit (e.g., max 5 active/queued jobs) to prevent users from creating an unlimited job queue and to protect system stability.
My idea is to enable published parameters to be passed to an FME Server app via the URL, in the same way as can be done for executing a workspace via the URL when shared.In my current use case, I have created a PowerBI report which the user will interact with and filter data into a single record - in this case it is a list of calls that the user will make to residents. I want them to record the outcome of each call, so have created an FME Server App which contains published parameters for each field in the database table I'm logging into, which provides them with a form with the relevant parameters and configuration options.What I'd like to do but cannot, is pre-populate some of the parameters in the FME Server App, but leave others for the user to select from/populate.
It would be great to create reports through MS-Word Writer. The attributes can be populated in Word Document based on the tags (e.g. ${attribute}). Something like Survey123 Reporting Concept.
I know that the STL format specification requires 3D models should always be represented in the positive coordinate space and therefore the FME STL writer automatically moves all the vertices to (1,1,1) or greater space if the source 3D model has a vertex less than (1,1,1). However, actually it seems to be usual to use STL datasets with verteces in the negative coordinate space, and also we sometimes would be required to create such ones.See the sample STL files publised in this web page, for example.https://ozeki.hu/p_1116-sample-stl-files-you-can-use-for-testing.htmlIt would be great if STL writer could write 3D models with 0 or negative coordinates into the destination datasets, just as the source geometry was.
To get to know your current amount of Dynamic Engine / CPU Usage Credits you need to navigate to the Licensing Menu within the FME Server GUI. To see this, you need the proper permission that should not be granted to a lot of people. A possible way to make this information more accessible could be done via the REST API. Right now, there is no such endpoint. Accessing the credit amount via the REST API will give you the opportunity to automatically get the Credit amount and, for example, enables you to monitor the usage and reduction of you credits. This monitoring could be done via FME Server itself or by implementing the REST API request within a third-party application (like Grafana).
It would be nice if the RasterExpressionEvaluator would include math functions like @max(A[0],A[1],A[2]) similar to the expressionEvaluator
Migration Note: Idea originally posted on 2016-04-20
When connecting to azure AD through a Web Connection, FME Form uses QT WebEngine to perform the authentication. QT WebEngine does not support conditional access from azure (https://learn.microsoft.com/en-us/azure/active-directory/conditional-access/overview).Make an option in the authentication process to choose a different browser for authentication (like edge or chrome where this is supported) or make the QT WebEngine supplied with FME Form support conditional access.
I would be good to have the ability to add new keyboard shortcuts for various menu and submenu items. At the moment most functions have shortcuts, but others do not including the "Update Reader..." and others which get used often.Having the ability for user to add new shortcuts and perhaps customize existing ones would be good for UI and better tailor the tool to the functions users use the most.
If a FeatureWriter is set to write dynamically, then the port which accepts the schema features should be a dedicated schema port, and not the main port that handles the features to be written.This is the design the FeatureReader transformer uses, and more recently the SQLCreator, to have a dedicated schema port. Dynamic writing can be done either by having a schema feature enter the writer before the features to be written, or by having each feature carry schema list attributes that describe how it should write. Potentially adding a schema port would make that second dynamic write pattern unviable, but we have tools now like the SchemaScanner to produce a schema feature for any workflows which would need to change from this.Also there are occasionally bugs where the writer tries to write out the schema feature, or schema attributes. Recently in 2023, a GDB writer will warn you that the schema attributes need to be renamed to follow GDB field name restrictions.It would be much more consistent design, and easier to teach how dynamic writing works if the FeatureWriter had a schema port to receive the schema. It only needs to appear when the write mode is set to dynamic.
Add an input port for Schemas to enter the FeatureWriter when writing dynamicallyThe FeatureWriter could then ensure it’s received all the schema features before it starts processing the data features. Currently, ensuring the schema feature hits the featurewriter before the data features can be problematic, especially when you’re developing with feature caching turned on.
I have seen use cases where an organisation has its authoritative web and database connections stored in Flow and wants to make those accessible to Form users. However, they don’t want Form users to subsequently be able to overwrite or upload their own connections to Flow in an effort to keep it organised and structured.They achieve this by restricting access to the database and web connections to read/view only. Therefore allowing them to be used in Form and Flow, but not changed.However as Form is now set to use Flow as it’s connection storage, a user can’t create their own as their associated Flow permissions block writing to the connection storage.It would be helpful if you could have both a local and Flow connection storage configured, with the ability to copy between them.This is similar to some ideas in:
Write in OBJ format, support adding id, add unique identifiers and groupings for each model
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.
