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 'NoFeaturesTester' custom transformer currently out on FME Hub is powerful. However, we're getting pushback from IT from using it in our production workspaces in FME Server. We've benchmarked their work-arounds, and it slows down the workspace significantly (2 seconds with NFT vs. 2.5 minutes with their suggested alternatives). My idea: Harden this transformer and turn into a standard transformer.
A Priority Attribute like in the AreaGapAndOverlapCleaner would be good for the anchor features. Use case is, there are many areas which have to be snapped to different line features with different priority.e.g. road has a higher priority than wall
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.
I have a question in community forum for a flow issue that cropped up. I previously had a ticket with my own IT with an issue that falls into this same category and now a third iteration.in each instance the reader fails and does not continue. whether in form or flow.instance:we receive a zip file that has been incorrectly named. When it is unzipped the folder name ends with a period. (eg. my folder-0name.it doesn’t\matter if there is a\period in the folder it only matters if the folder name ends with period.) this causes the reader to fail and cancel running in both flow and form. I have not identified why the second instance occurs but it is odd that if i am using a reader and it fails with ‘Media is write protected’. see this question here. I understand the 3rd instance is an error on our network. but still can’t the reader detect that it can’t really (with only symlink references) read this and just circumvent the folder? (the error is - PATH Reader: Error reading path '\\Tx-mio-mis01\fw-shared2\SURVEY\CHus\HM_PKG_9_LOWLINES\0_GIS\FOOTAGE_TABLE.xlsx' with error message: 'directory_entry::status: The symbolic link cannot be followed because its type is disabled. Response from my IT dept… From: Helpdesk <helpdesk@topo.sur>Date: Wed, 19 Aug 2026 16:13:56 (UTC -05:00) These are not corrupted. They are a new form of archiving that we have begun implementing. Are they giving you troubles? create specific exclusions. for instance maybe with regex. (e.g. _ARCHIVE) do not read
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!
Being able to reorder the attributes on a transformer is awesome. However, it's also tedious. Repeated right-clicks and selecting "Move Up" or "Move Down" in a long attribute list is painful.It would be great if you could drag/drop attributes to change the order. So instead of clicking and dragging anywhere on the transformer to move it on the canvas, clicking and dragging an attribute should allow it to be moved up or down the list. Then transformers would only be moved on the canvas if you clicked the top of the transformer (where the name is displayed) and dragged it around.
See https://knowledge.safe.com/questions/68957/get-the-last-index-of-an-array.htmlI now know how to access the last element in a list in a single statement thanks to @david_r's answer to this question. So I no longer have to count the list elements then subtract 1 from it before getting the value of the last element in the list. However, in the process of finding out how to do this, I discovered that the ListIndexer allows you to specify a negative number to start from the end of the list.I haven't yet had a scenario where I needed to get (for example) the 3rd element from the end of the list but these situations are bound to arise at some point! So I'd like to suggest that negative numbers be allowed e.g. _list{-3} to start from the end of the list rather than the start.
Request: Please add parameter options for for the Esri Geodatabase Open API reader that allows us to ignore the FeatureDataset path to featureclasses I have an esri GDB with featuredatasets (see featuredataset image)With FME using Esri Geodatabase (file geodb) reader and an ESRI license... it nicely drops the featuredatasets for feature types.... and keeps the featureclass nameDistributionCarrier_HV_OHUse the Esri geodatabase (Open API) reader however and you get ... featuretypes with the featuredatasets in the path. No parameter option to ignore themxxxxxx_Distribution_Carrier/DistributionCarrier_HV_OHI workaround for the OpenAPI is to use stringreplacer to format them such that I can get to the featureclass names, Thanks to AI assist in 2023.1, I can now write regex !
When granting access to connections via a security role in FME Flow, it would be nice to split out the Web Connections from the Database Connections via the interface. Or at least filter by connection type first, then the name. Currently, in the ‘Edit Role’ interface, all the connections are combined.We have over 450 connections in our organization it is cumbersome to assign access to the correct connection via a role.
Hi Safe Software team,We are looking to improve our automated data pipelines by integrating alternative object storage like Cloudflare R2 and Hugging Face with FME but the current Amazon S3 Compatible Storage connection is too strictly tied to AWS defaults.Could you expose a few standard SDK overrides in the S3Connector and Web Connection configurations? Specifically, we need: Free-text Region selection (e.g., to allow auto for Cloudflare R2). Addressing Style toggle (Path-style vs. Virtual-Hosted). Support for namespaced Endpoint URLs (to prevent FME from truncating trailing paths like /my-org for Hugging Face). Advanced Checksum controls (ability to disable strict AWS payload checksums). Adding these standard parameters would seamlessly unlock zero-egress and AI workflows directly within FME Form and Flow. Thanks :)
As of FME 2026.2, the new IFC_API Reader converts IFC geometry of type IfcFixedReferenceSweptAreaSolid into BRepSolids within FME (see IFC-to-FME Geometry Mapping). When these geometries are subsequently written using the IFC_API Writer, they are therefore written as IfcFacetedBrep.I would like to suggest native support for reading, preserving and writing IfcFixedReferenceSweptAreaSolid.The main issue with converting this type of geometry into a BRep is that a relatively compact parametric representation can become a very large explicit boundary representation. A swept-area solid can essentially be described using a cross-section, a directrix and an orientation rule, whereas a BRep needs to explicitly store the resulting vertices, loops and faces.As a practical example, FME currently does not appear to provide a native geometry type for sweeping an arbitrary profile along a path. For a railway use case, I therefore created the rail geometry manually in a PythonCaller by placing the individual rail-profile points along the input line and connecting them to form the final solid. While this works geometrically, the resulting object has to be represented inside FME as a BRepSolid and is therefore written to IFC as IfcFacetedBrep. This can result in considerably larger IFC files compared with representing the same geometry as an IfcFixedReferenceSweptAreaSolid.In one test containing only around 200 metres of rail geometry, the FME-generated IFC using IfcFacetedBrep was approximately 23 MB. After reconstructing the same rail geometry as IfcFixedReferenceSweptAreaSolid, the resulting IFC was only around 150 KB. While the converted file was created as a proof of concept through post-processing, the difference clearly illustrates the potential impact of the geometry representation on file size.Ideally, FME could provide a native swept-profile geometry type that retains the relationship between the profile and the path, instead of immediately converting the result into an explicit BRep. A comparable concept already exists for IfcSweptDiskSolid, which can be represented in FME using the Pipe geometry type.Such a geometry type could then allow the IFC_API Reader and Writer to preserve or create IfcFixedReferenceSweptAreaSolid geometry directly.
When doing a FME Flow Fault Tolerant installation you need to configure multiple environment, but they pretty much have all the same configuration steps, something that would be useful would be to export the configuration at the end. It would be similar to a parameter file that you could use for a Silent Install.And when you jump on the other machine that you are installing FME Flow, you could provide the configuration file at the start in the installer, you just have to do the change for the machine name.
Hi,When we need to rerun a workspace using the same parameter values from a previous execution, it can be quite time-consuming to go back to the log file and copy/paste each value one by one.It would be very useful if we could select the parameter section from the log, or even better, drag and drop the log file directly onto the parameter section to automatically populate all values.This would make debugging and rerunning workspaces much faster, especially when there are many parameters, and would also help prevent manual input errors. Ref:
When writing PDF it would be good if I could choose to write PDF/A version of the files. PDF/A is an ISO standard specialized for the digital preservation of electronic documents and in several cases it's a requirement when delivering PDF-files to a customer.
I fully understand that Safe wants to make the sending of Success or Failure emails in FME Flow Automations more granular. But the big issue for a lot of us users is that we are at a severe disadvantage due to limitations our IT faces with getting the whole SMTP info set up correctly in FME Flow Automations. For this reason alone, I think it would be useful for there to be a basic emailer that can provide us users with an option for actually being able to use FME Flow Automations and send the one thing we need … An email with success or failure info. As for our company (And I’m sure this is the case at a lot of companies) we can’t use FME Flow Automations and that’s a real waste considering we have a lot of uses for them. Sadly, the Emailer has become the major dealbreaker for us. It’s out of our control as users and wish there was a viable easy option to just have an emailer that can send without having to be tied to a company’s email server.
It would be nice to be able to use ArcGIS web connection to authenticate processes when using the ArcPy library
It would be nice to have the ability to utilize the AI Assist tool in order to read all annotations within a workspace and create summaries or the ability to “search through” annotations to look for something specific.
Is it possible to add the 'Attributes to Read' option from the Readers to the FeatureReader transformer, too?For the same basic reason: not to read unnecessary data when the feature type is large.
We use many custom PDF templates that include form fields (editable pdf fields). It would be great if the PDF reader transformer could read this metadata.
The following improvements to Role Based Security would be useful:1.Increased Granularity for Job Viewing and Job Management PermissionsI need the ability to allow users to see specific other user’s jobs and logs rather than all jobs and logs. We use different service accounts for different enterprise projects and currently I am having to share all jobs/logs with users so they can monitor their processes. Since not all groups need to see each other’s jobs this is not the best solution. (Thank you Safe for new search options in 2019 as they slightly help with this issue.)Likewise, in the current Role system being able to view all jobs requires job management permissions which let users cancel jobs in the queue or terminate running jobs. This puts me in a difficult position regarding how we implement SOX compliance. It is preferred users be locked out from managing running production processes. If the ability to view all logs but not manage jobs was made available that would be a move in a positive direction. If the option to say kill queued jobs but not running jobs was an option that may also be useful.2. Additional Options on Database ConnectionsHaving a Read option alongside the Full Control option for database connections would be excellent. I am seeing issues when I grant users access to connections without giving them full control over a connection. Since we have many processes using the same named database connection it is not ideal to grant users management access since one incorrect change by any user with access could disrupt jobs for all users using the connection. Something similar to how the Notification items are broken out would be amazing.3. Automatic Content Sharing with Administrator AccountsIt would be helpful if FME Server automatically shared user created content with members of the Super User role. If this could be an option for the FME Admin role that would also be appreciated. I have a plethora of users creating content and when they ask for help it is cumbersome to have to share their content with myself and my fellow Admins before I can help troubleshoot.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.