Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
Hi,I’ve been creating quite a few automations lately and in 1 case I’ve ran into a “limiting” factor where a “Sampler” (like present in FME Form as a transformer) would solve my problem. I think this could be a great addition to the “actions” like Merge, filter, log, etc. The case is as followed:I have 3 workspaces that can run parallel from each other based on a schedule. No matter if they succeed or fail, a fourth workspace should always run afterwards.This can be achieved by not connecting the 3 workspaces with the split merge output ports. Then 1 feature will always come out of the “success” port. (red and blue block below) and the workspace will run once.I however have a fifth workspace that should run “once” if “1 or more” of the workspaces in the red block succeeds.At this point, there is no way to achieve this without creating an extra workspace (the image below with the extra split merge block does not achieve this).I would therefor like to have a “sampler” transformer inside automations. This so i could connect all the Success ports from the red block with the sampler and only let 1 feature continue. This would ensure that my last workspace (green block) only runs once if any of the red block workspaces is successful.
This is a small thing, but might be a smart addition.In a bookmark you can “enable” all objects, and you can “disable” all objects.If one needs to create some sort of fixed “toggle” between some transformers in a bookmark, e.g. redirect to development or production, this is not very handy, at least if there are more than two.If a new right-click option of “Toggle All Objects in Bookmark” was added, this would be very easy.I.e. all disabled are enabled, and all enabled are disabled.Here’s how it is now:
The function to uncompact H3indeces seems to lack in the H3HexagonalIndexer. It would be nice if a new version of this transformer could get this functionality. Thanks.
Problem StatementThe DatabaseJoiner transformer in FME currently requires users to hardcode the database name, making it less flexible in situations where the target database changes based on data attributes or workflow conditions. While more complex transformers such as SQLExecutor or FeatureReader can handle dynamic database selections, they often come with added complexity and overhead for some usage. DatabaseJoiner, on the other hand, is lightweight and convenient but lacks the ability to select databases dynamically.Current StateAt present, the database name must be specified manually in the DatabaseJoiner parameters, which limits its usefulness in workflows involving multiple or changing databases. This constraint makes it challenging to integrate the transformer into more dynamic FME workspaces where workflows adapt based on data or business rules.Proposed EnhancementIntroduce dynamic database selection to the DatabaseJoiner by allowing the use of: Attributes: Enable users to specify the database name using an attribute, making it possible to choose the target database based on runtime conditions. For instance, an attribute that holds the database name could be used to direct data flows to the correct database connection. Conditional Values: Introduce support for conditional expressions, allowing users to select the database connection based on criteria derived from data values. Key Benefits Increased Flexibility: With dynamic database selection, DatabaseJoiner would better adapt to varying data sources and workflows without requiring manual intervention. Streamlined Workflows: Automating database selection based on attributes or conditions would reduce the need for user input and enable smoother integration across different databases. Improved Reusability: FME workspaces could become more generic and adaptable, capable of handling multiple database connections without extensive modifications
Provide additional support for additional authentication methods when logging into FME Flow including MFA, Microsoft Hello and eAuth.
When using the ChangeDetector to compare attribute values, decimal and datetime values create false-positives due to precision (i.e. 10.00 vs. 10.0001). Perhaps comparison of decimal values could be done via abs(value1 - value2) > epsilon. The user could enter the epsilon value. Dates vs. DateTimes could be handled similarly.
Across all of workspace, not just current tab. Provide for easy navigation of the reference places. Allows for easy "tracing" of operations affecting an attribute or published parameter.
Related to: In Flow, you have the ability to set the Queued and Running Job Expiry Time through the tm_ttc and tm_ttl Job Directives. You can also set them via the user interface: It would be helpful in certain scenarios to be able to set this at the workspace level, for example where external process call FME Flow and we (as the administrators) want to have overarching control of how long the processes are run without needing to update external processes.
There are Workspace Parameters for Last Save Date, Last Save Build, and History.Can these parameters be included, perhaps as metadata, when a workspace is published and then made available through the Flow interface?This would be very helpful when troubleshooting an automation or developing and improving workspaces that are in the process of being automated with Flow.
I would like to set the HTTP method within the HTTP caller to use an Attribute for dynamic HTTP method calls API calls. Currently the only way to set this is via the user parameter.
I can then use fmewebservices.FMENamedConnectionManager() to find out about the type of the connection and run it to the correct FeatureReader.At the moment I have to manually track the list of DB connections in question or have multiple Parameters for each DB system.
Adding a simple search box in the text editor makes a huge difference in text editor performance and can easily browse among the FME attributes and function easily
Catia is widely used 3D Software for design and engineerin and would be a valuable format for supporting BIM users.
The AttributeFilter has four default output ports: <Empty>, <Missing>, <Null>, and <Unfiltered>. It would be nice to have the option of a single output port instead of these four. This is because I don’t need to differentiate between <Empty>, <Missing>, <Null>, and <Unfiltered>. They can all go to <Unfiltered> and the transformer would take up less space in my workbench.
Hi, I’ve just discovered the JPG XL format and it looks quite promising as a future file format. I was wondering if there was any intention include this format as both reader and writer in FME?Also, I couldn’t discover if this format supports coordinates. Without coordinate support, my request to support this format can be ignored. But would I be asking too much to request that you lobby the relevant groups / corporations to include coordinate support in this file format? ThanksBrad
Context:The Backup and Restore feature in FME Flow is essential for safeguarding the server configuration and data. However, when specific elements like web connections or user roles need to be restored due to accidental deletion or mismanagement, restoring the entire server is often unnecessary, time-consuming, and can introduce additional risks. Proposed Improvements:Introduce a Partial Backup and Restore functionality that allows users to selectively back up and restore specific components of FME Flow, such as:Web Connections: Quickly recover deleted or misconfigured web services. DB Connections: Quickly recover deleted or misconfigured DB connections. User Roles and Permissions: Quickly recover deleted or misconfigured users/roles. Custom Groups for Backup: Enable users to define custom groups (e.g., web connections, database connections) for targeted backups. Allow users to set the backup frequency for these groups to align with their operational needs. Other Specific Components: Allow FME Admins to selectively restore any specific component they require, such as scheduled tasks, deployment parameters, or specific automations, etc.This enhancement would provide greater flexibility, efficiency, and safety in managing FME Flow.
Please add support to read I3S data.
When you read in a CAD file, it reads EVERYTHING, including entities that are not used in the file but still remain. These ‘purgeable’ features can add a significant burden to the Workspace right off the bat. Especially when working with a large number of files, these unpurged entities can crash your Workspace (ask me how I know). It may also be worth it to add some extra handling to prevent errors from killing the process.If we had a checkbox to filter these entities and maybe output to a separate port, this would be a huge boost to efficiency, with the added bonus of a clean file being written out!
This is a point cloud format that is often converted to LAS. Format spec: https://nsgreg.nga.mil/doc/view?i=4202
Could it be possible to create a transformer that uses AI image recognition to georeference for example aerial images? AI detects similarities between image and reference imagery and creates reference points that can be used in georeferencing.
A trigger for GCP buckets.
Migrate the history of jobs with logs in the backup and therefore in the restoration would ensure the continuity of production during a product version upgrade. This step is fundamental in monitoring production events (anomaly, justification, etc.)Tanks!
FME Flow Resource connections can be named with dash characters (example: my-resource), however, you cannot use dash characters in User Parameters. This means you cannot reference that Shared Resource Connection as a Private Parameter to be used locally in FME Form
As I worked to resolve errors with attempting to reference a User Parameter from within a Python Scripted User Parameter, I discovered the issue was previously mentioned 5 years ago in this thread: When I double-clicked on a user parameter (‘DAYS_PRIOR’) in version 2023.2.1 (build 23774) within the Python Scripted Configuration interface, FME Form inserted: FME_MacroValues['DAYS_PRIOR']In order to get the scripted parameter to function properly, I ended up changing the call to: fme.macroValues['DAYS_PRIOR']I also had to explicitly import the fme library.
When using an ESRI Geodatabase (ArcSDE Geodb) reader (or other formats that support aliases as well) set to read the schema it would be great if the alias names of the fields are stored in the list as well. The Alias Mode now has two options:Replace Attribute Names With Aliases → this will replace the attribute names in the schemaExpose Aliases as Metadata Attributes → this only works for data and not the schema If I have an attribute 'ElevationUOM’ with alias ‘Unit of Measurement for Elevation' I would like the schema to haveattribute{0}.name = ElevationUOMattribute{0}.alias = Unit of Measurement for Elevation
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.
