Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
The options for filtering on the jobs completed page have advanced (as discussed in other threads). I would like to be able to export the results I've filtered (e.g. to excel). Maybe I have missed some functionality somewhere or is this perhaps in the pipeline?
Create a Trigger in Automations for failed job (that would be applied globally, so whenever a job failed either manually ran, scheduled, or through an automation or subscription, it would trigger the automation.This would allow users to use actions such as filtering before sending an email.
One of the biggest issues that we have with reading in data from various web sources (several XML feeds that we read are especially prone to this) is that sometimes they like to hang or read-in an incomplete data set. To mitigate this issue, we are daisy chaining workflows together so 1 triggers the other one and on down the line so 1 bad dataset doesn't bring down the whole job and the other datasets. Ideally it would be nice if server was able to handle invalid datasets (possibly via auto completing/closing - even if all the data wasn't able to be read in - or more ideally would be attempting a second read at the dataset) and then proceed onto the other datasets.
It would be useful if the list duplicate remover could consider more than one list value when removing duplicates.So only remove list values as duplicates if list{0}.value1 matches list{1}.value1 AND list{0}.value2 matches list{1}.value2 etc.
Similar to SharePoint, request to write files to Documentum with FME. https://documentum.opentext.com/documentum-platform/
Can you consider replacing Flexlm with a newer tool? For instance keygen which got launched recently. Being API-based this will fit Safe Software nicely: https://www.producthunt.com/posts/keygen
I have some workspaces running on FME Server, where users sometimes upload (zip) files that are say > 10 Mb.I notice that in some cases users clicked on the run button before the file upload was complete, causing the workspace to fail. It would be nice if FME Server checks whether there are still file uploads ongoing for one of the workspace parameters, and doesn't allow the submission of jobs when this is the case; accompanied with an appropriate promp of course (e.g. 'file upload for a workspace parameter is still in progress, please wait for this to complete before submitting the job').
Use the IAM Role when authenticating in an Automation action, writing to an S3 bucket. When building the automation, it is required to specify a AWS Access Key ID and a AWS Secret Access Key.This should work in the same way that IAM Roles are supported in the S3Connector. That requires that FME is running on an EC2 instance with an IAM role configured on it.
Have you ever had a job complete successfully on FME Server but didn't realize there are warnings in the log? Warnings can range from must read to simple FYI's which the log displayed in FME Server's UI shows in blue text. Great! What would be even better is if the job completion page let me know if the job had any warnings or within the job history table there was a warning section. This would bring more awareness to the user that the job may have something to double check without explicitly looking through the log.What does everyone think of this idea? Let me know in the comments.
When dropping transformers into exiting workflows, automatically have FME move the rest along. Similar to the way Blender nodes work, like this https://twitter.com/i/status/1105453217138294784
Currently, as an FME Server Administrator if I want to receive notifications about a System Event I can enable email configuration but for this to be enabled I must also provide a system email. As an alternative I would like the option to be able to enable broadcast messages to be created from System Events AND be able to restrict what user/roles can see these messages. This would be particularly helpful for licensing related events that are critical to the smooth running of FME Server.---[FEEDBACK WANTED] FME Server Administrators - if these messages had restricted visibility would it be helpful to have messages related to licensing ('License about to Expire' and 'Low Credits') enabled by default?
Please add a {job.logUrl} key to the standard Output Keys from a workspace Action in Automations.This idea stems from my question on the Community Forum:https://community.safe.com/s/question/0D54Q000089GudfSAC/how-to-include-the-log-file-url-in-an-automation-emailI'd like to be able to include a URL link to the log file in emails sent after a workspace completes in an Automation. This used to be possible in the old Notification/Subscription architecture but is not available in Automations.It is possible to add the log file as an email attachment in Automations but this is not always desirable or even possible - some of our log files can grow too large to be accepted as attachments by our email server and the entire email will fail to be sent.
Exposing versioning options through the FME Server REST API would allow further control, customization, and especially automation to the versioning workflow.
With FME Server build 20787 it is only possible to retrieve automations containing a schedule only with the fmesuperuser role. It would be helpful and more logical if you can retrieve the Automations that your user has access to.
***Note from Migration:*** Original Title was: FME Server Projects: Option to maintain 'shared with' users between DEV>TEST>PROD systems In the Dev environment FME Server Projects are shared with users. When the Projects are exported from Dev and imported into another environment, like Test or Prod, it is necessary to share the projects again. It would be nice to have the option to maintain the original list of shared users or, at the very least, during the import of the Projects provide an option to share with new users in the new environment.
I like caching but usually I'm only concerned with a few 'breakpoints' to inspect values or run from/to, can we make caching controllable per transformer? @rahulsharma
I've seen several questions asking about the gbXML format. If you are interested in seeing FME support this format, please vote for this idea.
It would be great to have something similar to the Auto Connect button in the Feature Type Connections Window but in the main canvas. Just selecting some Reader and Writer feature types > right click > Auto Connect and done.
It would be really helpful if we could rename schedules in FME Server. The way it is now, you can change the description, schedule type, etc. Why not the name too?
we have loads of database connections, can we please sort by the header fields.
Currently it doesn't appear to be possible in the FME Server security settings to give a user the ability to access a specific repository on FME Server AND also be able to see all the other jobs that have been run by other users in that repository. To do this you have to elevate their security settings to be able to Manage Jobs and then they can see all jobs in all repositories, which is not desired.This would be a nice to have capability requested by a client.
The recently released GeometryPicker is really helpful as an enhancement to our FME Server Apps. Yet, the amount of applications (in which using the GeometryPicker would be beneficial) would greatly increase if the user is able draw multiple features (of the same geometry type, for now :)).
When the workspace stops at a breakpoint (previously called inspection points), I would like the possibility of changing the value of any of the feature attributes, before resuming the translation. I would also like to be able to create new and delete feature attributes.
It would be great to have a Coordinate System Gallery popup when selecting a value for a Coordinate System Name Parameter on FME Server/Cloud, similar to what can be done in Workbench. You can find more in-depth discussion about it in this post.
It would be very convenient to have navigation tools for the log at the top as well.
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.
