hrl change and xlate reconfigure

Johnny,

You only need to re-configure your Xlate if you are changing to a different inbound/outbound record definition; not simply updating the existing layouts being used.  Obviously, if you are adding/deleting fields in the record definition, you would need to update your mappings in your Xlate accordingly.

So, you only need to move the updated record definition.  But, you will need to bounce the process to invoke your change.  Technically, you should be able to simply ‘purge cache’ on the affected process to force a re-load of the Xlate, but I have always found it safer to bounce the process.

Hope this helps.

Jim Cobane

Henry Ford Health

It’s kinda weird.  I can reconfigure and the xlate usually updates.

We received a turnkey xlate which has a unusual oru message with only a few segments.  

When I try to use that variant in an Xlate that already had a variant with more segments defined, the reconfigure just won’t work.

I’ve restarted the process, etc., etc.

By the way, the reason behind the tps with the revised variant …

The idea being to not parse, i.e. pass thru some of the segments.

The concepts works with a tps that parses part of the message then stores the rest as a group into the meta data, retrieving the segments on the outbound.

If you use a TPS to change the records, your variant must match what the TPS is producing.  The variant is used to generate the “tags” that an Xlate uses to perform translation.  If those tags are reconfigured, the variant must change as well.