<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	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>Siebel Tech Blog</title>
	<atom:link href="http://www.mroshaw.co.uk/OllerenshawIT/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mroshaw.co.uk/OllerenshawIT</link>
	<description>Ollerenshaw IT Ltd - Oracle Siebel CRM Consultants</description>
	<lastBuildDate>Sun, 20 May 2012 12:26:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Messy Workflows</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/messy-workflows/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/messy-workflows/#comments</comments>
		<pubDate>Fri, 18 May 2012 17:59:01 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1303</guid>
		<description><![CDATA[Have you ever come across a Workflow process that looks something like this: There seems to be a popular misconception amongst some developers that Siebel Workflow can only have a single &#8216;End&#8217; instance. Similarly, some developers believe that they can only have one instance of their &#8216;Error Logging&#8217; Business Service step. The result is that [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/messy-workflows/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Siebel MSMQ Component Configuration</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/siebel-msmq-component-configuration/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/siebel-msmq-component-configuration/#comments</comments>
		<pubDate>Thu, 10 May 2012 19:50:29 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Configuration]]></category>
		<category><![CDATA[Integration]]></category>
		<category><![CDATA[MSMQ]]></category>
		<category><![CDATA[Siebel]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1389</guid>
		<description><![CDATA[Today, we&#8217;ll set up the Siebel components necessary for inbound and outbound communication between Siebel and our new MSMQ queues. There are a number of steps that we need to complete: Create a Message Queue profile &#8211; this will tell our &#8216;listener&#8217; component where the inbound queue is. This will contain reference to the MSMQ [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/siebel-msmq-component-configuration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MSMQ &#8211; Private Queues</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/msmq-private-queues/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/msmq-private-queues/#comments</comments>
		<pubDate>Mon, 07 May 2012 09:34:18 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Integration]]></category>
		<category><![CDATA[MSMQ]]></category>
		<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Configuration]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1377</guid>
		<description><![CDATA[The next steps involved in setting up MSMQ with Siebel is to create a couple of private queues &#8211; one for inbound, one for outbound. We can then use Siebel EAI to put messages onto the outbound queue for collection by a third party application and use the MSMQ component and profile to pull messages [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/msmq-private-queues/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Working with Microsoft Message Queuing &#8211; MSMQ</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/working-with-microsoft-message-queuing-msmq/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/working-with-microsoft-message-queuing-msmq/#comments</comments>
		<pubDate>Fri, 04 May 2012 10:50:53 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Integration]]></category>
		<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Configuration]]></category>
		<category><![CDATA[MSMQ]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1357</guid>
		<description><![CDATA[I&#8217;ve been working a lot with MSQM recently, as part of an integration framework allowing communication between a Siebel 8.1 system and a number of external data providers. I thought I&#8217;d share my thoughts and experiences of working with MSMQ in a Siebel environment. First up, installing MSMQ on a local machine is very easy [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/working-with-microsoft-message-queuing-msmq/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Decision, decisions&#8230;</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/decision-decisions/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/decision-decisions/#comments</comments>
		<pubDate>Wed, 02 May 2012 15:56:34 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Configuration]]></category>
		<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1290</guid>
		<description><![CDATA[Another odd piece of configuration cropped up the other day: I can see the developers thinking but the decision step is not limited to two branches. A far neater solution would be: Siebel Workflow can be really powerful but Workflow Processes can become cumbersome and complex very quickly if developers don&#8217;t put some effort into streamlining.]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/05/decision-decisions/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Siebel Code Challenge &#8211; #10</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/siebel-code-challenge-10/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/siebel-code-challenge-10/#comments</comments>
		<pubDate>Sun, 29 Apr 2012 14:05:49 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Code Challenge]]></category>
		<category><![CDATA[eScript]]></category>
		<category><![CDATA[Siebel]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1343</guid>
		<description><![CDATA[UPDATED: Well done Rick for spotting this one! It is considered bad practice to return from a finally block &#8211; the behavior of the code is unpredictable, based on the route the code takes and whether an exception is thrown or not. Here&#8217;s some further reading on the subject. If an exception must be thrown, [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/siebel-code-challenge-10/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
		<item>
		<title>Repository Analyser &#8211; Development Update</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/repository-analyser-dev-update/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/repository-analyser-dev-update/#comments</comments>
		<pubDate>Thu, 26 Apr 2012 21:10:37 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Configuration]]></category>
		<category><![CDATA[eScript]]></category>
		<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Upgrade]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1329</guid>
		<description><![CDATA[When I find a spare moment, I&#8217;ve been working away on my C# Repository Analyser tool. I&#8217;ve re-jigged the UI a little and added a new piece of functionality that can be used as part of your configuration management processes &#8211; Change Log. This process will parse the Siebel Repository, via Siebel Business Objects, and [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/repository-analyser-dev-update/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>Comparing properties in Siebel Workflow</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/comparing-properties-in-siebel-workflow/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/comparing-properties-in-siebel-workflow/#comments</comments>
		<pubDate>Mon, 23 Apr 2012 12:38:55 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Configuration]]></category>
		<category><![CDATA[eScript]]></category>
		<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1275</guid>
		<description><![CDATA[I came across this in a live Workflow the other day: What&#8217;s happening here is that the comparison of two Workflow Process properties is being done in a custom, eScript Business Service. Further digging revealed that the &#8216;Is Num &#62;= Max?&#8217; step invoked the following eScript: function GreaterThanOrEqual(Inputs, Outputs) { var res = &#34;Y&#34;; var [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/comparing-properties-in-siebel-workflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Repository Analyser &#8211; Source Code</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/repository-analyser-source-code/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/repository-analyser-source-code/#comments</comments>
		<pubDate>Wed, 18 Apr 2012 18:08:10 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Utilities]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1263</guid>
		<description><![CDATA[My Repository Analyser tool uses some cool code to connect directly to the Siebel Server object manager instance, via C#. It also does some neat things using the Repository BC&#8217;s which underly Siebel Tools. In the spirit of sharing, I want to make the source code available to you all under the GPL &#8211; you [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/repository-analyser-source-code/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Siebel Code Challenge &#8211; #9</title>
		<link>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/siebel-code-challenge-9/</link>
		<comments>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/siebel-code-challenge-9/#comments</comments>
		<pubDate>Thu, 12 Apr 2012 21:30:29 +0000</pubDate>
		<dc:creator>Oli</dc:creator>
				<category><![CDATA[Code Challenge]]></category>
		<category><![CDATA[Configuration]]></category>
		<category><![CDATA[Siebel]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://www.mroshaw.co.uk/OllerenshawIT/?p=1249</guid>
		<description><![CDATA[UPDATED: Thanks to Rick for spotting this one! The Today() function returns today&#8217;s date without a time component. As there is specialised class validation functionality all over the Action BC, the Workflow will fail if the planned start date is any time today &#8211; regardless if it&#8217;s before the current time or not. Using the Timestamp() [...]]]></description>
		<wfw:commentRss>http://www.mroshaw.co.uk/OllerenshawIT/index.php/2012/04/siebel-code-challenge-9/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
	</channel>
</rss>

