Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Level up to the parquet format (updates and snapshot)
Have noticed that many links within Transformer help files allegedly to Community articles about said Transformer do not actually work. Either they go to a generic page or you get a ‘does not exist’ error. Would you please add a task to backlog to fix these? Thankyou.
The ArcGISOnlineConnector supports paths to the service level for hosted feature services, but not to the layer level. To support managing sublayer metadata lets add support for Get Details and Set Details options to the layer path.https://developers.arcgis.com/rest/services-reference/enterprise/fs-update-metadata/https://<root>/<serviceName>/FeatureServer/<layerId>/metadatahttps://<root>/<serviceName>/FeatureServer/<layerId>/metadata/update
Hi there, When using readers in a larger workspace, sometimes I might need to reference the reader (or a bookmark involving the reader after some post processing like changing coordinate system or renaming some attributes) multiple times in the workspace, either at the start, middle, or end. If something is being used, say 5 times, and crosses multiple bookmarks and transformers, I will use hidden connections to keep things readable, however it can still be a hassle if I need to use a certain reader/transformer/junction that is at a certain place in a large workspace, where I might currently be working in another area. I will then need to zoom out and scroll to it, and then drag the connection all the way over to where I want to use it. A way to get around this, is to have the ability to pin readers/transformers/junctions that are used a lot in a workspace and have many connections already, so that if it needs to be used again, you can simply connect to it wherever it is pinned in the window (and then can unpin it again after that if preferred), so that you can connect to any part of a workspace from any other location without having zoom in and out and scroll and repeat, just to create one connection Cheers!
My idea is to update the ArcSDE reader so that you can read from a versioned database. Currently the only way you can do this is by using an SQL executer, it would be nice if there was something built into the ArcSDE reader so that the version of a database you were reading from was dynamic.
The web connection/webservice features have been around for a few years and it needs some improvement in the UX, especially to help new users. Here’s a few suggestions:1. once a web service is created by a user, services, templates and connections are all mixed up in the drop downs or that long list of templates and web services. Some type of separation or categories between user created services from web services templates either on the long list in FME options or the drop downs in the connectors.2. The Add Web Connection drop down from the transformers is confusing to new users, when the web connection is not a simple token or key or the web service is not created yet. 3. On the MCP Caller (Beta) web connection from FME Options, I have to type the MCP URL and API key three times before I can use it. Once the URL is configured from the template ans applied. Once applied, the URL should persist in the drop down when I Test the web service and create with Add my Web Connection.
Hi there,It would be useful to be able to rename web connections and services on import to FME Form. This would allow for updating names if required to match company policy or fixing errors. It is possible to edit the xml file, but if the file is a password protected .enc this is not available.Other wise the workaround is to import a connection and duplicate it, rename the duplicate and delete the original, but this seems like it should be streamlined.Thanks,Marc
Enhance Extruder transformer to have the option to extrude geometry along a complex path similar to the way AutoCAD does to create 3D lines, surfaces, and solids.
With the recent release from Leica regarding their BLK360 scanner coupled with Autodesk ReCap software the use of this format type will become widely used and delivered as a finished project file. In fact, I already have some .rcp files that have been delivered (although .e57 or .las files would be better). As such, please consider adding the .rcp format within the Reader Gallery.
Edit: Got the header of the post wrong but i cant change it. Should of course beTunnels: allow 1..N and N..1 connections Allow more efficient and cleaner workspace design with one-to-many connections for tunnels. Ideally if there is a 1..N or N..1 connection between transformers, one should be able to select all connections → right click → convert all connections to tunnels. The expected layout would be according to picture below. The N-side of the connection would only have one junction instead of N amount of junctions. Layout wise it is already achievable. It does however require many clicks as well as playing with alignment and placing tunnel junctions on top of each other. Therefore it is easy to snap connections by mistake.
I often want to view the source data is the native software and open it from FME Form via Open Containing Folder, then open that file. My suggestion is to add an option to open that file in the native Windows program, e.g. ‘View Source Data’ in native, or ‘Open in Native’ so you remove a step. If the file was a DWG it would auto-open in whatever Windows/user has assigned to open a DWG, e.g.AutoCAD 2027. If it’s a CSV, it opens in Excel (or Notepad++ for example) if that’s what the user has set. Thanks.
Hi there, Can we add a way to manually create the shape of a bookmark, not just a rectangle. When bookmarking transformers, rectangles can make a lot of wasted space and can make large workflows too spread out, whereas creating custom shapes or a nice fit (can use an auto-fit option) can allow space to be used more effectively in the workflow.
hi there, it could be a good idea to be able to add pinned annotations on a workbench for important messages or things to keep in mind for a workbench, so that no matter where you scroll in the workbench the pinned annotation will show in the exact same place. Ideally the annotations would be around the sides of the workspace frame
When using a Dynamic featureWriter with the PostGIS format you can handle the FeatureType geometry these ways :From first feature From schema definition Define one specific geometry typeNone of them are really satisfying for me :From first feature : if you have multiple datatypes you need to order your features or to coerce them leading to the second one From schema definition : no fme_geometry maps cleanly PostGIS geometry types (no support for multicurves or multisurfaces) Define one specific geometry type : not dynamicIt could be great to use a specific attribute : fme_native_geometry_type to define wich geometry type to use in a dynamic writer.This could be for any format (not just for PostGIS but I need it for PostGIS 😉) This could be populated by readers You could provide some transformers : to set this parameter depending on the feature geometry to set manually this parameter (choose format and then geometry type) to coerce geometries as defined by this parameter
In FME Server 2019 on the email subscriptions protocol settings there is a drop down Load Template menu to populate some of the settings as per popular email services.It would be nice if we could add a custom template to that list, to use when setting up new subscriptions, rather than having to duplicate an existing subscription.
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.
After an Active Directory group is imported, synchronization will add any new Active Directory users within that group to FME Server Users. Currently if an Active Directory user is removed from the Active Directory group or is deleted and FME Server is synchronized, the group is removed from the role on FME Server, but the FME Server User remainsManually removing the account sometimes gets missed. I would like to be able to remove those accounts from FME Server. For organizations that heavily use Active Directory it would be nice to have a checkbox option to automatically remove Active Directory type accounts that have been removed from Active Directory or an imported group.
Possibility of including images inside Annotation . Is better when we want to document our Workspace with images.
Summary Annotations contain a lot of information, and therefore take up a lot of screen space. On the other hand, summary annotations dynamically display the settings of a transformer, which can be better than using static Annotation.Therefore it would be nice to have the possibility to select what information is shown in a Summary Annotation.This would have the benefit of showing only the settings the user deems relevant, while at the same time automatically updating this information when these settings are changed.
It would be nice to add tunnels to FME Flow Automations like you can with FME Form workspaces. It would help organize complex automations and make them fit better in the UI.
There’s various suggestions out there explaining how to get the number of features written during an automation:https://support.safe.com/hc/en-us/articles/25407494315789-FME-Flow-Get-the-Count-of-Features-Written-in-an-Automation However, these processes seem a bit complicated given that the count exists in the log for the workspace. Maybe I am wrong and it would be very complicated to access this number.For the “Run a Workspace” action, I would like to have “Total Features Written” included within Output Attribute → Success → Event Attribute:This would allow it to be utilized in downstream actions such as emailing.Also, you would be able to use it within custom attributes and that would eliminate the need for additional workspaces, automation writers, split-merge blocks and http requests.
When a Flow App is created there is an option to customize it by adding header, footer and icon images. Often this will be a company logo or something that is common to all Apps.Currently, the images for each App need to be uploaded individually.It would be great to be able to reference a file from a Flow Resources location to avoid repeated uploading of the same image(s) for each App.
The current customization options for FME Flow Apps is quite poor. FME Flow Apps have the potential to be a centralised focal point/application for organisational/enterprise level ETL; however, they currently allow for minimal flexibility and design when it comes to styling.The lack of flexibility and options for design improvements mean that even with greatest graphics/design eye in the world, FME Flow Apps are often left looking nothing more than a data dropzone, workspace runner or ‘Click to Download’ link.Expanding the options for image customization and editing, greater flexibility in text design, or incorporating HTML would greatly enhance the visual appeal of FME Flow Apps. This would increase visibility and improve perceptions to none FME users who are given access to a Flow App.Documentation could also be created in the form of a technical article on ‘Designing and Styling an FME Flow App for your Organization’ to support this process.
Currently in FME Flow Automations, when using the “Run Workspace” action, the job queue must be selected from a fixed list of predefined queues. There is no ability to dynamically select the job queue using a published parameter or automation attribute.This enhancement proposes adding support for parameter-driven job queue selection, allowing users to pass a value (e.g., from an automation attribute or published parameter, etc.) to determine which job queue is used at runtime.
Probably most relevant for workspaces started through an app or webhook: Restrict the number of runs. I.e. if it's been triggered more than x times in y amount of time, or if there are more than x non-unique triggers, don't run the workspace.The main reason: one of the Flow's we're managing was recently hit by a DDOS attack, within the space of a few hours one particular workspace app was triggered about 4500 times. The workspace failed right away every time due to bad input, but it still took 1-2 seconds to do so, so that did eat up a big chunk of the capacity during those hours.Another reason would be to prevent a user from re-submitting a job if it's taking too long. They might think something is wrong so they try again, and again, and again.
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.
