No announcement yet.

Destination set filtering and reprocessing

  • Filter
  • Time
  • Show
Clear All
new posts

  • Destination set filtering and reprocessing

    Hello. I have a question about the interaction between destination set filtering, the reprocessing options, and destination filters.

    I'm thinking of replacing destination filters with 'destinationSet' filtering in the source transformer of a channel, but I am worried about what happens should I wish to reprocess messages.

    Say I have a destination that is currently filtering certain types of ADT message, but I move this logic into the source transformer and use destinationSet, removing the destination filters. Then I need to reprocess a batch of messages, but only for this destination. Should I expect that if I did a basic search for a day worth of messages (all ADT types) and reprocess and select only the intended destination in the options box, that I will still only sent the ADT types that I intended to this destination? I'm asking at what stage the logic is applied - is the filter option using destinationSet and which will take precedence - the source transformer or the reprocess options?

  • #2
    The destinations you select in the reprocess dialog comprise the initial destination set. And then in the source transformer you can further prune the set down. It's always taking away from the destination set, never adding.

    So if you have destinations 1-3, and on reprocess you only select destination 1, but in the source transformer you do "remove all except destination 3", then none of the destinations will be executed.
    Step 1: JAVA CACHE...DID YOU CLEAR ...wait, ding dong the witch is dead?

    Nicholas Rupley
    Work: 949-237-6069
    Always include what Mirth Connect version you're working with. Also include (if applicable) the code you're using and full stacktraces for errors (use CODE tags). Posting your entire channel is helpful as well; make sure to scrub any PHI/passwords first.

    - How do I foo?
    - You just bar.