Partly because I’m far more knowledgeable with TCL than Xlates; my last site was 100% TCL and this new one is 100% Xlate. And partly because Infor had recommended it due to Xlates being a little more top-heavy with resources. We’ve had issues where some of the heavy-traffic interfaces with Xlate filtering would spike to 100% CPU usage and choke out our entire prod server. We’ve already taken steps to fix that. Not everything can be converted due to the complexity. And things get even more complex when field length limitations impact the data. Like Pt Type comes out of our EMR is 6 characters but the output format has 2 characters allowed for that field.
