Business process verification method and device and electronic equipment

Abstract

Embodiments of the present disclosure disclose a business process verification method and device and electronic equipment. A specific embodiment of the method includes: in response to a detected operation satisfying a preset verification timing condition, determining a checkpoint set for a target business process, wherein the checkpoint is used to indicate a verification range; according to the checkpoint, determining a target process item to be verified from process items of the target business process; and based on a target verification rule matched with the target process item, verifying the target process item and generating a verification result. Thus, a new business process verification method is provided.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and in particular to a business process verification method, apparatus, and electronic device. Background Technology

[0002] With the development of computers, users can use electronic devices to perform various functions. For example, users can use electronic devices to work, watch videos, browse news, and so on.

[0003] In some scenarios, a user interface can be provided for business personnel to quickly configure business strategies. This interface allows for rapid configuration of business strategies using platform-provided options. The configured business strategies can then be published and applied to specific scenarios to implement concrete functionalities within business processes. Summary of the Invention

[0004] This disclosure is provided to briefly introduce the concepts, which will be described in detail in the subsequent Detailed Description section. This disclosure is not intended to identify key or essential features of the claimed technical solution, nor is it intended to limit the scope of the claimed technical solution.

[0005] In a first aspect, embodiments of this disclosure provide a business process verification method, the method comprising: in response to a detected operation satisfying a preset verification timing condition, determining a checkpoint set for a target business process, wherein the checkpoint is used to indicate the verification range; determining a target process item to be verified from the process items of the target business process according to the checkpoint; and verifying the target process item and generating a verification result based on a target verification rule matching the target process item.

[0006] Secondly, embodiments of this disclosure provide a business process verification device, comprising: a first determining unit, configured to determine a checkpoint set for a target business process in response to a detected operation satisfying a preset verification timing condition, wherein the checkpoint is used to indicate the verification range; a second determining unit, configured to determine a target process item to be verified from the process items of the target business process according to the checkpoint; and a verification unit, configured to verify the target process item and generate a verification result based on a target verification rule matching the target process item.

[0007] Thirdly, embodiments of this disclosure provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the business process verification method as described in the first aspect.

[0008] Fourthly, embodiments of this disclosure provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the business process verification method as described in the first aspect. Attached Figure Description

[0009] The above and other features, advantages, and aspects of the embodiments of this disclosure will become more apparent from the accompanying drawings and the following detailed description. Throughout the drawings, the same or similar reference numerals denote the same or similar elements. It should be understood that the drawings are schematic, and the originals and elements are not necessarily drawn to scale.

[0010] Figure 1 This is a flowchart of an embodiment of the business process verification method according to this disclosure;

[0011] Figure 2 This is a schematic diagram of an application scenario of the business process verification method disclosed herein;

[0012] Figure 3 This is a schematic diagram of an application scenario of the business process verification method disclosed herein;

[0013] Figure 4 This is a flowchart of an embodiment of the business process verification method according to this disclosure;

[0014] Figure 5 This is a schematic diagram of the structure of an embodiment of the business process verification device according to the present disclosure;

[0015] Figure 6 This is an example of a business process verification method according to an embodiment of the present disclosure, which can be applied to an exemplary system architecture.

[0016] Figure 7 This is a schematic diagram of the basic structure of an electronic device provided according to an embodiment of the present disclosure. Detailed Implementation

[0017] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0018] It should be understood that the steps described in the method embodiments of this disclosure may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of this disclosure is not limited in this respect.

[0019] The term "comprising" and its variations as used herein are open-ended inclusions, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Definitions of other terms will be given in the description below.

[0020] It should be noted that the concepts of "first" and "second" mentioned in this disclosure are used only to distinguish different devices, modules or units, and are not used to limit the order of functions performed by these devices, modules or units or their interdependencies.

[0021] It should be noted that the terms "a" and "a plurality of" used in this disclosure are illustrative rather than restrictive, and those skilled in the art should understand that, unless otherwise expressly indicated in the context, they should be understood as "one or more".

[0022] The names of messages or information exchanged between multiple devices in the embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

[0023] In one or more embodiments of this disclosure, a rule management platform can be provided, which may include a front-end rule management interface. The rule management platform can be used for rule creation and editing, rule debugging and testing, rule classification and storage, and rule version control and publishing. Here, rule creation and editing includes supporting the definition of rules through scripting languages. Rule debugging and testing includes providing rule debugging functions, allowing users to simulate data input on the interface and view the rule execution results in real time. Rule classification and storage includes supporting rule management and storing rules in a central rule repository. Version control and publishing manage the version history of rules, support rule publishing by version, and ensure that rule modifications do not affect rules running online.

[0024] In one or more embodiments of this disclosure, a rule base, also known as a rule set, may be provided. The rule base is used for centralized storage and management of rules. The rule base can store general rules, centrally managing and storing general validation rules for reuse by business systems. The rule base can also store custom rules; business systems can store their own specific rules in the rule base and manage and update them through a rule management platform. The rule base can support versioned rule management, with each rule having a unique version number, facilitating the selection of which version of the rule to use by business systems.

[0025] In one or more embodiments of this disclosure, a rule execution engine may be provided. The rule execution engine is responsible for dynamically loading and executing rules, and ensuring the flexibility and scalability of the rules. The rule execution engine may support scripting languages. Embedded development support may be provided for the rule execution engine; that is, for complex rules, a development interface (e.g., via an SDK) is provided, allowing technicians to write rule logic using standard development languages ​​and load it as a plugin into the system. The rule execution engine may support dynamically loading rules from a rule management platform without restarting the service, achieving hot rule updates.

[0026] In one or more embodiments of this disclosure, the rule execution engine allows the business system to insert checkpoints where verification is required. The engine will dynamically execute the verification logic according to the configured rules to ensure the flexibility and accuracy of rule execution.

[0027] In one or more embodiments of this disclosure, the timing of data verification can be optimized. When storing data, a data snapshot is taken, and the snapshot data is verified before the actual business interface is called. This brings forward the timing of the subsequent verification, and if a problem occurs, the process is directly blocked, thus preventing the generation of dirty data.

[0028] In one or more embodiments of this disclosure, a business system can be provided, which can provide the functionality to configure business processes. The business system can integrate with a rule engine. Here, a standardized interface can be provided, enabling the business system to integrate with the rule engine with minimal modifications; for example, rule validation integration can be achieved through middleware or decorators. The business system only needs to add calls to the rule SDK in key functions or processes, without needing to refactor existing code. Data context passing is achieved through reflection, that is, the context information of functions is automatically obtained through reflection, without the need to explicitly pass in business data.

[0029] In one or more embodiments of this disclosure, please refer to Figure 3 , Figure 3 A process for an exemplary scenario is provided. Figure 3 The process shown may include rule management steps, business system call steps, rule execution steps, and notification feedback steps.

[0030] During the rule management process, developers or business personnel can add, edit, debug, and test rules through the rule management platform. Rules are stored in the rule repository and automatically published to the rule engine.

[0031] During the business system call process, business personnel can configure strategies (operation strategies) on the platform. The business system inserts checkpoints at key locations via SDK or API; when the trigger condition is met (e.g., before or after save, update, etc.), before the specific business logic is called, a snapshot of the data to be verified is taken; the rule verification logic is then called; the SDK automatically loads the corresponding rule set from the rule engine based on the call context (e.g., the name of the current operation and the data passed in).

[0032] During the rule execution step, after receiving a verification request, the rule engine dynamically loads the corresponding rule script or embedded rule; based on the rule definition and the current data context, it executes the verification logic and returns the result.

[0033] In the notification and feedback process, if a rule fails, the rule engine can trigger the corresponding notification mechanism (such as message push, logging, etc.) according to the rule definition; the business system processes the feedback from the rule engine (such as stopping saving, blocking the operation, and prompting error messages when the rule fails; and executing the saving business logic when the rule passes).

[0034] Please refer to Figure 1 This illustrates a flow diagram of one embodiment of the business process verification method according to this disclosure. For example... Figure 1 The business process verification method shown includes the following steps:

[0035] Step 101: In response to the detected operation meeting the preset verification timing conditions, determine the checkpoint set for the target business process.

[0036] In this embodiment, the execution subject of the business process verification method (e.g., server and / or terminal device) can determine the checkpoint set for the target business process in response to the detected operation meeting the preset verification timing conditions.

[0037] Here, the detected operation can be any operation; when an operation is associated with a checkpoint, the operation can be considered to meet the verification timing condition. For example, if an operation to save a business process is detected, this operation meets the verification timing condition (if a checkpoint is set in advance for saving the business process, the verification timing condition includes before or after saving the business process).

[0038] Here, the preset verification timing conditions can indicate the pre-defined verification timing, such as before update, after update, before save, and after save. As an example, business users can set the verification timing as before the entire process is updated or saved; they can also set the verification timing as before the process item is updated or saved.

[0039] Here, checkpoints can be pre-set by business personnel for target business processes.

[0040] Step 102: Based on the checkpoints, determine the target process items to be verified from the process items of the target business process.

[0041] Here, based on the identified checkpoint, the verification range indicated by that checkpoint is determined. As an example, if a checkpoint is associated with a process item, then the process item associated with the checkpoint can be identified as the target process item to be verified.

[0042] Step 103: Based on the target verification rules that match the target process item, verify the target process item and generate verification results.

[0043] Here, a rule base can be pre-configured, and the validation rules in the rule base can be used to validate different process items. A validation rule matching the target process item can be determined from the rule base, serving as the target validation rule. The target process item is then validated based on the target validation rule, and the validation result of the target process item is determined.

[0044] It should be noted that the business process verification method provided in this embodiment, in response to the detected operation meeting the preset verification timing conditions, determines checkpoints set for the target business process, wherein the checkpoints are used to indicate the verification scope; based on the checkpoints, the target process item to be verified is determined from the process items of the target business process; based on the target verification rules matching the target process item, the target process item is verified and a verification result is generated. Thus, a checkpoint mechanism for business processes is introduced. Through the checkpoint mechanism, targeted verification of process items within a custom range can be achieved, ensuring dynamic and flexible targeted verification; verification is performed using rules matching the process item, that is, different check rules are applied under different ranges, ensuring the accuracy of the verification process and avoiding invalid verification caused by general verification rules.

[0045] In contrast, related technologies apply a set of rules to the entire dataset (e.g., the entire code repository), such as checking for spelling errors or infinite loops. Limitations of these technologies include: applying a single set of rules only applies when all data has the same structure; business processes differ across scenarios, not because the content of the data varies each time, but because the data structure is different. For example, product data and store data are completely different; product data must have a price greater than 0, but store data does not have a price field at all.

[0046] In some scenarios, as business platform capabilities increase and business process complexity rises, the probability and risk of mismatch also increase, leading to issues in strategy configuration (e.g., loops may exist in new merger capabilities, or the characteristics of solution requirements may not be injected into the preceding nodes). For the configured strategy (i.e., business process), the following methods can be adopted: Figure 1 The verification method for the process shown.

[0047] For example, please refer to Figure 2 , Figure 2 The interface for configuring business processes is shown. A business process can include multiple process items, such as whether there is an after-sales order, whether there is an after-sales order, whether there is no after-sales order, and whether it's a refund only. It should be noted that... Figure 2 The diagram illustrates a business process, which can be a segment of that process. There can be a process item before or after a refund request.

[0048] exist Figure 2 In the process, checkpoints (as shown by triangles) can be added to refund-only items to indicate that the content of the target process item is validated before saving the content of the process item; checkpoints (as shown by triangles) can also be added to submission nodes to indicate that validation is performed when submitting the process. Validation when submitting the process can include one or more of the following: validation of the target process item, validation of the process as a whole, and validation of both the target process item and the process as a whole.

[0049] As an example, in Figure 2 In the example shown, for the refund item, a pre-configured validation rule is matched (e.g., checking the refund amount for an after-sales order). The matched validation rule includes failing if there is no refund amount. Based on this validation rule, if the business process includes a step to confirm the refund amount, and the process does not include a step to confirm the refund amount, then the validation fails.

[0050] Optionally, the validation of the target process item may include validation of the process item content within the target process item and / or validation of the associated context of the process item content.

[0051] Optionally, when validating a process using validation rules, one can search for validation rules based on the process item and use the found rules to validate the process item; or one can match process items based on validation rules (with pre-written applicable information used to determine the process content to which the rule applies) and use the validation rules to validate the matched process items.

[0052] In some embodiments, the method further includes: taking a snapshot of the target process item.

[0053] Here, a data snapshot can be taken when storing data, allowing the data to be tested to be obtained before the actual business interface is called.

[0054] Therefore, by setting up a snapshot mechanism, the timing of data verification can be optimized, replacing the retroactive and static verification process with a proactive and dynamic one. That is, the snapshot data is verified before the actual business interface is called, bringing forward the retroactive verification time. If a problem occurs, the process is directly stopped, preventing the generation of dirty data.

[0055] In some embodiments, the step of verifying the target process item and generating a verification result based on the target verification rule matching the target process item includes: obtaining the target process item and the business context associated with the target process item, and generating process data to be verified; obtaining the target verification rule from the verification rule set based on the process data to be verified; verifying the process data to be verified based on the target verification rule, and generating a verification result.

[0056] Here, the business context associated with the target process item can be automatically obtained through reflection, without needing to explicitly pass in the business data flow.

[0057] The business context and the target process item are related in type, but no restrictions are made here.

[0058] As an example, in Figure 2 In the example shown, for a refund-only item, the context of the refund-only item, such as the refund amount, can be obtained. Based on the refund-only item and the refund amount (e.g., X yuan), a validation rule in the rule set for amounts greater than a first threshold is matched. The matched validation rule indicates that when the price of the goods exceeds the first threshold, the refund-only item is not suitable (this can be understood as requiring the more expensive goods to be returned to the merchant). Therefore, the refund-only item validation fails.

[0059] This allows for the acquisition of a wider range of data related to the target process items, and the determination of more accurate target verification rules based on the target context and target process data, thereby achieving comprehensive and accurate verification.

[0060] In some embodiments, obtaining a target verification rule from the verification rule set based on the process data to be verified includes: obtaining one or more verification rules from the verification rule set as the target verification rule based on one or more of the following: name and data content of the target process item and / or the process data to be verified.

[0061] As an example, the target process item could be a refund-only item, and the target validation rule could be named a validation for the cash-back policy. Therefore, the target validation rule can be determined based on the name of the target process item.

[0062] As an example, the data content of the process data to be verified may include the value of the goods, and the target verification rules may include verification rules specific to the value. Therefore, accurate verification can be performed based on the data content of the process data to be verified.

[0063] Therefore, it is possible to quickly and accurately determine the target verification rules, and achieve comprehensive and accurate verification.

[0064] In some embodiments, the operation node checkpoint is set at the operation node, and the processing object of the operation node indicates the verification scope; wherein, the operation node includes one or more of the following: save operation node, submit for review operation node. The processing object includes one or more of the following: process item, business process. As an example, if the operation node is a save process item content operation, then the processing object is the saved object, i.e., the process item content, and the verification scope is the saved object, i.e., the process item content; as an example, if the operation node is a submit process review operation node, then the processing object is the business process, and the verification scope is the business process.

[0065] Optionally, validation of business processes may include one or more of the following: validation of target process items, validation of the entire process, and validation of both target process items and the entire process.

[0066] In this scenario, checkpoints can be set for either process items or operational nodes within the business process.

[0067] In some embodiments, the method further includes: in response to a verification result indicating that the verification failed, performing a preset subsequent operation.

[0068] Here, the preset follow-up actions include one or more of the following: pushing notification messages, preventing the target business process from going live.

[0069] Therefore, actions can be taken quickly based on the verification results, prompting business personnel to modify the process and preventing erroneous processes from causing adverse consequences.

[0070] In some embodiments, the method further includes: displaying a target business process generated based on a configuration operation on a business process configuration interface, wherein the configuration operation is used to determine relevant data of the target business process based on pre-set process candidates, and the specific content of the relevant data varies depending on the business and is not limited here; and inserting a checkpoint at the target point of the target business process in response to a checkpoint insertion operation.

[0071] As an example, you can refer to Figure 2 ,exist Figure 2In the scenario shown, an insertion control (such as a triangle) can be set. Users can drag the insertion control to the point where they want to set a checkpoint (i.e., the checkpoint insertion operation), such as before saving the content of a process item and / or before saving the business process, thereby inserting a checkpoint at the target point.

[0072] Therefore, business process configuration can be completed quickly in the business process configuration interface, and checkpoints can be inserted conveniently and quickly based on the checkpoint insertion operation.

[0073] In some embodiments, the method further includes: displaying a verification rule setting interface; setting a verification rule name and verification rule content in the verification rule setting interface; and generating a verification rule set based on the verification rules set in the verification rule interface.

[0074] Here, the set of validation rules can also be called a rule base.

[0075] Here, the rule management platform's validation rule settings interface can be used for rule creation and editing, rule debugging and testing, rule categorization and storage, and rule version control and publishing. Rule creation and editing includes support for defining rules using scripting languages. Rule debugging and testing includes providing rule debugging functionality, allowing users to simulate data input on the interface and view rule execution results in real time. Rule categorization and storage includes supporting rule management and storing rules in a central rule repository. Version control and publishing manages the rule version history, supports rule publishing by version, and ensures that rule modifications do not affect rules running online.

[0076] This allows for the convenient generation and management of verification rules.

[0077] Please refer to Figure 4 This illustrates a flow diagram of one embodiment of the business process verification method according to this disclosure. For example... Figure 4 The business process verification method shown includes the following steps:

[0078] Step 401: In response to the detected operation meeting the preset verification timing conditions, determine the checkpoint set for the target business process.

[0079] In this embodiment, the execution subject of the business process verification method (e.g., server and / or terminal device) can determine the checkpoint set for the target business process in response to the detected operation meeting the preset verification timing conditions.

[0080] Step 402: Based on the checkpoints, determine the target process items to be verified from the process items of the target business process.

[0081] Step 403: Obtain the target process item and the business context associated with the target process item, and generate the process data to be verified.

[0082] Step 404: Based on the process data to be verified, obtain the target verification rule from the verification rule set.

[0083] Step 405: Based on the target verification rules, verify the process data to be verified and generate verification results.

[0084] Here, the business context associated with the target process item can be automatically obtained through reflection, without needing to explicitly pass in the business data flow.

[0085] The business context and the target process item are related in type, but no restrictions are made here.

[0086] As an example, in Figure 2 In the example shown, for a refund-only item, the context of the refund-only item, such as the refund amount, can be obtained. Based on the refund-only item and the refund amount (e.g., X yuan), a validation rule in the rule set for amounts greater than a first threshold is matched. The matched target validation rule indicates that when the product price is greater than the first threshold, the refund-only item is not suitable (this can be understood as requiring the more expensive product to be returned to the merchant). Therefore, the refund-only item validation fails.

[0087] This allows for the acquisition of a wider range of data related to the target process items, and the determination of more accurate target verification rules based on the target context and target process data, thereby achieving comprehensive and accurate verification.

[0088] Further reference Figure 5 As an implementation of the methods shown in the above figures, this disclosure provides an embodiment of a business process verification device, which is similar to... Figure 1 Corresponding to the method embodiments shown, this device can be specifically applied to various electronic devices.

[0089] like Figure 5 As shown, the business process verification device in this embodiment includes: a first determining unit 501, a second determining unit 502, and a verification unit 503. The first determining unit is used to determine checkpoints set for the target business process in response to a detected operation meeting a preset verification timing condition, wherein the checkpoints indicate the verification range. The second determining unit is used to determine the target process item to be verified from the process items of the target business process based on the checkpoints. The verification unit is used to verify the target process item and generate a verification result based on a target verification rule matching the target process item.

[0090] In this embodiment, the specific processing of the first determining unit 501, the second determining unit 502, and the verification unit 503 of the business process verification device, and the resulting technical effects, can be referred to respectively. Figure 1 The relevant descriptions of steps 101, 102 and 103 in the corresponding embodiments will not be repeated here.

[0091] In some embodiments, the apparatus is further configured to: snapshot store the target process item.

[0092] In some embodiments, the step of verifying the target process item and generating a verification result based on the target verification rule matching the target process item includes: obtaining the target process item and the business context associated with the target process item, and generating process data to be verified; obtaining the target verification rule from the verification rule set based on the process data to be verified; verifying the process data to be verified based on the target verification rule, and generating a verification result.

[0093] In some embodiments, obtaining a target verification rule from the verification rule set based on the process data to be verified includes: obtaining one or more verification rules from the verification rule set as the target verification rule based on one or more of the following: name and data content of the target process item and / or the process data to be verified.

[0094] In some embodiments, the checkpoint is set at an operation node, and the processing object of the operation node indicates the scope of verification; the processing object includes one or more of the following: process item, business process; wherein, the operation node includes one or more of the following: save operation node, submit for review operation node.

[0095] In some embodiments, the device is further configured to: in response to a verification result indicating that the verification failed, perform a preset follow-up operation; the preset follow-up operation includes one or more of the following: pushing a prompt message, preventing the target business process from going online.

[0096] In some embodiments, the apparatus is further configured to: display a target business process generated based on a configuration operation on a business process configuration interface, wherein the configuration operation is used to determine relevant data of the target business process based on pre-set process candidates; and insert checkpoints at target points for the target business process in response to a checkpoint insertion operation.

[0097] In some embodiments, the apparatus is further configured to: display a verification rule setting interface; set a verification rule name and verification rule content in the verification rule setting interface; and generate a verification rule set based on the verification rules set in the verification rule interface.

[0098] Please refer to Figure 6 , Figure 6An exemplary system architecture in which a business process verification method according to an embodiment of this disclosure can be applied is illustrated.

[0099] like Figure 6 As shown, the system architecture may include terminal devices 601, 602, and 603, a network 604, and a server 605. Network 604 serves as the medium for providing a communication link between terminal devices 601, 602, and 603 and server 605. Network 604 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0100] Terminal devices 601, 602, and 603 can interact with server 605 via network 604 to receive or send messages, etc. Various client applications, such as web browsers, search engines, and news apps, can be installed on terminal devices 601, 602, and 603. These client applications can receive user commands and perform corresponding functions, such as adding information to a message based on user instructions.

[0101] Terminal devices 601, 602, and 603 can be either hardware or software. When terminal devices 601, 602, and 603 are hardware, they can be various electronic devices with a display screen and supporting web browsing, including but not limited to smartphones, tablets, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III), MP4 players (Moving Picture Experts Group Audio Layer IV), laptops, and desktop computers, etc. When terminal devices 601, 602, and 603 are software, they can be installed in the aforementioned electronic devices. They can be implemented as multiple software programs or software modules (e.g., software programs or software modules used to provide distributed services) or as a single software program or software module. No specific limitations are imposed here.

[0102] Server 605 can be a server that provides various services, such as receiving information retrieval requests sent by terminal devices 601, 602, and 603, retrieving the corresponding display information according to the information retrieval request through various methods, and sending the relevant data for displaying the information to terminal devices 601, 602, and 603.

[0103] It should be noted that the business process verification method provided in this embodiment can be executed by a terminal device, and correspondingly, the business process verification device can be installed in terminal devices 601, 602, and 603. Furthermore, the business process verification method provided in this embodiment can also be executed by a server 605, and correspondingly, the business process verification device can be installed in server 605.

[0104] It should be understood that Figure 6 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0105] The following is for reference. Figure 7 It illustrates an electronic device suitable for implementing embodiments of the present disclosure (e.g., Figure 6 The diagram shows the structure of the terminal device or server in this disclosure. The terminal device in this embodiment may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle terminals (e.g., vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 7 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of the embodiments disclosed herein.

[0106] like Figure 7 As shown, the electronic device may include a processing unit (e.g., a central processing unit, a graphics processing unit, etc.) 701, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 702 or a program loaded from a storage device 708 into a random access memory (RAM) 703. The RAM 703 also stores various programs and data required for the operation of the electronic device 700. The processing unit 701, ROM 702, and RAM 703 are interconnected via a bus 704. An input / output (I / O) interface 705 is also connected to the bus 704.

[0107] Typically, the following devices can be connected to I / O interface 705: input devices 706 including, for example, touchscreens, touchpads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices 707 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 708 including, for example, magnetic tapes, hard disks, etc.; and communication devices 709. Communication device 709 allows electronic devices to communicate wirelessly or wiredly with other devices to exchange data. Although Figure 7 Electronic devices with various devices are shown, but it should be understood that it is not required to implement or have all of the devices shown. More or fewer devices may be implemented or have alternatively.

[0108] In particular, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication device 709, or installed from storage device 708, or installed from ROM 702. When the computer program is executed by processing device 701, it performs the functions defined in the methods of embodiments of this disclosure.

[0109] It should be noted that the computer-readable medium described in this disclosure can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this disclosure, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this disclosure, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wires, optical fibers, RF (radio frequency), etc., or any suitable combination thereof.

[0110] In some implementations, clients and servers can communicate using any currently known or future-developed network protocol such as HTTP (Hypertext Transfer Protocol) and can interconnect with digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (“LANs”), wide area networks (“WANs”), the Internet (e.g., the Internet of Things), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future-developed networks.

[0111] The aforementioned computer-readable medium may be included in the aforementioned electronic device; or it may exist independently and not assembled into the electronic device.

[0112] The aforementioned computer-readable medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to: determine checkpoints set for the target business process in response to a detected operation satisfying a preset verification timing condition, wherein the checkpoints are used to indicate the verification range; determine target process items to be verified from the process items of the target business process based on the checkpoints; and verify the target process items and generate verification results based on target verification rules matching the target process items.

[0113] Computer program code for performing the operations of this disclosure can be written in one or more programming languages ​​or a combination thereof, including but not limited to object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0114] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0115] The units described in the embodiments of this disclosure can be implemented in software or in hardware. The name of a unit does not necessarily limit the unit itself; for example, a verification unit can also be described as a "unit used for verification".

[0116] The functions described above in this document can be performed, at least in part, by one or more hardware logic components. For example, exemplary types of hardware logic components that can be used, without limitation, include: Field Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application Standard Products (ASSPs), System-on-Chip (SoCs), Complex Programmable Logic Devices (CPLDs), and so on.

[0117] In the context of this disclosure, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0118] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

[0119] Furthermore, while the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous. Similarly, while several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of this disclosure. Certain features described in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.

[0120] Although the subject matter has been described using language specific to structural features and / or methodological logic, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are merely illustrative examples of implementing the claims.

Claims

1. A business process validation method, characterized in that, include: In response to the detected operation meeting the preset verification timing conditions, a checkpoint is determined for the target business process, wherein the checkpoint is used to indicate the verification range; Based on the checkpoints, the target process items to be verified are determined from the process items of the target business process; Based on the target validation rules that match the target process item, the target process item is validated and validation results are generated.

2. The method according to claim 1, characterized in that, The method further includes: The target process item is stored in a snapshot.

3. The method according to claim 1, characterized in that, The process of validating the target process item and generating a validation result based on the target validation rules that match the target process item includes: Obtain the target process item and its associated business context, and generate the process data to be verified. Based on the process data to be verified, the target verification rule is obtained from the set of verification rules; Based on the target verification rules, the process data to be verified is verified, and verification results are generated.

4. The method according to claim 3, characterized in that, The step of obtaining the target verification rule from the verification rule set based on the process data to be verified includes: Based on one or more of the following: name and data content of the target process item and / or the data to be processed, obtain one or more validation rules from the validation rule set as the target validation rule.

5. The method according to claim 1, characterized in that, The checkpoint is set at the operation node, and the processing object of the operation node indicates the scope of verification; the processing object includes one or more of the following: process item, business process; The operation nodes include one or more of the following: save operation node, submit for review operation node.

6. The method according to claim 1, characterized in that, The method further includes: In response to a verification result indicating that the verification failed, perform the preset subsequent operations; Preset follow-up actions include one or more of the following: pushing notification messages, preventing the target business process from going live.

7. The method according to claim 1, characterized in that, The method further includes: The business process configuration interface displays the target business process generated based on the configuration operation. The configuration operation is used to determine the relevant data of the target business process based on the pre-set process candidates. In response to the checkpoint insertion operation, insert a checkpoint at the target point for the target business process.

8. The method according to claim 1, characterized in that, The method further includes: Displays the verification rule settings interface; In the verification rule settings interface, set the verification rule name and verification rule content; A set of verification rules is generated based on the verification rules set in the verification rules interface.

9. A business process verification device, characterized in that, include: The first determining unit is used to determine the checkpoint set for the target business process in response to the detected operation meeting the preset verification timing conditions, wherein the checkpoint is used to indicate the verification range; The second determining unit is used to determine the target process item to be verified from the process items of the target business process based on the checkpoint. The verification unit is used to verify the target process item and generate verification results based on the target verification rules that match the target process item.

10. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-8.

11. A computer-readable medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-8.

Images