Applying hl7 message filter to one destination, the filter is applied to the next destination #6165
Answered
by
pacmano1
HassanBosha
asked this question in
Q&A
-
Upon Applying a filter to a destination that is in between many destination the messages are altered (the messages come from source to the destination directly), but when it comes from source to a destination that has a filter, the next destination receives an altered message (filtered from the above destination. |
Beta Was this translation helpful? Give feedback.
Answered by
pacmano1
Apr 16, 2024
Replies: 1 comment 2 replies
-
I highly doubt that. Provide a channel export where you see this behavior. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You are storing messages to $c, you don't have to do that at all. Since you are not transforming msg on the source side, each destiantion can just process "msg".
It looks like you just want to send message to different destinations based on their type, your code should be far more simple.
What is likely happening here is you have queueing enabled and on failure your $c var being converted in the transformer isn't convertable in the same way to HL7 anymore based on how it is stored in the database waiting to be resent.
Remove all queuing on all destinations and see if this happens stil.
Please read the documetattion on
destinationSet.
commands which is better in your use case.