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.
For all transformers, it would be nice if feature caching would only cache for ports that had a connector on it. This could either be global functionality, or even better would be some kind of parameter that allows the user to cache or not cache un-connected ports.
I find the "Email results to" option is confusing, particularly for new FME Server users. They tend to think they would get the workspace results by email if they just write their email here, no matter the service chosen. Some of them might realize they have to configure an SMTP Email Server and do so in the System Email under admin > system configuration > network & email, but few understand they have to do it under the notifications. It's still quite tedious having to configure the same SMTP Server for all services and success/failure combinations, not to speak about maintaining configurations in 7 different places, but that might be a different story and could probably fall together with this other idea https://community.safe.com/s/bridea/a0r4Q00000HbrxSQAR/fme-server-email-subscription-custom-template.I think it would be great if this option could be renamed into something like "email notification to" or relocated under the advanced options. It would also be nice to make it more clear you need to configure notifications for this.
As the FME Server Administrator, I manage our FME Server Production environment. We make heavy use of Scheduling FME Jobs. Our organization has many jobs that run every day, all day, and this is a result of 100s of schedules jobs that are scheduled to run at different intervals, running every few minutes, hours, days, weeks, or months. I want to see a vertical bar graph report that shows the occurrence of schedule jobs over a period of time (day, month, x months, or year) - projected into the future. This would help identify times where there are just too many jobs scheduled in a period (ex. where hour, day, week, and monthly scheduled jobs all attempt to run in a very short time frame) and there are not enough engines to handle that many jobs efficiently. To do this, however, an enhancement to the Schedules would be to allow a user to add an estimated "Run Duration" so the vertical bar graph could accurately depict overlapping schedule jobs with the number of engines. (over time this information could be pulled from the job logs for more accurate estimation)As I continue to expand the number of scheduled jobs, I suspect at some point I'll need to add more engines or rework the schedules to avoid jobs from being queue longer than the business deems appropriate.The complexity of this calculation is increased by having parent/child jobs chained together... but the estimated "Run Duration" could be tweaked to include the duration of the child jobs as well.I want to be able to do this so that I can determine or detect future problems with engine availabilty and engine demand.
The ISO-8601 standard for week numbers in the DateTimeConverter is missing the Week 01 - 53 implementation, where week 01 is the one with the first Thursday of the year. This is referred to as %V in other scripting languages. Can this be added as a DateTime function?
Hello,For the date 01/01/2022 the DatetimeConverter return the year 2022 and the week 00.But in the ISO8601 norme, it should be the year 2021 and the week 52.I had these need resently for a client. I think, it would be good to have the choice between Naturel and ISO8601Thank you
I regularly have to save as to get the path of the workbench for pasting to other systems like email and Jira.Similar to Notepad++ and other apps it would be great to have a copy workbench path to clipboard in the edit menu. Alternatively a Workbench info window from the navigator. this would have paths and other metadata such as last save time could be very useful.
It would be nice if there was a link between initiator and schema. let say you read a folder containing XXX amount of datafiles and you are only interested in the ones that contain a specific schema. the you could read the folder, only read schema, test for the schema you want then merge that schema with the link to initiator. schema has the primary key, and initiator has the foregin key, with a 1:many relation.
We are using a 'generic' FeatureReader to handle numerous data formats (TAB, SHP, GDB, CSV, GML, DWG). This works well, but for the latter 3 formats I have had to add readers as resources due to settings which aren't directly accessible in the FeatureReader.Could the Generic option in the FeatureReader be modified to include format-specific settings and eliminate the need for the resource readers?
Similar to how the InlineQuerier and FeatureWriter work, have the ability for custom transformers to support the “Connect Input” functionality where new input ports are madeSpecifically thought around Marks creation of the DataLogicControllerhttps://www.linkedin.com/pulse/whats-up-wednesday-26th-june-2024-routing-features-logic-mark-ireland-r84oc/
Hi,It would be nice if we could in a Custom Transormer to create the same behavior of the FeatureWriter or XMLTemplater by addind dynamic Input port.Regards,Jean
It is really handy to set multiple presets in 2019 and this makes life a lot easier but i'm missing the ability to share these settings/presets with my colleagues. I would really love to see an export/import button or even a linked button so when changing some of the settings in the given preset it also changes everywhere else.
Hi!It would be usefull to be able to export the parameters from the translation parameter windows to share the preset with another person. For example, 2 people use the same workbench, but each one need to have specific present. It would be more easy when you have a lot of parameters.Thanks !
Highlight all selected features in the data inspector - There is a method to Save Selected features from within the data inspector, however, sometimes it's not clear what is selected. In the table view the selected features are highlighted, however, in the Map view only the feature which is seen in the Feature Informantin window is highlighted. It would be really nice is all selected features were automatically styled in such a way so see what is selected.
When two (2) objects are selected in the Table View of the Graphics View, clicking the "Zoom Selected" button in the maps view only zooms to the first selected object. not both.Similarly, when two objects are selected in the Table View only one is shown as selected in the Map View.And when one object is selected in the Map View, the Select button is active, holding down Control to click-select a second object zooms the map rather than selecting the second object. The only way to select multiple objects in the Map View is drag-select which can be problematic.
It would be nice to get the Transformer version history as a default option in the context menu. If you update a Transformer in FME 2016 you get to see the changes between the different versions that are used but you have to go via the update option and you aren’t able to see all changes. So in case you just want to see what changes occurred to a transformer, you have to find an old version of it to see the changes.
It would be very useful if it were possible to be able to check the differences between two different version of a transformer outside of FME Form. This would allow better planning and resiliency when upgrading environments. It would also allow much better auditing of existing workspaces en masse, particularly when combined with the workspace reader, rather than having to open each workspace individually. It would be ideal if this were provided through an API, or have these added to the https://fme.safe.com/changelog/ page with links to further details.
Please make the restoration of FME Server Version Control after upgrade more intuitive. This could be done by:1) Prompting to fetch from remote immediately after a restore, or2) Silently fetching from remote after a restore.Currently the back/restore tool will restore FME Server Version Control settings, but you have to fetch from remote before making any commits in FME Server to avoid remote ref and local ref errors (ie a sync to remote is needed before making changes in FME Server).
I am keeping extensive checks on changes to workspaces and when upgrading FME Flow I want to keep my history of version control in order to keep track of changes (by team members) post upgrade and have the possibility to revert to previous states.
The deployment parameters FME Flow feature is a very good idea but automations can’t take full advantage of them.For example, they can’t be used to set host, port, username and password of SFTP Directory external action.It would be an improvement to allow to fully configure actions using this new feature.
Hi all,By watching a new user struggle with an existing FME Flow install, I noticed the following 'inconvenience' / 'unexpected behavior' / 'point for improvement'.On the Workspaces-tab there is a search-bar, but that only searches the repositories. In most cases there are not so much that the alphabetically ordered list desperately needs a search.The actual thing you want to know is: 'Where is workspace 09-final-output.fmw'.The whole layout, Bold font 'Workspaces' above a field 'search' suggests this field will help you with that, just like you can search files in folders in any modern OS-file-explore-tool.I think this would greatly improve the user-friendliness for people who maintain processes they did not build themselves.Kind regards,Martin
In any view (FME Flow) where a table is presented including results, for instance the list of jobs, the list of scheduled jobs, the list of users and so onThere should be an option to sort that table by clicking on the title of the column, or any other sorting mechanism
Just a suggestion to increase the robustness of versioning in FME server. It would be nice to have a check out/check in process where, if a fmw is checked out, no one else (except an admin) could then update it in FME Server, until the person that checked it out, checks it back in.
I'd like to have an json option for the response of the metrics-api:https://[FMEServerURL]/fmerest/v3/metrics?fmetoken=xxxxxxxIn most cases it is easier to use a json-output than a text-output. But it isn't impementet yet. Hope to get it in some of the next versions.
I wondered, maybe Safe could add an option to the Sampler to drop unsampled data, instead of sending it out of the unsampled port.Why?Because when I run a workspace with caching turned on, it’s using up resources caching unsampled data that I don’t need. This is especially true since I was set up to sample only the first feature. Having obtained that single feature, I really don’t need the Sampler to carry on storing other data. In fact, I don’t really need it to carry on processing at all!
When authoring workspaces that process large datasets, as Sampler can limit the data while testing - such as the first 10 rows (ignoring the rest). If you are utilizing feature caching - the transformer continues to process the remaining rows of data through the 'Not Sampled' port, which takes longer (and increased the cache size).To improve performance of the Sampler, it would be handy to toggle the 'Not Sampled' port. The PointCloudFilter has a similar ability to toggle Output Unfiltered Points.
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.
