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.
The Message type user parameter will currently only accept a plain text string. It would be very handy (especially when used to build web apps) if you could incorporate hyperlinks and other rich text options into this string. Very much like you can in this description field...This idea was developed whilst creating a webinar on Conditional Visibility Parameters for 1Spatial UK.
I'd like to be able to maintain python scripts as .py files independant from my workspace (Like I do with sql scripts and SQLExecutor). The pythonCaller doens't allow to parse python code from an existing fme attribute.That would be handy to implement an AttributeFileReader to read from the .py file and a PythonCaller to run the python script from the _file_content attribute.Advantage: proper version control of the python scripts in GIT
The scenario: There are multiple databases which store datasets for the same feature types, but table names and column names are vary for each. The mission is to migrate the multiple databases to new multiple datasets which have common schema (i.e. common feature type names, common attribute names).Other than data tables, every database has two mapping tables - one defines the mapping rule between table names and destination common feature type names, another defines the mapping rule between column names and destination common attribute names for each feature type. Fortunately, schema of the mapping tables are common to every database.If it was possible to set user parameters or feature attributes to the SchemaMapper's Dataset parameters (including database connection parameters), a workspace containing a SchemaMapper could do the task with batch processing. However, the Dataset parameters cannot be parameterized in the current SchemaMapper, so you need to set the connection parameters manually for each database.In fact, I resolved this with a workflow containing Python scripts which perform schema mapping for each database based on the mapping tables, but I thought it would be easier if the SchamaMapper's Dataset parameters could be parameterized.
I would like to sort the Transformers listing in the Navigator Panel by Transformer Name or Title of Transformer. One could achieve this by right-clicking on the "Transformers" header and select "Sort by Transformer Name" versus "Sort by Title of Transformer". Currently there is no option to sort. The default is sorted by Title of Transformer.Most of the times, I tend to name my transformers by task then transformer name at the end. If I need to look for the Emailer transformer, because I need to change the smtp IP address, I then need to remember the Title to find it. If I sort by Transformer Name, I believe I could find it easier and also I may have multiple Emailers depending on the tasks at hand. It'd be a great way to group transformers and making changes accordingly.
Hi everyone,It would be nice to be able to directly use an attribute to define the name of the database connection instead of using a published parameter in the SQLCreator and Executor (see picture attached).I will allow more freedom when building dynamic workspaces.All the best,Aurélienhttps://fmecommunity-ideas.s3-us-west-2.amazonaws.com/sqlcreator.png" target="_blank">sqlcreator.png
Can the attributevalidator be made to allow for composite tests....e.g. Field type is Double but null is also possible.
Feature caching is very powerful when authoring complex workspaces. It would be great if the VariableRetriever / VariableSetter transformers supported then feature caching mechanisms with partial runs, etc.
It would be really helpful for both average users and newcomers if you could use the new ChatGPT feature in GPTs to create a tool that assists in building workspaces, maybe even ask users questions about what they need, the format they prefer, and even provide examples cases to make workspace creation easier.I've used ChatGPT a few times, and while it's helpful, sometimes it makes up transformers. Having a dedicated GPT for this purpose could potentially resolve such issues and even help generate Python code for PythonCaller for tasks that don't fit a transformer.If something like this already exists, please let me know where to find it.
Since it is very common to retrieve GeoJSON and EsriJSON, how about combining the fragment-as-format functionality of JSONFragmenter into HTTPCaller, in the response handling?
In the Desktop User Parameters dialog there is the option to "Save As User Parameter Default Values". It would be great if this feature was also available for use in server apps so that the parameter information the user entered is retained when they run the app again.
It would be great if user parameters in automation apps could be imported from some of downstream workspaces, and updated accordingly if that workspace is changed. Similar to what we have in Workspace apps now.
At the moment it is not possible to use special characters, such as '(' and ')' in feature type names in Writers. Many formats do support these characters, but it is not possible to use these in FME, since they are being replaced with an underscore. Please implement this. Note: It is also not possible to create an attribute containing the feature type name and use this as the feature type, it still gives an error since FME replaces these characters with an underscore.
When verifying DWG-files and see if they are according to standards in the AEC market one need to check information for the Layout tabs in DWG-files. The autocad_layout feature together with the Reader Parameter "Read Paper Space Layout Information" would need some updates regarding to this. It would be beneficial if we could also read:Paper sizePlot scaleDrawing scaleCTB-file (already a posted idea)
How great it would be to ask the user to draw a boundary on a map when running a workspace on a desktop version? I know there are plenty of fancy options like FME server/flow with an api. But I am out for something much simpler. Simpler to set up, simpler to run, simpler to maintain. Just a map and a polygon in the user prompt UI which returns a boundary as WKT-text for example, just like any other text prompt.
SIEM tools such as Splunk, Solarwinds, and Rapid7 perform analytics on log files and event streams to identify both security issues and network or application performance issues. SIEM tools typically work on the syslog or CEF formats but can also take an event feed through SNMP (Simple Network Monitoring Protocol).SIEM tools for monitoring are coming up more often in enterprise customer requirements. Some use cases to log from an application integration viewpoint include:start/stop events for FME Flow servicesConnection request to an application - success/failure event with error through HTTPCaller.Logger Support for syslog and CEF.Logger capturing, filtering, and formatting the published log up to the current execution point in a workspaceBatch export of FME Flow and Form jobs and log files in syslog and CEF formats.FME Automation start/stopAPI calls to FME (such as webhooks)Add/delete/update FME Flow user (including SSO users)FME Token access request through FME API, including the associated token useridPublishing these various FME-specific events through SNMP
I am working on a workflow which automates the download of an ArcGIS Online Feature Service and save it as a geodatabase. The service contains attachments which I'm trying to preserve. I can see that as of FME 2017.1 I can now download the attachments from AGOL which is awesome but saving these to a geodatabase becomes problematic. I can see from this article that there is a way to do it but it seems overly complex and still appears to involve a manual step.
As the title says, add the action get attribues on a blob in the AzureBlobStorageConnector. With x of files, and you want to find all the corrupt data which has a contentLength of 0, this would be very handy.
It would be handy if you could convert an sql creator to an sql executor without losing anything of the already filled in parameters. Imagine if you could just convert these transformers back and forth with a simple right mouse click. This can save some time when you are in your development process and suddenly you realize that all these sqlcreators that all have been configured should be transformed to sql executors for some reason.This could be a potentially real time saver!
It would be ergonomic to have a button to clear the list of provided values when entering attributes to expose.Actual workaround : CTRL+A, DELETE
The FMW Workspace Reader needs to be updated to return attributes in writers, along with their data types, lengths, and any other schema related information.
The RasterExpressionEvaluator supports only 1 or 2 rasters. It would be nice if you could add as many input ports as required. Similarly to how the MapnikRasterizer behaves.While it is possible to workaround by using a RasterBandCombiner to combine all the rasters into 1, this is not very efficient and can make for complicated expressions.
With the new deployment parameters it would be nice to upgrade the Jobsubmitter also. To handle:Tokens instead of username/password so you can more easily convert between different FME Flow instancesAlso start a DataDownload service
Allow styling of the tables in HTMLReportGenerator to make tables more personalised.Such as: Changing fonts and font colourChange the size of the columns and the format of the columns (right aligned, centre aligned, etc)Modify the colour of the rows when the table style is set to striped
If a transformer has a tabular sort of GUI, like an AttributeManager, or TestFilter, the default column width is determined by the length of the column header. This should be user-set, or FME Workbench should remember the width of column the user last set it to.For example, in the AttributeCreator, the column widths are set according to the lengths of the headers "Output Attribute", "Value", "Type", leading to the name of the attribute taking up over half the transformer window, and the space for where the attribute value is being set is squeezed to the side. In FME 2022, these were balanced roughly 50:50, because the column headers were "New Attribute", "Attribute Value".The appearance of several transformers in FME 2023 is significantly less readable than before. Column width needs to be user controlled, and not dependent on the arbitrary header name chosen in the latest update. It's not enough that this width can be modified in the transformer window, as it is not saved and reverts to default the next time it is viewed.
In transformers that build/create lists, perhaps we could check a box to immediately explode them so we don't have to add the ListExploder each time.
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.
