Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Is it possible to speed up the DWG-reader in the same way that the CSV-reader have been speeded up? Using the "tables/pointcloud" reading method?
FME Server uses Distinguished Name (DN) to associate a user with Active Directory. The DN name is a composite of many AD components and is not fixed (e.g. CN=Jeff Smith,OU=Sales,DC=Fabrikam,DC=COM). Therefore if there orgnaisation unit changes or is renamed, or they marry and change there surname, etc, etc the link will be broken between FME Server and Active Directory. They will be no longer able to access FME Server, although they will still be listed as a user. I have seen this occur in many organisations.I believe a better approach is to use the Active Directory SID which I do not believe changes for a user, and is unique to a domain. The other component to use would be a domain, as there may be more than one domain connected to FME Server. This way we would maintain a consistent link that is not affected by most AD changes.
Somebody has published a workspace to 3 services on FME server.As an Admin of this server I do not want the workspace to be published by 1 of those services.But I can not remove the workspace from that service without removing the workspace completely.Allowing an Admin user or the user who published the workspace to remove workspaces from a selected service would avoid removal of the workspace completely followed by publishing it with the 2 allowed services.
***Note from Migration:*** Original Title was: Move workspace service registration and notification settings from Publish Wizard to Web UI
A Loop in the new automations would be great. Like in the Custom Transformers.
It would be great to have a warning on non existing EPSG (Here typo : EPSG4326 instead of EPSG:4326)2020-01-22 10:00:07| 1.6| 0.0|ERROR |Reprojector: Reproject: Could not reproject the geometry of the preceding feature: Reprojector: Could not create reprojection engineError log could be more explicit :ERROR | Destination Coordinate System badly initialized.
***Note from Migration:*** Original Title was: Active Directory Users: Option to view AD Server associated with each user account I would like to be able to identify what AD server each AD user originated from directly in the FME Server Web UI. This would be helpful because if I need to remove an AD Server I must first remove all the associated user accounts, however if I have multiple AD servers configured it is not easy to identify which users need to be removed. Currently I can only get at this information using the Rest API.
I would really like a 5-10min weekly informal podcast from Safe Software discussing "smaller" topics more thoroughly with the Safe Staff. Similar to Coders on Couches (https://www.safe.com/blog/2017/08/episode-5-coders-couches-drinking-coffee-drones/ ) - just as a podcast.
A simple request really.I'm appreciating the new dark mode on 2019 Beta, however the difference between enabled/disabled connectors seems less apparent than on the white background and can be missed. A greater visual variation between the two would be useful, maybe also for transformers too.Thanks, Glenn
Just like the normal counter, it would come in handy if the ModuloCounter also had the scope global/local available. Now, you have to put different counternames to start from 0. It took me some time to figure out that the scope is global by default.
***Note from Migration:*** Original Title was: Also allow the operators 'Attribute has ...' for 'non attributes' (like e.g. parameters or direct fme feature functions) in test conditions It would be nice if the operator 'Attribute has ...' could also be used on 'non attributes'.It is quite tempting to use a testfilter with the condition 'input parameter', and operator 'Attribute has a value'. However, this won't work as expected as the input parameter is not an attribute. When your not aware of this it is also quite tricky to detect that a (test) statement like this doesn't work, because no error or warning is generated when you do use such a (invalid) statement.Also, it seems that I'm not the first one to have been confused that this operator is not possible for non attributes, see e.g. the following topic on the forum; linkOf course there are quite some easy workarounds to this;a) if you just create an attribute from the parameter (with e.g. a parameterfetcher) you can use the teststatement then on this newly created attribute. (Although this is the simple and obvious fix, I do feel it is a bit cumborsome as I think it shouldn't be neccessary to go into such a workaround. Also creating an attribute from your parameter will actually create an extra 'column' to your dataset, which might be quite costly on resources when you are dealing with large 'feature sets')b) I think in many cases you can also get away by using the operator 'Contains Regex'.E.g. I would think that the operator 'Attribute has a value' would be very similar to using the operator 'Contains Regex' with the regex '.+' (meaning 'one or more' (i.e. '+') of 'any single character' (i.e. '.')).
Hi Safe,This is now been a long standing issue and has not implemented or resolve since version 2015. I think it is driving ITS and FME developers wild
***Note from Migration:*** Original Title was: Add option to Data Inspector to set (/alter?) coordinate system of dataset if initially unknown (or wrong) Sometimes I get shapeFiles from users/clients that don't contain the .prj subfile specifying the coordinate system. In this case by default FME seems to assume that the coordinate system is equal to 'SPHERICAL MERCATOR'. However, in most of my usecases this is not correct. In this case a warning 'some features may not align with the background map' is displayed in the data inspector.However, there doesn't seem to be the option in FME data inspector to set/correct the unknown (or maybe in some usecases wrong) coordinate system. It would be nice if this could be added.Another less preferable option could be if the default coordinate system that is used in the data inspector could be altered in the settings.N.b. a quick search about this on the forum only provided this result , which seems to ask for a sort of similar implementation to be added to the data inspector (only more from a 'stability viewpoint').
Add support for writing to Mapbox Vector Tile format: https://www.mapbox.com/vector-tiles/specification/
Currently, when an automations underlying workspace(s) parameters change there is no way to get the automation to refresh the parameter list without removing it from the automation and adding it again or changing the action to another workspace then back to the original workspace.
Add possibilities to create multiple charts at once. There is a group by - but no option to parallell process. Workaround today is to put it in a Custom Transformer with parallell processing possibilities.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.