, its really rocks! . Now i want to do some
on that , .......................
I'm not sure if you're aware, but SharePoint v3, which is included in the Office 12 wave will utilize Windows Workflow Foundation for workflow. With SharePoint v3, workflow will be a tightly integrated with the technology and users will even be able to start workflows from the Office client applications. SharePoint v3 also includes additional activities for task management.
If you want to utilize workflow with SharePoint Portal Server 2003, then you could try implementing a custom solution that leverages SharePoint document event handlers to start/continue workflows. There are several different workflow examples in the community that have been built for SharePoint 2003. Here's one called Workflow lite for Sharepoint. It might be a starting point. If you do a quick search for Workflow and Sharepoint I'm sure you'll find several more.
James Conard
Architect Evangelist - Windows Workflow Foundation
http://www.WindowsWorkflow.net
http://blogs.msdn.com/jamescon
Yup i know that , cauz i am very keen viewer of channel9 i got that news. I personally think this is inevitable .But i am very much concerns about those enterprises that gona use new sharepoint release V3 , and going for upgrdation from V2 . Like if they are using 3rd party workFlow (e.g Teamplate,K2.Net (i know they will provide suppprt for WWF ) , Ultimus ) what options they got ?
PS:- what happen to the Left Alone child know as Micriosoft Content Managment Server 2002 . Nobody knows/Wants to see its workflow(author --editor ) to change from simple dual step to fully functional WWF enabled ?
In the channel 9 video on sharepoint V3 I believe the team said they had worked very hard to keep from breaking V2 addons, so I would assume most everything that works with V2 will work with V3.
Still, it would be nice to develop backwards compatibility to allow users of V2 to take advantage of WWF too.
well the backward compactability is not only required its inevitable for the product like SharePoint Server , you cant force a Billion Dollor Enterprise to move pack thier bags and move to new version its take huge amount of time and resource to do that . I am quite sure that in SharePoint V3 we certainly gona see couple of enhancment (as some of them are shown in channel9 video ) that gona made users much more comfartable with it .
Well the transformation of workflow from .Net to WFF is quite a big deal specially for the vendors who simply creates the wrapper around the COM components to made thier product work. This will certainly a turning point for those vendors who spend time on writing quality code rather than just publish thier un-mature code
Well for now happy programming with WFF
SPS and WF will certainly not work since .Net 2.0 is not supported on SharePoint Portal Server. However WSS does support .Net 2.0 so I'm taking a look at how to integrate these 2 - hosting WF runtime in SharePoint does not seem to work since I already get an error when modifying the web.config
Parser Error Message: Unrecognized configuration section WorkflowRuntime.
Let me know if you find out more,
kind regards,
Joris
You can take a look at the demo solution that I have built for the Microsoft DevDays 2006 in Sofia, Bulgaria.
It demonstrates an InfoPath document that is handled by a SharePoint document event handler. A web service receives all documents and creates/manages workflow instances. They are also presisted into the standard WF SQL persistence database and demonstrate wating for an external event.
http://www.kasev.net/blog/2006_06_01_kasev_archive.html
Best Regards,
- Nikola.
Nikola,
The code example looks cool, but what about implementing workflow Completed and Terminated events? Where/how do you declare the delegates? Where do you place the code implementation?
Sincerely,
John P.
Yup I came up with the same architecture for SPS, Win WF & Infopath with access security and use of Win WF rules in the workflow see
http://geekswithblogs.net/synboogaloo/archive/2006/07/05/84083.aspx
