At the moment the order of input/output ports on a Custom Transformer is determined by the vertical ordering in the workspace. This seems awkward at best. I would like to propose a system similar to that of ordering Creator transformers or Connections. An alternative would be to use drag 'n drop in the Navigator to set the order, similar to the order of Readers and Writers.
I am aware that it is now possible for the user to change this order. That's fine, but I would still like to be able to provide a reasonable default. For example: I'd like my Rejected output port to be the bottom one.
Archived
Modify Custom Transformer Input/Output Order
+5This 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.
+29- Enthusiast
Agreed! I wonder if there is a way to force it in the code as a workaround until this can be implemented? @Mark2AtSafe
+59- Safer
It's already filed with our developers as PR#51779 - but I mentioned the rejected port idea and suggested it might be a good stopgap for full control. We'll see what they say. In the meantime, I can't think of a good way to force this to happen.
I generally create the content in a workspace before moving it to a custom transformer, primarily because it is quicker to handle the attributes. Looking at this movie ( https://www.screencast.com/t/q8rVHXo8Uiy1) I'd say that the transformer at the bottom appears at the bottom on the custom transformer - so put any transformer with a rejected port there before you turn it into a custom transformer.
It's important to remember only connected ports will be added to the custom transformer by default, so don't connect more than you need. Also, the above won't be much use if you had more than one rejected port connected.
Ultimately I think we'll implement port control in the Navigator, because it makes way more sense than the Y order on the canvas. But I don't know when that might be.
+40- Contributor
This is something I've been asking for since 2012. And I absolutely agree that navigation pane order is the way to go.
In the meantime, I make sure to drag my <REJECTED> port to the bottom of the workspace to ensure it's the last one on the transformer.
Incidentally, upper case matters if you want it to behave like standard rejected ports (red bubble or terminate).
+40- Contributor
This is something I've been asking for since 2012. And I absolutely agree that navigation pane order is the way to go.
In the meantime, I make sure to drag my <REJECTED> port to the bottom of the workspace to ensure it's the last one on the transformer.
Incidentally, upper case matters if you want it to behave like standard rejected ports (red bubble or terminate).
+8Hi, had this problem too. That irritating custom transformer having the rejected port upstairs and it will not change position without a crossing line. I solved it by accepting the crossing line, however one could imagine a solution using an InlineQuerier with 2 ins and 2 outs, port 2 copying everything on input 1 and vice versa, or use a junction. Of course there is more to this then just swapping ports.
Login to the community
No account yet? Create an account
An FME Account is required to contribute
LoginEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.