Hi,

I'm having a customer transformer with a group by linked on an attribute:

Every feature that enters the Custom transformer (it has 3 input ports) has a value for that attribute.

I'm under the assumption that the custom transformer operates as follows:

reads all features, process features with value A first, next switches to value B and as last value C.

However in my workspace, the custom transformer processes all features in 1 go, regardless of the group settings:

(I've added a logger in the beginning to indicate on which group it's working and it's logging all 3 a few seconds apart, while the CT needs to work a few minutes on group 1 and again a few minutes on group 2 etc).

Am I under the wrong assumption on how the group by should work for the custom transformer? Or am I overlooking something?

Also noticed that I can't assign a attribute anymore to the group by parameter: