echo to process log from Xlate

Troy,

I have a reusable xltp proc that does nothing but echo out what is in the XlateIn… lists (if a switch is set on).

I use that to assist in debugging complex iterations and ifs.

If you would like a copy email me.

puts $xlateInVals

puts $xlateOutVals

They will show in the process log.

Maybe in 5.9  8)

When I want to do just Tcl code in Xlate, e.g. init a variable, echo, etc.  I simply:

COPY @null => @null

It is also somewhat self documenting as it is obviously a no op

Folks,

Another very useful debugging tool in an Xlate for CIS5.6 anyway

is the “deactivate/activate” logic feature.  Essentially, the actions are “Rem’d” or commented out.  (Look for REM in the Xlate file).

This allows you to turn off logic and turn it back on again.

Really helpful to find offending IF actions that fetch multiple values usually from applications that plug in ampersands (&) as data in an HL7 Version 2 message.

Not upgrading to 5.7? 🙂

Troy, we are moving to 5.7 from 5.6 in a few weeks.

Also, you should have a couple of scripts that you, Jamin, and I wrote years ago called xlt_echo and xlt_puts. And of course a simple tcl fragment works like ‘puts @tmp’. With the tcl frag, you don’t even need anything at all in the inbound or outbound fields. We used the scripts so that the output would be consistant ang grep’able (“DEBUG: ….”).