工作流程工具比较？
我们非常需要围绕各种流程设计一些工作流程。 问题是我们中没有人真正了解任何工作流程技术，并且寻找良好的数据来比较可用选项是乏味的，而且并不完全富有成效。
所以我想我会问你们。
我们关注的主要技术是 Windows Workflow Foundation 和 eDocs Workflow。 还有哪些其他选择？ Sharepoint 2007 也具有工作流程功能，对吗？ 这只是基于WF吗？
各种技术的优缺点是什么？ 他们如何比较？
编辑：此外，管理类型（例如 eDocs Workflow）的一个功能是，它为他们提供了一种自行编辑的方法。 我相信 Sharepoint '07 也能做到这一点。 是否有其他方法可以通过直接 WWF 实施来实现这一点？
There is a pretty strong need for us to design some workflows around various processes. The problem is none of us actually know any workflow technology yet, and finding good data to compare the available options has been tedious and not entirely fruitful.
So I figured I'd ask you guys.
The main technologies we are looking at are Windows Workflow Foundation and eDocs Workflow. What other options are there? Sharepoint 2007 has workflow functionality too, right? Is that just based on WF?
What are the pros and cons of the various technologies? How do they compare?
EDIT: Also, one feature the administrative types like with eDocs Workflow is that it provides a method for them to edit it themselves. I believe Sharepoint '07 does as well. Is there some other way to allow that with a straight WWF implementation?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Sharepoint 和 WF 更像是互补技术，被设计为同一生态系统中的两种不同的工作流创作工具。 有一个 Sharepoint 工作流设计器和一个 WF (Windows Workflow Foundation) 工作流设计器。
Sharepoint 设计器旨在提供类似 Office 的工作流程编辑体验，更易于上手，适合非技术类型，并自动生成所有 Web 表单。
另一方面，“WF”工作流设计器实际上是 Visual Studio 的一个组件（默认情况下 - 正如 Bernie 所说，您可以重新托管它），旨在允许程序员能够完全自定义工作流，并将其与任何其他代码集成/所需的系统。 通过使用“Sharepoint 活动”，以这种方式构建和部署共享点站点仍然是可能的，但更加复杂。
如果您采用前一种方式，您有望让管理类型进行自己的基本自定义（在该环境的限制范围内），而不会造成完全混乱。
Sharepoint and WF more like complementary technologies, designed as two different workflow authoring tools in the same ecosystem. There's a Sharepoint workflow designer, and a WF (Windows Workflow Foundation) workflow designer.
The Sharepoint designer is meant to be an Office-like workflow editing experience, easier to get started with, geared for non-technical types, and generates all the web forms automatically.
The 'WF' workflow designer on the other hand is actually a component of Visual Studio (by default - as Bernie says you can rehost it), and designed to allow programmers to be able to fully customize workflow, and integrate it with any other code/systems desired. Building and deploying sharepoint sites this way is still possible, through the use of 'Sharepoint Activities', but more complex.
If you take the former route, you can hopefully let the administrative types do their own basic customizations (up to the limits of that environment) without causing total chaos.
可以在您自己的应用程序中“重新托管”WF 设计器（来自 Visual Studio 的设计器），以便用户可以创作工作流。 网络上有许多代码示例，其中最重要的一个来自 MS 本身： http://msdn.microsoft.com/en-us/library/aa480213.aspx）。
在某些时候，在评估 WF 时，我实现了一个演示应用程序来执行此操作并添加了一些功能，并发现虽然它有效，但并不是每个人都可以理解和使用需要了解规则的更困难的活动（例如策略活动）发动机工作。
It is possible to 'rehost' the WF designer (the one from Visual Studio) in your own application, so that users can author workflows. There are a number of code examples on the web, the most important one from MS itself: http://msdn.microsoft.com/en-us/library/aa480213.aspx).
At some point, when evaluating WF, I implemented a demo application that did this and added some features and found that although it works, not everybody can understand and use the more difficult activities (like the policy activity) that require understanding of how the rules engine works.