Announcement

Collapse
No announcement yet.

Can one transformer apply to all message types?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Can one transformer apply to all message types?

    I currently have a channel set up to recieve any message sent to it (no filters). I created the mappings I needed to work with ADT messages. I now need to move to the next step and handle SIU messages.

    I see that the SIU messages and ADT messages both have a PID segment, which I need information from for either message. When the channel gets an ADT message its fine, but when it gets an SIU message it doesnt get any data from the SIU PID segment.

    Is there some way to make the PID segment mappings apply to all message types?
    Jon Bartels

    Zen is hiring!!!!
    http://consultzen.com/careers/
    Talented healthcare IT professionals wanted. Engineers to sales to management.
    Good benefits, great working environment, genuinely interesting work.

  • #2
    Re: Can one transformer apply to all message types?

    Change the parser type (incoming/outgoing data tab on the transformer - uncheck "Use strict parser"). You will need to change your mappings, but you can do something like:

    for (pid in msg..['PID']){

    }

    Now that I think of it - you might be able to do this with the strict parser as well. The for (pid in msg..XXX) will find XXX in any part of the XML.

    -Chris
    Chris Lang

    Comment


    • #3
      Re: Can one transformer apply to all message types?

      The difference in syntax is like this:

      Strict: msg['PID']['PID.5']['XPN.2'].toString()

      Not-Strict: msg['PID']['PID.5']['PID.5.2'].toString()
      Jon Bartels

      Zen is hiring!!!!
      http://consultzen.com/careers/
      Talented healthcare IT professionals wanted. Engineers to sales to management.
      Good benefits, great working environment, genuinely interesting work.

      Comment

      Working...
      X