CN117933950A - Automatic business process approval method, equipment and medium - Google Patents
Automatic business process approval method, equipment and medium Download PDFInfo
- Publication number
- CN117933950A CN117933950A CN202410338549.5A CN202410338549A CN117933950A CN 117933950 A CN117933950 A CN 117933950A CN 202410338549 A CN202410338549 A CN 202410338549A CN 117933950 A CN117933950 A CN 117933950A
- Authority
- CN
- China
- Prior art keywords
- rule
- business
- approval
- execution
- thread
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 243
- 230000008569 process Effects 0.000 title claims abstract description 211
- 238000001514 detection method Methods 0.000 claims abstract description 68
- 238000004458 analytical method Methods 0.000 claims abstract description 40
- 238000010276 construction Methods 0.000 claims abstract description 15
- 238000005096 rolling process Methods 0.000 claims abstract description 12
- 238000004801 process automation Methods 0.000 claims description 13
- 238000012986 modification Methods 0.000 claims description 12
- 230000004048 modification Effects 0.000 claims description 12
- 238000003860 storage Methods 0.000 claims description 4
- 238000009826 distribution Methods 0.000 claims description 3
- 238000012545 processing Methods 0.000 claims description 2
- 238000004590 computer program Methods 0.000 claims 2
- 238000012544 monitoring process Methods 0.000 description 7
- 230000000694 effects Effects 0.000 description 6
- 238000011161 development Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 5
- 230000001960 triggered effect Effects 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 4
- 238000012795 verification Methods 0.000 description 4
- 238000010924 continuous production Methods 0.000 description 3
- 230000009471 action Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 238000013467 fragmentation Methods 0.000 description 2
- 238000006062 fragmentation reaction Methods 0.000 description 2
- 238000005457 optimization Methods 0.000 description 2
- 238000011112 process operation Methods 0.000 description 2
- 230000004044 response Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 238000002372 labelling Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000012827 research and development Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 238000010200 validation analysis Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44536—Selecting among different versions
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Economics (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- General Business, Economics & Management (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The embodiment of the application discloses a business process automatic approval method, equipment and a medium. Belongs to the technical field of information management, and solves the problems that the construction of an approval process is complex and cumbersome, and the service requirement is difficult to respond through an optimal execution path quickly in the prior art. The method comprises the steps of constructing a rule component based on service information; obtaining an initial business approval process through a business process designer and a rule component; responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of an initial business approval process until the process flow is transferred to an ending node, recording business process approval data, rolling back the current transaction to an initial state so as to complete pre-analysis of the approval process, and entering an execution stage; and performing execution information analysis in the execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
Description
Technical Field
The present application relates to the field of information management technologies, and in particular, to a method, an apparatus, and a medium for automated approval of a business process.
Background
At present, in business systems and management systems of banks, enterprises and the like, a large number of matters needing to be manually examined and approved by different departments, different posts and different roles exist, and an examination and approval process is generally constructed by introducing a workflow component so as to realize on-line examination and approval. But currently workflow components are generally defined directly based on the flow of BPMN (Business Process Diagram, business process modeling and labeling) specifications. In an actual project, a person with a certain professional ability usually needs to manufacture different workflow components and different development platform plug-ins, and then the online approval process is built by deploying the workflow components and the development platform plug-ins.
Along with the increase of approval links and the complexity and the variability of business requirements, the approval process also needs to be adjusted along with the business requirements. Such as regulatory organization adjustments, business management system adjustments, and risk management requirement adjustments, all involve related adjustments to the overall approval process. The existing approval process directly constructed based on the BPMN specification requires a business person with a certain professional ability to execute a series of links such as analysis, research and development, test, online, acceptance and the like according to related requirements, and can realize the adjustment and construction of a more complex approval process by combining with a system program. The construction of the approval process is complex and tedious, not only is the labor cost consumed higher, but also the business requirement is difficult to respond quickly through the optimal execution path.
Disclosure of Invention
The embodiment of the application provides a business process automatic approval method, equipment and medium, which are used for solving the following technical problems: in the prior art, the construction of the approval process is complex and cumbersome, and the business requirement is difficult to respond quickly through the optimal execution path.
The embodiment of the application adopts the following technical scheme:
The embodiment of the application provides a business process automatic approval method. The method comprises the steps of constructing a rule component based on service information; the rule component construction at least comprises the establishment of a triggering condition and the establishment of an executing operation after triggering; constructing a business process by a business process designer and business information, and obtaining an initial business approval process based on the business process and a rule component; responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of an initial business approval process until the process flow is transferred to an ending node, recording business process approval data, rolling back the current transaction to an initial state so as to complete pre-analysis of the approval process, and entering an execution stage; and performing execution information analysis in the execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
The embodiment of the application solves the problems of excessive fragmentation, incomplete communication and the like of the automatic application of the business process by creating and managing the automatic rules, thereby ensuring that the automatic rules of the process are more comprehensive. The pre-analysis process in the embodiment of the application is to truly execute rules, truly go to process operation, finally record the result of the real operation, and restore all data to the state before pre-analysis by transaction rollback, so that the obtained pre-analysis result is more real. In addition, the embodiment of the application optimizes and adjusts the rule according to the detection result so as to improve the execution efficiency and quality of the rule. Meanwhile, the rule base is maintained and updated to adapt to the change of service requirements and the development of technology. The verification, execution and monitoring of the business process automation rule in the embodiment of the application is a continuous process, and the correctness, reliability and stability of the automation rule are ensured.
In one implementation of the present application, rule component construction is performed based on service information, and specifically includes: constructing a trigger based on the service information, defining a triggering condition corresponding to the service flow automation rule, and determining an operation executed after triggering; the operation executed after triggering at least comprises modification of the attribute value of the linkage data object and creation of a work item task; the trigger is defined by an expiration date and a rule execution sequence.
In one implementation of the present application, a business process is constructed by a business process designer and business information, and an initial business approval process is obtained based on the business process and a rule component, which specifically comprises: receiving and processing service information through a service flow designer; according to the processed service information, determining a service scene and a service approval node to construct a service flow through a service flow designer; acquiring a rule component; the rule component comprises a preset rule for business approval; and carrying out different distribution setting on different preset rules based on different business approval nodes so as to generate an initial business approval process.
In one implementation of the present application, in response to a transaction start instruction, a rule component interface is invoked to execute an operation corresponding to a rule to modify data of an initial service approval process until the process flow is transferred to an end node, and the method specifically includes: responding to a transaction starting instruction, triggering a rule corresponding to an approval node, calling a rule component interface, and executing the rule and business logic corresponding to the rule; under the condition that the initial business approval process has no branch, directly entering the next node, triggering the rule corresponding to the next node and executing corresponding business logic; and under the condition that branches exist in the initial business approval process, performing branch judgment according to the preset condition execution rule until the process flow reaches an end node.
In one implementation manner of the present application, business process approval data is recorded, and the current transaction is rolled back to an initial state to complete approval process preresolved, specifically including: recording business process data and performance data; wherein, the business process data is related to business modification data in the approval process; the performance data comprises a total request number, a total call number and an average call number; and rolling back the approval process corresponding to the current transaction to an initial state so as to respectively return the business data and the process flow nodes to the state before pre-analysis, thereby completing pre-analysis of the approval process.
In one implementation manner of the present application, the execution information analysis is performed in the execution stage to detect each execution rule, and specifically includes: grabbing dump files in the execution information to obtain thread states; under the condition that the thread is in a Blocked state, determining the thread as a Blocked thread, and inquiring a corresponding Blocked source thread according to the lock information in the thread; under the condition that the thread is in wait or time-wait state, determining to suspend the thread, and marking that a resource bottleneck exists when the stack number of the like products is larger than a preset stack threshold value; under the condition that the thread is Runnable, determining that the thread can run or is running, and marking the thread with the occurrence frequency larger than a preset frequency threshold value in the same thread snapshot or different snapshots as the performance bottleneck content; based on different states of the threads, the execution speed of each execution rule is detected.
In one implementation of the present application, the method dynamically adjusts the initial business approval process based on the detection result, specifically includes: based on the detection result, determining a first to-be-adjusted execution rule with the execution speed greater than a first preset speed threshold; determining a second execution rule to be adjusted, wherein the execution speed of the second rule is smaller than a second preset speed threshold; starting a thread for the first to-be-adjusted execution rule so as to perform single-thread approval; and placing a plurality of second execution rules to be adjusted in the same thread, and sequentially performing approval.
In one implementation of the present application, after dynamically adjusting the initial business approval process based on the detection result, the method further includes: generating a new version rule component based on the dynamically adjusted rule, and setting a serial number of the new version rule component; based on the set serial numbers, ordering rule components of different versions to determine version modification tracks through the ordered rule components; determining a sub-rule component corresponding to the new version rule component, and carrying out component detection on the sub-rule component based on a preset sub-rule component detection condition; if the sub-rule component meets the detection condition of the preset sub-rule component, determining that the sub-rule component corresponding to the preset sub-rule is detected to be in a passing state, otherwise, determining that the sub-rule component is not in a passing state; determining the detection passing number corresponding to the rule component of the new version according to each detection passing state; determining the detection progress of the new version rule component according to the ratio of the detection passing quantity to the preset detection quantity corresponding to the new version rule component; and when the detection progress meets the preset detection progress, determining the new version rule component state as the component passing state.
The embodiment of the application provides a business process automatic approval device, which comprises: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executable by the at least one processor to enable the at least one processor to: based on the service information, constructing a rule component; the rule component construction at least comprises the establishment of a triggering condition and the establishment of an executing operation after triggering; constructing a business process by a business process designer and business information, and obtaining an initial business approval process based on the business process and a rule component; responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of an initial business approval process until the process flow is transferred to an ending node, recording business process approval data, rolling back the current transaction to an initial state so as to complete pre-analysis of the approval process, and entering an execution stage; and performing execution information analysis in the execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
The non-volatile computer storage medium provided by the embodiment of the application stores computer executable instructions, and the computer executable instructions are set as follows: based on the service information, constructing a rule component; the rule component construction at least comprises the establishment of a triggering condition and the establishment of an executing operation after triggering; constructing a business process by a business process designer and business information, and obtaining an initial business approval process based on the business process and a rule component; responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of an initial business approval process until the process flow is transferred to an ending node, recording business process approval data, rolling back the current transaction to an initial state so as to complete pre-analysis of the approval process, and entering an execution stage; and performing execution information analysis in the execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
The above at least one technical scheme adopted by the embodiment of the application can achieve the following beneficial effects: the embodiment of the application solves the problems of excessive fragmentation, incomplete communication and the like of the automatic application of the business process by creating and managing the automatic rules, thereby ensuring that the automatic rules of the process are more comprehensive. The pre-analysis process in the embodiment of the application is to truly execute rules, truly go to process operation, finally record the result of the real operation, and restore all data to the state before pre-analysis by transaction rollback, so that the obtained pre-analysis result is more real. In addition, the embodiment of the application optimizes and adjusts the rule according to the detection result so as to improve the execution efficiency and quality of the rule. Meanwhile, the rule base is maintained and updated to adapt to the change of service requirements and the development of technology. The verification, execution and monitoring of the business process automation rule in the embodiment of the application is a continuous process, and the correctness, reliability and stability of the automation rule are ensured.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings can be obtained according to the drawings without inventive effort for a person skilled in the art. In the drawings:
FIG. 1 is a flowchart of a business process automation approval method provided by an embodiment of the present application;
FIG. 2 is a schematic diagram of a rule creation front end according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a business process automation approval device according to an embodiment of the present application.
Reference numerals:
200 business process automation approval equipment, 201 processor, 202 memory.
Detailed Description
The embodiment of the application provides a business process automatic approval method, equipment and medium.
In order to make the technical solution of the present application better understood by those skilled in the art, the technical solution of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
The following describes the technical scheme provided by the embodiment of the application in detail through the attached drawings.
Existing group enterprise ERPs (EnterpriseResourcePlanning ) lack intelligent and automated functions such as automated billing, automated data statistics, automated flow control, etc. This makes it necessary for the staff to spend a great deal of time and effort for repeated manual operations, reducing work efficiency and accuracy.
The embodiment of the application creates correct, effective and efficient automation rules based on the service scene, provides a rule monitoring optimization system, advances process deployment, evolution and creation, and improves the automation level and efficiency.
Fig. 1 is a flowchart of a business process automation approval method provided in an embodiment of the present application. As shown in fig. 1, the business process automation approval method includes the following steps:
And 101, constructing a rule component based on the service information.
In one embodiment of the application, a trigger is constructed based on service information, trigger conditions corresponding to service flow automation rules are defined, and an operation executed after triggering is determined; the operation executed after triggering at least comprises modification of the attribute value of the linkage data object and creation of a work item task; the trigger is defined by an expiration date and a rule execution sequence. The rule component construction at least comprises trigger condition establishment and execution operation establishment after triggering.
Specifically, it is first necessary to fully understand the business processes of the enterprise, including the responsibilities and operation processes of each department and station, and to define the input, output and operation steps of each business link, and the related data and resources. Comprehensive understanding and analysis of business processes is the basis for automated rule creation.
Further, in the process automation tool, the rule is created according to the service requirement, and the rule is created in a visual and custom-selected mode.
Fig. 2 is a schematic diagram of a rule creation front end according to an embodiment of the present application. As shown in fig. 2, firstly, a trigger is to be determined, a trigger rule corresponding to the automation rule of the business process is defined, secondly, a rule trigger condition is to be determined, and operations to be executed after the condition is met, including modifying a certain attribute value of the linkage data object, creating a task of a work item, and the like, are required. In addition, defining expiration dates, rule execution orders, etc. should be supported in the rules.
Further, the automation tool matches the business field rules, association rules and dependency rules in the automation rule base according to a rule engine algorithm, automatically makes a decision according to data transmitted by the rule assembly, is driven according to the automation business process rules, registers as an RPC (Remote Procedure Call ) interface for process call, and realizes the intelligent operation of the business process supported by the engine.
For example, for an automated tool assembly:
A trigger: the automation rule is triggered by the generation of an event;
Conditions are as follows: a complex set of conditions may be defined to manage when an operation should be run. These conditions are typically based on the attribute state OR value of the event AND its entity, AND may contain AND/OR/NOT/CONTAINS operators;
the operation is as follows: modifying a certain attribute value of the linkage data object, creating a work item task, a walking conditional branch and the like;
expiration date: an expiration date may be defined for the automation rule after which the rule will be disabled;
the sequence is as follows: the order in which the automation rules are run may be defined. The latter automation rule will evaluate the event condition based on the state after the previous automation rule took action on the event.
Further, the rules are divided into two types according to different triggers, one type is an active rule, and the nodes in the flow, which flow to the flow, trigger the rules triggered by the corresponding active nodes. The execution time of the activity rule is relatively simple and is divided into activity starting and activity completion.
The other type is a flow rule, which is triggered according to the execution time of the flow.
Table 1 shows the schematic table of the execution timing of the flow rule:
TABLE 1
Step 102, constructing a business process through a business process designer and business information, and obtaining an initial business approval process based on the business process and a rule component.
In one embodiment of the application, business information is received and processed by a business process designer. And determining a service scene and a service approval node according to the processed service information so as to construct a service flow through a service flow designer. Acquiring a rule component; the rule component comprises a preset rule of business approval. And carrying out different distribution setting on different preset rules based on different business approval nodes so as to generate an initial business approval process.
Specifically, service information is first received through a service information input module, and the information may include a service type, a service parameter, a service participant, and the like. And then, the business process designer constructs a corresponding business process according to the business information. Then, the rule components related to the current business are obtained from the rule component library, and the rule components comprise preset rules of business approval, such as approval sequence, approval conditions and the like. Finally, the flow generation module combines the business flow and the rule component to generate an initial business approval flow. The initial business approval process can be further optimized and adjusted to meet the actual business requirements.
According to the embodiment of the application, through automatic construction of the business approval process, the construction efficiency and accuracy are improved, and the degree of manual intervention is reduced. Meanwhile, the business process designer and rule component are combined, so that the business approval process is more flexible and customizable to be constructed, and different business scenes and requirements can be better adapted. In addition, the embodiment of the application has the advantages of easy expansion and modification, and can be flexibly adjusted and optimized according to actual requirements.
And 103, responding to a transaction start instruction, calling a rule component interface, executing operation corresponding to a rule to modify data of the initial business approval process until the process flow is transferred to an end node, recording business process approval data, and rolling back the current transaction to an initial state to complete pre-analysis of the approval process and enter an execution stage.
In one embodiment of the application, in response to a transaction start instruction, a rule corresponding to an approval node is triggered, a rule component interface is called, and the rule and business logic corresponding to the rule are executed. Under the condition that the initial business approval process is not branched, the next node is directly entered, the rule corresponding to the next node is triggered, and corresponding business logic is executed. And under the condition that branches exist in the initial business approval process, performing branch judgment according to the preset condition execution rule until the process flow reaches an end node.
Specifically, the validation of rules requires the configuration of rules into a business process in conjunction with the business process. The business process designer may design the process according to a specific business scenario, and the rule points may be configured at corresponding active nodes, such as department manager, etc. A certain active flow node may configure multiple rules and set the dependencies, order, execution conditions, etc. of the rules. The active node also provides automatic approval configuration conditions, when a certain condition is met after the rule is executed, the current node can perform automatic approval and go to the next node according to the conditional flow. When the process runs to the current node, the rule configured by the current node is executed, if the rule is executed and then the automatic approval condition is met, the process can automatically flow to the next active node according to the branch condition, and therefore the process of process automation is pushed.
In one embodiment of the application, business process data and performance data are recorded; wherein, the business process data is related to business modification data in the approval process; the performance data includes a total number of requests, a total number of calls, and an average number of calls. And rolling back the approval process corresponding to the current transaction to an initial state so as to respectively return the business data and the process flow nodes to the state before pre-analysis, thereby completing pre-analysis of the approval process.
Further, the process pre-analysis is performed through rules configured in the service process, the process triggers time, judging conditions, sequence and whether the rules are started or not according to the pre-prefabricated dependency relationship in the rule base, an RPC (Remote Procedure Cal, remote procedure call) interface generated by the rules is called, and the operation corresponding to the rules is executed to modify the service data. And pre-analyzing the business process by combining the conditional branch judgment process trend on the process, wherein the specific execution steps are to start a transaction, truly go to run the process, trigger rules on nodes, execute the rules and corresponding business logic, and if the process is relatively simple and has no branch, directly enter the next node to trigger the corresponding rules to execute the corresponding business logic. If the conditional branch is executed, judging according to the existing conditional execution rule until the flow flows to an end node, and recording business flow data and performance data, wherein the performance data comprises total request number, total call number, average call number and the like. And finally, rolling back the transaction, returning the business data, the flow circulation node and the like to the state before pre-analysis, and finally, verifying the feasibility of the rule by showing the operation result of the pre-analysis flow and the business data to an implementation personnel, wherein the final effect is that the flow does not actually operate but the result of the actual operation of the flow is shown.
The embodiment of the application can truly execute rules and truly execute flow operation through the pre-analysis process, and finally records the result of the real operation. And then, all data is restored to the state before preresolved by the transaction rollback, so that the preresolved result is more real.
After verification, the business process preliminarily has execution conditions, the business process is combined with rules to perform process automation operation, the rules push the process to progress, the rules are executed in the process of process circulation, and a large number of manual operations can be avoided in the process. In the process of actually executing the rules, the rules are matched and optimized according to the configuration of the flow rules, the unnecessary rules are executed asynchronously, and the rules affecting the flow operation are executed optimally.
And 104, performing execution information analysis in an execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
In one embodiment of the application, dump files in the execution information are crawled to obtain thread state. And under the condition that the thread is in a Blocked state, determining that the thread is a Blocked thread, and inquiring a corresponding blocking source thread according to the information of lock in the thread. And under the condition that the thread is in a wait or time-wait state, determining to suspend the thread, and marking that a resource bottleneck exists when the stack number of the like products is larger than a preset stack threshold value. And under the condition that the thread is in Runnable states, determining that the thread can run or is running, and marking the thread with the frequency of occurrence larger than a preset frequency threshold value in the same thread snapshot or with the frequency of occurrence larger than the preset frequency threshold value in different snapshots as performance bottleneck content. Based on different states of the threads, the execution speed of each execution rule is detected.
Specifically, real-time monitoring and feedback are needed in the execution process so as to adjust and correct in time. In the rule execution process, real-time monitoring and feedback are needed for the rule execution condition. These records will be used for subsequent performance analysis and bottleneck discovery. The monitored content comprises execution time, execution result, resource occupation condition and the like of the rule. And optimizing and adjusting the rule according to the monitoring result to improve the execution efficiency and quality of the rule. Meanwhile, the rule base needs to be maintained and updated to adapt to the change of service requirements and the development of technology. The verification, execution and monitoring of the automation rule of the business process is a continuous process, and the correctness, reliability and stability of the automation rule are ensured.
In one embodiment of the application, execution data, performance data, error data, etc. of the automation rule are collected, and the execution effect, performance bottleneck and error cause of the automation rule are analyzed. Based on the dependency relationship and execution sequence among the rules and the action and influence of the rules in the whole business process, the performance analysis is carried out by combining the process rule execution history record, and under the premise of eliminating the non-integral performance problem, the thread state is obtained by capturing dump files through a tool, wherein the thread state is the key information of the positioning problem: the Blocked state is a Blocked thread, and a corresponding Blocked source thread is found according to the lock information in the thread; the wait and time-wait state threads are suspension threads, and unless a large number of like product stacks are needed to consider whether resource bottleneck reasons exist or not, most of the situations do not need to be concerned; runnable state threads can run and are running threads, generally, the thread state is Runnable state, threads with high occurrence frequency in the same thread snapshot or high occurrence frequency in different snapshots are generally performance bottleneck contents, and the execution speed of rule logic is judged according to the thread state so as to evaluate the execution effect and performance of each rule.
The embodiment of the application finds out potential rating and low-efficiency links by comparing the execution time, the resource occupation condition and the like of different rules, and timely finds out the bottleneck in the flow. These bottlenecks may be due to problems with the rules themselves or due to dependencies or resource limitations between rules, and their impact on the overall process and possible risk are determined by analysis of the bottlenecks.
In one embodiment of the present application, a first execution rule to be adjusted, whose execution speed is greater than a first preset speed threshold, is determined based on the detection result. And determining a second execution rule to be adjusted, wherein the execution speed of the second rule is smaller than a second preset speed threshold. And starting the thread of the first to-be-adjusted execution rule to perform single-thread approval. And placing a plurality of second execution rules to be adjusted in the same thread, and sequentially performing approval.
Specifically, the embodiment of the application adopts a sensitive state execution mechanism, considers the optimal execution mode, such as that a rule which is executed slowly exists in a node, and can execute the rule and the rule depending on the rule preferentially under the condition of not influencing the operation of a flow. Under the condition of condition permission, a thread is independently started to execute corresponding code logic according to a rule with longer time, and the rule with shorter time and normal can be sequentially examined and approved in the same thread. Under the condition of multi-thread parallel triggering rule, the execution speed can be effectively reduced, the rule running speed is optimized, and the execution sequence and mode of the rule are dynamically adjusted on the premise of not changing the rule and the dependency relationship thereof, so that the performance optimization of the whole business flow is realized.
In one embodiment of the application, a new version rule component is generated based on the dynamically adjusted rule and a sequence number is set for the new version rule component. And ordering the rule components of different versions based on the set serial numbers so as to determine the version modification track through the ordered rule components. And determining a sub-rule component corresponding to the new version rule component, and carrying out component detection on the sub-rule component based on a preset sub-rule component detection condition. If the sub-rule component meets the detection condition of the preset sub-rule component, determining that the sub-rule component corresponding to the preset sub-rule is detected to be in a passing state, otherwise, determining that the sub-rule component is in a non-passing state. And determining the detection passing number corresponding to the rule component of the new version according to each detection passing state. And determining the detection progress of the new version rule component according to the ratio of the detection passing quantity to the preset detection quantity corresponding to the new version rule component. And when the detection progress meets the preset detection progress, determining the new version rule component state as the component passing state.
Specifically, after the rules are dynamically adjusted, new version rule components are generated, serial numbers of each generated new version rule component are marked, rule components of different versions can be ordered according to the marked serial numbers, and according to the ordered rule components, the modified rule components can be counted according to a time sequence, so that the track of rule adjustment along with time change is determined, and then the rule components of different versions are traced.
Further, the new version rule component in the embodiment of the present application includes a plurality of sub-rule components, and because different service nodes correspond to different approval logics, the new version rule component includes a plurality of sub-rule components corresponding to the current service flow. And carrying out component detection on the plurality of sub-rule components based on different preset sub-rule component detection conditions. Before the new version rule component is put into use, the new version rule component needs to be detected, and a plurality of sub rule components in the new version rule component are respectively detected. The detection mode can be to set a corresponding service scene according to the content of the sub-rule component, so that whether the service approval process can be successfully completed is detected.
Further, under the condition that the detected sub-rule component meets the detection condition of the preset sub-rule component, namely, the detected sub-rule component passes the detection, the detected sub-rule component is changed into a detection passing state, and if the detected sub-rule component does not meet the detection condition of the preset sub-rule component, the detected sub-rule component is determined to be in a non-passing state.
Further, in the process of detecting the sub-rule components corresponding to the new version rule component, the number of the sub-rule components passing the detection is counted in real time. Determining the total number of sub-rule components to be detected in the new version rule components, calculating the ratio of the counted sub-rule number passing the detection to the total number of the sub-rule components, and determining the detection progress of the new version rule components according to the obtained ratio.
Further, when the detection progress meets the preset detection condition, the current new version rule component is determined to be in a passing state. For example, the preset detection condition is 95%, and when the ratio calculated in the detection process reaches 95%, the current detection is determined to pass.
By the detection mode in the embodiment of the application, all sub-rule components can be detected without detecting, and the passing of detection can be determined only by reaching the preset detection condition in the detection process, so that the detection workload is reduced, and the detection speed is improved.
Fig. 3 is a schematic structural diagram of a business process automation approval device according to an embodiment of the present application. As shown in fig. 3, the business process automation approval apparatus 200 includes: at least one processor 201; and a memory 202 communicatively coupled to the at least one processor 201; wherein the memory 202 stores instructions executable by the at least one processor 201, the instructions being executable by the at least one processor 201 to enable the at least one processor 201 to: based on the service information, constructing a rule component; the rule component construction at least comprises the establishment of a triggering condition and the establishment of an executing operation after triggering; constructing a business process by a business process designer and business information, and obtaining an initial business approval process based on the business process and a rule component; responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of an initial business approval process until the process flow is transferred to an ending node, recording business process approval data, rolling back the current transaction to an initial state so as to complete pre-analysis of the approval process, and entering an execution stage; and performing execution information analysis in the execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
The embodiment of the application also provides a nonvolatile computer storage medium, which stores computer executable instructions, wherein the computer executable instructions are configured to: based on the service information, constructing a rule component; the rule component construction at least comprises the establishment of a triggering condition and the establishment of an executing operation after triggering; constructing a business process by a business process designer and business information, and obtaining an initial business approval process based on the business process and a rule component; responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of an initial business approval process until the process flow is transferred to an ending node, recording business process approval data, rolling back the current transaction to an initial state so as to complete pre-analysis of the approval process, and entering an execution stage; and performing execution information analysis in the execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on the detection result to perform business approval based on the optimized business approval process.
The embodiments of the present application are described in a progressive manner, and the same and similar parts of the embodiments are all referred to each other, and each embodiment is mainly described in the differences from the other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and changes may be made to the embodiments of the application by those skilled in the art. Such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.
Claims (10)
1. A business process automated approval method, the method comprising:
based on the service information, constructing a rule component; the rule component construction at least comprises the establishment of a triggering condition and the establishment of an executing operation after triggering;
Constructing a business process through a business process designer and the business information, and obtaining an initial business approval process based on the business process and the rule component;
responding to a transaction starting instruction, calling a rule component interface, executing an operation corresponding to a rule to modify data of the initial business approval process until the process flow is transferred to an ending node, recording business process approval data, and rolling back the current transaction to an initial state to complete pre-analysis of the approval process, and entering an execution stage;
and performing execution information analysis in an execution stage to detect each execution rule, and dynamically adjusting the initial business approval process based on a detection result to perform business approval based on the optimized business approval process.
2. The method for automatically approving the business process according to claim 1, wherein the rule component construction is performed based on the business information, specifically comprising:
constructing a trigger based on the service information, defining a triggering condition corresponding to the service flow automation rule, and determining an operation executed after triggering; the operation executed after the triggering at least comprises modification of the attribute value of the linkage data object and new work item tasks;
and defining the expiration date and rule execution sequence of the trigger.
3. The method for automatically approving a business process according to claim 1, wherein the steps of constructing a business process by a business process designer and the business information, and obtaining an initial business approval process based on the business process and the rule component comprise:
receiving and processing the service information through a service flow designer;
according to the processed business information, determining a business scene and a business approval node to construct a business process through the business process designer;
Acquiring a rule component; the rule component comprises a preset rule of business approval;
And carrying out different distribution setting on different preset rules based on different business approval nodes so as to generate the initial business approval process.
4. The automated business process approval method according to claim 1, wherein the responding to the transaction start command invokes a rule component interface, and performs an operation corresponding to a rule to modify data of the initial business process until the process flow reaches an end node, and specifically comprises:
responding to a transaction starting instruction, triggering a rule corresponding to an approval node, calling the rule component interface, and executing the rule and business logic corresponding to the rule;
under the condition that the initial business approval process is not branched, directly entering a next node, triggering rules corresponding to the next node and executing corresponding business logic;
And under the condition that branches exist in the initial business approval process, performing branch judgment according to a preset condition execution rule until the process flow is transferred to the ending node.
5. The method for automatically approving a business process according to claim 1, wherein the recording of the business process approval data and the rollback of the current transaction to the initial state to complete the pre-analysis of the approval process specifically comprises:
Recording business process data and performance data; wherein, the business process data is related to business modification data in the approval process; the performance data comprises a total request number, a total call number and an average call number;
And rolling back the approval process corresponding to the current transaction to an initial state so as to respectively return the business data and the process flow nodes to the state before pre-analysis, thereby completing pre-analysis of the approval process.
6. The method for automatically approving a business process according to claim 1, wherein the performing information analysis in the execution stage to detect each execution rule comprises:
grabbing dump files in the execution information to obtain thread states;
Under the condition that the thread is in a Blocked state, determining the thread as a Blocked thread, and inquiring a corresponding Blocked source thread according to the lock information in the thread;
Under the condition that the thread is in wait or time-wait state, determining to suspend the thread, and marking that a resource bottleneck exists when the stack number of the like products is larger than a preset stack threshold value;
under the condition that the thread is Runnable in state, determining that the thread can run or is running, and marking the thread with the occurrence frequency larger than a preset frequency threshold value in the same thread snapshot or different snapshots as the performance bottleneck content;
Based on different states of the threads, the execution speed of each execution rule is detected.
7. The method for automatically approving a business process according to claim 1, wherein the step of dynamically adjusting the initial business approval process based on the detection result comprises the following steps:
Based on the detection result, determining a first to-be-adjusted execution rule with the execution speed greater than a first preset speed threshold;
determining a second execution rule to be adjusted, wherein the execution speed of the second rule is smaller than a second preset speed threshold;
starting a thread for the first to-be-adjusted execution rule so as to perform single-thread approval;
And placing a plurality of second execution rules to be adjusted in the same thread, and sequentially performing approval.
8. The automated business process approval method of claim 1, wherein after the initial business process approval is dynamically adjusted based on the detection result, the method further comprises:
Generating a new version rule component based on the dynamically adjusted rule, and setting a serial number of the new version rule component;
based on the set serial numbers, ordering rule components of different versions to determine version modification tracks through the ordered rule components;
determining a sub-rule component corresponding to the new version rule component, and performing component detection on the sub-rule component based on preset sub-rule component detection conditions;
If the sub-rule component meets the detection condition of the preset sub-rule component, determining that the sub-rule component corresponding to the preset sub-rule is detected to be in a passing state, otherwise, determining that the sub-rule component is not in a passing state;
determining the detection passing number corresponding to the new version rule component according to each detection passing state;
Determining the detection progress of the new version rule component according to the ratio of the detection passing quantity to the preset detection quantity corresponding to the new version rule component;
and when the detection progress meets the preset detection progress, determining the new version rule component state as a component passing state.
9. A business process automation approval device, characterized in that the device comprises a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the device to perform the method of any of claims 1-8.
10. A non-transitory computer storage medium storing computer executable instructions, wherein the computer executable instructions are capable of performing the method of any one of claims 1-8.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410338549.5A CN117933950B (en) | 2024-03-25 | 2024-03-25 | Automatic business process approval method, equipment and medium |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202410338549.5A CN117933950B (en) | 2024-03-25 | 2024-03-25 | Automatic business process approval method, equipment and medium |
Publications (2)
Publication Number | Publication Date |
---|---|
CN117933950A true CN117933950A (en) | 2024-04-26 |
CN117933950B CN117933950B (en) | 2024-06-18 |
Family
ID=90761466
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202410338549.5A Active CN117933950B (en) | 2024-03-25 | 2024-03-25 | Automatic business process approval method, equipment and medium |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN117933950B (en) |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR20070011973A (en) * | 2005-07-22 | 2007-01-25 | 삼성에스디에스 주식회사 | Method for management of work-flow finance |
US20070179790A1 (en) * | 2002-06-28 | 2007-08-02 | Matthew Leitch | Dynamic workflow approvals |
US20080255903A1 (en) * | 2007-04-12 | 2008-10-16 | Ying Liu | Business process execution method, business process engine and method for deploying a business process engine |
CN102591286A (en) * | 2012-02-20 | 2012-07-18 | 宝山钢铁股份有限公司 | Online rolling plan dynamic pre-analysis and self-adjustment system and method |
CN111198748A (en) * | 2019-12-31 | 2020-05-26 | 航天信息股份有限公司企业服务分公司 | Automatic approval method for business document process, electronic equipment, storage medium and system |
CN114723391A (en) * | 2022-03-18 | 2022-07-08 | 深圳市小满科技有限公司 | Method and device for generating user-defined business process approval flow |
WO2023050570A1 (en) * | 2021-09-30 | 2023-04-06 | 明度智云(浙江)科技有限公司 | User-defined examination and approval method and apparatus for medical electronic experiment records and storage medium |
CN116468259A (en) * | 2023-04-18 | 2023-07-21 | 上海中通吉网络技术有限公司 | Workflow configuration method and device based on rule engine |
CN117436815A (en) * | 2023-11-17 | 2024-01-23 | 北京九思协同软件有限公司 | Flow intelligent approval method based on natural language big model |
-
2024
- 2024-03-25 CN CN202410338549.5A patent/CN117933950B/en active Active
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20070179790A1 (en) * | 2002-06-28 | 2007-08-02 | Matthew Leitch | Dynamic workflow approvals |
KR20070011973A (en) * | 2005-07-22 | 2007-01-25 | 삼성에스디에스 주식회사 | Method for management of work-flow finance |
US20080255903A1 (en) * | 2007-04-12 | 2008-10-16 | Ying Liu | Business process execution method, business process engine and method for deploying a business process engine |
CN102591286A (en) * | 2012-02-20 | 2012-07-18 | 宝山钢铁股份有限公司 | Online rolling plan dynamic pre-analysis and self-adjustment system and method |
CN111198748A (en) * | 2019-12-31 | 2020-05-26 | 航天信息股份有限公司企业服务分公司 | Automatic approval method for business document process, electronic equipment, storage medium and system |
WO2023050570A1 (en) * | 2021-09-30 | 2023-04-06 | 明度智云(浙江)科技有限公司 | User-defined examination and approval method and apparatus for medical electronic experiment records and storage medium |
CN114723391A (en) * | 2022-03-18 | 2022-07-08 | 深圳市小满科技有限公司 | Method and device for generating user-defined business process approval flow |
CN116468259A (en) * | 2023-04-18 | 2023-07-21 | 上海中通吉网络技术有限公司 | Workflow configuration method and device based on rule engine |
CN117436815A (en) * | 2023-11-17 | 2024-01-23 | 北京九思协同软件有限公司 | Flow intelligent approval method based on natural language big model |
Also Published As
Publication number | Publication date |
---|---|
CN117933950B (en) | 2024-06-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7634687B2 (en) | Checkpoint restart system and method | |
Castellanos et al. | ibom: A platform for intelligent business operation management | |
US8024615B2 (en) | Steady state computer testing | |
US7386577B2 (en) | Dynamic determination of transaction boundaries in workflow systems | |
US7856616B2 (en) | Action-based in-process software defect prediction software defect prediction techniques based on software development activities | |
US10817283B1 (en) | Automated risk assessment for software deployment | |
CN100428242C (en) | Database tuning method and system | |
US20170097850A1 (en) | Finding resource bottlenecks with low-frequency sampled data | |
CN111400011B (en) | Real-time task scheduling method, system, equipment and readable storage medium | |
CN101017546A (en) | Method and device for categorical data batch processing | |
US20090158286A1 (en) | Facility for scheduling the execution of jobs based on logic predicates | |
US20140279735A1 (en) | Process model generated using biased process mining | |
CN110262975A (en) | Test data management method, device, equipment and computer readable storage medium | |
Dhanalaxmi et al. | A review on software fault detection and prevention mechanism in software development activities | |
US9170915B1 (en) | Replay to reconstruct program state | |
CN117933950B (en) | Automatic business process approval method, equipment and medium | |
US12013845B1 (en) | Real time optimization apparatus using smart contracts for dynamic code validation and approval | |
US8151189B2 (en) | Computer-implemented systems and methods for an automated application interface | |
CN116149824A (en) | Task re-running processing method, device, equipment and storage medium | |
CN115543377A (en) | ERP system upgrading method based on artificial intelligence and ERP system | |
Xie et al. | Design and implementation of bank financial business automation testing framework based on QTP | |
Jacques-Silva et al. | Survivability modeling to assess deployment alternatives accounting for rejuvenation | |
CN117667362B (en) | Method, system, equipment and readable medium for scheduling process engine | |
CN118036983A (en) | Scheduling management method and system based on data quality management | |
KR102676519B1 (en) | Apparatus and Method for Providing Intelligent Task Automation Service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |