Process Engine Design Ideas

foreword

  In the modern enterprise management mode, a set of process-based operations will be formed through accumulated experience to meet the daily business activities of the enterprise, which can not only standardize work requirements, but also improve personnel work efficiency. It is often said that a process-based working model is a sign of a company's maturity, so in the process of enterprise information construction, the process engine is also an indispensable part.

Application Scenario

  In our daily work, we often use some system functions implemented by the process engine. Below I will enumerate some common application scenarios to deepen your understanding of the process engine.
  In the recruitment process of enterprises, the selection of candidates, interviews, and employment are all critical and important, and the mode is relatively fixed. Enterprises often use process systems to manage and control the entire process of recruitment activities. The whole activity is roughly as follows: HR will select a suitable resume, upload the data in the system and initiate the process. Each interviewer will receive the notification of the process review node and interview the candidate. After the interview is completed, the process will be completed. Fill in the corresponding interview results. If the interview is not passed, the process will be terminated. If the interview is passed, the process will continue to be executed and the next interviewer will be notified to conduct the interview. Finally, after all interviews are passed, the process will return to HR for approval. After the offer is issued by HR, the closed loop of the recruitment process is carried out.
  In work travel activities, we often need to inform the relevant leaders and colleagues of the travel activities before the business trip, and ask HR to follow up on attendance. At the same time, the leaders also need to approve the rationality of the travel. At this time, It will be time-consuming and labor-intensive to communicate offline, so most companies also control travel activities in a streamlined manner. The whole activity is roughly as follows: After the business traveler fills in the travel reason and budget, he initiates the travel application process, and the process approval node is notified to the corresponding leader. The leader reviews the travel reason and budget. If the travel reason is unreasonable or the budget If the budget is exceeded, the approval will not be passed, and the process will be terminated. If the final process is approved, HR will follow up the attendance matters, and the business traveler will perform business travel activities, and the process will be closed.
  In office collaboration activities, a job needs to be completed by multiple departments. At this time, it takes a lot of time to find people to communicate and advance. Therefore, many companies will implement process control for some solidified multi-department collaboration work. The whole activity is roughly as follows: the initiator of the work fills in the background reasons and supporting work content to initiate the process, and the approval node of the process is notified to the leaders of each department, who will review the rationality and content of the work. If passed, the process will be terminated. If the review is passed, the corresponding executor of the department will be assigned to complete the work. After receiving the process, the executors of each department will feedback the completion of the department's matters in the process, and control the work through the progress of the process. The progress of the process, if the collaborative work is finally completed, the process will be closed.

Business needs

  According to the application scenario described above, we can analyze and obtain the following business requirements:
  Requirement 1: The process engine needs to support adding any number of approval nodes in order. The approval nodes form a linked list, add approvers under the corresponding approval nodes, and record The current review node and the approver, when the approval is completed, the approval node moves backward one, and the process ends when the corresponding approval of the process end node is completed.
  Requirement 2: It is necessary to support the process approval and rejection function, and support the rejection to the specified process node.
  Requirement 3: The initiation form and approval form can support customization and set different form contents.
  Requirement 4: It is possible to record the approval information of each approval link, which is convenient for traceability and statistics.
  Requirement 5: It is necessary to support the setting of countersigned approval nodes, that is, multiple people can be added under one approval node, and the next approval node can only be entered after multiple people are approved.
  Requirement 6: It is necessary to support the setting of parallel approval nodes, that is, under this approval node, as long as one approver passes the approval, it can jump to the next approval node.
  Requirement 7: The process needs to support condition judgment (such as the leave process, the number of leave days is different, and the execution process is different), and different approval processes are executed according to different conditions.

Design

Overall solution

  The functional architecture diagram and information structure diagram are shown in the following figure

insert image description here
insert image description here

Demo design

   Demo design can refer to

Process Engine Page Demo

Guess you like

Origin blog.csdn.net/qq_40664711/article/details/125363452