[Lynda Chen]

It seems that it only sorts for a single SMATDB, but not when you’re using the SMAT Database tool across multiple files.

Does anyone have a workaround/solution for that?

[Lynda Chen]

I have not found the site name to work. Is there a mixture of cases or any special characters added?

[Lynda Chen]

Here are Notes added by R&D on 17 Dec 2014 09:27:41 :

We plan to fix the trailing sep char handling in CIS6.1.1.0, after the fix, engine will remove these trailing sep chars as what it did before.

The current behavior that cloverleaf handles component and subcomponent in tcl is the result of the HL7 subcomponent copy change. As mentioned, after the change, if user uses a component level address in COPY, cloverleaf will get the whole component content (not expand it into list), which is used for COPY source to solve the 5.8 copy issue.

There are 2 workarounds here:

1. Use sub-component level address as source in COPY

2. Split the xlateInVals by sub-component sep char in tcl pre/post proc.

Unfortunately, the new behavior is the base of the fix.

[Lynda Chen]

FYI: Infor has accepted the issue of the trailing sep chars and will try to work on removing them.

Another difference we noticed was:

CL 5.8 engine passes components and subcomponents as a list to tclprocs.

However, with CL 6.1 the engine continues to pass components as lists, but subcomponents as a string to tclprocs.

[Lynda Chen]

We are working on upgrading from CL 5.8.7 to CL 6.1. Found that CL 6.1 is not removing trailing subcomponent separators even when empty.

Thus in CL 5.8

incoming: |Lastname^Firstname^MI^^^MD&&|

outgoing from xlt with a copy: |Lastname^Firstname^MI^^^MD|

in CL 6.1

incoming: |Lastname^Firstname^MI^^^MD&&|

outgoing from xlt with a copy: |Lastname^Firstname^MI^^^MD&&|

[Lynda Chen]

Has Infor responded to this discovery with a fix by the CL 6.1 release?

[Author]

Replies