I guess the traditional form would be RouteToLabel followed by ResetContentDescriptor.
Otherwise, one could do it all in a single compute node with Create Field..Parse... and Propagate...To Label. _________________ I am *not* the model of the modern major general.
You have several options:
- Jeff's suggestions are good.
- Or make the sending application put an RFH2 header on the input message.
- Do all the messages have a common header structure which contains an identifying field ? If so, you could use multipart messages.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum