CN112487416A

CN112487416A - Business process verification method and device and electronic equipment

Info

Publication number: CN112487416A
Application number: CN202011366766.3A
Authority: CN
Inventors: 郑海波
Original assignee: Beijing Zitiao Network Technology Co Ltd
Current assignee: Beijing Zitiao Network Technology Co Ltd
Priority date: 2020-11-26
Filing date: 2020-11-26
Publication date: 2021-03-12

Abstract

When the business process to be verified is received, the business process to be verified is firstly input into a sandbox, and then operation data of a process engine operating the business process is input into the sandbox. Therefore, the operating environment in the process engine is kept consistent with the operating environment in the sandbox, and whether the business process to be verified meets the verification condition can be verified more accurately.

Description

Business process verification method and device and electronic equipment

Technical Field

The present disclosure relates to the field of internet technologies, and in particular, to a method and an apparatus for verifying a business process, and an electronic device.

Background

With the development of science and technology, various powerful terminal operating systems and terminal application programs are emerging continuously, and although a user has more convenient experience, many potential safety hazards may exist in the running process of the application programs, so that the application programs need to be tested before being put into use.

The sandbox can provide a closed test environment for the application program, the main application scene of the sandbox is to construct a closed environment independent of the system, and the implementation mechanism of the sandbox is to provide an operating environment capable of operating independently and being isolated from the outside at the system level mainly through a virtualization technology, or to provide a default mechanism to allow the application operating at the upper layer to use the sandbox function by supporting an independent process at the system kernel level.

The sandbox mainly provides a mechanism on a safety level, a set of closed running environment can be provided in a normal running production environment for application testing, and problems of application programs in the sandbox cannot affect an external normal running system.

Disclosure of Invention

This disclosure is provided to introduce concepts in a simplified form that are further described below in the detailed description. This disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

The embodiment of the disclosure provides a method and a device for verifying a business process and electronic equipment.

In a first aspect, an embodiment of the present disclosure provides a method for verifying a service flow, including: in response to receiving a business process to be verified, inputting the business process to be verified into a sandbox, wherein the sandbox is arranged in a process engine; and inputting the operation data of the process engine operating the business process into the sandbox, wherein the sandbox verifies the business process to be verified based on the operation data.

In a second aspect, an embodiment of the present disclosure provides a device for verifying a service flow, including: the system comprises a first input unit, a flow engine and a verification unit, wherein the first input unit is used for responding to the received business flow to be verified and inputting the business flow to be verified into a sandbox, and the sandbox is arranged in the flow engine; and the second input unit is used for inputting the operation data of the process engine for operating the business process into the sandbox, wherein the sandbox verifies the business process to be verified based on the operation data.

In a third aspect, an embodiment of the present disclosure provides an electronic device, including: one or more processors; a storage device, configured to store one or more programs, which when executed by the one or more processors, cause the one or more processors to implement the method for verifying a business process according to the first aspect.

In a fourth aspect, the disclosed embodiments provide a computer readable medium, on which a computer program is stored, which when executed by a processor, implements the steps of the business process verification method according to the first aspect.

According to the business process verification method, the business process verification device and the electronic equipment, when the business process to be verified is received, the business process to be verified is firstly input into the sandbox, and then the operation data of the process engine operating the business process is input into the sandbox. Therefore, the operating environment in the process engine is kept consistent with the operating environment in the sandbox, and whether the business process to be verified meets the verification condition can be verified more accurately.

Drawings

The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.

FIG. 1 is a flow diagram of one embodiment of a method for verification of a business process according to the present disclosure;

FIG. 2 is a schematic structural diagram of a business process in an embodiment of a method for verifying a business process according to the present disclosure;

FIG. 3 is a flow diagram of another embodiment of a method for verification of a business process according to the present disclosure;

FIG. 4 is a schematic structural diagram of a process data template in an embodiment of a business process verification method according to the present disclosure;

FIG. 5 is a schematic structural diagram of a business process in another embodiment of a business process verification method according to the present disclosure;

FIG. 6 is a flow diagram of yet another embodiment of a verification method for a business process according to the present disclosure;

FIG. 7 is a schematic block diagram illustrating one embodiment of a verification device for a business process in accordance with the present disclosure;

FIG. 8 is an exemplary system architecture to which the verification method of the business process of one embodiment of the present disclosure may be applied;

fig. 9 is a schematic diagram of a basic structure of an electronic device provided according to an embodiment of the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.

It should be understood that the various steps recited in the method embodiments of the present disclosure may be performed in a different order, and/or performed in parallel. Moreover, method embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.

The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, 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". Relevant definitions for other terms will be given in the following description.

It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.

It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.

The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.

Referring to fig. 1, a flow of one embodiment of a verification method of a business process according to the present disclosure is shown. The service flow verification method can be applied to terminal equipment or a server. The verification method of the business process shown in fig. 1 includes the following steps:

step 101, responding to the received business process to be verified, inputting the business process to be verified into the server.

Here, the sandbox is provided in the flow engine.

In some embodiments, a process engine may be understood as a type of business process that can be performed fully automatically; and (3) components for transmitting and executing the document, the information or the task among different executives according to the process rules defined by the flow.

In some embodiments, the business process to be verified may be understood as a process function, where the process function includes a plurality of sub-process functions, and the plurality of sub-process functions respectively process different process items. The verification of the to-be-verified business process can be understood as verifying whether the process function can process different process items according to an expected processing mode. For example, if the business process to be verified is an approval process, a leave-asking process, or the like, verifying the business process to be verified can be understood as: and checking whether the flow function can complete the whole flow item according to the logic expected by the staff. For example, the service flow to be verified is a leave-asking flow, and verifying the service flow to be verified can be understood as verifying whether the flow function can run the whole leave-asking flow in a manner expected by the staff when the user initiates a leave-asking flow. As shown in fig. 2, when the leave asking process is initiated by the service node a, the service node B should end, and if the leave asking process is ended by the service node C, it may indicate that the leave asking process does not meet the preset check condition, that is, it may indicate that the process function does not meet the expected logic.

In some embodiments, the sandbox is disposed in the flow engine, which may be understood as a sandbox disposed within the flow engine, which may be understood as a portion of the functionality disposed within the flow engine.

And 102, inputting the operation data of the process engine operating the business process into the sandbox.

Here, the sandbox verifies the business process to be verified based on the operational data.

In some embodiments, the operational data may be understood as a function that the process engine needs in order to facilitate the operation of the business process. In different environments, functions required for promoting the operation of the business process may be different (different versions of the functions, different types of the functions, and the like). Therefore, the operation data of the process engine operation business process can be input into the sandbox, so that the operation environment (which can be understood as function version, function type and the like) in the sandbox is ensured to be the same as the operation environment in the process engine, and the giant business to be verified can be directly operated in the process engine when the business process to be verified meets the verification condition. That is, whether the business process to be verified meets the verification condition can be more accurately verified.

It can be seen that, in the embodiment of the present application, when a to-be-verified business process is received, the to-be-verified business process is first input into a sandbox, and then operation data of a process engine operating the business process is input into the sandbox. Therefore, the operating environment in the process engine is kept consistent with the operating environment in the sandbox, and whether the business process to be verified meets the verification condition can be verified more accurately.

Furthermore, because the sandbox is arranged in the flow engine, the operation environment in the flow engine and the operation environment in the sandbox can be kept consistent only by inputting the operation data in the flow engine into the sandbox. In the prior art, the sandbox is built on the system layer, and the running environment in which the system layer pushes the business process to operate may be different from the running environment in which the process engine pushes the business process to operate, so that the running environment in the process engine and the running environment in the sandbox are difficult to keep consistent. That is, compared with the prior art, the scheme provided by the embodiment of the application can more conveniently synchronize the operating environment in the process engine and the operating environment in the sandbox.

In some embodiments, the method for checking a business process may further include steps 301 to 304, where details of implementation of

steps

301 and 302 are already described in detail at step 101 and step 102, and are not described herein again for brevity of description.

Step 303, determining a process data template corresponding to the service process to be verified.

Here, the flow data template includes service data sets respectively corresponding to each service node in the service flow to be verified

In some embodiments, the process data template may be understood as a set of dedicated data sets configured for the service process to be verified, and the process data template may be created by a worker and may define a branch condition of each service node in the service process. That is, the flow data template can be understood as where the flow node (one sub-flow function can be seen) reads the data.

Of course, in some implementations, the worker may also change the data in the flow data template (e.g., when the worker finds that some predefined data is wrong, or needs to add some new data to the business flow to be verified).

In some embodiments, the flow data template may further include a corresponding relationship between the service node and the service data, that is, a corresponding service data identifier may be added to each service data, and meanwhile, a corresponding service node identifier may also be added to the service node, and the flow data template records the corresponding relationship between the service data identifier and the service node identifier. That is, when one service data is extracted, the service node to which the service data needs to be input can be known, and correspondingly, when one service node is determined, the service data corresponding to the service node can be known. The flow data template may be as shown in fig. 4, and it can be seen from fig. 4 that a correspondence between part of service node identifiers and part of service data identifiers, that is, one service node may correspond to a plurality of service data, in other words, one service node may process a plurality of service data.

Step 304, input the flow data template into the sandbox.

Here, the sandbox verifies the business process to be verified according to the operation data and the process data template.

In some embodiments, in order to better test the function of the business process to be verified, a process data template corresponding to the business process to be verified may also be input into the sandbox. The process data template may include a service data set corresponding to each service node in the to-be-serviced process. That is, it can be understood that all data required for verifying the business process to be verified are stored in the process data template, so that in the verification process, the sandbox only needs to extract the data from the process data template. That is, the process of verification is simplified.

In some embodiments, the process data template is also stored in the storage space corresponding to the sandbox, that is, the business process running in the process engine cannot acquire the data in the process data template, thereby ensuring the security of the process engine in the process of running the business process.

In some embodiments, a sandbox engine corresponding to the sandbox runs the business process to be verified based on the running data and the process data template to obtain at least one running result, and the sandbox determines whether the business process to be verified meets the verification condition according to the at least one running result and the process data template.

In some embodiments, since the flow engine and the sandbox may be regarded as two relatively independent spaces (that is, the sandbox is isolated from the flow engine), in order to enable the to-be-verified business flow data to be smoothly operated, a sandbox engine may be configured for the sandbox, and the sandbox engine is used to push the to-be-verified business flow to be operated.

In some embodiments, the operation data (operation function) required by the sandbox engine to operate the business process to be verified can be obtained from the process engine, and the parameters required by the sandbox engine to operate the business process to be verified can be obtained from the process data template.

In some embodiments, since the corresponding relationship between the service node and the service data can be determined by the process data template, after the user initiates the inspection of the service process, the sandbox engine can push the service process to be inspected to operate by itself, so as to obtain at least one operation result. In the prior art, when the service process to be verified is tested, the operation of each service node needs to be confirmed by a worker, and the method simplifies the convenience in the process of verifying the service process to be verified.

For ease of understanding, the following is illustrated: as shown in fig. 5, the service flow to be verified includes 6 service nodes, and the flow data template stores data that can be input to the 6 service nodes. When the service data corresponding to the service node a in the flow data template is input to the service node a, the service node a outputs an operation result, where the operation result is the service data that can be responded by the service node B, and if the output result is different from the service data corresponding to the service node B, it may indicate that the logic of the service node a is wrong, that is, a logic error occurs in the sub-flow function corresponding to the service node a. And the operation data is used for extracting the data in the flow data template and correspondingly inputting the data in the flow data template into the corresponding service node.

In some embodiments, each service node may output an operation result, and if the operation result output by each service process to be verified meets the requirement, the service process may be characterized to meet the preset verification condition.

In some embodiments, the flow data template may further include flow logic between service nodes, for example, when a service node a initiates a service flow according to service data a (service data a is service data corresponding to the service node a), the service flow should be executed until a service node D ends, and if an end node of the service flow is not the service node D, but a service node F, a service node E, and the like, it may also be characterized that the service flow does not meet the check condition.

In some embodiments, the sandbox determines that the to-be-verified business process does not meet the preset verification condition in response to determining that the first operation result is different from any business data in the process data template.

Here, the at least one operation result includes a first operation result.

In some embodiments, since data that each service node in the service flow to be verified can respond to is recorded in the flow data template, if the first operation result is not data in the flow data template, it may be characterized that an operation result of a certain service node in the service flow to be verified is incorrect, that is, it may be characterized that a definition (which may be understood as a sub-flow function corresponding to the service node) corresponding to the service node is wrong, that is, it may be characterized that the service flow to be verified does not satisfy the preset verification condition.

In some embodiments, since the data required by each service node in the flow data template is stored in the flow data template, that is, the user may specify that a certain service node is detected, as shown in fig. 5, if the user needs to detect whether the service node C can normally operate, the service data that can be responded by the service node C may be extracted from the flow data template, and the service data may be respectively input into the service node C, and whether the service node C can normally operate may be determined according to the operation result of the service node C. That is, according to the technical scheme of the application, whether the whole service flow meets the preset requirement can be judged according to the operation result, and whether a certain service node can normally operate can be judged according to the operation result of the certain service node.

In some embodiments, the sandbox may determine a problem business node in the business process to be verified based on the at least one operation result and the process data template; and can add identification information for representing logic errors to the problem service node.

In some embodiments, if the operation result output by a certain service node is not data in the flow data template, it may be characterized that the service order is a problem service node. And further, identification information can be added to the service nodes, so that workers can conveniently change definitions corresponding to the problem service nodes. Meanwhile, the problem service nodes can be accurately positioned, so that the user can pertinently correct the sub-process function corresponding to the problem service nodes in the service process to be verified, namely, the efficiency of the service process to be verified in the verification (test) stage can be improved.

In some embodiments, the method for checking a business process may further include steps 601 to 605, where details of implementation of steps 601 to 604 are already described in detail in steps 301 to 304, and are not described herein again for brevity of description.

Step 605, in response to detecting the prompt information, storing the to-be-verified business process into the first storage space corresponding to the process engine.

The first storage space is different from the second storage space, the second storage space is a storage space corresponding to the sandbox, and the sandbox determines that the business process to be verified meets the verification condition in response to the fact that at least one operation result is the business data in the process data template, and generates prompt information for indicating that the business process to be verified is stored in the first storage space.

In some embodiments, when the business process to be verified meets the preset verification condition, the sandbox may generate a prompt message for prompting the process engine, and when the process engine detects the prompt message, the process engine may input the business process indicated by the prompt message from the second storage space to the first storage space for storage.

Since the sandbox is arranged in the process engine, the business process indicated by the prompt message only needs to be converted into a storage location, and the business process does not need to be firstly exported from the system layer sandbox and then imported into the process engine as in the prior art.

In some embodiments, the flow data templates and run data within the sandbox are deleted in response to receiving the reset instruction.

In some embodiments, in response to receiving a reset instruction, the indication of one run result stored within the sandbox may also be deleted.

In some embodiments, when a worker can adjust a process definition (a definition corresponding to a part of process nodes in a business process), the worker can also change values in the process data template. Therefore, the data in the first storage space may be increased, and therefore, the efficiency of acquiring the data from the first storage space when the sandbox engine in the sandbox runs the process to be verified may be affected. And at this moment, the working personnel can set the flow data template for the service flow to be verified again. Therefore, the sandbox engine can acquire the required data from the flow data template more quickly and the efficiency of the sandbox engine in verifying (testing) the business flow to be verified can be further improved.

With further reference to fig. 7, as an implementation of the method shown in the above diagrams, the present disclosure provides an embodiment of a verification apparatus for a business process, where the embodiment of the apparatus corresponds to the embodiment of the business process method shown in fig. 1, and the apparatus may be specifically applied to various electronic devices.

As shown in fig. 7, the verification apparatus for business process of this embodiment includes: a first input unit 701, configured to input, in response to receiving a to-be-verified business process, the to-be-verified business process into a sandbox, where the sandbox is arranged in a process engine; a second input unit 702, configured to input operation data of the process engine running the business process into the sandbox, where the sandbox verifies the business process to be verified based on the operation data.

In some embodiments, the apparatus further includes a determining unit 703 and a third input unit 704, where the determining unit 703 is configured to determine a flow data template corresponding to the service flow to be verified, where the flow data template includes service data sets respectively corresponding to service nodes in the service flow to be verified; the third input unit 704 is configured to input the process data template into the sandbox, where the sandbox verifies the to-be-verified business process according to the operation data and the process data template.

In some embodiments, the sandbox engine corresponding to the sandbox runs the to-be-verified business process based on the running data and the process data template to obtain at least one running result, and the sandbox determines whether the to-be-verified business process meets a verification condition according to the at least one running result and the process data template.

In some embodiments, the sandbox determines that the to-be-verified business process does not meet a preset verification condition in response to determining that the first operation result is different from any business data in the process data template, where the at least one operation result includes the first operation result.

In some embodiments, the sandbox determines a problem business node in the business process to be verified based on the at least one operation result and the process data template; and adding identification information for representing logic errors to the problem service node.

In some embodiments, the apparatus further comprises: the storage unit 705 is configured to, in response to detection of a prompt message, store the to-be-verified business process into a first storage space corresponding to the process engine, where the first storage space is different from a second storage space, the second storage space is a storage space corresponding to the sandbox, and the sandbox determines that the to-be-verified business process meets a verification condition in response to determining that the at least one operation result is business data in the process data template, and generates a prompt message used for instructing to store the to-be-verified business process into the first storage space.

In some embodiments, the apparatus further comprises: a deleting unit 706, configured to delete the to-be-verified business process and the running data in the sandbox in response to receiving a reset instruction.

Referring to fig. 8, fig. 8 illustrates an exemplary system architecture in which the business process method of one embodiment of the present disclosure may be applied.

As shown in fig. 8, the system architecture may include

terminal devices

801, 802, 803, a network 804, and a server 808. The network 804 may be the medium used to provide communications links between the

terminal devices

801, 802, 803 and the server 808. Network 804 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.

The

terminal devices

801, 802, 803 may interact with a server 808 via a network 804 to receive or transmit messages or the like. The

terminal devices

801, 802, 803 may have various client applications installed thereon, such as a web browser application, a search-type application, and a news-information-type application. The client application in the

terminal device

801, 802, 803 may receive the instruction of the user, and complete the corresponding function according to the instruction of the user, for example, add the corresponding information in the information according to the instruction of the user.

The

terminal devices

801, 802, 803 may be hardware or software. When the

terminal devices

801, 802, 803 are hardware, they may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, e-book readers, MP3 players (Moving Picture Experts Group Audio Layer III, mpeg compression standard Audio Layer 3), MP4 players (Moving Picture Experts Group Audio Layer IV, mpeg compression standard Audio Layer 4), laptop portable computers, desktop computers, and the like. When the

terminal devices

801, 802, 803 are software, they can be installed in the electronic devices listed above. It may be implemented as multiple pieces of software or software modules (e.g., software or software modules used to provide distributed services) or as a single piece of software or software module. And is not particularly limited herein.

The server 808 may be a server providing various services, for example, receiving an information acquisition request sent by the

terminal devices

801, 802, and 803, and acquiring presentation information corresponding to the information acquisition request in various ways according to the information acquisition request. And the relevant data of the presentation information is sent to the

terminal devices

801, 802, 803.

It should be noted that the information processing method provided by the embodiment of the present disclosure may be executed by a terminal device, and accordingly, the business process apparatus may be disposed in the

terminal devices

801, 802, and 803. Furthermore, the information processing method provided by the embodiment of the present disclosure may also be executed by the server 808, and accordingly, an information processing apparatus may be provided in the server 808.

It should be understood that the number of terminal devices, networks, and servers in fig. 8 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.

Referring now to fig. 9, shown is a schematic diagram of an electronic device (e.g., a terminal device or a server of fig. 8) suitable for use in implementing embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a vehicle terminal (e.g., a car navigation terminal), and the like, and a stationary terminal such as a digital TV, a desktop computer, and the like. The electronic device shown in fig. 9 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 9, the electronic device may include a processing means (e.g., a central processing unit, a graphics processor, etc.) 901 that can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)902 or a program loaded from a storage means 808 into a Random Access Memory (RAM) 903. In the RAM 903, various programs and data necessary for the operation of the electronic apparatus 900 are also stored. The processing apparatus 901, the ROM902, and the RAM 903 are connected to each other through a bus 904. An input/output (I/O) interface 905 is also connected to bus 904.

Generally, the following devices may be connected to the I/O interface 905: input devices 906 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 907 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 908 including, for example, magnetic tape, hard disk, etc.; and a communication device 909. The communication means 909 may allow the electronic device to perform wireless or wired communication with other devices to exchange data. While fig. 9 illustrates an electronic device having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.

In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present 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 method illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device 909, or installed from the storage device 908, or installed from the ROM 902. The computer program performs the above-described functions defined in the methods of the embodiments of the present disclosure when executed by the processing apparatus 901.

It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.

In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.

The computer readable medium may be embodied in the electronic device; or may exist separately without being assembled into the electronic device.

The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: in response to receiving a business process to be verified, inputting the business process to be verified into a sandbox, wherein the sandbox is arranged in a process engine; and inputting the operation data of the process engine operating the business process into the sandbox, wherein the sandbox verifies the business process to be verified based on the operation data.

Computer program code for carrying out operations for the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The units described in the embodiments of the present disclosure may be implemented by software or hardware. The name of a unit does not in some cases form a limitation on the unit itself, for example, the first input unit 701 may also be described as a "unit inputting the business process to be verified to a sandbox".

The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), systems on a chip (SOCs), Complex Programmable Logic Devices (CPLDs), and the like.

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

The foregoing description is only exemplary of the preferred embodiments of the disclosure and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the disclosure herein is not limited to the particular combination of features described above, but also encompasses other embodiments in which any combination of the features described above or their equivalents does not depart from the spirit of the disclosure. For example, the above features and (but not limited to) the features disclosed in this disclosure having similar functions are replaced with each other to form the technical solution.

Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.

Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method for verifying a business process is characterized by comprising the following steps:

in response to receiving a business process to be verified, inputting the business process to be verified into a sandbox, wherein the sandbox is arranged in a process engine;

and inputting the operation data of the process engine operating the business process into the sandbox, wherein the sandbox verifies the business process to be verified based on the operation data.

2. The method of claim 1, further comprising:

determining a process data template corresponding to the service process to be verified, wherein the process data template comprises service data sets corresponding to all service nodes in the service process to be verified respectively;

and inputting the flow data template into the sandbox, wherein the sandbox verifies the business flow to be verified according to the operation data and the flow data template.

3. The method according to claim 2, wherein a sandbox engine corresponding to the sandbox runs the business process to be verified based on the running data and the process data template to obtain at least one running result, and the sandbox determines whether the business process to be verified meets a verification condition according to the at least one running result and the process data template.

4. The method of claim 1, wherein the sandbox determines that the business process to be verified does not meet a predetermined verification condition in response to determining that the first operation result is different from any of the business data in the process data template, wherein the at least one operation result includes the first operation result.

5. The method of claim 3, wherein the sandbox determines problem business nodes in the business process to be verified based on the at least one operation result and the process data template;

and adding identification information for representing logic errors to the problem service node.

6. The method of claim 3, further comprising:

and in response to the detection of the prompt information, storing the business process to be verified into a first storage space corresponding to the process engine, wherein the first storage space is different from a second storage space, the second storage space is a storage space corresponding to the sandbox, and the sandbox determines that the business process to be verified conforms to the verification condition in response to the determination that the at least one operation result is the business data in the process data template, and generates prompt information for indicating the storage of the business process to be verified to the first storage space.

7. The method of claim 1, further comprising:

and in response to receiving a reset instruction, deleting the business process to be verified and the running data in the sandbox.

8. An apparatus for verifying a business process, comprising:

the system comprises a first input unit, a flow engine and a verification unit, wherein the first input unit is used for responding to the received business flow to be verified and inputting the business flow to be verified into a sandbox, and the sandbox is arranged in the flow engine;

and the second input unit is used for inputting the operation data of the process engine for operating the business process into the sandbox, wherein the sandbox verifies the business process to be verified based on the operation data.

9. An electronic device, comprising:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.

10. A computer-readable medium, on which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1-7.