span8
span4
span8
span4
Ideabyroger7467··fme desktop
1 Map out the logic of all the transformers. (map creation)
2 Detect unnecessary logic steps. (shortest path calculation)
3 Merge transformers without breaking the logic. (shortest path implementation)
3.1 Merge multiple adjacent Testers into one Tester or TestFilter
3.2 Merge multiple adjacent AttributeManipulators into one AttributeManager
3.3 Replace (Bufferer+Dissolver) with AreaAmalgamator or vice versa
3.4 Replace PointOnLineOverlay with SpatialFilter or vice versa
3.5 Replace AttributePivoter with Aggregator or vice versa
3.6 ...
daleatsafecommented·
To be clear, is this to merge adjacent Testers into a TestFilter? Not sure what other transformers can be merged? (Testers->TestFilter is a great idea by the way)
The original idea was multiple testers to one tester, I hijacked the idea to make it multiple testers to one test filter (one output port per original tester)
jdhcommented·
The number of times I have a several testers that I later decide need to be a testFilter instead...
Share your great idea, or help out by voting for other people's ideas.
Add a Workspace Explorer to find old workspaces by name or format or transformer content
Prompt and Run Workspace with Breakpoints
Make it easier to save a custom transformer as a new version
Example of each transformer in doc/fmepedia
Ability to freeze the translation log during a translation (pause the auto scroll)
Auto clear text when Test String textbox is focused (FME 2016's Regular Expression Editor)
Store a Snapshot of which Connectors, Transformers, Readers, and Writers are Enabled or Disabled
Add Writer PRE and POST SQL methods to the canvas to increase visibility
© 2019 Safe Software Inc |Legal