WPF 还是工作流？
我有一个问题，希望你能引导我走向正确的方向。
我正在开发一个应用程序，该应用程序需要某种形式的决策树/工作流程，但缺乏更好的术语。 为了清楚起见，我将在下面描述它。
我有一个请求表，用户将在网页上填写。 表格的开头是“推荐类型”。 根据所选的推荐类型，某些表格问题将会发生变化。 根据推荐类型，可能有 2、3 或 4 组问题。 整组问题可能会通过，也可能会失败。
如果第一组问题失败……那么表单将停止处理，等等。
处理此问题的最佳方法是什么？ WPF 在这种情况下能正常工作吗？
I have a question and hopefully you can steer me in the right direction.
I'm working on an application that needs some form of decision tree/work flow for lack of a better term. I'll describe it below for some clarity.
I have a request form that users will fill out on a web page. At the beginning of the form is a 'Referral Type'. Bases on the referral type selected some of the form questions will change. There could be 2, 3 or 4 groups of questions depending on the Referral type. Entire groups of questions can be pass or fail.
If the first group of questions fail..then the form stops processing, etc.
What would be the best approach to handle this? Would WPF work well in this situation?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不确定 Workflow 与 ASP.NET 的配合效果如何，因为我从未尝试过。 我相信一些示例可能实际上涵盖了这一点，所以这是可能的。 这是第一个技术障碍。
听起来逻辑并不太复杂。 根据推荐类型，用户可以采取的“路径”数量有限。 每条路径都相当线性，有 2-4 个“组”问题。 每个组可以坐在一个页面上吗？ 这将大大简化事情。
Web 框架，例如 Spring.NET Web Framework 可能比工作流更适合此任务。 你试图表达一些条件逻辑——本质上是“如果 X 则转到下一页，否则结束提问”。 Spring.NET 通过其验证框架和结果映射来处理这种精确的逻辑。
工作流当然非常适合这种逻辑，但是除了验证之外，在响应每组问题时还会发生什么吗？ 如果没有，这可能有点矫枉过正。
I am unsure how well Workflow works with ASP.NET as I've never tried it. I believe some of the samples may actually cover this so it's possible. That is the first technical hurdle.
It sounds like the logic isn't too complicated. There are a finite number of "paths" that a user can take based on the referral type. Each path is fairly linear, with 2-4 "groups" of questions. Can each group sit on a single page? That would simplify things greatly.
A web framework such as Spring.NET Web Framework might be better suited for this task than Workflow. You are trying to express some condition logic--essentially, "go to the next page if X, else end questioniare". Spring.NET handles this exact sort of logic with its Validation Framework and the Results Mapping.
Workflow is certainly well-suited for this kind of logic, but is there anything that happens in reasponse to each group of questions other than validation? If not, it may be overkill.
WPF 是 Windows Presentation Foundation，更多的是关于用户界面，而不是工作流程管理系统。 对于工作流程，您可以构建自己的本地数据库驱动解决方案，也可以使用 Ultimus 或 Sharepoint 等工具。
您可能还会想到Windows Work Flow Foundation。
我使用 Ultimus 和自行开发的实现来进行工作流程管理。 同行都用过Sharepoint。 每个都有好处或优点/缺点。
WPF is the Windows Presentation Foundation and is more about the User Interface than a work flow management system. For work flow, you could build your own home-grown database driven solution, or you could use tools like Ultimus or Sharepoint.
You may also be thinking of the Windows Work Flow Foundation.
I have used both Ultimus and home-grown implementations for work flow management. Peers have used Sharepoint. There are benefits or pros/cons to each.