Sharepoint Workflow Vs. WFF -


itemprop = "text">

The title is not very accurate I am currently developing an additional site on a site that allows many people to enter data Allows I want WFF / want because people will enter the data in a certain order. This is a customer complaint form, a seller will enter the complaint by filling the initial form. The complaint will be reviewed and either will be rejected or forwarded in the investigation section. At the end the complaint will be handled and closed.

My dilemma is that I am also implementing Sharepoint, both projects are around the same time. Eventually SharePoint will be our only website, and the complaint project will be transferred to Sharepoint.

As long as the sharepoint is not in place, I wait and then chase the customer complaint project.

Any ideas, suggestions, any comments?

Originally a hosting engine for the SharePoint Windows Workflow Foundation is some of the elements that you will find in the WWFF workflow Is required to be included in the development, which you need to run on a SharePoint workflow engine, but you can create them in your project because you know this workflow will be ported to SharePoint at some point.

However, as long as you have implemented the UI components (form etc.) to operate your workflow, and the engine has to deploy it to you at least with the WSS 3.0 installation Have done

My advice, to run within the SharePoint workflow engine, design your WWF workflow in Visual Studio and take advantage of the InfraRost coming along. Otherwise, you will spend extra weeks on your complaint project, which will soon become unnecessary when you close the portpoint.


Comments

Post a Comment