决定 Web 项目使用哪些工具(SharePoint、Workflow、ASP .NET)

发布于 2024-12-27 13:29:50 字数 1410 浏览 1 评论 0原文

我对我们计划开发的项目有疑问。

我将首先描述该项目,然后我将展示我所看到的解决此任务的可能方法。我希望你能给我你对他们的意见。

有两个主要部分:

第一部分:

在我们的组织中,我们希望创建一种中央访问点,用户将在其中登录(仅一次),并从那里获得链接(取决于他们的角色) )到我们提供的不同服务。

方法: 我们使用 Active Directory 来管理用户,因此我们考虑使用 SharePoint Foundation 创建这个中央访问点。 您认为这是一个好方法吗?

第二部分:

我们提供 SharePoint 服务,用户可以共享文档以及其他 Web 应用程序。这个想法是将所有这些集成到前面描述的中央接入点中。

到目前为止,一切都很好。现在我们被要求开发一个新的网络应用程序。该应用程序也将成为我们服务的一部分;因此需要将其集成到中央接入点中。

应用程序描述:这将是一个应用程序,其中 3 个不同角色的人将填写一些信息(按照特定顺序,第一个角色将填写,然后是第二个角色,然后是第三个角色)。每一步填写信息后,都会通过电子邮件通知下一个人,他/她的部分已准备好填写。要填写的信息是对产品的评估(仅供您参考)。

组织的经理还希望有一个控制面板,以便他们可以对应用程序的使用情况进行一些统计。在那里,他们可以看到待评估、每年评估、每个角色的评估等内容。

方法:

正如您所见,我们的主要疑问是关于使用

SharePoint 网站< --> ASP .NET Pages (C#)

工作流(SharePoint Workflow 或 Workflow Foundation)<--> 在内部代码中使用一些标志来控制工作流

我们在想至:

1- 提出我们希望使用 SharePoint 作为我们的“中央访问点”的想法。我们将该应用程序创建为 SharePoint Web(如果可能,使用 SharePoint Designer 2010)。并将 SharePoint 工作流应用到该流程中。

2- 创建 ASP.NET 站点并将其导出为 Web 部件,我们可以将其集成为 SharePoint 中的应用程序。尝试以某种方式使用 SharePoint 工作流程。 (我们实际上不太知道该怎么做)。

3- 创建一个 ASP .NET 站点并忘记工作流工具,因为我们的工作流非常小且连续,并使用一些标志控制代码中的所有内容。

您目前对我们的想法有何看法?您能给我们提出一些不同的建议吗?

非常感谢您的帮助

我们的SharePoint是SharePoint Foundation的免费版本。

I have a question about a project we are planning to develop.

I will start by describing the project and later I will expose the possible approaches I see to tackle this task. I hope you can give me your opinion on them.

There are 2 main parts:

First part:

In our organization we want to create a kind central access point where users will log in (just one time) and from there they will have links (depending on their roles) to the different services we provide.

Approach:
We are using Active Directory to manage our users, so we thought to create this central access point with SharePoint Foundation.
Do you think that it is a good approach?

Second part:

We have services as a SharePoint were users can share documents, and also other web apps. The idea is to integrate all that in to the previously described central access point.

So far, so good. Now we were asked to develop a new web application. This application will be also part of our services; therefore will be needed to integrate it in the central access point.

Description of the application: It will be an application were 3 different roles of people will fill some information (in an specific order, 1st role will fill in, then the 2nd role, and then the 3rd role). After each step of filling information the next person will be informed by email that his/her part is ready to be filled in. The information to be filled in is an evaluation of a product (just for your information).

The managers of the organization will also want to have a control panel were they can have some statistic over the use of the application. There they can see thing like pending evaluations, evaluation per year, per role, …

Approaches:

As you will see our main doubt are about using

SharePoint Site <--> ASP .NET Pages (C#)

Workflow (SharePoint Workflow or just Workflow Foundation) <--> Using some flags in the internal code to control the workflow

We were thinking to:

1- Giving the idea that we would like to use SharePoint for our “central access point”. We would create the app as a SharePoint web (Using SharePoint Designer 2010 if possible). And apply the SharePoint Workflow to the process.

2- Create an ASP.NET Site and export it as a web part that we can integrate as an application in SharePoint. Try to use somehow the SharePoint Workflow on that. (We actually don’t know well how to do it).

3- Create an ASP .NET Site and forget about the Workflow tools, as our workflow is quite small and sequential, and control all that in the code with some flag.

What do you think about our ideas at the moment? Would you propose us something different?

Thank you very much for your help

Our SharePoint is the free version SharePoint Foundation.

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

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

发布评论

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

评论(1

神魇的王 2025-01-03 13:29:50

只要 Web 应用程序不希望完全超出 SharePoint 范围,选项 1 听起来最适合您的方法。

就基本工作流程支持而言,SP 基金会应该不是问题。 中工作流支持的更多详细信息,请参阅本文

有关 SP Foundations选项 2 3 听起来有点冒险,并且会涉及很多自定义代码,SP 无论如何都会为您提供 OOTB。

Option 1 sounds the best fit for your approach as long as the web-app isn't aspiring to be something totally outside SharePoint bounds.

As far as basic workflow support goes, the SP Foundations should not be an issue. Refer this article for further details on workflow support in SP Foundations

Options 2 and 3 sound a little adventurous and will involve a lot of custom code which SP will provide you OOTB anyways.

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