Introduction to Workflow Technology JBPM Development (IV)--The discovery of Mind Touch (2)

For this workflow is really the process of continuous deepening, the total feel can not understand, impossible to achieve the requirements, now it appears in front of you, sincerely let you laugh and cry!

Let's talk about the advantages of using workflow:

1 , Process management business (remember)

2 to easily respond to business changes (business node and process separation)

3 to realize the reuse of the process and the reuse of the node.

4 , document process tracking process

5 , maintenance of state, etc.

have been saying that to use the process to manage the business (control of the business process), each node of the workflow does not know what to do next, do not know what the business wants to do, but just according to the order of the process execution, as to what to do I do not care.

Understanding misunderstanding:

for WF4.0 Workflow , each node is developed by our developers themselves, simply to develop the business node, to achieve the corresponding business functions, and then the abstract step is that we will all the business node abstraction, so that an abstract business node can be reused by all business. So it's easy for us to understand the abstract nodes and then we need to use the workflow to drag the nodes into the workflow, and then the nodes are managed by the workflow, and all we have to do is develop the node pool and implement what we call the workflow without knowing what to do, but to control the execution of the business process.

well, again. JBPM , made a JBPM after the instance, feel jbpm There is no common node to develop, because I drag directly into the process of the task, do not need to write what code, only need to assign to someone, or bound on some forms, these are just some properties of the settings, do not need to develop what node AH? So it's always confusing to develop a node pool. And in the process of implementation, we are constantly thinking, what does the workflow bring to us? Do it, the way to achieve it is like this (described below), we can see what the problem!

Implementation method:

1 , first, I abstracted all the methods that invoked the workflow for all business use (Implementing a workflow method reuse)

2 , for the well-painted flowchart, the workflow engine will give us the implementation, according to the flowchart of automatic execution, do not need us to implement what

3 , each node's operator and action page is configured for each of the process nodes

4 , each business requires a workflow operation that can be invoked (interoperable), and the specific business is doped with workflow methods.

Implementation features:

1 , the changes to the flowchart (business) are addressed for the business that has applied the workflow.

For example:

the order of the flowchart is: Start --- request to revise course information -- Guide Approval -- Teaching Secretary Approval -- End

modified to: Start -- request to revise course information -- Supervisor Approval or monitor approval --- Teaching Secretary Approval -- End

We don't need to re-modify the code for this business process change, the only thing to do is to deploy a new process to

Because all process processing is handled and documented by the workflow (forms and personnel designations are available)

2 that records the flow of the process.

3 , for this business, no matter how I change my business, the workflow can help us deal with it (and treat other businesses as well)

So we thought we were done, really? Of course not, only to say we are limited!

So, what else is wrong? Isn't that what we need? Where's the problem? Deal with change, record circulation. When this step was done, I really thought it was all over, everything was OK , but I didn't understand what the teacher said about the development node pool, and the workflow didn't know what I was going to do next. At this point we only see the change that can deal with the current business, seemingly realized the idea of the workflow, but did not stand at a higher level to think.

The following article continues to introduce the above questions

Introduction to Workflow Technology JBPM Development (IV)--The discovery of Mind Touch (2)