@david-barr
Forum Replies Created
-
AuthorReplies
-
I’d keep troubleshooting. I don’t think HTTPS is the answer.
I don’t think we have any HTTPS connections from Cloverleaf to Epic. We do have HL7 connections from Cloverleaf to HL7 listeners in Interconnect. Those are sometimes tricky to troubleshoot. You have to set up routing tables and point to them with the IC_IN_TABLE in system defaults. We have multiple levels of routing. The first table routes on message type and it points to other tables that route on either sending application or sending facility.
How are you calling the TCL proc?
That sounds very tricky. Normally that’s done with two pairs of threads: order_ib -> order_ob, result_ib -> result_ob. I wouldn’t recommend your pattern. Acknowledgements are going to be going over these interfaces as well, and it seems like they’re going to get mixed up with the messages.
You can also add “-c” to your hcidbdump command if you want to see TCL errors.
February 25, 2026 at 2:52 pm in reply to: Best practices for Cloverleaf interface support tools #122310Is there a document with release notes for 2025.01? I found the release report which is an Excel document. Is there anything more readable? The spreadsheet doesn’t make it easy to find release highlights; you have to wade through descriptions of minor bug fixes, etc.
If you run the IDE from Linux, the shell button opens up an Xterm window. If you’re using MobaXterm or other software that tunnels you GUI traffic over SSH, then it should be secure.
We’re on Rackspace for our servers, so Cloverleaf is sort of running in a cloud, but not the Infor cloud.
David Barr (david_barr@valleymed.org)
February 9, 2026 at 10:32 am in reply to: How to escape the ampersand (&) character in an Xlate #122274You can use \T\.
October 8, 2025 at 6:20 pm in reply to: Trying to replace an entire message with msgset, still only sending old message #122193You could always add a “msgdump $mh” command in your script for more debugging information. It should add messages to the process log to show you if the message has been modified, and if the msgdump output isn’t showing up it would indicate a problem getting your interface to run the script (not applied in the GUI or process not restarted).
October 7, 2025 at 5:07 pm in reply to: Trying to replace an entire message with msgset, still only sending old message #122186The code looks fine to me, and if the testing tool says that it works, then your actual interface is probably still running the old code. I think you can “reload procedure” through the gui to apply your change, but I always just restart the process where the proc is getting run.
If you’re just decoding the base64 data and not passing it anywhere you may not need to remove the linefeeds. The decode will ignore them, and they shouldn’t affect your field lookups since they are using \r and | as delimiters. If you do want to remove the linefeeds, I think you could do something like this:
<pre>set msg [msgget $mh]
set msg [string map { \n “” } $msg]
set ctr_val [msgmetaget $mh “USERDATA”]
set segmentList [split $msg \r]</pre>Do you have an example message? Is the line feed part of the encoded characters, or is it after? Is Cloverleaf decoding the base64 or is it being passed to another system? This should be easy to do in TCL.
In my experience there are very few tutorials for any Cloverleaf usage outside of official Infor training. There is online documentation for the Python API, and at least one example that is installed with the Cloverleaf. I don’t know how much the official training classes would cover Python. The Python API seems very similar to the Java API, so it’s possible that you could infer additional information from the Java documentation and examples.
I think you just put the site folders under version control. That’s pretty much what we did. What questions do you have?
If you’re using SVN, you would set up an SVN server then run “svn add” in each of your site folders.
-
AuthorReplies
