Rdiframework.net━. NET rapid Information System development framework-Introduction to Workflow components

rdiframework.net - . NET Development framework of rapid information system

Introduction to Workflow Components

Rdiframework.net, based on the. NET Rapid Information system development, integration framework, to users and developers the best. NET Framework deployment scenarios.

1 , rdiframework.net Framework Introduction

Rdiframework.net, based on the. NET Rapid Information system development, integration framework for enterprises or individuals in. NET environment, the rapid development system provides strong support, developers do not need to develop the system's basic functions and public modules, the framework itself provides a powerful library of functions and development package, developers only need to focus on the development of the business sector, so greatly improve development efficiency and save development costs. The framework is developed using the most mainstream C # language, supporting a variety of database types and supporting WinForm and the Web. The use of rdiframework.net can improve the overall quality of the management software system, improve the compatibility between modules and modules, improve the reuse of code, make the software system architecture more reasonable, the quality is more perfect, so that the maximum extent of labor results re-use.

2 , rdiframework.net Work Flow Components

Rdiframework.net Framework V2.8 The following versions do not contain workflow components, in the actual use process, many customers have asked us to provide a framework for the work flow ideas, finally after months of fighting, in the V2.8 version began to provide support for the workflow.
The Rdiframework.net workflow component is supported by the Rdiframework.net framework, based on our years of Project experience and project practice, combined with a set of process management components developed with the characteristics of major domestic workflow products. This component takes into account not only the construction of a business system from zero, but also the integration with existing business systems. From a zero-build system, we can use the Rdiframework.net framework to build a business system quickly. With the integration of existing systems, our process engine provides a rich functional interface for three-party business system calls, and provides the full source of components for user-friendly integration. The Rdiframework.net Workflow component takes the SOA architecture pattern and the process engine supports WCF-mode access. Support B/S/C system, support SQL Server, Oracle and other mainstream databases.

The Rdiframework.net━ Workflow component mainly covers the design and definition of workflow, the initiation and operation of process instances, the monitoring and management of business processes, the integration and collaboration of workflow components with business systems, and so on.

2.1 , functional characteristics

The Rdiframework.net━ Workflow component has the following characteristics:

1, the perfect combination with the rdiframework.net framework, support b/S, c/s system, SQL Server, Oracle and other multi-database type support, while you can use the framework itself provides all the service interface.

2, customizable forms: In the BS structure, the user can freely develop UserControl, and through the process management tools to establish the form and the business platform, the form can flow in the system. In C/s structure, components load different function modules by dynamically loading DLLs or EXE files, which facilitates software management and upgrading.

3. Distributed Process Engine: a truly SOA-oriented architecture (service tiers can be deployed as WCF, Windows service, WEB service, remote, etc.), providing standard WCF interface calls that enable remote invocation, distributed deployment. The rich development interface, the user can realize the process initiation, the flow and so on by invoking the interface in the program.

4, the Process engine support complex business flow: independent research and development of the process engine, taking into account the characteristics of domestic users, support complex and changeable flow, simple flowchart configuration, business logic at a glance. Organization, processor and position distribution close to the user enterprise.

5, Process Designer: Visualization of the flowchart production tools, what you see is the resulting production flowchart, and you can export the flowchart to an XML file, you can also import the process from the XML file.

6, with the existing system integration: can be easily integrated with the system, you can call the process engine interface to integrate the process functions into the current business system, and the user's original system only a few changes can be. The process engine is all represented by an interface, with 2 features: Business agnostic, program structure agnostic. That is, to adapt to any business system, and adapt to B/S and C/s structure of the program, as long as the corresponding interface method can be called.

7, Instant Messaging: Instant Messaging can help online and offline users to get process notifications in a timely manner, convenient implementation of collaborative work.

8, Process Statistics Chart: Can statistics process task processing situation, study task processor work efficiency, achieve performance appraisal, and can monitor the other state of the process to facilitate decision-making.

9, easy to understand the code, suitable for common design patterns, comments in detail. Provide all the design documents, source code implementation, supporting documentation, can be reused in different software projects, improve work efficiency. Provide perfect interface function call description, open Interface, open source, open database structure design. Fully support the end user's personalized 2-time development needs, can be reused in different software projects, improve work efficiency.

10, other.

2.2 , Process designer

Before starting, introduce the current market on the flow of the design of several forms, is nothing more than two forms of a B/s, a C/s, personal feeling these two forms do not need to be demanding that one, each has advantages and disadvantages, b/s without the installation can be used directly, but the operating flexibility than C/s, B/ S process designer currently has several technologies to implement, one is JS, one is Silverlight or Flex, and the other is an ActiveX plugin. Process Designer is generally the administrator, the implementation of the use of users, the user group is relatively single fixed, but the use of higher requirements, it must be convenient and flexible, so our process designer using the C/S method, combined with the framework provides a variety of services, absolutely no pressure on the B/s process designer.

Process Designer is the tool to edit the process template, the visual process designer can intuitively edit the process template, WYSIWYG, the process template to store the flow of information needed to use the process designer to manage the process template is a more common way, As the process designer for the Rdiframework.net━ workflow component:

2.3 , Process engine

The design of a very flexible engine to meet any complex business needs, so that the end user through the modification of flowcharts, configuration of business forms to complete the process reengineering, no need to modify the program code, the process engine can flow according to the new template. Process engine set up 6 types of task nodes, basically can complete any situation of the spread, for example, sign, approval, according to business conditions flow, etc., process engine design independently, provide external interface, can be integrated with any system. The Rdiframework.net━ Workflow component process engine provides the following basic functionality.

1. Sequential flow: Like sending an email, work flows to the next handler, handling the same view of tasks and processing tasks as a person handling a message.

2, conditions of circulation: according to business data, to meet the different conditions of the transfer to different processing people. For example, the purchase amount of more than or equal to 100,000 of the purchase order to flow to the general manager, less than 100,000 of the purchase order to transfer to the manager.

3, the task back: In the leadership of the approval process is not satisfied with the results, the need to return to the previous task handler, let him re-processing and then submit.

4, the task of the sign: to some of the work requires a number of leaders are signed to perform the task, set the task of the leader, the leaders involved in the approval, the task can continue to flow downward.

5, Task merging: Multiple tasks flow to a task summary process

6. Task Timeout Reminder: When the task exceeds the set time, the task performer or designated person is alerted.

7, the mandate: May authorize a person to temporarily own the business execution right.

8, Task assignment: When the task flows to itself, we can assign someone to perform this task.

9, Support shared task processing: Many people have the right to handle the task, can see the task, not one of them to deal with, the other people will not see the task.

10, support recall: can be recalled before the next task is processed.

11, Support sub-process (process nesting).

12, support multi-boot node: In the process is basically the same as the beginning of the task is not the same, you can take advantage of multiple start nodes and create a more process.

13, simplify the task node type to achieve complex flow: rdiframework.net Workflow components of the Task node type is deep induction and abstraction, type less functional, flowchart closer to the actual business process, no redundant nodes, at a glance, what you see is the income.

14, Task arrival notification: When the task is reached, the task performer or designated person to remind.

3 , rdiframework.net Business Collaboration Platform

The Business collaboration platform is the working platform of the process system interacting with the user, and all the business forms are presented through the platform, where the user processes the daily business (initiating tasks, processing tasks, viewing the tasks involved, and viewing the status of the process). Users do not have to care about how the process flows, as long as the processing of their own business forms, the task will automatically flow to the next processor according to the conditions. The business platform supports both WinForm and WebForm in two different ways.

3.1 , WinForm Collaborative Platform 3.3.1, daily business

The "Daily Business" module focuses on the list of business processes that the current logged-on user can initiate. The process engine automatically loads the list of processes into the available business tree based on the business process that the current user can start. The main interface of the "daily business" module is as follows:

3.1.2 , unclaimed Tasks

Before you handle a task, you must first claim the task. Claim the task to the "Unclaimed Tasks" main interface to claim, as shown in. Select the task you want to claim and click "Claim task" to claim the selected tasks, the claimed task entered the "to Do" list. We can also make precise or fuzzy queries by business name and task time.

3.1.3 , to-dos tasks

The "To do" module is where we really deal with the business, and the claimed tasks go to the "to Do" list, where we can search for to-do tasks, process the selected tasks, discard the selected tasks, view the flowchart of the selected task, and view the processing records for the selected task. To-do task the main interface looks like this:

　　

3.1.4 , completed Tasks

When the task processing is complete, go to the Completed Tasks list, as shown in. In the completed task module, you can query the completed tasks by criteria, view the selected tasks, view the task flowchart, and so on.

3.1.4 , Process monitoring

Process Monitoring module is mainly used to monitor the implementation of the process, the interface through a different color display process of several states, such as: not implemented, is processing, the normal end. In the process monitoring main interface, we can combine conditions to search the business process, while also viewing the status of the selected business process and processing records. The process monitoring main interface looks like this:

3.2 , Web Collaborative Platform 3.2.1 , daily tasks

The "Daily Business" module focuses on the list of business processes that the current logged-on user can initiate. The process engine automatically loads the list of processes into the available business tree based on the business process that the current user can start. The main interface of the "daily business" module is as follows:

3.2.2 , unclaimed Tasks

Before you handle a task, you must first claim the task. Claim the task to the "Unclaimed Tasks" main interface to claim, as shown in. Select the task you want to claim and click "Claim task" to claim the selected task. We can also make precise or fuzzy queries by business name and task time. First you need to claim the task. Claim the task to the "Unclaimed Tasks" main interface to claim, as shown in. Select the task you want to claim and click "Claim task" to claim the selected task. We can also make precise or fuzzy queries by business name and task time.

3.2.3 , to-dos tasks

The "To do" module is where we really deal with the business, and the claimed tasks go to the "to Do" list, where we can search for to-do tasks, process the selected tasks, discard the selected tasks, view the flowchart of the selected task, and view the processing records for the selected task. To-do task the main interface looks like this:

3.2.4 , completed Tasks

When the task processing is complete, go to the Completed Tasks list, as shown in. In the completed task module, you can query the completed tasks by criteria, view the selected tasks, view the task flowchart, and so on.

3.2.5 , Process monitoring

Process Monitoring module is mainly used to monitor the implementation of the process, the interface through a different color display process of several states, such as: not implemented, is processing, the normal end. In the process monitoring main interface, we can combine conditions to search the business process, while also viewing the status of the selected business process and processing records. The process monitoring main interface looks like this:

3.2.6 , I am involved in the task

The main interface of my task is as shown in:

4 , rdiframework.net Series Articles

Rdiframework.net-based on. NET rapid Information System development Framework-Series catalogue

Rdiframework.net━. NET rapid Information System development Framework-Workflow component WinForm Business platform
Rdiframework.net━. NET rapid Information System development Framework-Workflow component Web business platform

Example demonstrates how to define a business process using the workflow component of the Rdiframework.net framework-leave application process

Rdiframework.net━. NET rapid Information System development framework-Introduction to Workflow components