If the output of a transformer/reader is split into two or more Connections, it would be incredibly helpful for more complex workspaces to specify which connection features should go down first. Or at the very least the ability to see what order the connections will be used in would be nice.
Released
Control or at least label the order of the runtime flow of features
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+21- Safer
Physically moving ports up or down is now captured in over at idea:
https://knowledge.safe.com/content/idea/19787/adju... .
This idea is about controlling or otherwise labelling the runtime flow of data.
+21- Safer
I can't count the number of workspaces I've created where the ability to control which of the two (or more!) forks that features go down first would have been useful. Given the massive performance benefits that you get from "Clippers First" and similar, this has proven critically important to optimising quite a lot of workspaces.
I know that in theory, once an order has been "set" # it will keep using that order, but I've encountered at least one situation where the ordering changed between versions of FME (filed with Safe under c98882) ! So relying on the currently undocumented method doesn't work so well. The ordering also changes when you do something with one of the transformers that the forks are connected to, making editing such workspaces an exercise in frustration.
(# If you use breakpoints and then run with "next breakpoint", you can see which fork data will take first. It's an exercise in trial and error.)
+21- Safer
Right clicking on a link now lets you bring up a dialog so you can control the execution order. The link tooltip tells you its order too.
+1This has been released as part of FME 2016.1 . Visit http://www.safe.com/downloads to download and try it.