定制开发还是利用 SharePoint 和 Web 部件等？
我们目前正在为现有客户制定解决方案，创建许多电子服务。客户目前拥有 MOSS 2007。建议的解决方案是使用 MOSS 作为电子服务的启动板……
要求包括起草几个提供注册设施并促进某种工作流程的在线表格。我被告知所提出的解决方案需要复杂的网络表单。
大多数都是复杂的表单，其中包含具有多个窗口的父子详细信息。建议的解决方案是进行一些定制开发，开发 ASP .NET 表单。这些表单将部署在当前 MOSS 门户的 _layouts 文件夹下，继承当前站点上的母版页设计。
有人告诉我，这种方法使开发和部署更加简单，并且与 MOSS 具有“完全集成”。
我的问题是：
这是利用 SharePoint 的最佳方式吗 - 似乎提议的解决方案根本没有利用 MOSS...！我认为也许利用 Web 部件会更好，但有人告诉我，这更复杂，并且开发更智能、更直观的 UI 也更困难。事实真的如此吗？如果不是，推荐的方法应该是什么？
我们将利用 Ultimus 作为工作流程引擎。不过，有人向我推荐 K2 Workflows。有人使用过两者/对其中任何一个有意见吗？
非常感谢！
亲切的问候，
We are currently in the process of drawing up a solution for an existing client, creating a number of eServices. The client currently have MOSS 2007. The proposed solution is to use MOSS as the launching pad for the eServices…
The requirement involves drawing up several online forms which provide registration facilities as well as facilitating a workflow of some sort. I have been told that the proposed solution requires complex web forms.
Most are complex forms with parent child details that have multiple windows. The proposed solution is to do some bespoke development, developing ASP .NET forms. These forms would be deployed under the _layouts folder of the current MOSS portal, inheriting the master page design on the current site.
I have been told that this approach make development and deployment more simple, as well has having ‘complete integration’ with MOSS.
My questions are:
Is this the best way to leverage SharePoint – it seems like the proposed solution is not leveraging MOSS at all..! I thought perhaps utilizing Web Parts would be better, but I have been told that this is more complex and developing more smarter intuitive UI is more difficult. Is this really the case? If not, what should be the recommended approach?
We will be utilizing Ultimus as the workflow engine. However, I have been recommended K2 Workflows. Anyone used both/have any opinions on either?
Many thanks in advance!
Kind Regards,
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
如果他们有 MOSS 2007 Enterprise，您可能会考虑 Web 呈现的 InfoPath 表单是否可以满足您对“复杂 Web 表单”的需求。归根结底，可能所有这些技术都可以满足需求，这只是您和您的客户拥有哪些技能以及如何促进该解决方案保持最新的问题。
If they have MOSS 2007 Enterprise, you might consider if web rendered InfoPath forms can meet your needs for "complex web forms". When it comes down to it, probably all of these technologies can meet the neeed it is just a matter of what skill sets you and your customer have and how that will facilitate keeping this solution up to date.
阿西姆，他们提出的是一个可能的解决方案。不过，它们可以通过使用 Web 部件来提供相同的功能。根据您提供给我们的详细信息，我们实际上无法决定哪个选项更容易。我根据每个功能的要求在同一个项目中使用了这两种方法。
我可以理解，他们看起来并没有利用 MOSS，但他们实际上是在 MOSS 的上下文中构建页面。
我还没有真正听说过 Ultimus，我确实在概念验证中使用了 K2，而且我对它非常满意。话又说回来，选择正确的工作流程解决方案取决于您的要求。
Asim, what they propose is a possible solution. They can however provide the same functionality by making use of webparts. With the details you are giving us that isn't really possible to decide which option would be easier. I used both approaches in the same project depending on the requirements of each functionality.
I can understand that it doesn't seem like they are leveraging MOSS, but they actually are building pages within the context of MOSS.
I haven't really heard about Ultimus, I did use K2 in a proof of concept and I was quite happy with it. Then again, choosing the right workflow solution depends on your requirements.