SharePoint Designer 工作流程 - 提示和资源?
我正在修改一些现有的 SPD WF,并努力解决一些概念,包括为什么 2 个看起来相似的 WF 不会产生相同的输出。
你们中是否有人使用过 SharePoint Designer/工作流并知道任何好的资源(比 MSDN 介绍更详细)或有关此事的提示。 例如,关于调试以及如何检查设置以及如何连接来自多个工作流程的信息...
换句话说:提出最佳的 SPD WF 链接和链接。 提示:o)
我目前无法选择其他解决方案,因此欢迎提供任何提示。 我有关于 SharePoint Designer 工作流程的 USPJ 特刊。 这还不错,但一定还有更多好东西:o)
I'm working on revising some existing SPD WF's and strugling with some of the concepts including why 2 appearingly alike WF's doesn't produce the same output.
Are there anyone of you that has worked with SharePoint Designer / Workflows and knows any good resources (more detailed than the MSDN introductions) or tips on the matter. E.g. on debugging and how to inspect settings and how to connect information from several workflows...
In other words: come up with your best SPD WF links & tips :o)
I'm not able to choose another solution at the moment, so any tips are welcome. I have the USPJ Special Issue on SharePoint Designer Workflows. It' not bad, but there must be more goodies out there :o)
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
从您的问题来看,您似乎遇到了 SharePoint Designer 旨在解决的解决方案的限制。
实际上没有调试支持,因为向导方法不需要它,但实际上我们知道这真的很有帮助! 同样,连接工作流程正在突破界限,为此我会考虑转向 Visual Studio。 您可以考虑开发自定义操作(如果合适)作为创建完整的 Visual Studio 工作流程的解决方法或桥梁(以下是示例带有源代码)。
我首先查看的 Web 资源是 SharePoint Designer 团队博客(显然)和 < a href="http://www.google.co.uk/search?q=sharepoint+designer+workflow+site%3Aendusersharepoint.com" rel="nofollow noreferrer">EndUserSharePoint.com 上的工作流程文章。
此外,具有合理数量的 SharePoint Designer 工作流内容的书籍:
2007 Microsoft Office System:不详细介绍如何使用 SPD,而是介绍使用 Visual Studio (2005) 构建工作流程。
专业 Microsoft Office SharePoint Designer 2007:启动、变量、步骤、条件、行动、考虑。 工作流程只是众多章节中的一章。
Microsoft Office SharePoint Designer 2007 圣经:架构、条件、操作、管理、先进技术、审批。 工作流程只是众多章节中的一章。
It appears from your question that you are hitting the limits of the solutions that SharePoint Designer is designed to solve.
There really isn't debugging support as the wizard approach shouldn't require it, however in reality we know this would really help! Similarly, connecting workflows is pushing the boundaries and I would consider moving to Visual Studio for that. You could consider developing custom actions if appropriate as a workaround or bridge to creating a full-blown Visual Studio workflow (here are examples with source code).
Web resources I would look at first are the SharePoint Designer Team Blog (obviously) and workflow articles on EndUserSharePoint.com.
Also, books that have a reasonable amount of SharePoint Designer workflow content:
Workflow in the 2007 Microsoft Office System: Doesn't go into much detail for using SPD, leads into building workflows with Visual Studio (2005).
Professional Microsoft Office SharePoint Designer 2007: Initiation, variables, steps, conditions, actions, considerations. Workflow is one chapter of many.
Microsoft Office SharePoint Designer 2007 Bible: Architecture, conditions, actions, administration, advanced techniques, approval. Workflow is one chapter of many.
我从编程工作流程以及使用 SPD 部署它们中学到了以下内容。
1.不要依赖于在工作流标注中传递您需要的所有字段:定义看起来合理的内容,但请记住,一旦您有权访问 SPList 项,您就可以从工作流中处理对象模型,而无需反复更改接口并重新部署。
即,一旦您在 .actions 文件中定义了这三件事并将它们传递到您的工作流程,
您就可以访问部署时可能忘记显式传递的任何内容。
2.直接使用上下文创建所需共享点项目的实例时要小心,因为您可能会在不知不觉中传递调用工作流的人的权限。 即执行此操作
而不是此操作:
3.如果您没有将 Visual Studio 与共享点安装在同一机器上,则很难设置调试。
I've learnt the following from programming workflows and deploying them with SPD.
1.don't rely on passing all the fields you need in the workflow callout: define what seems sensible, but remember that once you have access to the SPList item, you can work your way around the object model from within your workflow without having to repeatedly change the interface and redeploy.
i.e. once you have defined these three things in your .actions file and passed them to your workflow
you're set up to access whatever you might have forgotten to pass explicitly when deploying.
2.Watch out when using the Context directly to create your instance of the sharepoint item you want, as you may unknowingly pass on the permissions of the person calling the workflow. i.e. do this
instead of this:
3.Debugging is difficult to set up if you don't happen to have visual studio installed on the same box as sharepoint.