Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Currently the datadownload service only supports output from writers. It would be nice to also support featurewriters. For more information see Question
User works at a higher level and simply specifies the key elements Trigger: Email, s3, File, message, etc. Action: workspace that is to run Delivery: email, S3, Directory, Ftp, web socket etc.
Outlook - reminder for when license expires: check. However when noone see that notification..... it expires and everything will be a disaster. So:Auto send e-mail to all users (or only admins) - 7 days before a license expires - and also 1 day before. From FME Server.This way all the users that do not know about licensing are atleast aware that the license might expire at a certain time - even though there is another person responsible for renewing the license.
A security audit of an FME Server application has highlited that users can have simple passwords to login as a problem. It would be nice to be able to set the rules a users password must adhere too.
It would be very helpful if you had an option for a concatenation of workspaces in the scheduler of the FME server.At the moment, I use an additional FME process (with various FMEServerJobsubmitters) to concatenate the workspaces.I would prefer it, if you could set this chaining in the admin interface of the FME server for the scheduled jobs.This would not require an additional management process in the future.In my case, I can not set up several scheduled jobs because they have a temporal dependency. For example, the following process may be started after the previous one completes successfully.
Since you now have the workspace viewer it would be helpful to have a minimal workspace workflow designer web UI where one could chain/link/connect multiple workspaces to run in certain order with success/fail logic.I feel that FME Server does not handle parent / child workspaces very well (more it’s just seeing the master workbench). We use this a lot since a lot of our datasets have to process in a certain order.I would use this by linking the flow of workspaces, some can run as soon as an engine is free, some have dependency’s etc.This would solve the challenge with the master locking up an engine when run in sequence and also we can get log files and reporting as default on child workspaces
Currently, in FME Server the number of active tokens per user is limited to 1. For some applications it would be useful if multiple tokens could be used per user.
This idea has been created to track interest from the FME Community for displaying line numbers for the Log on the Job Details section of the Jobs Page (pictured below). For example, the line numbers could appear when the 'Show Time Stamps' is toggled on. Please add any additional comments or suggestions!
Simplified exposure of any ERROR level events in job results. So rather than have to wade through and find and open log files, and then try and find the error (something that most end users cannot do), publish whatever the ERROR level event(s) are somewhere nice and obvious if the job fails. Should increase the ability to self-help, at least a little.
Add dynamic log filtering to FME Server just as it has been added to FME Desktop 2018. It would be a time saver over having to scroll through multiple pages of long log files in one's web browser or downloading the file and scrolling/searching through it.
Many settings on the FeatureReader/Writer transformers are format agnostic (e.g. the transformer name). It would be great if the transformers could be configured to NOT re-read from database connections when these types of settings are changed.I almost always pass in my connection details as attributes or published parameter values so having to navigate the file system to find an SDE connection file, or specify a database connection each time I make a minor change to the transformer settings is frustrating. It's a minor inconvenience, I know, but just one of the "little things" that I think could be easily fixed.I used to be able to work around this in many cases by editing the settings directly in the Navigator pane but in FME 2017 this option has been removed as the settings are more tightly integrated with the transformer.
Add MapInfo Workspace Reader/Writers. Read and write .wor, .mws, and This would be great especially if the .mxd reader/writer were implemented.
An internal Alter/Notification would be very helpfull to monitor the FME Server without additional software.So an Notification should be triggered, if one or all engines are down...
Would be nice if the ChartGenerator would be able to produce space time cube visualisation (in 3D as a bonus). Could also be an option for an separate transformer. I can do it now with the R caller but would be nice to include it in the software itself.Input route/point data with time and date + raster or spatial as 'back/underground'output: (3D) Space time cube, Space time path or Space time prism.Also, everything with space time in front of it just sounds cool. :)Example
I want to have an pause-mode (break) to do changes in large workspaces. For example to change connections or transformers without an internal validating the workspace after every action.In very large workspace it may take a long time for FME to ckeck, if everything is valid after every change.So i'd like to have a possibility to stop this validation temporally.
HiAGOL has no UI to create an attribute index, there is only a REST endpoint:https://developers.arcgis.com/rest/services-reference/add-to-definition-feature-layer-.htm#example2if you need to make queries on a key field an attribute index would speed things up.
My organisation uses a floating licence server which contains licences for different FME Desktop editions (e.g. Professional, ESRI, Database etc.). However, the end users often do not know which edition they are using and sometimes end up using inappropriate licences for their roles.I am aware this information is available under Help > About FME Workbench, but it would be useful if users could easily see which edition they are using each time they open the application. This information could be displayed either:On the splash screen – after ‘Checking license…’ the edition could be displayed below ‘FME Desktop 201X.X’On the status bar – next to the FME version/build number
Add reading and writing support for object properties such as Constraints, Identity Data, and Phasing among others for DWF.
Hi,I hope that oneday that FME could have a voice contrl feature to make converting data so easy like to use Alexa.Cheers,Jing
It'd be cool if there was a waterfall view of a running workbench similar to the one in chrome tools so you can see how long each part of the model is taking in a graphical manner, rather than trying to interpret the logs. Each reader/transformer/writer would be a line on the table. If a transformer rejected features it could be highlighted in red. You could also have columns with the number of features that pass through each transformer, its start and end times etc
It would be nice to have the ability to convert a writer into a reader. In some occasions you write a dataset and then want to use it right away.
Include the options for setting the time limit for an objects expiration.
Until now, FME is creating new dgn/dwg files with the help of writer.But there is no option to update / change / delete specific feature i.e. changing the colour of line from red to blue / deleting the specific feature / changing the layer/level / etc... This is something like UPDATE in database. If we have to update small changes then we have to create entire dgn/dwg file which is not advisable...
The answer to the following KB question lists some limitations on the S3Uploader (and I would assume the other S3* transformers):https://knowledge.safe.com/questions/31838/s3uploader-and-network-proxy.htmlSpecifically, the limitations are listed as:...there are some non-supported configurations:Custom proxy mapsNTLM or Digest proxy authentication (as seen when you go to Tools-->FME Options-->Network Proxy-->'Use Authentication')It would be great to see the S3* suite of transformers updated to honour the full set of proxy configurations. We are specifically interested in NTLM authentication, but why not bring it inline with the rest of the FME software and support everything?
In all parameter boxes, there is today an option to "Save As My Defaults". This would extend this to allow named sets of defaults so you could have several setups that you flip between in a parameter box.
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.
