The timeless path to the process (iv) the implementation phase of the BPM lifecycle

In the previous article, we talked about the lifecycle of BPM including design, modeling, execution, monitoring, and optimization 5 phases, and this article gives a detailed anatomy of the implementation process of BPM in the main line of the pre-sales license approval process for the housing industry.

Execution analysis of 1.1.1 Pre-sale license Mainline process

Processes in BPM include executable processes and non-executable processes. Non-executable processes occupy a very important place in the enterprise, including strategic processes, planning processes, and management-level processes, and most of the current BPMS suite only implements support for the executable processes in BPM and does not support non-executable processes. Some vendors support the Business process in BPM through products called BPA, which refer to the Aris and Control-es products in section 8.3.1.1. Let's look at the executable process first, and before we go through the process, we'll analyze the composition of the process. From the modeling period of the process definition, the process consists of multiple active nodes (in BPMs, this active node can generally continue to be decomposed into sub processes) according to a certain pattern of a transfer sequence, the specific composition of the analysis is as follows.

1. Executable Process Composition Analysis

The process composition of BPM is shown in Figure 1.

Figure 1 The end to end of the pre-sale license approval business process diagram

The dotted box in the figure is the graphical composition of the process, which can be seen as an End-to-end pre-sale license approval business process. To run this process, you need to hook up some resources on the process attributes (the entire process) and link attributes (on each link) and configure some properties. There are both business and technical aspects of these attributes.

Process Properties

List of recipient names: This property describes what documents are required to handle a pre-sale license. Just like when you go to a bank for a credit card, you need to provide ID card, income certificate, real estate, car proof and so on. Different business processes require different proof materials, so this property is configured as a process attribute. Some might say that this attribute is a business attribute, how can it be treated as a process attribute? Yes, the list of recipient names is indeed a business attribute, and for a completely closed, general-purpose BPM product, it is certainly not developed as a process attribute to develop BPM products, but for industry process products, it is a technical matter to deal with as process attributes, because it is easier to use.

This property is essentially a business attribute, although it is encapsulated as a process attribute by the industry process product, but is defined by the business staff when it is used.

Composition implementation of process definition

(1) Custom process definition specification

You can specifically define a collection of properties for the process to store the name of the recipient data. As follows:

<process>
<requiredDocs>
        <doc> name </doc>
        <doc> name </doc>
     </ requireddocs>
<activities>
    <activity>...</activity>
</activities>
<trasitions>
    <transition>...</transition>
</transitions>
</process>

(2) Implementation in the BPMN 2.0 specification

In the BPMN 2.0 specification, the extensiondefinitions extension mechanism can be used to store related attributes on the business that need to be bound to the process definition, such as the name of the recipient in this example. However, when this property is extended, this BPMN 2.0 process is no longer a common process. When swapping to other BPMS products that conform to the BPMN 2.0 specification, the Extensiondefinitions property cannot be exchanged. That's why we've said many times that we don't want products that follow the same specifications to be compatible with each other. If it is really compatible, it must be a lab product, because any vendor will take the customer's requirements as the first element, and will inevitably add a lot of specifications on the basis of the specifications allowed by the extension.

In addition to taking advantage of the Extensiondefinitions attribute, you can define a single relational table, which is the relational table of the process definition template name and the collection data set. This also enables you to bind the list of recipient names to the process.

Form: A form is a key point of contact between a business and a process, and is a necessary attribute of the process. Especially in MIS information system, the main work of the business staff is to do the related work through the form (input data, scan the attachment, edit the processing, fill in the examination and approval opinion, print, statistics, query, etc.). The whole business process, summed up is the staff of different positions, in different business links, through different business forms for different operations. The business process is driven by processes, so each business process must establish a binding relationship with its corresponding business form. For example, the pre-sale certificate approval process must be bound with the business form of the presale certificate declaration. It's important to note that if you bind a form to a process, the corresponding business scenario can only be that the entire business uses the same form in the process of moving through different links. This scenario is generally in a single system of workflow applications more (such as telecommunications, mobile work orders delivery, OA in the Leave list, etc.).

This attribute is a technical attribute, but if it is simple enough to be easy to use, it can be defined by the business person (for example, by providing a single list of selectable forms with sufficient business implications for the form name to be bound by the business person's selection).

Composition implementation of process definition

(1) Define the process definition language yourself

<process>
<form  id= ' url= '/>
</process>