Hi,
I've just upgraded to Mirth Connect 3.1.1 on our test machine to test before rolling out to production.
Our current production versions are Mirth Connect 2.2.1
I have a number of channels which use a filter to determine the message types to allow through.
I have seen the message that the messageObject.getType() is deprecated and should be replaced by the "mirth_type". this is fine but I cannot any documentation on the syntax for the "mirth_type" variable
See below for the filter code:-
==============================
// this filter will only allow in ADT A01, A04 & A08 messages
logger.info('Message Type = ' + messageObject.getType() );
if (messageObject.getType() == 'ADT-A04' || messageObject.getType() == 'ADT-A08'|| messageObject.getType() == 'ADT-A01' )
return true
else
return false;
================================
Can anyone help with replacing this code with the recommended new way or has anyone done something similar.
Many thanks Robin
I've just upgraded to Mirth Connect 3.1.1 on our test machine to test before rolling out to production.
Our current production versions are Mirth Connect 2.2.1
I have a number of channels which use a filter to determine the message types to allow through.
I have seen the message that the messageObject.getType() is deprecated and should be replaced by the "mirth_type". this is fine but I cannot any documentation on the syntax for the "mirth_type" variable
See below for the filter code:-
==============================
// this filter will only allow in ADT A01, A04 & A08 messages
logger.info('Message Type = ' + messageObject.getType() );
if (messageObject.getType() == 'ADT-A04' || messageObject.getType() == 'ADT-A08'|| messageObject.getType() == 'ADT-A01' )
return true
else
return false;
================================
Can anyone help with replacing this code with the recommended new way or has anyone done something similar.
Many thanks Robin
Replacing messageObject with "mirth_type"
0 commentaires:
Enregistrer un commentaire