SharePoint 2010 中的工作流入门

发布于 2024-09-03 08:40:23 字数 1122 浏览 9 评论 0原文

我是一名初级 sharepoint 开发人员,被要求在 sharepoint 2010 中实现以下场景。 我们对开始的最佳方法有点迷失。我真的很难找到最佳实践解决方案。

这是请求的流程:

  • 用户可以发出带有标题和描述的请求。
  • 一封包含表格链接的邮件将发送给代表。
  • 代表可以批准或拒绝该请求。
    • 如果获得批准:将向董事会发送一封包含表单链接的邮件
    • 如果被拒绝:系统会向用户发送一封邮件,其中包含已被拒绝的消息。
  • 当该请求获得代表批准后,董事会可以批准或拒绝该请求。
  • 根据董事会的决定,将向用户和代表发送一封邮件。

因此该列表具有以下字段:

  • 请求标题
  • 请求描述
  • 代表批准
  • 代表描述
  • 委员会批准
  • 委员会描述

用户应看到以下表单:

  • 请求标题(可编辑)
  • 请求描述(可编辑)

代表应看到以下表格:

  • 请求标题(只读)
  • 请求描述(只读)
  • 代表批准(可编辑)
  • 代表描述(可编辑)

董事会应看到以下内容格式:

  • 请求标题(只读)
  • 请求描述(只读)
  • 代表批准(只读)
  • 代表描述(只读)
  • 董事会批准(可编辑)
  • 董事会描述(可编辑)

我的问题:

  • 什么工具最适合制作表格?信息路径?社会民主党? VS2010?我如何处理权限以确保只有董事会可以访问董事会编辑表单?
  • 我使用什么样的工作流程?我什么时候开始工作流程?我用什么来开发工作流程?
  • 显示包含所有请求的列表视图时如何处理权限?
  • 如何在发送给不同组的邮件中建立链接。

预先感谢您的任何建议。

I'm a starting sharepoint developer asked to implement the following scenario in sharepoint 2010.
We're a bit lost on the best approach to get started.. I'm really struggling to find the best practise solution.

This is the requested flow:

  • A user can make a request with a title and a description.
  • A mail gets sent to the representative with a link to a form.
  • A representative can approve or reject the request.
    • If approved: A mail gets sent to Board with a link to form
    • If rejected: A mail gets sent to the user with the message that it has been rejected.
  • when the request was approved by the representative, the board can approve or reject the request.
  • A mail gets sent to the user and the representative with the descision of the board.

So the list has the following fields:

  • Request title
  • Request description
  • Representative approval
  • Representative description
  • Board approval
  • Board description

The user should see the following form:

  • Request title (editable)
  • Request description (editable)

The representative should see the following form:

  • Request title (read-only)
  • Request description (read-only)
  • Representative approval (editable)
  • Representative description (editable)

The Board should see the following form:

  • Request title (read-only)
  • Request description (read-only)
  • Representative approval (read-only)
  • Representative description (read-only)
  • Board approval (editable)
  • Board description (editable)

My questions:

  • What tool is most appropriate for making the forms? Infopath? SPD? VS2010? How do I handle rights to make sure only the board can access the board edit form?
  • What kind of workflow do I use? When do I start the workflow(s)? What do I use to develop the workflow(s)?
  • How do I handle rights when showing the listview with all requests?
  • How can I build the links in the mails sent to the different groups.

Thanks in advance for any advice.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

jJeQQOZ5 2024-09-10 08:40:23

关于你的一些问题......我不是100%确定,但是在2007版本中,InfoPath是一个企业功能。因此,InfoPath 的使用可能与您所拥有的版本有关(Foundation 与 2010 Enterprise)。

SPD 对您来说可能是一个良好的开始,特别是因为您现在可以导出 SPD 开发的工作流程并将其导入 VS 2010 中以更新功能。

关于板编辑...根据您的安全实施(FBA 与 AD),您可能希望对编辑表单的负载进行某种角色检查。我可能会首先使用一个 ASPX 表单(不是 Infopath)来确定您拥有的用户类型。根据用户,您可以显示或不显示适当的字段,并根据需要启动按钮的事件处理程序。

我很可能会从顺序工作流程开始,因为您没有需要担心的许多步骤。状态工作流用于更复杂的实现。

Regarding some of your questions.... I am not 100% sure, but in the 2007 version, InfoPath was an enterprise function. So the use of InfoPath may be a function of the version you have (Foundation vs 2010 Enterprise).

SPD may be a good start for you, especially since you can now export your SPD developed workflows and import them into VS 2010 to update the functionality.

Regarding the board editing... Based on your security implementation (FBA vs AD) you probably want to do some kind of role check on the load of the edit form. I would probably start by having a ASPX form (not Infopath) that you can determine the type of user you have. Based on the user, you can display or not display appropriate fields and fire up event handlers to buttons as need be.

I would most likely start with a sequential workflow since you do not have numerous steps that need to be worried about. State Workflows are for more complex implementations.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文