Skip to main content

Open ideas have been reviewed by our Product Management and are open for commenting and voting.

Filter by idea status

Filter by product area

4589 Ideas

gisbradokla
Enthusiast
gisbradoklaEnthusiast

directory and pathnames Reader skip invalid pathsOpen

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  

OpenID Connect (OIDC) authentication support across the FME Platform - Have Your Say!Gathering Interest

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! 

mladenm
Participant
mladenmParticipant

IFC_API Reader/Writer: Native support for IfcFixedReferenceSweptAreaSolidOpen

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.

davisblack
Contributor
davisblackContributor

FME Flow User Role Security EnhancementsOpen

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.