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.
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.
Level up to the parquet format (updates and snapshot)
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
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/
I would like to have a selectable profile/configurable setting that is saved in the workspace to have the following: Set Feature Caching enabled in Development mode and off in Production mode instead of a general default setting for the Form product.
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.
Hi!It will be great to use AttributeValueMapper on a list to avoid to have to explode it.Thanks!
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).
When downloading data using Data Download service (e.g. from an FME Workspace App), a Zip file is created containing the output files. The zip file is automatically named something that looks like “FME_4B425D3A_1772473610895_13172.zip”. It would be nice if an option was implemented to allow customizing that name to something that is more user friendly. For example allow authors to specify what exact name the Zip file should have, or allow the use of parameters to create a string to use as file name. Even if the final filename has to have some extra characters at the end like 4B425D3A_1772473610895_13172, giving authors some customization capability would be beneficial.
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!
It would be helpful if FME Server 2017 had an SFTP Watcher. Currently the regular FTP Watcher does not support SFTP. I am aware that the Notification Service supports SFTP subscriptions but currently in 2017.0.1.1 there is no corresponding SFTP publication option.
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!
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.
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.
