Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be nice to optionally produce an attribute on the NeighborFinder with the count of the close candidates. There are many times when I generate a Close Candidate List for the sole purpose of counting the number of list elements.
Hi, It would be great if Safe could add the following subdomains to safe.com:1. ideas.safe.com 2. questions.safe.com Cheers. Lyes
Add the option to save the users email address to be used throughout FME Server, that could be used when creating new publications.
Hi,Integrating QT with the workbench in order to create custom dialog boxes.
Create simple HTML 5 documents. Features specify headings, text, pictures, tables which are strung together to make a document. Potentially embed SVG, three.js inside.
It would be very useful to have notifications that are able to be scheduled (i.e. they will only run for certain times of the day). For example some of the functionality this would allow for: Being able to set a email publisher to only watch an email outside of work hours, rather than the whole day Running websockets as a notification process when engine demand may be higher for specific processes, but then allowing for websocketreceiver process to be always on when you know that engine demand won't be high. This is an additional requirement to being able to enable/disable a notification https://knowledge.safe.com/idea/38651/disable-a-notification.html
It would be helpful to get informed about security updates which require manual reboots of your FME Cloud instances.
A "HTMLTemplater" or HTML option in XMLTemplater would be really handy to create simple HTML content the same convenient way as XMLs (especially using sub templates) instead of AttributeManagers and Aggregators.
***Note from Migration:*** Original Title was: Use an external file with table for any transformers with attribute parameters table like in SchemaMapper.
A request to add some sort of schema version identification tag to the FME Server System Database. ex. a new metadata table.This would serve as a way to confirm the schema version and if it matches the FME Server Core connecting to it.Currently there is no way to determine the schema version. This can be troublesome when working in distributed environments where one needs to ensure the correct sql scripts were used to create the FME Server System Database. An example where this might manifest is during a restore where a new Core could try to insert a record that has a new attribute, however, fails because the table doesn't have the new column. It can take time to sort out the issue and learn that it is caused by an older schema being created.Often, we are not aware that a different database script must be run for new versions of FME Server. Other benefitsCould be exposed via the Rest API. Then exposed in the Web UI.Allow System Admins to confirm quickly via Database Admin tools the versionThe core could check the version and produce warnings/errors in the log and Web UI when an Admin user logs in.Distributed installs of FME Server continue to grow and this could help system admins and support staff in the long run.
Often when I drag-drop an FFS file into DataInspector to view it I would like to be able to split the data into layers by an attribute. It is what the Group By does for a viewer in workbench.Countless times I had to create a workspace only to be able to do this ...
Idea from FMWT 2017 at Lyon, France :FeatureReader & FeatureWriter work like datasets but are blue like normal transformers.A specific color could be great to distinguish them in the workspace. Maybe the features type color or a new specific color.@KenAtSafe
Create an entry in the navigator window for annotations in the workspace to easly navigate beteween them.
This transformer would operate similar to the XMLValidator, but specific to HTML.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.