Business Process presentation,

I remember how to use the functional modules of the process to display the business process many years ago when I demonstrated the process in the workflow management center.

The traditional way is to create a business table based on business documents, and then add some status fields to control the flow of documents to complete the business process.
For example, a procurement application process:
Create Table Structure fields according to the purchase order;
Formulate the purchase order module;

The document prepared by the buyer will be transferred between different departments of the seller, and it will be controlled through the added Status field:
1. Application Status; 2. Delivery status; 3. warehouse stock-up status; 4. Delivery status; 5. Delivery in transit; 6. acceptance by the buyer; 7. completion; 8. Cancellation
Create a module based on each status. The main function is to list records by status and modify the current status to the next status.

Mount the completed modules to the menu and assign them to the role. After logging on to the system, the operating user executes the menu function based on the assigned permissions to complete the procurement business process one by one.

After a workflow system is used, the development of a procurement process is greatly changed.
First, create a business table based on the purchase order, or add a Status field (but the added Status field is not used to control the flow)

Establish a business flow between different departments based on the purchase application form:
Purchase Order (buyer)-seller approval-warehouse preparation-delivery-buyer acceptance

 

Then, according to the above business flow, use the custom form tool to make the corresponding business form
Create purchase order
Seller approval
Warehouse stock-up
Delivery and delivery
Buyer acceptance

These nodes all have business forms. You can make a form that shows the content of a purchase order,
When creating a purchase order, the buyer can fill in the purchase order. Other information is invisible.
When the seller approves the purchase order, the seller can modify the content of the Purchase Order, and send the content to the warehouse at the same time to invalidate these two functions.
When warehouse stock-up, you can only view the content of the purchase order and add the confirm delivery and out-of-stock functions.
During delivery and delivery, you can only view the content of the purchase order and add the delivery function.
When the buyer signs the order, he can only view the content of the purchase order and add the buyer's receipt function.

 

The developed form is attached to the node of the business process. At the same time, set some business data as the action result conditions of the process.

After the configuration is complete, this process is developed, just like using the state for hard coding to complete this business process. Only the business processes completed by the workflow system are transferred in the XML file of process modeling, and the Status field is no longer needed to control the flow.
The Status field is used only for business data. It is used to show the current stage. In fact, the track chart of the process instance is used to show the current stage more clearly.

(Trajectory chart)

How can the procurement application process be presented in this way? I was confused .....
Confused 1: The purchase application process is directly attached to the menu. Click it to open the purchase order? Or do I create a common module. Every time a new business flow is added, it is listed according to the name of the business flow. Click one to start a business flow instance?

Confused 2: The process instance id is obtained through initialization first, and then the form associated with the first node is opened; or is the process instance id obtained when business data is submitted first?

Confused 3: How does one process the second node of the Process instance and wait for the third node? Is the menu directly suspended or executed through a common module?

I still remember that these problems had plagued me for a long time. After many discussions, I made them into a general workflow module that triggers a process instance to display the process.
The functions of the Process Management Center focus on workflow.
Confused 1: The solution lists all business processes.

Confused 2: the solution is used to START process instances in the Process Management Center. The process instance id is initialized first, and then the node that executes the process opens the business form associated with the first node.

Confused 3: handling of the second node of the Solution Process instance, through the to-do task list, handling tasks associated for execution. Nodes that do not have task information defined are associated with the execution of actions through the process instance.

If you need to customize a menu, such as creating a purchase order. In addition, you need to open the document and click submit before executing the initialization process, then you can only customize the development.
Custom development is achieved by calling the Process Engine API.

------------------- I am upgrading the separation line ^_^ else ----------------------------------------------------------------------------------------------------------

As we continue to upgrade and implement custom development for users, we finally understand. In implementation, it should be the workflow universal module trigger process instance and the user-defined implementation process instance. Both methods should be provided, and the general implementation module and call module should be well implemented.

 

When testing the running process, it can be triggered by a common workflow module.
When the real release process is officially run, you can modify several parameters to switch to the custom implementation method. For example, click "create purchase order" to open the menu. After the user completes filling out the information, submit the form data and start the process instance together.

Implementation Method, To be continued... it's too late today, and it will be resumed in another day.