当组织结构和文档管理系统也应该共存时，使用哪种 BPM 解决方案？
我正在寻找一款可以为我解决问题的产品，希望您能尽快帮助我。
我有一个客户需要将软件模块集成在一起，以下是我认为可以实现其目标的软件模块：
- 文档管理系统（DMS）：Sharepoint Portal。
- 公司组织结构（工作流程所需，也在 DMS 中使用）：可能是与 Active Directory 和共享点门户集成的自定义开发。
- 工作流管理系统（或 BPM）：Nintex Workflow。
问题是：
- 以上几点是否符合逻辑，或者是否缺少某些内容。
- 将公司组织结构与工作流管理和共享点集成起来是否会花费太多时间进行开发，或者是否有更简单的解决方案，例如共享点或 Nintex Workflow 中的内置组织结构？
我仍在审查软件解决方案，我不熟悉 sharepoint，软件解决方案的组合导致了我以后可以将其用作未来客户的产品，这也是我正在寻找的。
例如，假设我们有一个请假工作流程，流程如下：
开始->填写休假表格 ->由当前活跃经理批准表格 ->由人力资源团队保存休假表格数据（存档或单独的人力资源管理系统）->关闭流程
定义了组织结构，然后为一组人定义了“当前活跃经理”，该流程将由“工作流管理系统”/BPM软件构建，“请假表格”可以是Web表单，或存储在文档管理系统上的模板。
I am looking for a product that can solve a problem for me, and I hope you can help me with this ASAP.
I have a client which needs software modules to be integrated together, the following are the modules with what I think is the software that fulfills its goals next to it:
- Document Management System (DMS): Sharepoint Portal.
- Company Organization Structure (needed for workflows and used in DMS also): Probably custom development integrated with Active Directory and sharepoint portal.
- Workflow Managment System (or BPM): Nintex Workflow.
The questions are:
- Are the points above logical, or is there something missing.
- Will it take too much time for development to integrate the Company organization structure with the workflow management and sharepoint, or is there a simpler solution, such as a built in Organization Structure in sharepoint or in Nintex Workflow?
I am still reviewing software solutions, I am not familiar with sharepoint, a combination of software solutions which lead to this product/solution I can use as a product later on for future clients is what I am looking for also.
For example, let's say we have a Leave request workflow process, the process is as follows:
Start -> Fill Leave Form -> Approve Form by CURRENT active manager -> save leave form data by HR team (on file or on separate HRMS) -> Close process
The organization structure is defined, and then the "CURRENT active manager" is defined for a group of people, the process will be built by a "workflow management system"/BPM software, the "Leave Form" can be a webform, or a template stored on a document management system.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我不熟悉 Nintex Workflow，但是如果您的活动目录信息在组织结构和用户详细信息方面是最新的，组，SharePoint 可能支持开箱即用的组织结构。
因此，可能剩下的就是工作流组件，该组件可能再次使用标准 SharePoint 功能创建，并使用 SharePoint Designer 进行少量自定义。
话虽如此，配置和安装 SharePoint 并不简单，需要一些思考。
I'm not familiar with Nintex Workflow however if your active directory information is up to date, in terms of the organisation structure and user details & groups, the organisation structure is probably supported out of the box by SharePoint.
Thus all that might remain is the workflow component which again could probably be created using standard SharePoint functionality, with minor customization with SharePoint Designer.
Having said that, configuring and installing SharePoint is not simple, and needs some thought.
根据我使用 Nintex Workflows 的经验，它可以很好地集成到 SharePoint 中，并且可以在分层的公司组织结构中工作。如果 Active Directory 正确设置为指示“老板”、“下属”等，则可以在工作流程中使用此信息。例如，“将此工作流发送给我的老板”，然后是“将其发送给他的老板”，编程起来很简单，因为该信息可以从 Active Directory 中获得。
根据需要，标准 OOB SharePoint 和 Nintex 可以一起使用来产生令人惊叹的工作流程。使用 Nintex Workflows 的主要优点之一是无需编程即可使用。但是，如果程序员可用，则可以添加额外的逻辑来增强工作流程（例如事件级编程）。
From my experience with Nintex Workflows, it integrates really well into SharePoint and would work in a hierarchical company organization structure. If Active Directory is correctly set to indicate "bosses", "subordinates", etc, this information can be used within the workflow. For instance, "Send this workflow to my boss", followed by "send it to his boss", would be simple to program, since that information would be available from Active Directory.
Depending on what is needed, standard OOB SharePoint and Nintex can be used together to produce amazing workflows. One of the major advantages of using Nintex Workflows is that it can be used without programming. However, if programmers are available, additional logic can be added to augment a workflow (such as event-level programming).