[Chris Adams]

Hah it’s funny, I came to Clovertech this morning to ask the same thing!  I wish I had something helpful to add, but we are trying to connect to the State of MO for reportable results sent over via HTTPS using Cloverleaf.  From what I’ve been able to learn, CAA-WS is the way to go, but I’m not having much luck finding any information on CAA-WS.  Does this require any additional licencing on Cloverleaf 5.8.5 or should we be good to go?

The funny part is I have this connection working from Epic -> Interconnect -> State, but per Epic’s advice we are being told if we can use Cloverleaf instead of Interconnect for this connection, we should, due to the limitations of Interconnect.  Awesome..

So add me into the hat of needing CAA-WS information!

[Chris Adams]

Hey all!

I’ll certainly take a look at any code you have available!  Given where this is failing (on the UUDECODE line) I have a feeling it’s not an issue in the TCL at this point, since the UUDECODE pretty much has to be done with the UUENCODE:UUDECODE line, but examples are always good!

It almost feels like we are hitting some environmental issue, but I have no idea where else to check at this point!

Thanks!

[Chris Adams]

Hey all,

Thanks for the replies!  I’m trying to come up with a decent way to test this- the trick I’m having currently is I can’t just mock up a string to a certain size, it would fail the uudecode.

I’m going to try and mock up some uuencoded messages when I get some free time to mess around.

My other thought on this would be to have our pre-xlate proc call to a specific UUENCODE execuable instead of using the uuencode.tcl functionality, but I’m still brainstorming this.

Another thought actually would be trying to replace the uuencode.tcl with a more updated verison- just ideas I have floating in my head that I haven’t been able to test yet.

[Author]

Replies