Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
Level up to the parquet format (updates and snapshot)
The current version of the AutodeskDocsConnector can download a specified source file. However this will not include any annotations or stamps added to PDF documents in ACC, which must be done through a dedicated export method. These annotations and stamps may contain critical information about the state of the PDF and its position in the lifecycle.It would be great if this package could implement the following two endpoints to allow PDF exports that include stamps and annotations:https://aps.autodesk.com/en/docs/acc/v1/reference/http/v1-files-export-pdf-files-POST/ https://aps.autodesk.com/en/docs/acc/v1/reference/http/v1-files-export-status-and-result-GET/
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.
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
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.
Add to the scheduling screen the ability to view schedules in a calendar view. It would be nice to be able to format it daily/weekly/work week/monthly. It would also be nice to be able to click on an opening in the calendar to start scheduling a new job.Merged Ideas:FME Server Schedule - Ability to identify the schedule(s) that gets executed on by atiul on August 8, 2018***Note from Migration:***Original Title was: FME Server Schedule - Ability to identify the schedule(s) that gets executed on a give time range (future date/time range)It would be great, if FME Server provides an interface that can list out the schedules that get executed during a give time range (future date/time range). This would be helpful to disable the affected schedule(s) during outages (server maintenance activities).
StringPairReplacer has been deprecated at FME 2025.2.However, there are use cases where StringPairReplacer would be farther convenient than StringReplacer.For instance, sometimes we have to replace multi-byte alpha-numeric characters with single-byte ones. In StringPairReplacer, it's easy to set replacement pairs, as in:Ａ A Ｂ B Ｃ C Ｄ D Ｅ E Ｆ F Ｇ G Ｈ H Ｉ I Ｊ J Ｋ K Ｌ L Ｍ M Ｎ N Ｏ O Ｐ P Ｑ Q Ｒ R Ｓ S Ｔ T Ｕ U Ｖ V Ｗ W Ｘ X Ｙ Y Ｚ Z ａ a ｂ b ｃ c ｄ d ｅ e ｆ f ｇ g ｈ h ｉ i ｊ j ｋ k ｌ l ｍ m ｎ n ｏ o ｐ p ｑ q ｒ r ｓ s ｔ t ｕ u ｖ v ｗ w ｘ x ｙ y ｚ z ０ 0 １ 1 ２ 2 ３ 3 ４ 4 ５ 5 ６ 6 ７ 7 ８ 8 ９ 9How can you perform the same replacement with StringReplacer? Not impossible but you will have to define 62 replace strings rows. Too tedious!I strongly hope StringPairReplacer will be back! [Addition] Alternatively, it would be great if StringReplacer would have "Replace String Pair" mode, in order to perform the pair replacement with this setting.Text to Replace: ０ １ ２ ３ ４ ５ ６ ７ ８ ９ こんにちは！ さようなら。Replacement Text: 0 1 2 3 4 5 6 7 8 9 Hello! "Good Bye."
Hello FME Community 👋We at Safe Software are busy working on some exciting FME Platform enhancements, many focused on product security. We would like your thoughts on one of the ideas that is currently up for consideration.We’ve received previous requests to add OpenID Connect authentication support to FME Flow, and we think that OpenID Connect (OIDC) authentication could be supported broadly across both FME Form and FME Flow.So, before we dive right into development efforts on this idea, we’d like to know what you think about it! Would you benefit from the FME Platform supporting OpenID Connect (OIDC) authentication? If so, can you provide a brief description of how FME supporting OpenID Connect authentication would enhance your experience with the FME Platform? We are also looking for anyone who might be interested in testing out our implementation of OpenID Connect authentication, once available. If you would like to be included as an early tester, please indicate that interest in your response!Here’s a bit of background on OpenID Connect (OIDC) authentication. If you’ve ever tried to create an account with a new app you’ve downloaded, you might be presented with options to use another account (like Google or Facebook) to login to the new app. In this way, you can use an account you already have, instead of creating a new account. This is OIDC authentication at work, and can be considered an extension to the OAuth 2.0 protocol already supported across the FME Platform. More information on OpenID Connect (OIDC) authentication can be found by visiting the OpenID Foundation’s How OpenID Connect Works page. We look forward to hearing from you on this exciting idea!
I would like to propose an enhancement to FME Flow regarding administrative security.Although administrators are already authenticated when logged into the system, certain critical actions pose a significantly higher risk and impact. These include, for example: Creating or restoring backups Connecting or modifying Authentication Services Adding or deleting users Changing security-related configurations Other high-impact administrative operations To increase security and reduce the risk of unintended or malicious changes (e.g., in case of session hijacking, unattended sessions, or compromised credentials), I propose that FME Flow require administrators to re-enter their password before executing such critical actions.This additional verification step would: Strengthen security for sensitive operations Reduce the risk of accidental misconfiguration Align with best practices for secure administrative interfaces Provide an extra layer of protection without significantly impacting usability The re-authentication prompt should only appear for clearly defined high-risk actions to maintain a smooth user experience for routine administrative tasks.
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!
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.
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!
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.
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:
Currently, FME Flow supports database connections via JDBC, but authentication typically relies on static credentials such as username and password. In modern cloud environments like Azure, using Managed Identity is a best practice for secure, secretless authentication.This idea proposes adding support for Azure Managed Identity including System Assigned and User Assigned identities for JDBC connections to databases such as Azure SQL Database, Azure Synapse, and other services that support token-based authentication.Why is this important?Eliminate hardcoded credentials: Reduces security risks and simplifies credential management. Cloud-native security: Aligns with Azure best practices and enterprise compliance requirements. Automatic token refresh: Improves reliability and reduces operational overhead. Flexibility: Support for both System Assigned and User Assigned identities allows organizations to choose the right approach for their architecture.How it could work:FME Flow detects it is running in Azure and uses the assigned Managed Identity. When establishing a JDBC connection, FME Flow retrieves an OAuth 2.0 access token from the Azure Instance Metadata Service (IMDS). The token is injected into the JDBC connection string or passed as a driver property (depending on the database/JDBC driver). Configuration options in FME Flow to select: Authentication mode: Managed Identity Identity type: System Assigned or specify a User Assigned identity (via client ID) Use Case Example: An organization runs FME Flow on an Azure VM with a User Assigned Managed Identity that has access to multiple Azure SQL Databases. Instead of storing credentials in FME Flow, the system automatically retrieves tokens for secure, passwordless connections. Security NecessityStoring static credentials in FME Flow or any application introduces significant risks:Credentials can be leaked through logs, backups, or misconfigurations. Manual rotation of passwords is error-prone and often neglected. Compliance frameworks (ISO, SOC, GDPR) increasingly require secretless authentication methods.By leveraging Azure Managed Identity, FME Flow can achieve zero-secret architecture, reducing attack surfaces and aligning with modern security standards.
We would like to request support for Azure DevOps as a remote Git provider in the Version Control functionality of FME Flow. One of our clients recently upgraded from FME Flow 2024.2.1 to FME Flow 2025.1.2. In the previous version, they were successfully using Azure DevOps Git repositories to manage workspace versioning. After the upgrade, they are no longer able to push changes to their remote repository. The UI reports: “There was a problem communicating with the REST API.”And the backend logs show HTTP 500 errors when attempting to push.According to the documentation, only GitHub.com is officially supported. Azure DevOps is not listed, although it previously worked without issue. This limitation significantly impacts their ability to maintain version history and collaborate effectively. Could you please consider:Adding official support for Azure DevOps Git repositories in FME Flow Version Control. Providing documentation or configuration guidance for Azure DevOps integration. Ensuring compatibility with common enterprise Git platforms beyond GitHub.com.This feature would be highly valuable for organizations using Microsoft and would align FME Flow with broader enterprise DevOps practices. Please let us know if this request will be considered for a future release and if so, in which upcoming release. Thank you for your support! Kind regards,Joëlle Jansen-SoepenbergFME Consultant
Hi,When you select a date using the calendar in FME Flow UI the calendar persists until you click away. This is a bit counterintuitive and annoying for users . Our users would prefer it disappears on date click. date is chosen and calendar is still there. Thanks,Marc
The new DV functionality seems amazing, I haven’t tried it out yet, but I understand it as one has to provide workspaces for every api endpoint one is creating.Wouldn’t be great if one could easily, in the FME Flow interface, create CRUD (Create, Read, Update, Delete) functionality? This is all functionality that is available in reader/writers, one just have to specify required attributes, primary keys etc.
It would be nice to have FME Flow have file extension restrictions as to what types of files can be uploaded to the resource folders. The ability to restrict types of extensions, especially executable, would be a major safety addition to Flow. If this could be added by user/groups level, that would allow the sys admins to restrict or allow file types based on their groups. For example, some users only allowed to upload CSV files, others more privileged users can upload spatial datasets, others can upload anything except executable. This also will have the benefit of keeping the resources clean and not be a dumping ground for less experienced users not knowing what the intended purpose of that resource is.
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?
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.
