Shape the future of FME with your ideas
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
In FME Flow, the list of automations is ordered by descending update date by default. Filtering is possible, however It would be nice to be able order it based on name (I include a numbering system to now the processing sequence of the different automations)
There should be an option to sort files and folders in the Shared Resources folders.They are sorted by name by default.
Presently Data Download result links while temporarily available are accessible without authentication. Propose honoring user authentication for accessing the result links or generating a longer token based URL that would be hard to brute force generate. Per this thread, https://community.safe.com/s/question/0D54Q00008Kq1hiSAB/security-of-fme-server-results-download-link
Add the option to send a ZIP file via email that can only be downloaded once and also combine it with the expiration date
It would be nice if there was some sort of toggle option when running with feature caching as to whether a custom transformer produced a single output cache (like a collapsed bookmark) or if every transformer within it had a cache (current behaviour).I can see the latter being useful when actual developing the custom transformer, but in most cases I don't care about the interim portions of the custom transformer, when developing a workspace that uses one.I could put a bookmark around each custom transformer and collapse it, but that becomes tedious when there are several (dozens) of custom transformers.
Make "Run with feature caching" work with parallell processing
Hi,I would like to see more options on the Filter action in Automations.Today (FME Flow 2023.2) you are able to search if a certain string is contained within an attribute or a message. To do a more fine grained filtering you need to chain multiple Filters within the Automation.A great improvement would be if we were able to filter on multiple attributes using common operators like OR/AND etc, within the same Filter. Like a simpler version of the Tester transformer in FME Form.
When it is about to move or copy a workspace to another repository (from test repo to live/scheduled, making it available to other teams, etc) the way to do is to download and publish to the other repository taking care of the data upload and service settings.It would be much more convenient if a workspace could be copied in the web interface with uploaded data, services and notification settings.
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.
It would be helpful if FME Server 2017 had an SFTP Watcher. Currently the regular FTP Watcher does not support SFTP. I am aware that the Notification Service supports SFTP subscriptions but currently in 2017.0.1.1 there is no corresponding SFTP publication option.
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.
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).
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.
***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.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK