CN113467782B - Method, device and equipment for determining business process - Google Patents
Method, device and equipment for determining business process Download PDFInfo
- Publication number
- CN113467782B CN113467782B CN202110753594.3A CN202110753594A CN113467782B CN 113467782 B CN113467782 B CN 113467782B CN 202110753594 A CN202110753594 A CN 202110753594A CN 113467782 B CN113467782 B CN 113467782B
- Authority
- CN
- China
- Prior art keywords
- information
- node
- flow
- link
- business
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/40—Transformation of program code
- G06F8/41—Compilation
- G06F8/43—Checking; Contextual analysis
- G06F8/433—Dependency analysis; Data or control flow analysis
Abstract
The embodiment of the specification provides a method, a device and equipment for determining a business process, and the method, the device and the equipment for determining the business process can be used in the technical field of big data. The method comprises the steps of obtaining a process identification corresponding to a target transaction; acquiring corresponding process information according to the process identification; acquiring node information of each link in the service flow according to the node identification included in the flow information; and determining the business process of the target transaction based on the process information and the node information. By using the embodiment of the specification, the coupling degree of the business process and the specific business requirement is lower, the business adjustment does not depend on code control, the programming difficulty can be effectively reduced, the universality of the business process is stronger, and the development efficiency is higher.
Description
Technical Field
The present application relates to the field of process control, and in particular, to a method, an apparatus, and a device for determining a service process.
Background
With the continuous development of internet technology, complex processes need to be developed for processing various services in many applications.
In the prior art, when a business process is developed, a developer first judges branch conditions included in a corresponding scene, and then writes corresponding codes. When the branch situation is more, the method not only easily causes the problem of weak adaptability of business change due to poor consideration, but also needs to rewrite the code as long as the flow changes because the dependency of business adjustment on the code is high, thereby causing the universality of the business flow to be weak and the development efficiency to be lower.
Therefore, there is a need for a solution to the above technical problems.
Disclosure of Invention
The embodiment of the specification provides a method, a device and equipment for determining a business process, which can not only make the degree of coupling between the business process and specific business requirements lower, make business adjustment independent of code control, but also effectively reduce programming difficulty, make the business process have stronger universality and higher development efficiency.
The method, the device and the equipment for determining the business process provided by the specification are realized in the following modes.
A method of determining a business process, comprising: acquiring a process identifier corresponding to a target transaction; acquiring corresponding process information according to the process identification; acquiring node information of each link in the service flow according to the node identification included in the flow information; and determining the business process of the target transaction based on the process information and the node information.
An apparatus for determining a business process, comprising: the first acquisition module is used for acquiring a process identifier corresponding to the target transaction; the second acquisition module is used for acquiring corresponding process information according to the process identification; a third obtaining module, configured to obtain node information of each link in the service flow according to the node identifier included in the flow information; and the determining module is used for determining the business process of the target transaction based on the process information and the node information.
An apparatus for determining a business process, comprising at least one processor and a memory storing computer-executable instructions, which when executed by the processor, implement the steps of any one of the method embodiments of the present specification.
A computer readable storage medium having stored thereon computer instructions which, when executed, implement the steps of any one of the method embodiments in the present specification.
The specification provides a method, a device and equipment for determining a business process. In some embodiments, a process identifier corresponding to the target transaction may be obtained, and corresponding process information may be obtained according to the process identifier. The node information of each link in the business process can be obtained according to the node identification included in the process information, and the business process of the target transaction is determined based on the process information and the node information. The process and the key link are pre-configured with parameters, so that the related parameters can be directly read to determine the business process when the business process needs to be determined subsequently, the coupling degree of the business process and the specific business requirement is lower, the business adjustment does not depend on code control, the programming difficulty can be effectively reduced, the universality of the business process is stronger, and the development efficiency is higher.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification, are incorporated in and constitute a part of this specification, and are not intended to limit the specification. In the drawings:
FIG. 1 is a flow diagram of one embodiment of a method for determining a business process provided herein;
FIG. 2 is a flow definition interface diagram provided herein;
FIG. 3 is a ring definition interface diagram provided in the present specification;
FIG. 4 is a block diagram illustrating an exemplary embodiment of an apparatus for determining a business process;
fig. 5 is a block diagram of a hardware structure of an embodiment of a server for determining a business process provided in the present specification.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments in the present specification, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on one or more embodiments in the present specification without making any creative effort shall fall within the protection scope of the embodiments in the present specification.
The following describes an embodiment of the present disclosure with a specific application scenario as an example. Specifically, fig. 1 is a schematic flow chart diagram of an embodiment of a method for determining a business process provided in this specification. Although the present specification provides the method steps or apparatus structures as shown in the following examples or figures, more or less steps or modules may be included in the method or apparatus structures based on conventional or non-inventive efforts.
One embodiment provided by the present specification can be applied to a client, a server, and the like. The client may include a terminal device, such as a smart phone, a tablet computer, and the like. The server may include a single computer device, or may include a server cluster formed by a plurality of servers, or a server structure of a distributed system, and the like.
It should be noted that the following description of the embodiments does not limit the technical solutions in other extensible application scenarios based on the present specification. In an embodiment of a method for determining a business process provided by the present specification, as shown in fig. 1, the method may include the following steps.
S0: and acquiring a process identifier corresponding to the target transaction.
Wherein the target transaction may be an application to be developed. Since a transaction may be implemented including one or more flows, a target transaction may correspond to one or more flow identifications. In some implementation scenarios, the flow identifier may be composed of one or more of numbers, letters, symbols, and the like, which is not limited in this specification.
In some implementation scenarios, after determining the target transaction, the corresponding flow identifier may be correspondingly determined, so as to subsequently determine the flow information according to the flow identifier.
S2: and acquiring corresponding flow information according to the flow identification.
In this embodiment of the present description, after the flow identifier corresponding to the target transaction is obtained, corresponding flow information may be obtained according to the flow identifier.
In some embodiments, before obtaining the corresponding flow information according to the flow identifier, the flow information corresponding to each business flow may be determined in response to configuration of a user on flow parameters in a visual interface; responding to the configuration of link parameters in a visual interface by a user, and determining the node information of each link in each business process; each business process comprises a plurality of links, and each link corresponds to one node identifier. The visual interface can comprise editable text boxes for configuring attribute information of each process. Of course, the above description is only exemplary, and other information, pages, etc. may be included in the visualization interface, and the embodiments of the present disclosure are not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the present disclosure, but all the functions and effects that are achieved by the embodiments are also covered by the scope of the present disclosure.
In some implementation scenarios, the flow information may include: the system comprises a process applicable mechanism, a process name, a process identifier, a node identifier, an identifier representing the execution sequence of the nodes, a node name, a service classification, a service name and the like. The flow applicable mechanism may include a head office, a branch office 1, a branch office 2, and the like. The process name can be plan management, plan budget management, field visit, license management, visit report, etc. The flow identification and the node identification may be composed of one or more of numbers, letters, symbols, and the like. The node identification may also be referred to as a link ID. The identifier indicating the execution order of the nodes may be sequence numbers 1, 2, 3 \8230;. The node name may also be referred to as a link name, for example, the node name in the plan management process may include draft, department review, department summary, department review, and the like. The business classification may be a category to which the process belongs, such as plan management, license management, and the like. The business names may be a leader group, a subgroup leader group, etc.
In some implementations, the flow definition may be performed in a visualization interface. The process definition may be understood as configuration of process parameters, so as to determine process information corresponding to each business process, which may include configuration of basic process information and link information setting. As shown in fig. 2, fig. 2 is a flow definition interface diagram provided in this specification. The configured basic information of the process includes a process applicable mechanism, a service classification, a service name, a process name and all links. The configured link information includes an identifier indicating the execution order of the nodes, a link name, a link identifier, and the like. The process applicable mechanism is a head office, the business is classified into plan management, the business name is a head group, the process name is plan management, and all links are draft planning, department auditing, department summarizing, department auditing and department draft checking. The identifiers representing the execution sequence of the nodes are serial numbers 1 and 2, the link ID corresponding to the draft link is 07f91be 709643ca857afa06276a1a62, and the link ID corresponding to the processing room auditing link is a8716b459421471eb40b8dc1748a8448. It is to be understood that the above description is only exemplary, the process information is not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the present disclosure, and the function and effect of the present disclosure should be covered by the protection scope of the present disclosure.
In some implementation scenarios, the node information may include: node name, node handler information, node constraint condition information, subsequent node information, and the like.
In some implementation scenarios, the link definition may be performed in a visual interface. The link definition can be understood as the configuration of link parameters, so as to determine the node information of each link in each business process. As shown in fig. 3, fig. 3 is a ring definition interface diagram provided in this specification. The handler selection scope may be used to determine node handler information, which may include department and specific personnel. In some implementation scenarios, a department and a specific person may be designated or selected according to an actual scenario, which is not limited in this specification. The link characteristics of the conditions to be constrained can be used to determine node constraint condition information, which can be selected according to an actual scene, and this specification does not limit this. The subsequent link may be used to determine subsequent node information, for example, the link after the draft creating link may include office review and department summary, and of course, the subsequent link may also be selected according to an actual scene. Of course, the above description is only exemplary, the node information is not limited to the above examples, and other modifications may be made by those skilled in the art in light of the technical spirit of the present application, and all that is needed is to achieve the same or similar functions and effects as the present application and to be included in the scope of the present application.
In some implementation scenarios, after determining the process information and the node information, the process information and the corresponding process identifier may be stored in an associated manner; and storing the node information and the corresponding node identification in a correlation manner.
In some implementation scenarios, after the visual interface defines the business process and links, the process and link description may be stored in the data file in a data form. The data file may be a data table in a database, or an Excel table, or the like.
In the embodiment of the present specification, parameter configuration is performed on a service process and a link based on a visual interface, a complete service process description is established, datamation and parameterization control of an actual service scene can not be achieved, and a guarantee can be provided for subsequently acquiring process information and node information.
In some implementation scenarios, after the configuration of the flow parameters, the flow parameters may be further manipulated, such as modified, viewed, deleted, and the like.
In some implementation scenarios, after configuring the flow parameters, the corresponding flow information and/or node information may be adjusted in response to modification of the flow parameters and/or link parameters by the user in the visual interface. In some implementation scenarios, the user may modify only the flow parameters, may modify only the link parameters, and may modify the flow parameters and the link parameters at the same time, which is not limited in this specification.
For example, in some implementation scenarios, if the business process needs to be adjusted, the predefined process and link information may be adjusted by accessing the page. Of course, the above description is only an exemplary illustration, and the embodiment of the present disclosure may also adjust the predefined process and link information in other manners, for example, by means of voice control, manual modification, and other manners, and those skilled in the art may make other changes within the spirit of the present disclosure, but the present disclosure shall be covered by the scope of the present disclosure as long as the achieved functions and effects are the same as or similar to those of the present disclosure.
In the embodiment of the specification, the business model can be converted into the data model by defining the flow and the link in advance and describing the business logic by using the mathematical language, so that the business flow of the application can be determined by directly reading the data parameters, and the development efficiency of the business flow is improved.
In the embodiment of the specification, the business process can be dynamically adjusted without adjusting application codes, so that the application and specific business requirements are low in coupling degree, and business adjustment does not depend on code control.
In some implementation scenarios, after the flow parameters and the link parameters are configured through the visual interface and are kept in the database, the corresponding flow information can be obtained from the database according to the flow identifier corresponding to the target transaction. Wherein, the database can be MySQL, oracle, etc.
S4: and acquiring the node information of each link in the service flow according to the node identification included in the flow information.
In the embodiment of the present specification, after the corresponding flow information is obtained according to the flow identifier, the node information of each link in the service flow may be obtained according to the node identifier.
In some implementation scenarios, since the process information includes the node identifier corresponding to each link, after the process information is obtained, the node information of each link in the service process can be obtained from the database according to the node information included in the process information. Wherein, the node information may include: node name, node handler information, node constraint condition information, subsequent node information, and the like.
S6: and determining the business process of the target transaction based on the process information and the node information.
In the embodiment of the present specification, after the node information of each link in the business process is obtained, the business process of the target transaction may be determined based on the process information and the node information. The business process can be understood as a working process formed by orderly process nodes and execution modes.
In some implementation scenarios, the determining the business process of the target transaction based on the process information and the node information may include: and combining the process information and the node information based on service logic to obtain the service process of the target transaction.
For example, in some implementation scenarios, when controlling the transaction process in the application system, the related data of the related process definition and the link definition may be extracted from the database, and then the data is quickly assembled in combination with the business logic to obtain different business processes. It is to be understood that the above description is only exemplary, the assembling manner of the flow information and the node information is not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the present application, but all the functions and effects achieved by the present application are covered by the scope of the present application.
In some implementation scenarios, after determining the business process of the target transaction, the business process may be executed to obtain an execution result. The execution result may include an execution result corresponding to each link, and may also include a final execution result.
In some implementation scenarios, in the process of executing the business process, the process parameters and link parameter release changes can be monitored in real time.
In some implementation scenarios, when a process parameter and/or a link parameter corresponding to the business process is monitored to be changed, the changed information can be acquired; re-determining the business process of the target transaction based on the changed information; correspondingly, the business process is executed, and an execution result is obtained.
For example, in some implementation scenarios, when it is determined that the process parameter changes, the changed process parameter may be correspondingly obtained, and then the service process of the target transaction is determined again according to the changed process parameter and the node information, so that the service process may be quickly determined without modifying the background code, and the development efficiency of the service process may be improved.
In some implementation scenarios, in the process of executing the business process, a first execution result of the first link may also be obtained; and judging whether the first execution result is in a preset result range or not, and sending execution error information under the condition of determining that the first execution result is not in the preset result range. The first link may be any link in the business process. The preset result range may be a range in which an execution result set for each link in advance is located. The preset result range can be set according to an actual scene, which is not limited in this specification. The preset result ranges corresponding to different links can be the same or different.
In some implementation scenarios, the execution error information may include at least: and node identification, error type and error data corresponding to the error link. Of course, the above is only an exemplary description, the execution error information is not limited to the above examples, and other modifications are possible for those skilled in the art in light of the technical spirit of the present application, and all that can be achieved is intended to be covered by the scope of the present application as long as the achieved functions and effects are the same as or similar to the present application.
In some implementations, after the business process is executed, the business process may be encapsulated and then individual microservices are provided. Microservice (or microservice architecture) is a cloud-native architecture approach in which a single application is composed of many loosely-coupled and independently deployable smaller components or services. Microservices may split an application into multiple core functions. Each function is called a service, which can be built and deployed individually, and the services do not affect each other when working (and failing).
In some implementation scenarios, an error correction procedure may also be initiated if the first execution result is not within a preset result range. The error correction process may be used to recommend data corresponding to each service attribute in the error link or may be used to provide a data range corresponding to each service attribute in the error link. One or more business attributes may be included in each link. In some implementation scenarios, a value range, that is, a data range, may be preset for each service data.
In some implementation scenarios, when the execution result is determined not to be within the preset result range, the service flow may automatically remind the error occurrence link, the error type and the error data, and provide correct data reminding and service attribute recommendation according to the configuration parameters. Therefore, the problem that errors cannot be found or are difficult to locate can be solved, and the fault tolerance rate of code coding can be reduced, so that the universality is improved.
In the embodiment of the present specification, when the service flow exceeds the preset result range, the error correction flow can be automatically started, so that the error troubleshooting efficiency and the error resolution efficiency can be improved.
The embodiment of the specification can be applied to a collaborative office scene. The cooperative work is an important matter processed by multiple departments and multiple roles together. For example, after a department 1 develops a business process 1, corresponding process parameters and link parameters can be configured on a visual interface, and after a department 2 develops a business process 2, corresponding process parameters and link parameters can be configured on the visual interface, wherein a process applicable mechanism of the business process 1 is configured as the department 1, and a process applicable mechanism of the business process 2 is configured as the department 2, so that when multiple departments and multiple roles need to process an important business (the business at least comprises the business process 1 and the business process 2), different departments can call corresponding business processes to realize cooperative office, and further, business advantages of each department can be fully utilized. It can be seen that the embodiments of the present specification can adopt a parameterized and configurable manner to solve the flow control problem encountered in the cooperative office flow control process.
In the embodiment of the specification, the design function of parameterization and configuration in key links such as a process, a node and the like is provided, and the service process is managed and defined in advance, so that the relevant parameters can be directly read subsequently to determine the service process, thereby not only effectively reducing the programming difficulty and enabling the code to be more standard, but also being easy to troubleshoot errors.
The embodiment of the specification can configure the trend of the driving process links according to the business requirements, add and adjust the successor and predecessor processes of the process, realize the parameterized configuration of the process, and change the business process links through the adjustment of the parameters. In the embodiments of the present description, node configuration, such as adding a node and adjusting a node, may be performed according to an organization, so as to implement parameterized node configuration.
In the embodiment of the present specification, parameterized configuration information such as a process, a node, and the like may be stored in a configuration file database to form a workflow parameter information matrix. Therefore, the logic realization design of the workflow does not need to be considered in the system development process, and the accurate control of the process can be carried out only by reading the data in the workflow parameter information matrix.
In the embodiment of the specification, for the adjustment and change of the process and the node, the application code does not need to be changed, and only the parameter or the configuration link needs to be adjusted, so that the complexity of programming can be greatly reduced, the probability of error occurrence can be effectively controlled, and the usability and the adaptability of the system can be improved.
It is to be understood that the foregoing is only exemplary, and the embodiments of the present disclosure are not limited to the above examples, and other modifications may be made by those skilled in the art within the spirit of the present disclosure, and the scope of the present disclosure is intended to be covered by the claims as long as the functions and effects achieved by the embodiments are the same as or similar to the present disclosure.
From the above description, it can be seen that, in the embodiment of the present application, the flow identifier corresponding to the target transaction may be obtained, and the corresponding flow information is obtained according to the flow identifier. And node information of each link in the business process can be acquired according to the node identification included in the process information, and the business process of the target transaction is determined based on the process information and the node information. The process and the key link are pre-configured with parameters, so that the related parameters can be directly read to determine the business process when the business process needs to be determined subsequently, the coupling degree of the business process and the specific business requirement is lower, the business adjustment does not depend on code control, the programming difficulty can be effectively reduced, the universality of the business process is stronger, and the development efficiency is higher.
In the present specification, each embodiment of the method is described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from other embodiments. Reference is made to the description of the method embodiments in part.
Based on the method for determining the business process, one or more embodiments of the present specification further provide a device for determining the business process. The apparatus may include systems (including distributed systems), software (applications), modules, components, servers, clients, etc. that use the methods described in the embodiments of this specification in conjunction with any necessary apparatus to implement the hardware. Based on the same innovative concept, the embodiments of the present specification provide one or more embodiments with devices as described in the following embodiments. Since the implementation scheme of the apparatus for solving the problem is similar to that of the method, the specific implementation of the apparatus in the embodiment of the present specification may refer to the implementation of the foregoing method, and repeated details are not repeated. As used hereinafter, the term "unit" or "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware, or a combination of software and hardware is also possible and contemplated.
Specifically, fig. 4 is a schematic block structure diagram of an embodiment of an apparatus for determining a business process provided in this specification, and as shown in fig. 4, the apparatus for determining a business process provided in this specification may include: a first obtaining module 120, a second obtaining module 122, a third obtaining module 124, and a determining module 126.
A first obtaining module 120, configured to obtain a flow identifier corresponding to the target transaction;
a second obtaining module 122, configured to obtain corresponding flow information according to the flow identifier;
a third obtaining module 124, configured to obtain node information of each link in the service flow according to the node identifier included in the flow information;
the determining module 126 may be configured to determine a business process of the target transaction based on the process information and the node information.
Wherein the target transaction may be an application to be developed. Since a transaction may be implemented to include one or more flows, a target transaction may correspond to one or more flow identifications. In some implementation scenarios, the flow identifier may be composed of one or more numbers, letters, symbols, and the like, which is not limited in this specification.
In some implementation scenarios, after the target transaction is determined, the corresponding flow identifier may be determined accordingly, so as to determine the flow information according to the flow identifier subsequently.
In some implementation scenarios, before acquiring the corresponding flow information according to the flow identifier, the method may include:
the first response unit is used for responding to the configuration of the flow parameters in the visual interface by the user and determining the flow information corresponding to each business flow;
the second response unit is used for responding the configuration of the link parameters in the visual interface by the user and determining the node information of each link in each business process; each business process comprises a plurality of links, and each link corresponds to one node identifier. Editable text boxes can be included in the visualization interface for configuring attribute information of each process.
In some implementation scenarios, the flow information may include: the system comprises a flow applicable mechanism, a flow name, a flow identifier, a node identifier, an identifier for indicating the execution sequence of the node, a node name, a service classification and a service name. The node information may include: node name, node handler information, node constraint condition information, and subsequent node information.
In some implementation scenarios, after determining the flow information and the node information, the method may further include:
the first storage unit is used for storing the flow information and the corresponding flow identifier in an associated manner;
and the second storage unit is used for storing the node information and the corresponding node identifier in an associated manner.
In some implementations, the flow definition may be performed in a visualization interface. The process definition may be understood as configuration of process parameters, so as to determine process information corresponding to each business process, which may include configuration of basic process information and link information setting. In some implementation scenarios, the link definition may be performed in a visual interface. The link definition can be understood as the configuration of link parameters, so as to determine the node information of each link in each business process.
In some implementation scenarios, after the visual interface defines the business process and links, the process and link description may be stored in the data file in a data form. The data file may be a data table in a database, or an Excel table, or the like.
In some implementation scenarios, the method may further include:
and the third response unit is used for responding to the modification of the flow parameters and/or the link parameters in the visual interface by the user and adjusting the corresponding flow information and/or the node information.
In some implementation scenarios, a user may modify only a flow parameter, may modify only a link parameter, and may modify the flow parameter and the link parameter at the same time, which is not limited in this specification. For example, in some implementation scenarios, if the business process needs to be adjusted, the predefined process and link information can be adjusted by accessing the page.
In some implementation scenarios, the determining module 126 may include:
and the determining unit is used for combining the flow information and the node information based on service logic to obtain the service flow of the target transaction.
For example, in some implementation scenarios, when controlling the transaction flow in the application system, the related data of the relevant flow definition and the link definition may be extracted from the database, and then the different business flows may be obtained by combining with the business logic for fast assembly.
In some implementation scenarios, after determining the business process of the target transaction, the method may further include:
and the execution module is used for executing the business process and obtaining an execution result. The execution result may include an execution result corresponding to each link, and may also include a final execution result.
In some implementation scenarios, in the process of executing the business process, the process parameters and link parameter release changes can be monitored in real time.
In some implementation scenarios, the process of executing the business process may include:
the monitoring unit is used for acquiring changed information under the condition that the process parameters and/or link parameters corresponding to the business process are/is monitored to be changed;
the determining unit is used for re-determining the business process of the target transaction based on the changed information;
correspondingly, the business process is executed, and an execution result is obtained.
For example, in some implementation scenarios, when it is determined that the process parameter changes, the changed process parameter may be correspondingly obtained, and then the service process of the target transaction is determined again according to the changed process parameter and the node information, so that the service process may be quickly determined without modifying the background code, and the development efficiency of the service process may be improved.
In some implementation scenarios, the process of executing the business process may further include:
the acquisition unit is used for acquiring a first execution result of the first link;
and the sending unit is used for sending execution error information under the condition that the first execution result is not in a preset result range. The first link may be any link in the business process. The preset result range may be a range in which an execution result set for each link in advance is located. The preset result range can be set according to an actual scene, and the specification does not limit the preset result range. The preset result ranges corresponding to different links can be the same or different. The execution error information may include at least: and node identification, error type and error data corresponding to the error link.
In some implementation scenarios, in a case that the first execution result is not within a preset result range, the method may further include:
the starting unit is used for starting an error correction process; the error correction process is used for recommending data corresponding to each business attribute in the error link or providing a data range corresponding to each business attribute in the error link.
In some implementation scenarios, when the execution result is determined not to be within the preset result range, the service flow may automatically remind the error occurrence link, the error type and the error data, and provide correct data reminding and service attribute recommendation according to the configuration parameters. Therefore, the problem that errors cannot be found or are difficult to locate can be solved, and the fault tolerance rate of code coding can be reduced, so that the universality is improved.
In the embodiment of the present specification, when the service flow exceeds the preset result range, the error correction flow may be automatically started, so that the error troubleshooting efficiency and the error resolution efficiency may be improved.
In some implementations, after the business process is executed, the business process can be encapsulated and then individual microservices are provided. Microservices (or microservices architecture) are a cloud-native architecture approach in which a single application consists of many loosely coupled and independently deployable smaller components or services. Microservices may split an application into multiple core functions. Each function is called a service, which can be built and deployed separately, and the services do not affect each other when working (and failing).
In the embodiment of the specification, when a background application is required to determine the business processes corresponding to different business scenes, the parameterization configuration of the processes and the nodes is performed in advance, the actual business is subjected to data processing, and a corresponding data description matrix is established, so that a subsequent application developer can accurately realize process control by only reading corresponding process and node data from a database, thereby greatly improving the development efficiency, reducing the development difficulty and preparing for positioning problems.
In the embodiment of the specification, for the adjustment and change of the process and the node, the application code does not need to be changed, and only the parameter or the configuration link needs to be adjusted, so that the complexity of programming can be greatly reduced, the probability of error occurrence can be effectively controlled, and the usability and the adaptability of the system can be improved.
It should be noted that the description of the apparatus according to the method embodiment may also include other embodiments, and for a specific implementation, reference may be made to the description of the related method embodiment, which is not described in detail herein.
This specification also provides an embodiment of an apparatus for determining a business process, comprising a processor and a memory for storing processor-executable instructions, which when executed by the processor, implement steps comprising: acquiring a process identifier corresponding to a target transaction; acquiring corresponding process information according to the process identification; acquiring node information of each link in the service flow according to the node identification included in the flow information; and determining the business process of the target transaction based on the process information and the node information.
It should be noted that the above-mentioned apparatuses may also include other embodiments according to the description of the method or apparatus embodiments. The specific implementation manner may refer to the description of the related method embodiment, and is not described in detail herein.
The method embodiments provided in the present specification may be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Taking an example of the server running on a server, fig. 5 is a hardware structure block diagram of an embodiment of a server for determining a business process provided in this specification, where the server may be an apparatus for determining a business process or a device for determining a business process in the foregoing embodiments. As shown in fig. 5, the server 10 may include one or more (only one shown) processors 100 (the processors 100 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 200 for storing data, and a transmission module 300 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 5 is only an illustration and is not intended to limit the structure of the electronic device. For example, the server 10 may also include more or fewer components than shown in FIG. 5, may also include other processing hardware, such as databases or caches, GPUs, or may have a different configuration than shown in FIG. 5, for example.
The memory 200 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the method for determining a business process in the embodiments of the present specification, and the processor 100 executes various functional applications and data processing by executing the software programs and modules stored in the memory 200. Memory 200 may include high speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 200 may further include memory located remotely from processor 100, which may be connected to a computer terminal through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission module 300 is used for receiving or transmitting data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal. In one example, the transmission module 300 includes a Network adapter (NIC) that can be connected to other Network devices through a base station so as to communicate with the internet. In one example, the transmission module 300 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The method or apparatus provided by the present specification and described in the foregoing embodiments may implement service logic through a computer program and record the service logic on a storage medium, where the storage medium may be read and executed by a computer, so as to implement the effect of the solution described in the embodiments of the present specification. The storage medium may include a physical device for storing information, and typically, the information is digitized and stored using an electrical, magnetic, or optical media. The storage medium may include: devices that store information using electrical energy, such as various types of memory, e.g., RAM, ROM, etc.; devices that store information using magnetic energy such as hard disks, floppy disks, tapes, core memories, bubble memories, and usb disks; devices that store information optically, such as CDs or DVDs. Of course, there are other ways of storing media that can be read, such as quantum memory, graphene memory, and so forth.
The method or apparatus embodiment for determining a service flow provided in this specification may be implemented in a computer by a processor executing corresponding program instructions, for example, by using a c + + language of a windows operating system at a PC end, a linux system, or by using android and iOS system programming languages, for example, at an intelligent terminal, and by using processing logic of a quantum computer.
It should be noted that descriptions of the above apparatuses, devices, and systems according to the related method embodiments may also include other embodiments, and specific implementation manners may refer to descriptions of corresponding method embodiments, which are not described in detail herein.
The embodiments in the present application are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.
For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, when implementing one or more of the present description, the functions of some modules may be implemented in one or more software and/or hardware, or the modules implementing the same functions may be implemented by a plurality of sub-modules or sub-units, etc.
The present invention has been described with reference to flowchart illustrations and/or block diagrams of methods, apparatus, devices, systems according to embodiments of the invention. It will be understood that the implementation can be by computer program instructions which can be provided to a processor of a general purpose computer, special purpose computer, embedded processor or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified. These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
As will be appreciated by one skilled in the art, one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects.
The above description is merely exemplary of one or more embodiments of the present disclosure and is not intended to limit the scope of one or more embodiments of the present disclosure. Various modifications and alterations to one or more embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims.
Claims (13)
1. A method for determining a business process, comprising:
acquiring a process identifier corresponding to a target transaction;
acquiring corresponding process information according to the process identification;
acquiring node information of each link in the service flow according to the node identification included in the flow information;
determining a business process of the target transaction based on the process information and the node information;
before obtaining the corresponding flow information according to the flow identifier, the method further includes:
responding to the configuration of a user on the flow parameters in the visual interface, and determining the flow information corresponding to each business flow; wherein the flow information includes: the system comprises a flow applicable mechanism, a flow name, a flow identifier, a node identifier, an identifier for indicating the execution sequence of nodes, a node name, a service classification and a service name;
responding to the configuration of link parameters in a visual interface by a user, and determining the node information of each link in each business process; each business process comprises a plurality of links, and each link corresponds to one node identifier.
2. The method of claim 1, wherein the node information comprises: node name, node handler information, node constraint condition information, and subsequent node information.
3. The method of claim 1, after determining the flow information and the node information, further comprising:
the process information and the corresponding process identification are stored in a correlated manner;
and storing the node information and the corresponding node identification in a correlation manner.
4. The method of claim 3, further comprising:
and responding to the modification of the flow parameters and/or the link parameters in the visual interface by the user, and adjusting the corresponding flow information and/or the node information.
5. The method of claim 1, wherein the determining the business process of the target transaction based on the process information and the node information comprises:
and combining the process information and the node information based on service logic to obtain the service process of the target transaction.
6. The method of claim 1, wherein after determining the business process of the target transaction, further comprising:
and executing the business process to obtain an execution result.
7. The method according to claim 6, wherein the executing the business process comprises:
acquiring changed information under the condition that the process parameters and/or link parameters corresponding to the business process are/is changed;
re-determining the business process of the target transaction based on the changed information;
correspondingly, the business process is executed, and an execution result is obtained.
8. The method of claim 6, wherein the performing the business process comprises:
acquiring a first execution result of a first link;
and sending execution error information under the condition that the first execution result is not in a preset result range.
9. The method of claim 8, wherein the execution error information comprises at least: and node identification, error type and error data corresponding to the error link.
10. The method of claim 8, further comprising, in the event that the first execution result is not within a preset result range:
starting an error correction process; the error correction process is used for recommending data corresponding to each business attribute in the error link or providing a data range corresponding to each business attribute in the error link.
11. An apparatus for determining a business process, comprising:
the first acquisition module is used for acquiring a process identifier corresponding to the target transaction;
the second acquisition module is used for acquiring corresponding process information according to the process identification;
a third obtaining module, configured to obtain node information of each link in the service flow according to the node identifier included in the flow information;
a determining module, configured to determine a service flow of the target transaction based on the flow information and the node information;
before obtaining the corresponding flow information according to the flow identifier, the apparatus is further configured to:
responding to the configuration of a user on the flow parameters in the visual interface, and determining the flow information corresponding to each business flow; wherein the flow information includes: the system comprises a process applicable mechanism, a process name, a process identifier, a node identifier, an identifier representing a node execution sequence, a node name, a service classification and a service name;
responding to the configuration of link parameters in a visual interface by a user, and determining the node information of each link in each business process; each business process comprises a plurality of links, and each link corresponds to one node identifier.
12. An apparatus for determining a business process, comprising at least one processor and a memory storing computer-executable instructions, the processor implementing the steps of the method of any one of claims 1-10 when executing the instructions.
13. A computer-readable storage medium having stored thereon computer instructions which, when executed, implement the steps of the method of any one of claims 1-10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110753594.3A CN113467782B (en) | 2021-07-02 | 2021-07-02 | Method, device and equipment for determining business process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110753594.3A CN113467782B (en) | 2021-07-02 | 2021-07-02 | Method, device and equipment for determining business process |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113467782A CN113467782A (en) | 2021-10-01 |
| CN113467782B true CN113467782B (en) | 2022-12-09 |
Family
ID=77877706
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110753594.3A Active CN113467782B (en) | 2021-07-02 | 2021-07-02 | Method, device and equipment for determining business process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113467782B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114816368B (en) * | 2022-06-23 | 2022-10-18 | 深圳市瓴码云计算有限公司 | Object-oriented business process development system, method, device and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017125015A1 (en) * | 2016-01-18 | 2017-07-27 | 中兴通讯股份有限公司 | Method for processing workflow of distributed system and workflow engine system |
| WO2018000878A1 (en) * | 2016-06-29 | 2018-01-04 | 华为技术有限公司 | Distributed task processing method and apparatus |
| CN110059233A (en) * | 2019-03-01 | 2019-07-26 | 阿里巴巴集团控股有限公司 | The methods of exhibiting and device of operation flow |
| CN112099768A (en) * | 2020-08-04 | 2020-12-18 | 北京奇艺世纪科技有限公司 | Business process processing method and device and computer readable storage medium |
| CN112561386A (en) * | 2020-12-24 | 2021-03-26 | 建信金融科技有限责任公司 | Method, device and equipment for acquiring business process |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8516175B2 (en) * | 2009-12-30 | 2013-08-20 | International Business Machines Corporation | Graphical development tool for compensation actions and compensation scope in a process flow environment |
| US20130145371A1 (en) * | 2011-12-01 | 2013-06-06 | Sap Ag | Batch processing of business objects |
| CN109359949B (en) * | 2018-10-30 | 2022-05-27 | 中国建设银行股份有限公司 | Flow display method and device |
| US20200285449A1 (en) * | 2019-03-06 | 2020-09-10 | Veritone, Inc. | Visual programming environment |
| CN110007902B (en) * | 2019-03-12 | 2023-11-24 | 中国平安财产保险股份有限公司 | Method and device for configuring business processing flow |
| CN112132548A (en) * | 2020-09-28 | 2020-12-25 | 建信金融科技有限责任公司 | Approval transfer method and device, electronic equipment and storage medium |
-
2021
- 2021-07-02 CN CN202110753594.3A patent/CN113467782B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017125015A1 (en) * | 2016-01-18 | 2017-07-27 | 中兴通讯股份有限公司 | Method for processing workflow of distributed system and workflow engine system |
| WO2018000878A1 (en) * | 2016-06-29 | 2018-01-04 | 华为技术有限公司 | Distributed task processing method and apparatus |
| CN110059233A (en) * | 2019-03-01 | 2019-07-26 | 阿里巴巴集团控股有限公司 | The methods of exhibiting and device of operation flow |
| CN112099768A (en) * | 2020-08-04 | 2020-12-18 | 北京奇艺世纪科技有限公司 | Business process processing method and device and computer readable storage medium |
| CN112561386A (en) * | 2020-12-24 | 2021-03-26 | 建信金融科技有限责任公司 | Method, device and equipment for acquiring business process |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113467782A (en) | 2021-10-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9921569B2 (en) | Field device commissioning system and method | |
| CN112561386A (en) | Method, device and equipment for acquiring business process | |
| CN104932480A (en) | Automobile diagnostic system design method and apparatus | |
| CN111258900A (en) | Interface test script generation method, system, equipment and storage medium | |
| US10354343B2 (en) | Automated process control hardware engineering using schema-represented requirements | |
| CN111399828B (en) | Model-driven logic device modeling method and terminal | |
| CN111106899B (en) | Data verification method and device in Internet of things, computer equipment and storage medium | |
| CN111414391A (en) | Method and system for accessing multiple data sources | |
| CN108897587B (en) | Pluggable machine learning algorithm operation method and device and readable storage medium | |
| EP3413149B1 (en) | Field device commissioning system and field device commissioning method | |
| CN110633959A (en) | Method, device, equipment and medium for creating approval task based on graph structure | |
| CN111767144A (en) | Transaction routing determination method, device, equipment and system for transaction data | |
| CN113467782B (en) | Method, device and equipment for determining business process | |
| CN114003451B (en) | Interface testing method, device, system and medium | |
| CN114443039A (en) | Input parameter verification method and device, electronic equipment and storage medium | |
| CN112001707A (en) | Business workflow generation method and system based on business data | |
| CN111651494A (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN112395339B (en) | Intersystem data admission verification method, device, computer equipment and storage medium | |
| CN110275731B (en) | Information processing method, information processing apparatus, storage medium, and electronic device | |
| CN113591448A (en) | Report generation method and device and storage medium | |
| CN113568614A (en) | Task issuing method, electronic device and storage medium | |
| CN112418796A (en) | Sub-process node activation method and device, electronic equipment and storage medium | |
| CN116521348A (en) | Decision service scheduling method, device, equipment and storage medium | |
| CN112051987B (en) | Service data processing method, device and equipment, program generating method and device | |
| CN114785847B (en) | Network control software development configuration method, terminal and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20221031 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 12 / F, 15 / F, No. 99, Yincheng Road, Shanghai pilot Free Trade Zone, 200120 Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |