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 we are only able to use standard connection to FME Flow within the FMEFlowJobSubmitter transformer. Since we migrated to SAML we cannot use FMEFlowJobSubmitter anymore. We are using very complex workaround to be able to run another workbench on conditions after another one.
When discarding an Automation, I’m having to locate the workflows, using Workspaces which were linked to it.Is it, therefore, possible to have an option to delete the “linked workflows” when deleting an Automation?
On FME Server flag out Workbenches that are Part of an(one or more) AutomationWould be more comfortable in case of editing the Workbench or in organizing between Repositorys.
I must not be alone in being driven crazy by the lack of the ability to center the run button in a Flow Workspace App. Everything else is center aligned and then the run button is out there on the left and it looks just awful!!
Hi,in the record information you can nicely see data types (uint8, buffer, date, time, varchar) for all available attributes when selecting an individual feature: However, when accessing these information in Python we only get the basic types: Would it be possible to also get the full list of data types in Python?In my current use case, I’m supposed to convert all date attributes to another format. Since it’s a generic workflow, I don’t know in advance which attributes are containing dates. When looking at the schema feature I can see that the data types have been recognized correctly by FME. There is just no way easy way to get that information for each feature.Kind regards,Dennis
Hi there, it could be a good idea to have a ‘zoom to’ button on a hidden connection, that takes you to the other end (start or end) of a hidden connection. Sometimes I instantly want to see where the other end of the hidden connection is without having to manually scroll and find it
Hi everyone,wouldn’t it be cool to have a list of favorite Transformers in the Transformer Gallery? Say, one has a number of Transformers that one uses for most of their workspaces. Instead of typing them in to Quick Add each time, it might be more convenient to have a list in the Transformer Gallery for those few Transfomers. It might also be the case that one does not remember the name of a often used Transformer. With a “list of favorites” it might be easier to add often-used Transfomers to Workspaces. But that would mean that there needs to be the possibility to mark a Transformer as a “favorite”.[Edit:Doesn’t have to be in the Transformer Gallery, a selection of favorite Transformers could also be useful after clicking on “Transformer”]Let me see your feedback on the topic. Is it something others would like too or is it just me?Cheers :)
Hi there, I’ve built workspaces for clients that I need to go over and show them. It is very helpful if I add annotations and bookmarks so the client can follow along with me. However, in a workspace a lot of secondary or unimportant transformers are used (things that are not useful for a client to see to understand the logic of a workspace - think things like attribute removers, csmapreprojectors, list exploders, area and gap overlap cleaners, etc.) It would be nice to have a tickbox inside a transformer to mark the transformer as important to the workspace. So then there could be a toggle to select that could, say, highlight all the important transformers (a different colour, a glow etc.), or it could generate a separate, collaborative workspace that you can use to go over with clients, that just show the important transformers that have been tagged, this can act as a sort of ‘pseudocode’ for FME Cheers,
Custom Transformers to automatically output a Rejected port which returns all Rejected ports from within the transformer
Instead of clicking the green magnifying glass, imagine "hovering" over a port to see a live sample of the data (schema and first 5 rows) in a pop-up, like in the picture below:
The SpatialRelator has the option to output the cardinality of the intersections. It would be really useful to also have the optional functionality to output the actual geometry of the intersection.
May be terribly niche, but I’ve just come across a situation where having a ‘counter’ that assigns sequential letters in alphabetical order starting at C through to J would have been useful. If it’s of use to anyone else, maybe the Counter could count letters...or gets a cousin called the Alphabetiser?
In Jobs; Completed I would like an extra filter option: Succesful jobs with errors. Could you add that one?
I have a need to send Kafka header information as part of a producer workflow. Currently header information is only available to receive as part of a consumer. Note that headers for sent messages are not available.
Allows the user to be able to gracefully handle failures
In our standard FME Flow training course we have one excercise where Workspace A does some checks on user parameters and if they are succesful it runs Workspace B through an FMEFlowJobSubmitter.One of our trainees accidentally set up the FMEFlowJobSubmitter to run Workspace A instead and when he published it to Flow he made a recursive loop: every time Workspace A ran, it queued Workspace A again. I was busy helping somebody else at that time so when I got around to his question I noticed it had ran 17000+ jobs in a matter of minutes. These were low-impact jobs, so it wasn’t an immediate problem, but it’s safe to say that this has the potential of completely overwhelming an FME Flow setup.After talking to Safe we decided to post it as an idea here to see if others have come across this as well or have opinions about it.The big question would be:Should FME be able to detect these recursion risks?And in a broader sense: have you had this happen to you? Or something similar that you think FME should be able to detect and warn you about?
Having user-configurable syntax highlighting colors to FME’s syntax highlighting (Python, SQL, Expression Editor), similar to how Visual Studio Code handles token-based color customization would be a nice addition.I find some of the default colors for JSON syntax highlighting to be difficult to read, so it would be great if there were some customizations for this.Text Editorhttps://code.visualstudio.com/api/language-extensions/syntax-highlight-guide
With the upcoming release where a Python IDE will be integrated with FME, the next, and most important logical steps is to pass cached data into the IDE for the purposes of debugging calculations and logic flow. I do not know how the integration with the Python IDE will be released but being able, at design time, to open the IDEA in debug mode is a powerful way of seeing how cached data flows into the PythonCaller, through the python logic, and then back out again.
PDF/Word documents have the ability to create form fields for users to fill in. Looking for the ability to auto-populate some or all of these fields from a database record. Ideally, the writer would accept a template .docx or .pdf and allow the field from the database to write to a field in the form.
I can’t see an obvious way to do this already at FME 2024.2, but it would be nice to be able to set the “Out Fields” parameter on ESRI service readers.Often I only need a handful, or even only 1 field from feature classes with enormous schemas. It would be nice if that could be configured in the reader itself seeing as the rest endpoint handles this parameter.Something like this as an example:
Currently, we can only set the default layer color in the DWG Writer using a color index. Various CAD standards also work with layer colors based on RGB values. I would like to see this expanded so that it can be set using both color index and RGB values.This will avoid having to create templates with thousand of layers manually (extensive cad standard).
I believe this was mentioned in a webinar, but being able to import an endpoint’s schema - from the dataset it is going to be accessing of course - without having to manually create every property would be a great thing to have. This could be from a local file, cloud source, anything. Beyond saving time, it should also ensure accuracy.
Hi FME Server Team,I would like to request an enhancement to the FME Server REST API.API Endpoint:/transformations/jobs/completedEnhancement Request:Currently, it is not possible to filter completed jobs by their finish time using this endpoint. I would like to request support for querying completed jobs by finishTime, in addition to filtering by repository and workspace.Use Case:For monitoring and automation purposes, I need to programmatically retrieve jobs that have successfully finished within the past 5 minutes, filtered by a specific repository and workspace name.Example Query:repository: <repository_name>workspace: <workspace_name>completed successfully (completedState: success)finished within the past 5 minutes (finishTime >= <timestamp>)Having the ability to query by finishTime (ideally with support for both a start and end range, or a relative time based on current time eg. last 5 minutes) would greatly streamline our integration workflows.Thank you for considering this request.
Currently, FME Workbench allows users to define parameters in custom transformers or published workflows, but the ability to provide detailed guidance for each parameter is limited. I propose adding a new feature to User Parameters that enables authors to attach rich descriptions to each parameter. This would include:Formatted text (Markdown or HTML) Web links to documentation, tutorials, or external tools Images or diagrams to illustrate usageWhen a user runs the workspace, they would see an information icon next to each parameter (show it only if it has content). Clicking this icon would open a dedicated window or pane displaying the enhanced description, helping users understand the context, expected input, and any dependencies or external resources required. BenefitsImproves usability and user experience, especially for complex parameters. Reduces support requests by providing self-service guidance. Enables better documentation and onboarding for new users.
Further, it would be convenient if the description and Workspace/Transformer Help would be synchronized automatically, for published parameters.Add Description field to Add/Edit User Parameter dialog (below).For published parameters, link the Description and Workspace/Transformer Help. If you edit Description of the parameter, apply it to the Help automatically, vise versa.
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.
