<?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 | Walter Beatty | Activity</title>
	<link>https://clovertech.infor.com/members/wbeattyjr/activity/</link>
	<atom:link href="https://clovertech.infor.com/members/wbeattyjr/activity/feed/" rel="self" type="application/rss+xml" />
	<description>Activity feed for Walter Beatty.</description>
	<lastBuildDate>Tue, 14 Apr 2026 23:12:53 -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">205a4b110f15142cc066979699506a98</guid>
				<title>Walter Beatty started the topic one OBX in source to multiple OBX in destination in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/one-obx-in-source-to-multiple-obx-in-destination/</link>
				<pubDate>Mon, 15 Aug 2022 14:10:19 -0400</pubDate>

									<content:encoded><![CDATA[<p>I am trying to pull several fields from one source OBX segment and create multiple OBX segments into the destination</p>
<p>Example.  I am trying to pull OBX-21 OBX-22 and OBX-23 from source and in destination I need an individual OBX for each of those data fields.</p>
<p>I am still sort of new to Cloverleaf so not sure if this can be done in xlt.</p>
<p>Has&hellip;<span class="activity-read-more" id="activity-read-more-24721"><a href="https://usspvlclovertch2.infor.com/forums/topic/one-obx-in-source-to-multiple-obx-in-destination/" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">9b855292bd60df204b6949aec0c8e192</guid>
				<title>Walter Beatty replied to the topic TCP connection using SSL configuration in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/tcp-connection-using-ssl-configuration/#post-119841</link>
				<pubDate>Thu, 30 Jun 2022 12:58:38 -0400</pubDate>

									<content:encoded><![CDATA[<p>Thanks Mike &#8211; I did have to convert to PEM format but was trying to do so from Windows cert manager and since I did not have a private key from the vendor cert I was not able to generate a key in PEM format from Windows.  I had to use Portecle to do that.  I was able to get it to work after doing that.</p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">5825627b8ea991f33c77d324fe60356d</guid>
				<title>Walter Beatty started the topic TCP connection using SSL configuration in the forum Cloverleaf</title>
				<link>https://usspvlclovertch2.infor.com/forums/topic/tcp-connection-using-ssl-configuration/</link>
				<pubDate>Tue, 21 Jun 2022 12:42:37 -0400</pubDate>

									<content:encoded><![CDATA[<p>I am somewhat new to Cloverleaf and all of our organizations existing interfaces with outside vendors are all configured using a VPN.  We are trying to configure an interface using SSL.  I was provided the certs (.pfx files) from the vendor and no private key needed.  I have imported these certs into the trusted root cert authority on the cl&hellip;<span class="activity-read-more" id="activity-read-more-24615"><a href="https://usspvlclovertch2.infor.com/forums/topic/tcp-connection-using-ssl-configuration/" rel="nofollow ugc">Read more</a></span></p>
]]></content:encoded>
				
									<slash:comments>0</slash:comments>
				
							</item>
					<item>
				<guid isPermaLink="false">42ef8ed4cae295efc9b6f15826dfa573</guid>
				<title>Walter Beatty became a registered member</title>
				<link>https://clovertech.infor.com/activity/p/24602/</link>
				<pubDate>Thu, 16 Jun 2022 11:51:36 -0400</pubDate>

				
									<slash:comments>0</slash:comments>
				
							</item>
		
	</channel>
</rss>