Open ideas have been reviewed by our Product Management and are open for commenting and voting.
As an FME Server user, when I update the default values for Published Parameters in workbench, I would like an easy solution to apply these changes to all the functions that use this workspace when I re-publish it to FME Server i.e. schedules and workspace subscribers.I suggest adding a checkbox option within the publishing wizard in FME Workbench, which list all scenarios where this workspace is run that were created by my user account so that I can choose which ones should be updated with the new default values at publishing time.
As an FME Server user, when I update the default values for Published Parameters in workbench, I would like an easy solution to apply these changes to all the functions that use this workspace when I re-publish it to FME Server (functions would be defined as schedules and workspace subscribers here). I suggest adding a refresh button on the main landing page for these functions, so that you can quickly easily choose what needs updating. Currently in Schedules there is a Reset button per Schedule only, but in Subscribers the only option is to update the values manually.
The possibility to download an older version of a transformer/reader/writer. Sometimes the use of an older version of a transformer/reader/writer is more convenient then the latest version. And not everybody has 9 versions of FME installed.
When I create a CustomTransformer to re-use the functionality that I need often, I like to make it in the oldest version of FME. So when I need it in the previous version, I can use that.But when I want to make changes to the linked CustomTransformer I can right-click the transformer and pick Edit...Then when the CustomTransformer opens I get the dialog asking if I want to edit my CustomTransformer in a new version of FME. All changes made will not be made to the CustomTransformer that is linked in older workbenches that need to stay compatible with the old version.Could you make it so FME reads the FME version where it is made with and tries to open it with this version, so the transformer stays compatible?Another question related: I have some workbenches that don't work in the Beta version of FME and some workbenches that only work in the Beta version. But I sometimes loose track which version I need to open with. Is it possible to tell windows what version of FME the default version should be. I tried something like create an extention "*.19.fme" and ".18.fme" but that didn't work. This could be a solution for the other issue as well.
This helps when the newly created version of a custom transformer is no good. Currently workaround per Safe is to override the current version with the prior version.
I would love to have "backward compatability" rollback where i can pull older versions of transformers from store. In case i need to save-as to a lower build target.
It would allow the user to insert a Junction anywhere more quickly.
Very often vertices on connection lines are placed carefully on the canvas. And than you find out that you have a connection line that needs to follow the same path. So you'll add Junction, but than the vertices in the connection line are removed and all your efforts go down the drain. It would be a great solution if you can just right click the vertex and tell it to convert to a Junction on that exact position without bothering the other vertices in the connection line.
Add a check in the Navigator window under Scripting to allow Enable or Disable the Startup or Shutdown scripting to run.During debugging, I frequently need to disable the workspace to run the Startup Python scripting. either I Cut and paste to Notepad, or I have to o comment out all script lines just for the sake of testing.i can add a private parameter Type Choice "Debug" with values Yes/No, but I guess it'll be more handy if it is set by default in the Navigator window for any workspace.
It would be nice to be able to quickly enable/disable startup/shutdown scripts without having to comment everything out or remove all the text. Maybe a right-click option in the Navigator tree with 'Enable' and 'Disable' as options.
Similar to http://knowledge.safe.com/content/idea/19244/function-to-enable-and-disable-the-startup-and-shu.html it would be nice to be able to temporarily disable scripted parameters instead of having to comment them out.
I realise this might "change" the ChangeDetector (it maybe becomes more similar to the UpdateDetector custom transformer?) but it would be good if it could provide some details about exactly what's changed between datasets, i.e. a summary attribute describing why it thinks things have changed.
***Note from Migration:*** Original Title was: Additional ChangeDetector functionality request for 2019 release of FME in April. I have been working with the UpdateDetector Transformer in FME 2018. I have been informed that ChangeDetector will be replacing this transformer in the April 2019 release of FME and I think that there should be some additional functionality included in this upcoming release. I find that there are "Updates" detected by the transformer that are sometimes not clearly seen by the user and thought that it would be very useful if the transformer included a ChangesDetected Attribute that would list out the changes detected by the transformer. It wouldn't have to be that detailed, especially at first, it could just list all the attributes where changes were detected along with "geometry" being one of the other, possible detected changes. This would help so much in finding issues in data that are causing discrepancies between two versions of the same data as it can be like finding a needle in a haystack otherwise.
When UpdateDetector routes features to DELETED, ADDED, UNCHANGED it is pretty easy to understand why. But when routing to UPDATED, the reason may be geometry or changes in one or many attributes. Sometimes the differences are not so obvious, ie spaces, different data types.I would like an output attribute stating the reason for update, and also attribute output with a list of the attribute names that caused the update. This would also make it easier to look for different types of updates for logging or stats.For performance reasons this could possibly be turned off.
I'd be very happy if the ChangeDetector could give me more clues about what had changed - for instance, if it could indicate which attribute(s) were different and what the two values were. Also, if I could change its accuracy for numeric values!
For transformers that accept a list of values, e.g. AttributeCreator, AttributeFilter, AttributeValueMapper, AttributeExposer..., allow editing by pasting to several lines at once a single multi-line value.
With FME 2018 we can now copy and paste attributes from one AttributeManager(AM) to another. When I copy 1 attribute from AM1, it pastes as expected into AM2. When I copy 2 or more attributes from AM1 over to AM2, only the first attribute pastes as expected with no Input Attribute filled in. The additional attributes include the copied input attribute field names and they are not editable and then get highlighted in red. It would be nice to be able to copy many attributes and have all of them show up without the input attribute field names if those attributes are not already included in the attached feature.
I'd like to do some customization of the FME Server Web User Interface and I wondered if other people also want to do that? What would you like to customize in the Web UI?
Hi,It would be useful to be able to change the color scheme of FME Server web interface, to quickly distinguish between DEV, STG and PROD servers.Thanks,
I administer multiple FME Server environments across multiple client sites. Sometimes, I'm trying to make changes to the same workspace or schedule on TEST and PRODUCTION servers. However, there have been times that I have accidentally modified a PRODUCTION server when I meant to modify the TEST server. The reason for this is that both server interfaces are identical. I lost track of which server I was modifying. It would be nice for the ability to customise the server interface to highlight that I am working on a particular server. For example, if there was a big red banner on the top of the screen of the PRODUCTION server, or red font, basically anything to differentiate it from the TEST server, I may not have modified the wrong server.
Right now, the Extruder transformer can only extrude with a value (=distance), thus creating an object with the extruded surface (or line) parallel to your input data. I would very much like to be able to extrude to a certain value. See this topic also:https://knowledge.safe.com/questions/30130/extrude-3d-face-untill-a-certain-z-value-is-reache.html
It might be useful if every writer feature type and the FeatureWriter would have <Rejected> port and Filter tab.<Rejected> port: Outputs features that have been rejected by the writer. e.g. features which have null or missing attributes for non-nullable fields in the destination feature type, features which have an invalid geometry against allowable geometry type or structure in the destination feature type, etc.Filter tab: Optionally the user can specify a condition to filter features that should be written into the destination feature type, like the Tester transformer. When a condition is specified in this tab, features that do not match the condition will be output via the <Rejected> port.Expected Advantage:Allow the user to collect rejected features and create a report about them as another output dataset. Make it easier to investigate the reason for the rejection in conjunction with the Inspector. A Tester may be removed from the workspace for a simple data extraction and loading.
When a user has a workbench running on desktop or server it would be useful if a report is generated identifying attributes/schema that has changed since the last run; i.e. additions, deletions, and modifications - and what the changes are. In an environment with many stakeholders contributing data, it can be very time consuming and involves much manual effort to review updates
I love using feature caching in FME whenever I can. I find it's the easiest way for me to test whether my transformation is working correctly. Sometimes I am testing a workspace to see if it will filter objects the way I expect. So I might make changes to a database or a file after I have features cached. If I run the workspace using caching, it won't load new features, because they are cached. Even if I say "Run just this", I get an updated feature in the inspector on that reader, but not on the next transformer. So the rest of my cached workspace runs the same as before even though there's a different feature up the pipe. I know I can get what I'm asking for just by renaming a transformer, if I'm using a SQLReader or FeatureReader. But I'd like to have an option for any type of reader where I can do something like right click and clear cached values. That way on any reader, I can update a feature without updating the rest of the workspace. I don't know of a way to do this now, but I'm definitely not an expert.
This has probably been up to discussion before, but I could not find the exact idea. It would be an amazing feature if FME could write directly to rvt, 3dm and other 3D formats. This would be helpful for many people who are in need of these formats, who don't want to use the other 3D formats that FME can write (e.g. skp, 3ds, dwg, dae etc).
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.
