Using Mirth 3.1.1.7461, on windows server 2008 R2.
The source of my channel is a TCP listener using MLLP as the transmission mode.
I have a database writer destination which looks up a record in a database based on a value in the message I received. It then populates the channel map with values from the database record.
Next I have a channel writer destination. It doesn't actually write to another channel, it's just used for the transformer, which is a javascript block:
msg['OBR'][0]['OBR.2'][0]['OBR.2.1'] = $('OV');
msg['OBR'][0]['OBR.2'][0]['OBR.2.2'] = $('Clinic');
It's purpose is to update the message prior to sending the message out to several other destinations (a file writer, and an TCP Sender (MLLP)).
What I found was that the transformed and sent message for that destination reflected the new values, but the transformed and sent message for the subsequent destinations. So my first question is, is that intended behavior? Can I cause it to affect all subsequent destinations?
As a second test, I decided to copy the javascript transformer to all the destinations. I then found that the TCP Sender transformed and sent message had the new values, but not the File Writer. That doesn't seem like intended behavior, or am I doing something wrong here?
The source of my channel is a TCP listener using MLLP as the transmission mode.
I have a database writer destination which looks up a record in a database based on a value in the message I received. It then populates the channel map with values from the database record.
Next I have a channel writer destination. It doesn't actually write to another channel, it's just used for the transformer, which is a javascript block:
msg['OBR'][0]['OBR.2'][0]['OBR.2.1'] = $('OV');
msg['OBR'][0]['OBR.2'][0]['OBR.2.2'] = $('Clinic');
It's purpose is to update the message prior to sending the message out to several other destinations (a file writer, and an TCP Sender (MLLP)).
What I found was that the transformed and sent message for that destination reflected the new values, but the transformed and sent message for the subsequent destinations. So my first question is, is that intended behavior? Can I cause it to affect all subsequent destinations?
As a second test, I decided to copy the javascript transformer to all the destinations. I then found that the TCP Sender transformed and sent message had the new values, but not the File Writer. That doesn't seem like intended behavior, or am I doing something wrong here?
Troubles updating message
0 commentaires:
Enregistrer un commentaire