Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I'd like to be able to reorganize repositories by moving some workspaces into more topically-arranged repositories. Currently, we have to republish them to the new repository and then delete the old one from the existing repository - which destroys the version commit history. Git (the underlying technology behind the Version Control in FME Server) is able to track file moves (they are treated as renames) and not lose the commit history associated with them.
When filtering FME Server logs (Completed jobs), it would be useful to be able to filter by date and time. When certain jobs are running every 5 minutes and we want to find one from 3 days ago at 4:30am, it would be very useful to filter based on date and time.
One of our clients brought to my attention that FME Flow doesn’t support SFTP triggers, even though SFTP is a supported protocol for external actions and FTP triggers are supported.The current work around is to use an FTPCaller transformer in the workspace and use a schedule for change detection. Adding an SFTP trigger in FME Flow Automations would be beneficial for lots of organizations as it enables a secure file transfer protocol for automations triggers that’s not possible with just FTP.
Default styles in Data Inspector, e.g. default opacity, line thickness, point symbol, color, etc.
I’ve been enjoying some great API token functionality on other platforms which I’d love to see on FME Flow.A notification before a token is due to expire. When configuring an api token I can specify an expiry date, however, without knowing how long the token is needed I tend to put in something soonish. Of course the application eventually breaks because I forgot to extend the life of the token. A reminder that a token is due to expire in 7 days or so would be really nice. If I don’t want an application to break I need to set this expiry time quite far in the future, e.g., a number of years. In this case if an application eventually stops being used then there is still an active token which I’d like to avoid. Setting shorter times coupled with a reminder would be much better. A “Last Used” field to indicate the last time a token was used. This helps to identify tokens which are no longer used so they can be removed/disabled. These two features would be really nice to have. At the moment I would need to set up my own notification service to check if a token is due to expire. And at the moment I can’t tell when a token was last used.
It would be nice if there was the possibility of setting up a notification that a security token for an FME Server account has expired (or is about to).
***Note from Migration:*** Original Title was: Enable Different WHERE Clause for Different Feature Types within the FeatureRader I'd like to be able to set different WHERE clauses, or choose to apply a WHERE clause to only one FeatureType within the FeatureReader.
To better manage Named Connections on FME Flow there should be a way to list which workspaces that uses which Named Connection. It would be useful to both have this in the GUI of FME Flow and as an API endpoint.Here is just two common situations when this would be very useful:If one updates or overwrite a Named Connection, which workspaces will be affected? Remove unused Named Connections that shouldn't be used any more or when upgrading/migrating between FME Flow version.
It would be great to see a easier process built into the Server platform for managing SSL Certificates. ESRI and a couple other companies have invested heavily into building a UI and RESTful interface to help update SSL certs.
I would like the option to use .pdf as fileextension when using the docx writer, so that the document is converted to a pdf in the end
When a bookmark is expanded, the context menu has the option to disable/enable all objects in bookmark. It would be nice if this option were present in a collapsed bookmark, so that it is not necessary to expand it first before disabling.
can we please have the ability to sort schedules by their run time, by name by next run time etc. also the ability to filter by workspace or folder path? managing these is getting tricky
I recently had to change computers. I realized there is a lot of customization to the look/feel as well as the Database/Web connections that are embedded in the old computer's FME, but I didn't find any easy way to port those into the new machine's FME Desktop. I am stuck rebuilding my settings on the new machine from scratch.Perhaps this could be a future enhancement to the tool or some documentation on how to migrate those customizations could be published?
Currently FME Desktop allows only to enable or disable statistics logging completely.I think it would be nice to be able to distinguish between "Transformer statistics" and "Reader/Writer statistics":Some transformers (especially when used with grouping or custom transformers) are very verbose with logging and it would be nice to silence them without loosing the reader/writer statistics in the logfile!We have experienced logfile sizes up to 600MB ;)Ping @DanAtSafe
It would be beneficial for FME to develop its own ChatBot and integrate it into the FME Form. Users could ask questions while developing their workspace and receive direct suggestions from the ChatBot on effective ways to build and continue developing the workspace.
Make it possible in the jobs page on FME Server to open a job in a new window - to make it possible to easily open multiple jobs.
I'd like my FME Server App output to be streamed into a new tab/window, either automatically or by clicking Ctrl + click on the OK button
In FME Server 2019 beta, triggers and actions are individual objects with a single action. Therefore If you had 100 automations, and 30 automations that send an email utilising the same configuration, you actaully have 30 seperate email actions. If something changed in that email configuration, you would need to find the 30 locations and change this in each one. If would be great if there was a parent template that held connection information, that update child objects?N.B. Currently, you could utilise the "notify topic" option, but then you are jumping back to notifications (publishers/topic/subscribers)
With the Civil 3D reader you are able to read Property Sets which is great. However, writing Property Sets is not possible yet. This will be very helpful in order to facilitate CAD users with a DWG in which they can easily enrich features with information with more possibilities than with the AutoCAD Map Object Data.
***Note from Migration:*** Original Title was: Publish FME Server REST API endpoints for retrieval of Automation workflow components Per this question: https://knowledge.safe.com/questions/111871/fme-server-rest-api-get-automation-tasksitems.html It appears that Safe has REST endpoints available for retrieving Automation component details but they are currently unpublished. It would be great if Safe could publish this information.Specifically, I would like to be able to retrieve details of FME workspaces used in an Automation, including Published Parameter values configured in the Automation. I need this information to help with documentation of current state of an FME Server instance (I am using an FME workspace, via the FME Server REST API, to produce a current state report).In a more general sense, it would be great if Safe could document all undocumented REST API endpoints: https://knowledge.safe.com/content/idea/75119/more-fmerest-api-calls-documented.html
Would be nice if there were filters (similar to how there are on the completed jobs page) to filter by repository, category, enabled/disabled, and all the other columns that are on the schedule page. This would make it easier to find schedules/automations when you have hundreds of them, keep it consistent with the other UI, and partially resolve the need for sorting (which was removed due to resource issues).
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.