我不明白 Windows Workflow 给了我什么
以此作为一个简单的工作流程。员工创建一个文档，从这里该文档进入一级主管审批，如果获得批准，则进入下一级主管，依此类推，直到最终批准和文件存储库。如果不是每个级别都可以回到上一个级别。
Windows Workflow Foundation 为我提供了哪些我可以自己完成的工作？这些听起来像是简单的编码规则，所以我不确定我从 WWF 中获得了什么。
谢谢。
编辑：现在，如果我在 Visual Studio 中制作的流程图实际上创建了一个向导或我可以使用的东西，那就会有所不同。我什至不知道这会是编码，但至少我可以更好地理解它。
Take this for a simple workflow. An employee creates a document, from here the document goes to level one supervisor for approval, if approved it goes to next level and so on until final approval and file repository. If not each level can kick back to previous level.
What does Windows Workflow Foundation give me that I can do on my own? Those sound like simple rules to code so I'm not sure what I am gaining with WWF.
Thank you.
EDIT: Now if that flow chart that I make in Visual Studio actually created a wizard or something that I could use that'd be different. I don't know that would even be coding but at least I could understand it better.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我自己从未使用过 WF，请允许我向那些使用过 WF 的人介绍一下：
以下是上一篇文章中的引用：
Having never used WF myself, allow me to direct you to those who have:
Here's a quote from that last article:
我想说，工作流给组织带来的好处比开发人员带来的好处更多。作为开发人员，在一些无关的框架中定义我们可以自己做的事情对我们没有好处。但是，如果您不是开发人员，并且您需要向最高级别主管发送电子邮件，在您的示例中，当没有人在这么多天后批准该文档时，该怎么办？如果您设计了一个允许事件重新排序的应用程序，那么除了您之外的其他人也可以指定此流程。诚然，您必须非常通用地编写代码，但如果您的场景需要外部人员来决定流程并且不是开发人员，那么这是值得的。
例如，在 Microsoft CRM 中，某些工作流程包含需要遵循的步骤。您可以编写自己的工作流程，使用周围的框架来创建新的工作流程。您无需担心以某种拙劣的方式将代码添加到系统中。系统知道工作流程，知道如何遵循这些步骤，并且可以执行它们。 WF有好处，但有限。
I would say that Workflow presents more benefit to the organization than the developer. As developers, it does us no good to define things we can do on our own in some extraneous framework. But what if you aren't the developer, and you needed an email shot to the top level supervisor, in your example, when nobdy approves the document after so many days. If you designed an application that allowed the reordering of events, someone besides yourself could designate this flow. Granted, you would have to code things pretty generically, but it is worthwhile if your scenario requires outside people to dictate flow and who are not developers.
For example, in Microsoft CRM, certain workflows contain steps to be followed. You could write your own workflow that uses the surrounding framework to create new workflows. You have no need to worry about adding your code in some hackeyed way to the system. The system knows workflows, it knows how to follow the steps, and it can execute them. There is benefit to WF, but it is limited.