Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In FME Flow, Automations can be triggered by various FME Flow System Events, such as the creation or modification of repository items. This provides a powerful and flexible way to build event-driven workflows and governance mechanisms.However, currently these system events are primarily focused on repository-based entities. There is no equivalent event available for entities that exist outside of repositories.For example, the creation (or modification/deletion) of an FME Flow App does not trigger a corresponding FME Flow System Event. As a result, it is not possible to directly react to such changes using Automations.This limitation makes it difficult to: Implement governance or auditing processes for FME Flow Apps Automatically enforce naming conventions or security policies Trigger notifications when new public apps are created Maintain synchronization with external systems Track lifecycle events of non-repository entities
When bookmarks are closed, transformers inside the bookmark are not cached. While this is a great feature, I barely use it as closing and opening bookmark usually change the layout, and I really like to see the transformers and how many features go where. It would be nice to have a featurecaching enable / disable switch on bookmarks.
Just been trying to get a picture of the used connections in workspaces - This would be helpful. I can see it in the workspace file but the reader doesn’t include them.
Writers - Redirect to Inspectors - should also work on FeatureWriters
It is my understanding that the initial installation of Flow Hosted is done by Safe Software, but upgrades are the responsibility of the customer. I would like to see upgrades offered as part of the service. It should be automated, but not automatic.
To understand the purpose of the workbench, we will have a look at the name of the workbench at first step. Secondly, we have to go through entire workbench from reader to writer to understand more and understand that all the changes are included or missed out.On the other side, SRS documents will be in another document (i.e., name.docx) file which we have to refer for better clarity.I would be better if workbench have minimum functionality of MSWord with allowing images from SRS documents to refer. This will help us to maintain the same vocabulary between SRS and Workbench. It will even help team members to coordinate in much better approach.It is advisable to place the document just beside Main tab as shown in screenshot. Thank you
It would be great to have a direct integration in FME Form to do git commits, etc. in the GUI itself. It could be in the form of a developer command line/powershell or even as a built-in git integration much like what we have with FME Flow. As it stands today, I do this indirectly through Visual Studio. I essentially save my .fmw files in a Visual Studio project, and do all the version control through there. I would love it if I could bypass that altogether.
There are several situations where I would like to use a transformer that manipulates attributes on every element in a list. The current option is to explode the list, do the manipulation and then reconstitute the list, which is inefficient (introduces blocking transformers) and can cause issues with the geometry of a feature, create a looping custom transformer with a listIndexer for every element in the list, or alternatively code the list manipulation in python. It would be nice if the following transformers could work on lists.Manipulates the attributes directly:AttributeTrimmerStringCaseChangeStringFormatterDateFormatterStringPadderCreates parallel structure list:AttributeValueMapperFilenamePartExtractorStringConcatenatorSubstringExtractori'm sure there are other transformers that would benefit from this as well.
The Tester and TestFilter transformers have five distinct Comparison Modes:Automatic Numeric Case Sensitive Case Insensitive Date/TimeAs well as the option to Specify Per Test.The FeatureJoiner and FeatureMerger transformers have three Comparison Modes:Automatic String (presumably the same as Case Sensitive, above, but I have not validated that and don’t see it specified in the documentation) NumericAnd the way that these transformers are designed, they are inherently “Per Test” or per “Join On” condition, as it were.The general Idea here is to make the Comparison Modes more consistent across transformers - there are likely other transformers that could be included in this, beyond the four mentioned above.Case Sensitive, Case Insensitive, and Date/Time could be useful in the Feature-type transformers, in addition to the Test-type transformers. There are other ways to achieve these, of course, but there may be value in having them readily available. The order in which Comparison Modes are listed could be consistent - this is a minor point.If the various types of Comparison Modes are already tailored to best match each class of transformer, then the idea may not have merit, but posing it in case others could see any value in the proposed change or a similar change.
Hi there,When using deployment parameters from various Flow environments, it would be great to actually used the stored information from those deployment parameters instead of having a local copy of that connection that is needed within the workspace.The reason is, if I want to test and debug a workspace that happens to fail in a UAT environment. I would want to connect to Flow UAT environment, open that workspace and test it using the configuration that is stored in Flow UAT instead of the local version as this doesn’t represent to the environment’s configurations of connection, password, etc.
Hi there, It would be helpful to add some kind of percentage progress indicator during workbench execution. For example when working with point clouds it can be hard to estimate how far through a process you are as the numbers can get quite large.Thanks,Marc
I would like to identify custom annotations attached to objects using WorkspaceReader. This is possible with summary annotation because the transformer name is included in the annotation attribute. Custom annotations take up less space than summary annotations and allow the author to document the workspace. Having the ability to export this information helps with cataloging and reporting.Can we have the transformer name or transformer ID included in the annotation feature type either in the annotation attribute like in summary annotation) or as a separate attribute?See the posthttps://community.safe.com/authoring-6/workspacereader-find-annotation-linked-to-transformers-37719?postid=164422#post164422
Hi!It will be great to use AttributeValueMapper on a list to avoid to have to explode it.Thanks!
DB connections in Flow, and corresponding Deployment parameters can become difficult to navigate and manage if you have more than a small handful of connections to keep track of.It would be really helpful if these could be stored in groupings, or subfolders, to make the list more manageable. For Deployment Parameters especially, this grouping would be very handy when listing in the Form navigator!
Hi there, I like to create hidden connections for larger workspaces to keep things tidy. However, so many times when I select and grab a group of transformers I end up accidentally selecting the hidden connection and removing it. It doesn’t help also that the hidden connection colour is too light when you select a transformer that uses it.
I often find in some scenarios it would be helpful to have annotations point to multiple transformers.In the scenario below, the annotation applies to both the AttributeExposer and the AttributeRemover, but I can only connect it to one An alternative way is adding it to a bookmark and annotating like below. I think a bookmark is overkill in this situation and having the annotation attached to both would be helpful
Hi there, I like the idea of being able to look at a workspace and seeing easily what transfomers change attributes, which change geometry, which filter etc. To do this, it would be nice to change the colours of transformers, so I could have say green transfromers are filter transfromers etc. I could add annotations to the top of these but it becomes a bit cumbersome. If you can rename transfomers, changing their colours should not cause any unintended issues.
It seems a lot of users are taking to using FeatureReader and FearureWriters in place of traditional readers and writers.I wonder if it’s time to give these two transformers a new color to help them stand out?
I would like to request the reactivation of the Workspace Viewer as it has been marked as obsolete and is no longer available on the platform.This tool was essential for my work, as it facilitated my understanding of the data transformation process and was very useful for debugging and optimizing my workflows.I would like to know if there is any possibility of recovering it or if there is an alternative that I could use.Thank you in advance for your attention
Currently, access to AGOL/Portal photo attachment information is available only thru a true reader when the option is enabled. It would be nice to have that option available when using FeatureReader transformers as well. I'm currently using Build 20264 (FME 2020) maybe this has already been released.Thanks!
For my current use case - a workspace app - I do not want users to see either option highlighted in the attached image and only wish to allow them to drag/drop or upload from their own machine. I attempted to try multiple file paths and uncheck the ‘Allow URL Path’ option within Form’s user parameter manager, which had no effect on the URL/path option showing, and see no option to disable browsing resources which has been asked about in the past:For simple file uploads by users not needing to provide a URL or browse Flow resources, I think disabling both should be possible.
Add option to hide "Browse Resources" button on FME Server App. It confuses some users and there aren't usually any files users need to access in the resources. We prefer to design the input parameters on our apps as simple as possible to avoid overwhelming users with too many input fields and options. Minimizing the upload functionality to only one one button will certainly make the input apps more compact and easy for users to use.
A minor bug I’ve possibly just discovered, though something in my memory is thinking I’ve heard about it before. If the FeatureMerger transformer is not connected to any data connections and you move the requestor port down below supplier then drag it to a connection, the connection goes to the uppermost port - in this case the ‘Supplier’ port. I would say the default most people would want is that it looks for the ‘Requestor’ port, regardless of whether it is the uppermost port or not. So this is a bit of a bug report and idea at the same time. Screen recording gif is attached to show current behaviour in FME(R) 2025.1.1.0 (20250730 - Build 25615 - WIN64)
In Workbench's Visual Preview window it would be handy to be able to search/filter the table values by null, missing, empty. These null values are available in the Filter for the Graphics View, but not in the Table View search box. If available, this would allow a quick count of features that have missing values in a particular attribute field/column.This functionality would have come in handy during the Desktop Basic training for Best Practice - Exercise 1 during step 4 when you confirm that the CrimeValue attribute is missing values on some of the features. If you could filter the CrimeValue column using a '<missing>' value, then it would easily confirm the number of features missing a value (instead of sorting the column and scrolling down the table see which row numeric values start appearing).The same would apply to Data Inspector.
In my use case I’ve got plenty of overlapping old aerial images, which I am stitching together.Many are too bright or too dark, so always using maximum or minimum data value for overlapping cells is not the best option. Averaging or summing doesnt make sense either, so my only option is something like this Calculate the median of overlapping pixel values from 24 input raster bands | Community + sorter + using ‘last’.So my suggestion is to simply add ‘Median’ as option:
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.
