Forum Replies Created
-
AuthorReplies
-
Hello,
I am seeking customers that have upgraded to Cloverleaf 20.1 on AIX platform.
I am asking for feedback on your experience with performance, any issues etc.. on the 20.1 version.
Thank you for your response
January 5, 2015 at 8:13 pm in reply to: 6.1 – comparison method violates its general contract #81628Peter, did you receive a response from Infor Support on this topic ? I encountered the error while saving an xlate after making modifications to tcl code within the xlate. We are currently performing unit testing on 6.1
Tom, We have been on CL 5.8.5 for several months and what you are experiencing with the SMAT files we have discovered as well. As you mentioned, a new SMAT session has to be reopened and file reloaded to get a refresh. Also, if the SMAT file is open and the process is cyled, the SMAT file gets cycle saved. Very annoying for development work for both issues. Another issue we are seeing is the copy / paste feature within an xlate quits working. Closing and reopening the xlate will usually solve but will return. Again very annoying for development work as we are here with Epic go-live fast approaching. I consider these issues that should have been discovered and corrected before release. My 2 cents worth.
Bob, we installed Rev5 last week on AIX5.3. There is an issue discovered with the re-loading of SMAT files. The reload does not refresh the file. Closing SMAT and opening a new SMAT session does refresh. This has been escalated to Lawson development support. No other issues have been discovered. We installed Rev5 to address a hcitpstest issue. See release notes for Rev5. Sorry if I am too late responding but others might be interested.
Jim, our CodeRyte interface is SFTP for file delivery ( using FTP server, not CL) on results and charges. Cloverleaf file-set local threads to create the daily files and ksh scripts to process.
Virginia, for our thread notes, we created html links to a MSWord document We created the link to go directly to a specific bookmark in the document for each thread. Check the “Show as HTML” for my example.
<a href="http://PATH/Support_Document.doc#cerner_res_o”>Support Document
#cerner_res_o represents the bookmark name in Support_Document.doc
Hey Belaid, I was overthinking the solution. Your solution would work. I was tryng to keep the thread creation to only the one new outbound and possibly using a UPOC (Send OK Save for instance) on the test thread to send message to dev thread. Thanks Belaid ! Hello to all for me. 🙂
-
AuthorReplies