<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Clovertech | Lynda Chen | Activity</title>
	<link>https://clovertech.infor.com/members/lynda-chen/activity/</link>
	<atom:link href="https://clovertech.infor.com/members/lynda-chen/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for Lynda Chen.</description>
	<lastBuildDate>Wed, 08 Apr 2026 20:21:38 -0400</lastBuildDate>
	<generator>https://buddypress.org/?v=</generator>
	<language>en-US</language>
	<ttl>30</ttl>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>2</sy:updateFrequency>
	
						<item>
				<guid isPermaLink="false">e036203295b51833a345eca0fe7139ef</guid>
				<title>Lynda Chen replied to the topic SMATDB Message Order in 19.1.1 in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/smatdb-message-order-in-19-1-1/#post-118249</link>
				<pubDate>Thu, 26 Nov 2020 00:31:23 -0500</pubDate>

									<content:encoded><![CDATA[<p>It seems that it only sorts for a single SMATDB, but not when you&#8217;re using the SMAT Database tool across multiple files.</p>
<p>Does anyone have a workaround/solution for that?</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">ca4b2153b1d3cf029bbda4e4a7c77724</guid>
				<title>Lynda Chen replied to the topic smat db enryption default key v19.1.1 in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/smat-db-enryption-default-key-v19-1-1/#post-118140</link>
				<pubDate>Tue, 27 Oct 2020 23:05:21 -0400</pubDate>

									<content:encoded><![CDATA[<p>I have not found the site name to work. Is there a mixture of cases or any special characters added?</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">e2517fb628eb43cd89a5ef652e209132</guid>
				<title>Lynda Chen started the topic AIX to Linux Migration Inquiry in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/aix-to-linux-migration-inquiry/</link>
				<pubDate>Mon, 09 Mar 2020 15:04:04 -0400</pubDate>

									<content:encoded><![CDATA[<p>Hi,</p>
<p>Has anyone run into any issues/surprises using CL 6.1.2 on Redhat 7.5?</p>
<p>Currently, we are running CL 6.1.2 on AIX.</p>
<p>We are planning our migration path in stages to minimize risk. Our plan is to eventually move to CL 19.1.x on Linux before the end of the year.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">b4403516a600f614e9ac45872650ce62</guid>
				<title>Lynda Chen replied to the topic CL 6.0: subcomponent reference issue in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/cl-6-0-subcomponent-reference-issue/#post-79023</link>
				<pubDate>Fri, 19 Dec 2014 00:48:31 -0500</pubDate>

									<content:encoded><![CDATA[<p>Here are Notes added by R&amp;D on 17 Dec 2014 09:27:41 :</p>
<p>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.</p>
<p>The current behavior that cloverleaf handles component and subcomponent in tcl is the result of the HL7 subcomponent copy change. As mentioned, after&hellip;<span class="activity-read-more" id="activity-read-more-13981"><a href="https://usspvlclovertch2.infor.com/forums/topic/cl-6-0-subcomponent-reference-issue/#post-79023" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">7295095b3d341381553a8529a2ff2c5d</guid>
				<title>Lynda Chen replied to the topic CL 6.0: subcomponent reference issue in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/cl-6-0-subcomponent-reference-issue/#post-79020</link>
				<pubDate>Wed, 10 Dec 2014 17:55:16 -0500</pubDate>

									<content:encoded><![CDATA[<p>FYI: Infor has accepted the issue of the trailing sep chars and will try to work on removing them.</p>
<p>Another difference we noticed was:</p>
<p>CL 5.8 engine passes components and subcomponents as a list to tclprocs.</p>
<p>However, with CL 6.1 the engine continues to pass components as lists, but subcomponents as a string to tclprocs.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">095429822186c47e96c6da4516319c4e</guid>
				<title>Lynda Chen replied to the topic CL 6.0: subcomponent reference issue in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/cl-6-0-subcomponent-reference-issue/#post-79016</link>
				<pubDate>Tue, 09 Dec 2014 16:02:52 -0500</pubDate>

									<content:encoded><![CDATA[<p>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. </p>
<p>Thus in CL 5.8</p>
<p>incoming: |Lastname^Firstname^MI^^^MD&amp;&amp;|<br />
outgoing from xlt with a copy: |Lastname^Firstname^MI^^^MD|</p>
<p>in CL 6.1</p>
<p>incoming: |Lastname^Firstname^MI^^^MD&amp;&amp;|<br />
outgoing from xlt with a copy:&hellip;<span class="activity-read-more" id="activity-read-more-12557"><a href="https://usspvlclovertch2.infor.com/forums/topic/cl-6-0-subcomponent-reference-issue/#post-79016" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">a1027357a08ce719c0f714eb61f7a59e</guid>
				<title>Lynda Chen replied to the topic CL 6.0: subcomponent reference issue in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/cl-6-0-subcomponent-reference-issue/#post-79013</link>
				<pubDate>Mon, 08 Dec 2014 23:46:44 -0500</pubDate>

									<content:encoded><![CDATA[<p>Has Infor responded to this discovery with a fix by the CL 6.1 release?</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>