Kill message using routes?

[Rick Pritchett]

My problem is that i am sending from one source to many vendors and of course everyone doesnt want everything so i am trying to do a per-vendor filter.  Each vendor will be receiving ADTs and ORM messages on the same port and the filtering is to be done mostly on the OBR segment of the orders with some filtering of the ADTs as well.  Would the best way to do this be a filter placed in the in the Pre-Procs in the xlate details?

Topic

[Rob Abbott]

Yes … if you can determine the filter with minimal parsing it’s best to get rid of the message before it goes into translation.

Another way is to write a trxid determination proc and filter using specialized trxids — but it sounds like this could get complicated and hard to maintain rather quickly in your environment.

Rob Abbott
Cloverleaf Emeritus

[Alan James]

I use the kill_msg.tcl proc extensively.  Suits my needs well, because it’s flexible enough to filter any message you can find a unique datum point to filter on.  I’m attaching a screenshot, and the proc itself.  If the screenshot’s not self-explanatory, feel free to call or email me.

[santiago guzman]

Hello,

I’m on 5.8.2 version, after downloading the file where do I place it so that i can see it in Cloverleaf?

Thanks,

[Russ Ross]

If you are talking about the kill_msg.tcl file that would need to be placed in soemthing like $HCISITEDIR/tclprocs then cd to that directory and run mktclindex.

If you want the TCL proc to be visible to all your sites, then I would put it in the global master site tclprocs directory and mktclindex their.

Russ Ross
RussRoss318@gmail.com

[Author]

Replies