<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: SharePoint Workflow and when to use it&#8230;</title>
	<atom:link href="http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/feed" rel="self" type="application/rss+xml" />
	<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/</link>
	<description>Whatever Andy Burns is working on...</description>
	<pubDate>Sat, 22 Nov 2008 10:44:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Priyanka</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-3056</link>
		<dc:creator>Priyanka</dc:creator>
		<pubDate>Tue, 14 Oct 2008 10:58:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-3056</guid>
		<description>Andy,

I have created a workflow on a document library. This workflow creates several tasks inside a replicator activity. Now I have another workflow on the task list, that has to start off when a new task gets added to the task list. The 1st workflow works fine, the tasks get created (by default on the "Workflow Task" content type). But the problem is with the second workflow. It simply doesn't start off at all. I thought maybe this has to do something with replicator, so had a simple workflow with a single create task. But even then my second workflow doesn't start off. I am hopelessly trying out why the workflow does not get initiated at all.

Please can you help.

Thanks</description>
		<content:encoded><![CDATA[<p>Andy,</p>
<p>I have created a workflow on a document library. This workflow creates several tasks inside a replicator activity. Now I have another workflow on the task list, that has to start off when a new task gets added to the task list. The 1st workflow works fine, the tasks get created (by default on the &#8220;Workflow Task&#8221; content type). But the problem is with the second workflow. It simply doesn&#8217;t start off at all. I thought maybe this has to do something with replicator, so had a simple workflow with a single create task. But even then my second workflow doesn&#8217;t start off. I am hopelessly trying out why the workflow does not get initiated at all.</p>
<p>Please can you help.</p>
<p>Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-3036</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Tue, 07 Oct 2008 14:48:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-3036</guid>
		<description>Hmm. You're using SharePoint Designer? I don't have a whole lot of experience building workflows in that, and the problem you've had isn't one I've come across (in fact, I'm not sure I've ever sent emails from a SharePoint Designer workflow).

I guess one question is is the 'Current Item' the same item both times? I.e., is this an email reminder for another task step which has been created in the same way?</description>
		<content:encoded><![CDATA[<p>Hmm. You&#8217;re using SharePoint Designer? I don&#8217;t have a whole lot of experience building workflows in that, and the problem you&#8217;ve had isn&#8217;t one I&#8217;ve come across (in fact, I&#8217;m not sure I&#8217;ve ever sent emails from a SharePoint Designer workflow).</p>
<p>I guess one question is is the &#8216;Current Item&#8217; the same item both times? I.e., is this an email reminder for another task step which has been created in the same way?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alicia</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-3022</link>
		<dc:creator>Alicia</dc:creator>
		<pubDate>Thu, 02 Oct 2008 19:14:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-3022</guid>
		<description>Andy,
I've made a bit of progress building a custom workflow in sharepoint designer 2007 and have even gotten some guidance from our IT folks! However, I'm stuck on kind of a weird thing:

I've started creating a workflow attached to a task list. The first step includes an action to send an email message to the "assigned to" for a task. I've created a workflow lookup to look up the information in the "assigned to" column and send an email reminder--this step works. 

When I created this step (Email this message), I clicked on "this message" and it brings up "define email message". 
In the "to" line, I clicked the "addressbook" icon 
In the "select users" box, I clicked "workflow lookup..."
In "define workflow lookup" I selected "current item" as the source, and "assigned to" as the field
The action looked like this: Email test:Assigned To ("test" is the name of the task list)

I created subsequent email reminder steps and saved the workflow (it indicated no errors). 

When I reopened the workflow later and wanted to create another email reminder action, I followed the same steps, but when I got to "define workflow lookup" and selected "current item" as the source, when I went to select "assigned to" for the field, it is not there among the options that can be selected. 

Do you have any idea why this would happen?? I even tried creating an entirely new workflow attached to the same list ("test") but the same thing happens...
 
HELP!</description>
		<content:encoded><![CDATA[<p>Andy,<br />
I&#8217;ve made a bit of progress building a custom workflow in sharepoint designer 2007 and have even gotten some guidance from our IT folks! However, I&#8217;m stuck on kind of a weird thing:</p>
<p>I&#8217;ve started creating a workflow attached to a task list. The first step includes an action to send an email message to the &#8220;assigned to&#8221; for a task. I&#8217;ve created a workflow lookup to look up the information in the &#8220;assigned to&#8221; column and send an email reminder&#8211;this step works. </p>
<p>When I created this step (Email this message), I clicked on &#8220;this message&#8221; and it brings up &#8220;define email message&#8221;.<br />
In the &#8220;to&#8221; line, I clicked the &#8220;addressbook&#8221; icon<br />
In the &#8220;select users&#8221; box, I clicked &#8220;workflow lookup&#8230;&#8221;<br />
In &#8220;define workflow lookup&#8221; I selected &#8220;current item&#8221; as the source, and &#8220;assigned to&#8221; as the field<br />
The action looked like this: Email test:Assigned To (&#8221;test&#8221; is the name of the task list)</p>
<p>I created subsequent email reminder steps and saved the workflow (it indicated no errors). </p>
<p>When I reopened the workflow later and wanted to create another email reminder action, I followed the same steps, but when I got to &#8220;define workflow lookup&#8221; and selected &#8220;current item&#8221; as the source, when I went to select &#8220;assigned to&#8221; for the field, it is not there among the options that can be selected. </p>
<p>Do you have any idea why this would happen?? I even tried creating an entirely new workflow attached to the same list (&#8221;test&#8221;) but the same thing happens&#8230;</p>
<p>HELP!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-2992</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 15 Sep 2008 16:01:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-2992</guid>
		<description>Hmm. I've gotta admit, I don't know - my experience with the out-of-box workflows is pretty limited! I tend to be more on the 'writing custom workflows' end of things (unless I can avoid it!)

I'll take a look and get back to you. 

Oh, and for what it's worth, I am a developer and I feel that SharePoint workflows are beyond me sometimes (Damn InfoPath!)</description>
		<content:encoded><![CDATA[<p>Hmm. I&#8217;ve gotta admit, I don&#8217;t know - my experience with the out-of-box workflows is pretty limited! I tend to be more on the &#8216;writing custom workflows&#8217; end of things (unless I can avoid it!)</p>
<p>I&#8217;ll take a look and get back to you. </p>
<p>Oh, and for what it&#8217;s worth, I am a developer and I feel that SharePoint workflows are beyond me sometimes (Damn InfoPath!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alicia</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-2988</link>
		<dc:creator>Alicia</dc:creator>
		<pubDate>Thu, 11 Sep 2008 16:09:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-2988</guid>
		<description>Andy,
Thanks so much. Yes, we do have a great IT team, however, they are understaffed and underfunded at the moment, AND none of them have experience with workflows. I thought I'd try to figure it out on my own if I could. BUT--not being a developer myself, it is proving to be a little beyond me. 

Could you answer the question about whether or not the workflow initiation notices that appear in the 3-state workflow can be sent to another list or location in sharepoint so that they do not "clutter up" the task list with additional information? We would still want to know if the workflow stages have been initiated, and what the progress is, we just don't want them in the task list along with hundreds of tasks!! This is something we really want to know, because if you can't, we may not want to use a workflow at all and just use "alerts" by manually changing the status.
Thanks, again!</description>
		<content:encoded><![CDATA[<p>Andy,<br />
Thanks so much. Yes, we do have a great IT team, however, they are understaffed and underfunded at the moment, AND none of them have experience with workflows. I thought I&#8217;d try to figure it out on my own if I could. BUT&#8211;not being a developer myself, it is proving to be a little beyond me. </p>
<p>Could you answer the question about whether or not the workflow initiation notices that appear in the 3-state workflow can be sent to another list or location in sharepoint so that they do not &#8220;clutter up&#8221; the task list with additional information? We would still want to know if the workflow stages have been initiated, and what the progress is, we just don&#8217;t want them in the task list along with hundreds of tasks!! This is something we really want to know, because if you can&#8217;t, we may not want to use a workflow at all and just use &#8220;alerts&#8221; by manually changing the status.<br />
Thanks, again!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-2987</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 11 Sep 2008 13:55:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-2987</guid>
		<description>Hmm. What you really need is a full engagement with someone like the consultancy I work for, or for another professional services organisation. 

There are a number of options for what you want, and we've implemented similar, bespoke solutions, but as you've identified, out-of-the-box SharePoint doesn't do what you're asking for.

An "escalation" workflow is just the generic business term for the process you're trying to implement. It's not related to SharePoint or the technology side of things. I don't think SharePoint comes with an "escalation" workflow in the same way as it comes with a "three-stage approval" workflow.

What you're looking to build probably requires Visual Studio, although I'm no expert with SharePoint designer - it may be possible that way. However, even building workflows in SharePoint designer quite a steep learning curve anyway.

All of which leads me back to my original thought - you really want to engage with a specialist third party, or start training up to do it yourself - and workflow is a bit painful.

I'm afraid (being one of them), I'm not quite sure how you set about finding a professional services group. If you have a local SharePoint User Group, it might be worth asking there - there are also usually a lot of freelance consultants who I'm sure would offer their services.  Here in the UK our local group is http://suguk.org/

Or, actually, looking at your email address, would you have an internal IT team who might be able to assist? If you guys don't have a strong IT team, nobody does!</description>
		<content:encoded><![CDATA[<p>Hmm. What you really need is a full engagement with someone like the consultancy I work for, or for another professional services organisation. </p>
<p>There are a number of options for what you want, and we&#8217;ve implemented similar, bespoke solutions, but as you&#8217;ve identified, out-of-the-box SharePoint doesn&#8217;t do what you&#8217;re asking for.</p>
<p>An &#8220;escalation&#8221; workflow is just the generic business term for the process you&#8217;re trying to implement. It&#8217;s not related to SharePoint or the technology side of things. I don&#8217;t think SharePoint comes with an &#8220;escalation&#8221; workflow in the same way as it comes with a &#8220;three-stage approval&#8221; workflow.</p>
<p>What you&#8217;re looking to build probably requires Visual Studio, although I&#8217;m no expert with SharePoint designer - it may be possible that way. However, even building workflows in SharePoint designer quite a steep learning curve anyway.</p>
<p>All of which leads me back to my original thought - you really want to engage with a specialist third party, or start training up to do it yourself - and workflow is a bit painful.</p>
<p>I&#8217;m afraid (being one of them), I&#8217;m not quite sure how you set about finding a professional services group. If you have a local SharePoint User Group, it might be worth asking there - there are also usually a lot of freelance consultants who I&#8217;m sure would offer their services.  Here in the UK our local group is <a href="http://suguk.org/" rel="nofollow">http://suguk.org/</a></p>
<p>Or, actually, looking at your email address, would you have an internal IT team who might be able to assist? If you guys don&#8217;t have a strong IT team, nobody does!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alicia</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-2986</link>
		<dc:creator>Alicia</dc:creator>
		<pubDate>Wed, 10 Sep 2008 17:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-2986</guid>
		<description>Andy,
I have created a task list in Sharepoint 3.0 to manage a large number of action items (100) for my office. I'm not a programmer or a developer. Now I want to create a custom workflow to send reminders periodically BEFORE an action is due and also periodically AFTER the items are OVERDUE. The 3-state workflow that comes with Sharepoint does NOT meet our needs at all. I was told that the type of workflow I need is called an "escalation" workflow--is that correct? Can this be done using Sharepoint Designer? I do not have Visual Studio. I have never used Designer nor have I had any training yet. I have used Sharepoint for a couple of years.

Other questions:
- We do not want our task list populated with any workflow progress items ("workflow initiated", etc.) Is there a way to have those go somewhere else? a different list? a different view?
- Does sharepoint know when to start each stage of a workflow automatically once you set up the workflow, or will we have to manually change the status of an action item to initiate each stage (open, reminder, overdue...)?

What we would like the workflow to do is:
- at the halfway point between the date the action was assigned and the due date, generate the first email reminder automatically to the "assignee". 
- auto-generate the 2nd reminder approx. one week before due date
- auto-generate 1st Overdue reminder the day after the due date passes
- auto-generate 2nd Overdue reminder 2 weeks later
- auto-generate subsequent Overdue reminders every 2-3 weeks until the action is closed.

I would greatly appreciate any help/advice you can give me.</description>
		<content:encoded><![CDATA[<p>Andy,<br />
I have created a task list in Sharepoint 3.0 to manage a large number of action items (100) for my office. I&#8217;m not a programmer or a developer. Now I want to create a custom workflow to send reminders periodically BEFORE an action is due and also periodically AFTER the items are OVERDUE. The 3-state workflow that comes with Sharepoint does NOT meet our needs at all. I was told that the type of workflow I need is called an &#8220;escalation&#8221; workflow&#8211;is that correct? Can this be done using Sharepoint Designer? I do not have Visual Studio. I have never used Designer nor have I had any training yet. I have used Sharepoint for a couple of years.</p>
<p>Other questions:<br />
- We do not want our task list populated with any workflow progress items (&#8221;workflow initiated&#8221;, etc.) Is there a way to have those go somewhere else? a different list? a different view?<br />
- Does sharepoint know when to start each stage of a workflow automatically once you set up the workflow, or will we have to manually change the status of an action item to initiate each stage (open, reminder, overdue&#8230;)?</p>
<p>What we would like the workflow to do is:<br />
- at the halfway point between the date the action was assigned and the due date, generate the first email reminder automatically to the &#8220;assignee&#8221;.<br />
- auto-generate the 2nd reminder approx. one week before due date<br />
- auto-generate 1st Overdue reminder the day after the due date passes<br />
- auto-generate 2nd Overdue reminder 2 weeks later<br />
- auto-generate subsequent Overdue reminders every 2-3 weeks until the action is closed.</p>
<p>I would greatly appreciate any help/advice you can give me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: areej</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1644</link>
		<dc:creator>areej</dc:creator>
		<pubDate>Thu, 15 May 2008 17:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1644</guid>
		<description>Thanks a lot for your quick responses,

i will try your idea using events ... it seems it can be done in this way. 

thanks so much for your great post, you saved me a lot of time</description>
		<content:encoded><![CDATA[<p>Thanks a lot for your quick responses,</p>
<p>i will try your idea using events &#8230; it seems it can be done in this way. </p>
<p>thanks so much for your great post, you saved me a lot of time</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1640</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 15 May 2008 10:58:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1640</guid>
		<description>Don't really know, you'll have to take a look around. As I say, K2 BlackPearl and Nintex both allow workflows to control site lifecycle, that's where I'd start looking. I suspect that the main problem will be the cost, if it isn't budgetted for.


Otherwise, if you're stuck with SharePoint only, you could do something like:

- Have a ListItem with a URL field. 
- When the ListItem is created, capture that event and create a folder in a document library somewhere.
- Store the URL to the folder in the URL field
- Attach your workflow to your ListItem

I've not tried that, but it might be worth a go at prototyping.</description>
		<content:encoded><![CDATA[<p>Don&#8217;t really know, you&#8217;ll have to take a look around. As I say, K2 BlackPearl and Nintex both allow workflows to control site lifecycle, that&#8217;s where I&#8217;d start looking. I suspect that the main problem will be the cost, if it isn&#8217;t budgetted for.</p>
<p>Otherwise, if you&#8217;re stuck with SharePoint only, you could do something like:</p>
<p>- Have a ListItem with a URL field.<br />
- When the ListItem is created, capture that event and create a folder in a document library somewhere.<br />
- Store the URL to the folder in the URL field<br />
- Attach your workflow to your ListItem</p>
<p>I&#8217;ve not tried that, but it might be worth a go at prototyping.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: areej</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1631</link>
		<dc:creator>areej</dc:creator>
		<pubDate>Wed, 14 May 2008 17:55:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1631</guid>
		<description>Yup exactly, a workflow has to belong a single item in a list or a single document in a document library ...

so what other third party products can give me such option?

Thanks a lot for all your help and support and feedback ... I am really lost here and this functionality is a must :(</description>
		<content:encoded><![CDATA[<p>Yup exactly, a workflow has to belong a single item in a list or a single document in a document library &#8230;</p>
<p>so what other third party products can give me such option?</p>
<p>Thanks a lot for all your help and support and feedback &#8230; I am really lost here and this functionality is a must <img src='http://www.novolocus.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1623</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Wed, 14 May 2008 12:12:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1623</guid>
		<description>Hmm. As I said, then you probably want a container for your documents, and your process to control that container. Something like a Document Workspace would be appropriate. To control creation/deletion/lifecycle of that site, though,would require a third party product of some kind.

You can't have many documents 'sharing' a workflow in SharePoint's Workflow functionality. A workflow has to belong to a single item.</description>
		<content:encoded><![CDATA[<p>Hmm. As I said, then you probably want a container for your documents, and your process to control that container. Something like a Document Workspace would be appropriate. To control creation/deletion/lifecycle of that site, though,would require a third party product of some kind.</p>
<p>You can&#8217;t have many documents &#8217;sharing&#8217; a workflow in SharePoint&#8217;s Workflow functionality. A workflow has to belong to a single item.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: areej</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1622</link>
		<dc:creator>areej</dc:creator>
		<pubDate>Wed, 14 May 2008 09:37:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1622</guid>
		<description>Thanks Andy for your reply,

I am not sure if i understand what you mean...

well ...this is my case:-

we have a business entity (peice of information) that consists of multiple documents. we want to create an approval workflow for this type of information without approving each document separately.

it is like having "attachemnet" workflows. where multiple documents are attached to the workflow instance. 

 
is this possible?

thanks alot in advance</description>
		<content:encoded><![CDATA[<p>Thanks Andy for your reply,</p>
<p>I am not sure if i understand what you mean&#8230;</p>
<p>well &#8230;this is my case:-</p>
<p>we have a business entity (peice of information) that consists of multiple documents. we want to create an approval workflow for this type of information without approving each document separately.</p>
<p>it is like having &#8220;attachemnet&#8221; workflows. where multiple documents are attached to the workflow instance. </p>
<p>is this possible?</p>
<p>thanks alot in advance</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1600</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Mon, 12 May 2008 14:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1600</guid>
		<description>Well, workflows can be started against multiple documents - so I guess you're saying that you need a design of workflow where one workflow instance can encompass multiple individual documents?

My current thinking on this is that this sort of functionality would be best implemented using a Site for each workflow instance - this would give the location for many documents to be saved to and worked with. Some third party products allow workflows to handle site lifecycle - K2 and Nintex can do this, I believe.

The only other alternative that strike me - don't use workflow. You can support a  business process in SharePoint using just views and statuses.</description>
		<content:encoded><![CDATA[<p>Well, workflows can be started against multiple documents - so I guess you&#8217;re saying that you need a design of workflow where one workflow instance can encompass multiple individual documents?</p>
<p>My current thinking on this is that this sort of functionality would be best implemented using a Site for each workflow instance - this would give the location for many documents to be saved to and worked with. Some third party products allow workflows to handle site lifecycle - K2 and Nintex can do this, I believe.</p>
<p>The only other alternative that strike me - don&#8217;t use workflow. You can support a  business process in SharePoint using just views and statuses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: areej</title>
		<link>http://www.novolocus.com/2007/09/24/sharepoint-workflow-and-when-to-use-it/#comment-1598</link>
		<dc:creator>areej</dc:creator>
		<pubDate>Mon, 12 May 2008 11:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.novolocus.com/?p=35#comment-1598</guid>
		<description>Thanks for the very useful post, 

We want to design a workflow that can be started on multiple documents which is not possible using sharepoint workflow designer or Visual Studio workflows as you mentioned :)

would you suggest  a BPM engine that we can use to enable us starting such workflows on MOSS ?

Thanks alot in advance,

Best Regards,
Areej</description>
		<content:encoded><![CDATA[<p>Thanks for the very useful post, </p>
<p>We want to design a workflow that can be started on multiple documents which is not possible using sharepoint workflow designer or Visual Studio workflows as you mentioned <img src='http://www.novolocus.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>would you suggest  a BPM engine that we can use to enable us starting such workflows on MOSS ?</p>
<p>Thanks alot in advance,</p>
<p>Best Regards,<br />
Areej</p>
]]></content:encoded>
	</item>
</channel>
</rss>
