K2黑珍珠工作流系统设计最佳实践

3星 · 超过75%的资源需积分: 9 53 浏览量更新于2024-07-29 收藏 749KB PDF 举报

"该文档是关于K2 BlackPearl工作流系统的最佳实践指南，涵盖了从选择、设计到部署和维护过程驱动应用程序的建议和指导。文档由经验丰富的BlackPearl设计师的方法提炼而成，并将随着更多最佳实践的发现而更新。主要内容包括：声明式模板、动作与结果、智能对象的安装配置安全、智能对象设计最佳实践、流程选择以及流程设计最佳实践，如项目结构、命名规范和图形化设计推荐等。" 在设计工作流系统时，K2 BlackPearl提供了一套全面的方法论来帮助用户实现高效的过程管理。以下是其中的关键知识点： 1. **声明式模板(Declarative Templates)**: 这是一种定义流程逻辑的方式，允许设计者以声明性的方式指定流程的行为，而不是通过编写大量代码。这种模板简化了流程设计，使得非开发人员也能理解和修改流程。 2. **动作与结果(Actions and Outcomes)**: 动作是流程中的操作，而结果则表示这些动作的预期影响。理解并有效地使用动作和结果可以确保流程的可预测性和控制性。 3. **智能对象(SmartObjects)**: 智能对象是K2中的核心组件，它们封装了业务逻辑和数据，可以作为流程中的交互点。设计良好的智能对象能提高流程的复用性和灵活性。 4. **安装配置和安全(K2 BlackPearl Installation, Configuration, and Security Best Practices)**: 安装时需考虑服务器的配置和安全性，以确保系统的稳定运行和数据保护。这部分涵盖了如何正确设置和配置K2环境，以及实施必要的安全措施。 5. **智能对象设计最佳实践**: - **业务对象为中心(Business Object Centric)**: 以业务对象为中心的设计强调将业务逻辑和数据紧密集成，优点是直接反映了业务实体，但可能导致过度复杂化。 - **流程为中心(Many Process Data Fields)**: 这种方法将数据字段集中在流程中，有利于流程控制，但可能增加数据管理的复杂性。 - **InfoPath为中心(Everything in the InfoPath XML field)**: 使用InfoPath表单，所有数据都在XML字段中，提供灵活的用户界面，但可能造成数据不易管理和维护。 6. **流程选择(Process Selection)**: 在设计流程时，应根据业务需求、参与人员和基础设施条件进行选择。流程问题涉及流程的目标和复杂性，人员问题关注用户角色和参与度，基础设施问题则涵盖技术环境的兼容性和扩展性。 7. **流程设计最佳实践(Process Design Best Practices)**: - **项目结构(Project Structure)**: 保持良好的项目组织结构，包括命名规则，有助于提高代码的可读性和团队协作。 - **图形化设计推荐(Graphical Design Recommendations)**: 使用图形化工具清晰地展示流程逻辑，使流程易于理解和维护。 - **源代码控制(Source Control)**: 引入源代码控制系统，如Git，可以跟踪版本变化，协同编辑，防止冲突，保证流程设计的版本管理和追溯。设计K2 BlackPearl工作流系统时，应遵循这些最佳实践，以提升流程的效率、可维护性和用户体验。同时，持续学习和适应新的最佳实践，是确保系统长期成功的关键。

PAGE 7

 User Base – Where will users be coming from? Within the network, over VPN, from the Internet

or a three? Will all these users have accounts in Active Directory or is another user store

required?

 Domains – How many domains are there? Where will the K2 server reside and which domains

will it interact with?

 Trusts – What trusts are existent between the identified domains? Are there any one-way trusts

which will block K2 Active Directory User Manager (ADUM) from carrying out LDAP queries?

 Forests – If there are there multiple forests involved, is there forest trust to allow Kerberos

tickets? Two-way forest trusts are usually required but it depends on where users and other

required resources are located. Contact K2 support if you do not have a two-way trust established

and your K2 server cannot authenticate some users.

 Functional Levels – What level do the domains and forests run at? Do you require any of the

features provided by a native Windows 2003 level?

SMARTOBJECT DESIGN BEST PRACTICES

Ideally in K2 blackpearl, the focus for process design is centered on a business object approach. All items in the

process are evaluated on how they interact with these business objects, in this case SmartObjects, and what the

data represented by these business objects means to the business itself. Where the process intersects the

business data should become evident during the process discovery phase of the project, and will represent the

critical results of processes activities and events.

An individual process is broken down into its smallest business components. These components are then used as

the data source of the following components:

PAGE 8

 All rules of the process

 User Interfaces

 Reports

The SmartObjects are then mapped to their appropriate backend systems via SmartObject Services. This allows

changes to the back-end system at any point in time without affecting the business application. When using the

SmartObject Services shipped with the product, no code needs to be written for read and write access to backend

systems. Custom SmartObject Services, often referred to as Service Objects, can also be written to talk to various

backend systems that do not have a corresponding SmartObject Service that ships with K2 blackpearl.

Note: The Active Directory service objects that ship with K2 blackpearl 0807 do not allow updates to Active

Directory. There is a service object available on K2 blackmarket that allows updates

(http://k2underground.com/k2/ProjectHome.aspx?ProjectID=3).

Using SmartObjects in this manner allows a process to store nothing but a reference to a SmartObject ID in the

process data fields, which abstracts data from the process and offloads work from the K2 workflow server. Using

this one data field, a SmartObject Reference can be made in the process definition. This SmartObject reference

becomes a re-useable object in the process definition which, in turn, is employed in line rules, start rules,

escalation rules, destinations and the like. As a benefit of abstracting data from the process, the process becomes

more lightweight in terms of instance data handled by the server and database storage needs as well as

permitting this business data to be more easily leveraged outside of the process.

Follow your company's naming conventions when defining properties and methods in your service objects, and

provide understandable descriptions for service type properties and methods, since these are surfaced to users

that need to design SmartObjects that consume these methods and properties.

SmartObjects are developed once the underlying service types have been registered on the K2 server and an

instance of the service type created. This instance registration is accomplished through the K2 Workspace, and

can also be accomplished with the BrokerManagement.exe tool that allows you to supply a specific service

instance GUID for each custom service type.

You might choose to keep all SmartObjects within separate solutions based on the service types, but since

SmartObjects do not necessarily have to be bound to a specific service type, this approach may not be logical. A

single solution for all SmartObjects may be a better approach, as you can ensure consistency and avoid naming

conflicts, duplicated and overwritten SmartObjects, and to centralize the deployment of SmartObjects. Where this

is not possible, develop groups of SmartObjects, each within a single solution, using an approach that makes

sense to your business, but try to avoid having any single SmartObject contained within multiple groups. A hybrid

approach that may work in your environment is to develop all business-related, common SmartObjects in a single

solution, and have separate solutions for application-specific SmartObjects.

With the single solution approach, developers are able to work on individual SmartObjects at the same time,

although deployment requires them to „exclude‟ SmartObjects they are not currently designing.

Note: When deploying SmartObjects, K2 will automatically create a Category for the project name and sub-

categories for each of the folders in the project. By including all SmartObjects in a central solution, you can

ensure that SmartObjects are logically grouped, named and deployed to the K2 category system.

There are two more important things to remember when designing SmartObjects.

 K2 provides two mechanisms to retrieve data from SmartObjects: The.NET Data Provider for

SmartObjects (a standard ADO.NET data provider) and the SourceCode.SmartObject.Client API. Each

剩余36页未读，继续阅读

富商大贾

粉丝: 0

K2黑珍珠工作流系统设计最佳实践

工作流管理系统详解：工作流与表单设计

基于JAVA的集成型工作流引擎设计与实现

Activiti5定制中国式工作流系统开发手册

驰骋工作流引擎CCBPM系统概要设计与功能解析

jBPM工作流应用开发入门：工作流管理系统解析

web工作流设计-myflow

C#完整工作流系统源码(vs2005)

群友分享的FLEX工作流设计器(含源码)

SpringBoot结合Flowable打造高效工作流系统

Activiti6.0工作流设计与使用指南

最新资源