需要技术推荐/建议

发布于 2024-07-12 19:59:28 字数 1539 浏览 12 评论 0原文

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

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

发布评论

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

评论(5

假面具 2024-07-19 19:59:41

我还建议 k2 blackPearl.. 它具有出色的工作流程功能并与 sharepoint 集成,

但 K2 blackPoint(另一个 k2 软件)也与 SharePoint 集成得很好,实际上您只能将它与 sharepoint 一起使用。 如果您想降低成本,k2 blackPoint 可能是一个选择,而不是 k2 blackPearl。 而且由于 BlackPoint 可以与 infopath 集成,因此当您想要创建新项目时,您可以制作更好的 gui,而不是填写 Sharepoint 列表。 并不是说我反对填写列表,外观对我来说很重要(我猜是个人偏好),

无论如何,

使用任何 k2 应用程序都会缩短开发时间,因为它相对容易开发(拖放之类的东西)。 K2说没有编码,但是你可以添加代码。

I would also suggest k2 blackPearl.. it has great workflow capabilities and integration with sharepoint

but K2 blackPoint (another k2 software) also integrates very nicely with SharePoint, actually you can only use it with sharepoint. if you want to cut costs k2 blackPoint could be an option rather than k2 blackPearl. and because BlackPoint can integrate with infopath, you can make better gui rather than filling out Sharepoint lists when you want to make a new item. not that i have anything against filling out lists, look are important for me (personal preference i guess)

anyway,

using any k2 application cuts development time, coz its relatively easy to develop (drag n drop kinda stuff). K2 say's no coding, but you can add code.

七秒鱼° 2024-07-19 19:59:40

在与客户的沟通中,我获得了需求列表,其中客户写道平台必须是SharePoint Services 3.0。 所以现在我所有的决定都将基于开发一个解决方案。 因此,我感谢大家在这里提出的许多好的建议,特别是 StingyJack,他建议了我将在未来的项目中考虑的另外一些产品。

现在我必须专注于我的项目的建筑设计。

In communication with the client, I obtained the requirement list where the client wrote that the platform must be SharePoint Services 3.0. So now all my decisions will be based on developing a solution based on that. Therefore I thank you all for many good suggestions given here especially StingyJack who suggested another few products I will consider for my future projects.

Now I must concentrate on architectural design for my project.

衣神在巴黎 2024-07-19 19:59:38

k2 BlackPearl 已用于通过 SharePoint 提供复杂的工作流解决方案,BlackPearl 使用 Windows Workflow Foundation,如果您想要 SharePoint 中的 Microsoft Office 集成和协作功能,这两个产品值得探索。

SharePoint 是一个大型且复杂的平台,对于小型解决方案来说可能有些过大,但如果您计划集成整个组织,它可能会提供一个具有成本效益的解决方案。

SharePoint 最大的问题是知识。 很难找到具有必要经验的人来指导您绕过在 SharePoint 部署中容易犯的一些陷阱,并且很难从中恢复。

k2 BlackPearl has been used to provide complex Workflow solutions with SharePoint, BlackPearl uses the Windows Workflow Foundation and the two products are worth exploring if you are wanting the Microsoft Office integration and collaboration features found in SharePoint.

SharePoint is a large and complex platform that may be overkill for small solutions, but if you are planning on integrating your entire organisation it may provide a cost effective solution.

The biggest issue with SharePoint is knowledge. It is hard to find people who have the requisite experience to guide you around some of the pitfalls that are easy to make in a SharePoint rollout and hard to recover from.

风吹短裙飘 2024-07-19 19:59:36

我相信 Windows Sharepoint Services (WSS) 3.0 可以满足您所需的一切。

您可以像您计划的那样使用 Windows Workflow Foundation,并且文档库提供文档管理,包括版本控制、文档签出和搜索。

除非您计划将门户与旧系统集成或需要其他复杂功能(例如文档中的权限管理),否则我认为您不需要 Microsoft Office Sharepoint Server (MOSS) 2007。

您应该使用 Microsoft Office(如果可能,请使用 2007 版 ) ) 当您使用 SharePoint 时; 请参阅白皮书:好、更好、最好:Office 和 SharePoint 产品和技术

更多详细信息请参见:什么是 Microsoft Sharepoint?

I believe Windows Sharepoint Services (WSS) 3.0 can deliver all that you need.

You can use the Windows Workflow Foundation like you plan to do, and document-libraries deliver document management including versioning, document check-out and searching.

Unless you plan to integrate the portal with a legacy system or need another complex function (like rights-management in documents) i do not think you need Microsoft Office Sharepoint Server (MOSS) 2007.

You should be using Microsoft Office (Version 2007 if possible) when you use SharePoint; see White paper: Good, better, best: Office and SharePoint Products and Technologies

More details here: What is Microsoft Sharepoint?

一个人的夜不怕黑 2024-07-19 19:59:35

好吧,我只想说,我对 Sharepoint 的一次体验并不好,而且我每天都对它的局限性感到恼火,这不断增加我对它的挫败感。 我确信它可以变得更有用,但目前还没有。

您正在寻找的是与文档管理相关的业务流程管理(工作流)解决方案。 我从事这项工作已经有十年的时间了,所以我知道有几家提供这些产品的公司。 (其中一些可能有点过头了,但话又说回来,sharepoint 也是如此)

  • FileNet - 两者都提供BPM 和 DM。 价格昂贵,但有 30 年的工作经验,而且他们的产品坚如磐石。 (培训也在 SoCal 进行。很好!)
  • Epitome - 提供 BPM 和 DM(称为 EPM - 我讨厌营销) )。 许可可以按每个席位或按交易运行。 (所有 .NET api,如果需要,可以设计或托管解决方案)
  • OpenCMS - 只是 DM,免费,但您需要连接 BPM (WWFF)。
  • OTG - 提供 BPM 和 DM。 目前对定价没有想法,但很容易理解产品结构,并且很容易排除故障。

不要打扰

  • OnBase - 支持很困难,而且它们都是 COM 组件,.NET 集成很困难,而且他们并不真正愿意帮助集成商。
  • Fortis / FileMagic - 上次我与他们合作时还不够成熟。

如果您打算自己动手,请确保您至少拥有以下几样东西。

  • 文档版本控制/变更审核。 每个更改都应记录为新的单独文档。 (即使您可能使用电子表格,每次更改数据时,都应保留旧版本)
  • 文档的锁定/签出。 源代码控制的工作方式大致相同。
  • 把事情简单化。

Well, I should just say that my one experience with Sharepoint is not great, and I am irritated by it's limitations every day, which is constantly adding to my frustration with it. I'm sure that it could be made more useful, but not as of yet.

What you are looking for is a Business Process Management (Workflow) solution that is tied into Document Management. I did this work for the better part of a decade, so I know of a few companies that offer these products. (Some of these may be overkill, but then again, so is sharepoint)

  • FileNet - Offers both BPM and DM. pricey but 30 years experience doing the work and their products are Rock Solid. (Training is also in SoCal. Nice!)
  • Epitome - Offers both BPM and DM (called it EPM - I hate marketing). licensing can run as a per seat or per transaction. (All .NET api's and can design or host the solution if you want)
  • OpenCMS - Just DM, free, but you will need to hook into BPM (WWFF).
  • OTG - Offers both BPM and DM. No current idea on pricing, but very easy to understand product structure and is very easy to troubleshoot.

Dont bother with

  • OnBase - Support is difficult and they are all COM components, .NET integration is difficult and they are not real willing to help integrators.
  • Fortis / FileMagic - Just not mature enough last time I worked with them.

If you are going to roll your own, make sure that you have at least these few things.

  • Document versioning /change auditing. Each change should be recorded as a new separate document. (Even though you may be working with electronic forms, each time the data is changed, the old version should be preserved)
  • Locks / checkout for a document. In much the same way source control works.
  • Keep it simple.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文