CN112286572A - Configuration method and device of business process - Google Patents
Configuration method and device of business process Download PDFInfo
- Publication number
- CN112286572A CN112286572A CN202011149945.1A CN202011149945A CN112286572A CN 112286572 A CN112286572 A CN 112286572A CN 202011149945 A CN202011149945 A CN 202011149945A CN 112286572 A CN112286572 A CN 112286572A
- Authority
- CN
- China
- Prior art keywords
- configuration
- sub
- service
- configuration data
- configuration file
- 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.)
- Withdrawn
Links
- 238000000034 method Methods 0.000 title claims abstract description 155
- 230000008569 process Effects 0.000 title claims abstract description 108
- 238000004590 computer program Methods 0.000 claims description 17
- 238000003860 storage Methods 0.000 claims description 16
- 238000012795 verification Methods 0.000 description 20
- 230000006870 function Effects 0.000 description 15
- 238000010586 diagram Methods 0.000 description 14
- 230000006872 improvement Effects 0.000 description 9
- 238000012545 processing Methods 0.000 description 9
- 238000005516 engineering process Methods 0.000 description 5
- 239000003550 marker Substances 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013524 data verification Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005055 memory storage Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 229920001296 polysiloxane Polymers 0.000 description 1
- 238000004801 process automation Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The specification discloses a configuration method and a configuration device of a business process, which are used for determining a business of the business process to be configured as a target business. And determining at least one public sub-configuration data contained in the business process corresponding to the target business, wherein each public sub-configuration data corresponds to one sub-business process of the target business. And acquiring at least one public sub-configuration data from the configuration files corresponding to other services. And generating a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service. And configuring the business process of the target business according to the configuration file corresponding to the target business. The method avoids repeated writing of the same business process code by acquiring the public sub-configuration data from the configuration files corresponding to other businesses, thereby improving the working efficiency and reducing the time cost.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for configuring a business process.
Background
Currently, as various services become more complex, there are often a large amount of service logic and branch flows. In order to effectively deal with the complexity of the business, the business development and management of the business are facilitated through business process automation.
In the prior art, it is often necessary to separately and completely develop a corresponding automated business process for each business or product, and each business process corresponds to a business or product one to one. Due to the characteristic of fast iteration in the internet field, frequent service changes lead related developers to continuously adjust service logic in the code. When a new business or product is added, a developer needs to re-develop codes from scratch, the workload is large, the time cost is high, and the condition that the business process codes need to be re-written after a fine adjustment at the later stage can occur.
Therefore, how to avoid rewriting the business process code due to frequent business changes is an urgent problem to be solved.
Disclosure of Invention
The present specification provides a method and an apparatus for configuring a business process, so as to partially solve the above problems in the prior art.
The technical scheme adopted by the specification is as follows:
the present specification provides a method for configuring a business process, including:
determining a service of a service process to be configured as a target service;
determining at least one public sub-configuration data contained in a business process corresponding to the target business, wherein each public sub-configuration data corresponds to one sub-business process of the target business;
acquiring the at least one public sub-configuration data from configuration files corresponding to other services;
generating a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service;
and configuring the service process of the target service according to the configuration file corresponding to the target service.
Optionally, before the at least one piece of common sub-configuration data is obtained from the configuration file corresponding to the other service, the method further includes:
determining an original configuration file to which the target service belongs;
acquiring the at least one public sub-configuration data from the configuration files corresponding to other services, specifically including:
and acquiring the at least one public sub-configuration data from the original configuration file, wherein the original configuration file comprises a configuration file corresponding to at least one other service.
Optionally, determining the original configuration file to which the target service belongs specifically includes:
determining a service type corresponding to the target service;
and determining the original configuration file to which the target service belongs according to the service type.
Optionally, generating a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one specific sub-configuration data of the target service, specifically including:
generating a configuration file corresponding to the target service in the original configuration file according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service;
and updating the original configuration file according to the configuration file corresponding to the target service, and taking the updated original configuration file as the configuration file corresponding to the target service.
Optionally, generating a configuration file corresponding to the target service in the original configuration file according to the acquired at least one public sub-configuration data and the acquired at least one specific sub-configuration data of the target service, specifically including:
for each acquired public sub-configuration data, determining a sub-configuration node corresponding to the public sub-configuration data in the original configuration file as a first sub-configuration node, and for each appointed sub-configuration data, determining a sub-configuration node corresponding to the appointed sub-configuration data in the original configuration file as a second sub-configuration node;
generating a corresponding configuration node of the target service in the original configuration file according to the first sub configuration node and the second sub configuration node;
and generating a configuration file corresponding to the target service in the original configuration file according to the configuration node corresponding to the target service in the original configuration file and at least one specified sub-configuration data of the target service.
Optionally, the method further comprises:
receiving a service request sent by a user;
determining a configuration file of a service corresponding to the service request as a target file according to the service request;
and executing the service corresponding to the service request through the configuration node corresponding to the service, the at least one public sub-configuration data corresponding to the service and the at least one designated sub-configuration data corresponding to the service, which are contained in the target file.
This specification provides a configuration device of a business process, including:
the first determining module is used for determining the service of the service flow to be configured as a target service;
a second determining module, configured to determine at least one public sub-configuration data included in a service flow corresponding to the target service, where each public sub-configuration data corresponds to one sub-service flow of the target service;
the acquisition module is used for acquiring the at least one public sub-configuration data from the configuration files corresponding to other services;
a generating module, configured to generate a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one specific sub-configuration data of the target service;
and the configuration module is used for configuring the business process of the target business according to the configuration file corresponding to the target business.
Optionally, before the obtaining module obtains the at least one piece of public sub-configuration data from the configuration files corresponding to other services, the first determining module is further configured to determine an original configuration file to which the target service belongs;
the obtaining module is specifically configured to obtain the at least one piece of public sub-configuration data from the original configuration file, where the original configuration file includes a configuration file corresponding to at least one other service.
The present specification provides a computer-readable storage medium storing a computer program which, when executed by a processor, implements the above-described configuration method for a business process.
The present specification provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the processor implements the above configuration method for the business process.
The technical scheme adopted by the specification can achieve the following beneficial effects:
in the configuration method for a service flow provided in this specification, a service of the service flow to be configured is determined as a target service, and at least one piece of common sub-configuration data included in the service flow corresponding to the target service is determined, where each piece of common sub-configuration data corresponds to one sub-service flow of the target service. And then, acquiring the at least one public sub-configuration data from the configuration files corresponding to other services, and generating the configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service. And finally, configuring the business process of the target business according to the configuration file corresponding to the target business.
It can be seen from the above configuration method for the service process that the method can obtain the common sub-configuration data from the configuration files corresponding to other services according to the target service, and generate the configuration file corresponding to the target service according to the common sub-configuration data and the designated sub-configuration data of the target service. Compared with the condition that each business process needs to rewrite the business process codes in the prior art, the method can acquire the public sub-configuration data required by the target business from the existing configuration file, thereby effectively avoiding repeated writing of the same business process codes.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
fig. 1 is a schematic flow chart of a configuration method of a business process in this specification;
FIG. 2 is a schematic diagram of a configuration structure of a business process provided in the present specification;
FIG. 3 is a schematic diagram of a configuration device for a business process provided herein;
fig. 4 is a schematic block diagram of an electronic device corresponding to fig. 1 provided in this specification.
Detailed Description
In order to make the objects, technical solutions and advantages of the present disclosure more clear, the technical solutions of the present disclosure will be clearly and completely described below with reference to the specific embodiments of the present disclosure and the accompanying drawings. It is to be understood that the embodiments described are only a few embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present specification without any creative effort belong to the protection scope of the present specification.
The technical solutions provided by the embodiments of the present description are described in detail below with reference to the accompanying drawings.
Fig. 1 is a schematic flow chart of a configuration method of a service flow in this specification, which specifically includes the following steps:
s101: and determining the service of the service flow to be configured as a target service.
In the embodiment of the present specification, a service of a service flow to be configured is determined as a target service. The execution main body of the business process provided by the present specification may be a terminal device such as a desktop computer, a notebook computer, or the like, or may be a client installed in the terminal device, or may be a business platform. For convenience of description, the following describes a configuration method of a business process provided in this specification, with only a business platform as an execution subject.
In this embodiment of the present specification, a target service may refer to a service that needs to configure a service flow according to an actual development requirement. For example, if a credit payment service flow needs to be configured according to actual requirements, the credit payment is the target service.
S102: and determining at least one public sub-configuration data contained in the service process corresponding to the target service, wherein each public sub-configuration data corresponds to one sub-service process of the target service.
In the embodiment of the present specification, a plurality of sub-business processes are provided in a business process, where a sub-business process may refer to each execution step in a business process, for example, a credit payment business process includes a plurality of sub-business processes, such as card verification (verifying whether a credit card is valid), blacklist verification, transaction data recording, and the like. The common sub-configuration data refers to sub-business process configuration data corresponding to a sub-business process, and the same sub-business process can exist in business processes of different businesses, and the sub-business process configuration data corresponding to the same sub-business process is the common sub-configuration data, that is, the same sub-business process in the business processes of different businesses corresponds to the same common sub-configuration data.
For example, in both the credit payment service and the bill installment service, card verification is involved, so the service process involved in card verification is a sub-service process commonly involved in the two services, and correspondingly, the configuration data involved in the card verification service process is common sub-configuration data of the two services.
S103: and acquiring the at least one public sub-configuration data from the configuration files corresponding to other services.
In this embodiment of the present specification, since a part of the sub-service flows of the target service may be the same as the sub-service flows of other services, when configuring the service flow of the target service, the common sub-configuration data related to the target service may be directly obtained from the configuration file corresponding to the other services.
Before the at least one piece of public sub-configuration data is obtained from the configuration files corresponding to other services, an original configuration file to which the target service belongs may be determined. The original configuration file mentioned here may contain configuration files of all services that have been currently configured with the service flow. Furthermore, since the configuration files of different services include the common sub-configuration data corresponding to the sub-service flows in the service flows, the original configuration file also includes all the common sub-configuration data currently.
If the common sub-configuration data is obtained from the configuration files corresponding to other services, the sub-service flows in the service flow of the target service can be compared with the sub-service flows in the service flows of all the current services, the service with the same sub-service flow in the service flow of the target service is determined, the common sub-configuration data is obtained from the configuration file corresponding to the service, or the common sub-configuration data corresponding to the sub-service flow in the service flow of the target service is directly searched in the original configuration file.
For example, the service flow of the payment service includes a sub-service flow: card verification, the sub-business process: comparing the card verification with the sub-business processes in the business processes of all the current businesses, determining the business related to the card verification, and further acquiring the sub-business processes from the configuration file corresponding to the business: and the card verifies the corresponding public sub-configuration data. Of course, since the original configuration file includes all the current public sub-configuration data, the identification information of this sub-business process can be verified according to the card, and the sub-business process can be directly searched in the original configuration file: and the card verifies the corresponding public sub-configuration data.
In addition, different service types may also correspond to different original configuration files, that is, the configuration files of services of the same service type may be in the same original configuration file. For example, credit card payment and credit card installments belong to credit card services, so the configuration files of the credit card payment and the credit card installments on the service flow are both located in the same original configuration file, while the configuration file of the deposit card payment on the service flow belongs to other original configuration files if the deposit card payment does not belong to the credit card services.
Based on this, in the embodiment of the present specification, a service type corresponding to a target service may be determined first, and then an original configuration file matching the service type is found from each original configuration file, and common sub-configuration data is obtained from the original configuration file. Because the original configuration file only contains the configuration files of the services of the same service type, but not the configuration files of all the services, the method can effectively improve the query efficiency of the public sub-configuration data.
S104: and generating a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service.
In this embodiment of the present specification, for a configuration file of a target service in a service flow, the configuration file may be roughly composed of two parts, one part is the above-mentioned common sub-configuration data, and the other part is designated sub-configuration data that needs to be acquired by a service platform. The specific sub-configuration data is configuration data which is specific to the target service and does not belong to the public sub-configuration data, and the specific sub-configuration data can be customized for the target service by developers according to actual requirements. Based on this, after the service platform acquires the public sub-configuration data and the designated sub-configuration data, the service platform may generate a configuration file corresponding to the target service according to the acquired public sub-configuration data and the acquired designated sub-configuration data.
It should be noted that, after the configuration file corresponding to the target service is generated, the original configuration file is updated correspondingly. That is to say, the configuration file corresponding to the target service is added to the original configuration file, and the specified sub-configuration data acquired by the target service becomes the common sub-configuration data in the original configuration file. The target service can call the public sub-configuration data in the updated original configuration file according to the corresponding configuration file, so that the service flow of the target service is completed.
In this embodiment, the service platform may determine a configuration node corresponding to a service flow of a target service, and then generate a configuration file corresponding to the target service according to the configuration node, the obtained public sub-configuration data and the obtained designated sub-configuration data. The configuration node mentioned here can represent the execution sequence of each sub-service flow related to the target service, and the configuration node includes a plurality of sub-configuration nodes, and each sub-configuration node may correspond to one sub-service flow.
Specifically, the sub-configuration node corresponding to the common sub-configuration data acquired by the service platform in the original configuration file is used as a first sub-configuration node, and the sub-configuration node corresponding to the acquired pointing sub-configuration data in the original configuration file is used as a second sub-configuration node. And then, generating a configuration node corresponding to the target service in the original configuration file according to the first sub configuration node and the second sub configuration node.
In this embodiment of the present specification, the first sub-configuration node calls common sub-configuration data corresponding to a same sub-service flow in the service flows of the target service and other services, and the second sub-configuration node calls specific sub-configuration data corresponding to a different sub-service flow in the service flows of the target service and other services. Further, since the common sub-configuration data corresponding to the first sub-configuration node already exists in the original configuration file, the configuration file corresponding to the target service in the original configuration file can be generated according to the configuration node corresponding to the target service in the original configuration file and the designated sub-configuration data of the target service.
In the embodiment of the present specification, the corresponding configuration node in the configuration file includes a start marker, an end marker, and contents between the two markers. The configuration node is composed of a plurality of sub configuration nodes, and each sub configuration node also comprises a start marker, an end marker and the content between the two markers. The configuration node structure comprises a checker, a context initializer and a service processor. The checker, the context initializer and the service processor can respectively correspond to one or more sub configuration nodes.
How the sub-business processes in the business process are operated can be seen from the corresponding configuration nodes of the target business in the original configuration file, as shown in fig. 2.
Fig. 2 is a schematic diagram of a configuration structure of a business process provided in this specification.
In the embodiment of the present specification, the configuration node structure is divided into a checker, a context initializer and a service processor. The verifier is a verification part in the business process, and verifies the account data of the user in the business request sent by the user with the data in the database to complete a sub-business process related to data verification in the business process (such as a card verification sub-business process and a limit verification sub-business process related to the periodic business in fig. 2). The context initializer is a cache part in the business process, caches the account data of the user and the data in the database in the verification process, and avoids the business processor from reacquiring the data in the verification process in the processing process (for example, the sub business process of the staging context initialization related to the staging business in fig. 2). The business processor is a processing part in the business process, processes the business request sent by the user, and uploads the processed business result to the database (for example, fig. 2 shows two sub-business processes, namely an staging record and an accounting record, related to the staging business).
In fig. 2, if the existing service is a staging service, the original configuration file includes public sub-configuration data corresponding to a sub-service flow in the configuration file of the staging service. That is, the sub-business process card verification, the limit verification, the staging record and the accounting record have corresponding sub-configuration data in the original configuration file. When new services are configured: when the business process of the payment business is carried out, the business platform can determine the configuration nodes in the configuration file corresponding to the payment business and all the sub-configuration nodes in the configuration nodes, and obtain the common sub-configuration data corresponding to the card verification and the account record of the same sub-configuration nodes in the original configuration file. As can be seen from fig. 2, the blacklist check involved in the payment service, the payment context initialization, and the configuration data involved in recording the transaction data are designated sub-configuration data. Based on this, the service platform may generate a configuration file corresponding to the payment service from the acquired public sub-configuration data corresponding to the card verification and the account record and the acquired appointed sub-configuration data corresponding to the blacklist verification, the payment context initialization, and the record transaction data. The service platform can sequentially arrange the sub-configuration nodes of card verification, blacklist verification, payment context initialization, transaction data recording and account recording according to a preset configuration node structure of a checker, a context initializer and a service processor to generate a configuration node corresponding to the payment service, and further generate a configuration file corresponding to the payment service according to the configuration node corresponding to the payment service, public sub-configuration data corresponding to the payment service and appointed sub-configuration data.
S105: and configuring the service process of the target service according to the configuration file corresponding to the target service.
After the configuration file corresponding to the target service is obtained, the service process of the target service can be configured in the service platform according to the configuration file. Correspondingly, in subsequent practical applications, the service platform may receive a service request sent by a user, determine, according to the service request, a configuration file of a service corresponding to the service request as a target file, and execute the service through a configuration node corresponding to the service, at least one public sub-configuration data corresponding to the service, and at least one designated sub-configuration data corresponding to the service, which are included in the target file.
The process engine used in the aforementioned configuration method of the business process may be a Financial Open Financial Architecture (SOFA) or an activti process engine, and the description does not limit the specific form of the process engine. In addition, the configuration file referred to in the present specification may have various forms, such as Extensible Markup Language (XML).
It should be noted that, an extension interface is provided in the embodiments of the present specification, and a plug-in may be customized to implement other functions. For example, a log record can be added after each sub-business process through the function of an extension point built in the SOFA architecture, and the result output by each sub-business process is recorded, so as to facilitate the troubleshooting work when the business process has problems, or a database transaction management is added at the beginning of each business process to manage the read-write operation of the database, thereby avoiding the database error caused by misoperation.
Furthermore, due to the expansion function, the function expansion is very convenient when the function expansion is needed according to the actual service requirement, only corresponding configuration data of the assigned sub-unit is needed to be added, the influence on the original service logic is small, and the configuration efficiency on the service expansion is effectively improved.
According to the method, on one hand, the public sub-configuration data are obtained from the configuration files corresponding to other services, so that repeated writing of the same service flow code is avoided, the working efficiency is improved, and the time cost is reduced. On one hand, the operation process of the business process can be clearly seen through the configuration node structure, if the business process is changed, the sub-configuration node can be directly replaced and modified, the business process code does not need to be modified, and the working efficiency is improved.
Based on the same idea, the present specification further provides a corresponding configuration apparatus of a business process, as shown in fig. 3.
Fig. 3 is a schematic diagram of a configuration device of a business process provided in this specification, which specifically includes:
a first determining module 300, configured to determine a service of a service flow to be configured as a target service;
a second determining module 302, configured to determine at least one common sub-configuration data included in a service flow corresponding to the target service, where each common sub-configuration data corresponds to one sub-service flow of the target service;
an obtaining module 304, configured to obtain the at least one piece of public sub-configuration data from configuration files corresponding to other services;
a generating module 306, configured to generate a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one specific sub-configuration data of the target service;
the configuration module 308 is configured to configure a service flow of the target service according to the configuration file corresponding to the target service.
Optionally, the obtaining module 304 is specifically configured to determine an original configuration file to which the target service belongs; and acquiring the at least one public sub-configuration data from the original configuration file, wherein the original configuration file comprises a configuration file corresponding to at least one other service.
Optionally, the obtaining module 304 is specifically configured to determine a service type corresponding to the target service; and determining the original configuration file to which the target service belongs according to the service type.
Optionally, the generating module 306 is specifically configured to generate a configuration file corresponding to the target service in the original configuration file according to the acquired at least one public sub-configuration data and the acquired at least one specific sub-configuration data of the target service; and updating the original configuration file according to the configuration file corresponding to the target service, and taking the updated original configuration file as the configuration file corresponding to the target service.
Optionally, the generating module 306 is specifically configured to, for each obtained public sub-configuration data, determine a sub-configuration node corresponding to the public sub-configuration data in the original configuration file as a first sub-configuration node, and for each designated sub-configuration data, determine a sub-configuration node corresponding to the designated sub-configuration data in the original configuration file as a second sub-configuration node; generating a corresponding configuration node of the target service in the original configuration file according to the first sub configuration node and the second sub configuration node; and generating a configuration file corresponding to the target service in the original configuration file according to the configuration node corresponding to the target service in the original configuration file and at least one specified sub-configuration data of the target service.
Optionally, the apparatus further comprises:
a processing module 310, configured to receive a service request sent by a user; determining a configuration file of a service corresponding to the service request as a target file according to the service request; and executing the service corresponding to the service request through the configuration node corresponding to the service, the at least one public sub-configuration data corresponding to the service and the at least one designated sub-configuration data corresponding to the service, which are contained in the target file.
Optionally, the obtaining module 304 is specifically configured to obtain the at least one piece of public sub-configuration data from the original configuration file, where the original configuration file includes a configuration file corresponding to at least one other service.
The present specification also provides a computer-readable storage medium storing a computer program, which can be used to execute the configuration method of the business process provided in fig. 1.
This specification also provides a schematic block diagram of the electronic device shown in fig. 4. As shown in fig. 4, at the hardware level, the electronic device includes a processor, an internal bus, a network interface, a memory, and a non-volatile memory, and may also include hardware required for other services. The processor reads a corresponding computer program from the nonvolatile memory into the memory and then runs the computer program, so as to implement the configuration method of the business process described in fig. 1. Of course, besides the software implementation, the present specification does not exclude other implementations, such as logic devices or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may be hardware or logic devices.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may 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 in the flowchart flow or flows and/or block diagram block or blocks.
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.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification 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 system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The above description is only an example of the present specification, and is not intended to limit the present specification. Various modifications and alterations to this description will become apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the scope of the claims of the present specification.
Claims (10)
1. A method for configuring a business process is characterized by comprising the following steps:
determining a service of a service process to be configured as a target service;
determining at least one public sub-configuration data contained in a business process corresponding to the target business, wherein each public sub-configuration data corresponds to one sub-business process of the target business;
acquiring the at least one public sub-configuration data from configuration files corresponding to other services;
generating a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service;
and configuring the service process of the target service according to the configuration file corresponding to the target service.
2. The method of claim 1, wherein before obtaining the at least one common sub-configuration data from the configuration files corresponding to other services, the method further comprises:
determining an original configuration file to which the target service belongs;
acquiring the at least one public sub-configuration data from the configuration files corresponding to other services, specifically including:
and acquiring the at least one public sub-configuration data from the original configuration file, wherein the original configuration file comprises a configuration file corresponding to at least one other service.
3. The method according to claim 2, wherein determining the original profile to which the target service belongs specifically comprises:
determining a service type corresponding to the target service;
and determining the original configuration file to which the target service belongs according to the service type.
4. The method according to claim 2, wherein generating a configuration file corresponding to the target service according to the acquired at least one common sub-configuration data and the acquired at least one specific sub-configuration data of the target service specifically includes:
generating a configuration file corresponding to the target service in the original configuration file according to the acquired at least one public sub-configuration data and the acquired at least one designated sub-configuration data of the target service;
and updating the original configuration file according to the configuration file corresponding to the target service, and taking the updated original configuration file as the configuration file corresponding to the target service.
5. The method according to claim 4, wherein generating a configuration file corresponding to the target service in the original configuration file according to the acquired at least one common sub-configuration data and the acquired at least one specific sub-configuration data of the target service specifically includes:
for each acquired public sub-configuration data, determining a sub-configuration node corresponding to the public sub-configuration data in the original configuration file as a first sub-configuration node, and for each appointed sub-configuration data, determining a sub-configuration node corresponding to the appointed sub-configuration data in the original configuration file as a second sub-configuration node;
generating a corresponding configuration node of the target service in the original configuration file according to the first sub configuration node and the second sub configuration node;
and generating a configuration file corresponding to the target service in the original configuration file according to the configuration node corresponding to the target service in the original configuration file and at least one specified sub-configuration data of the target service.
6. The method of claim 5, wherein the method further comprises:
receiving a service request sent by a user;
determining a configuration file of a service corresponding to the service request as a target file according to the service request;
and executing the service corresponding to the service request through the configuration node corresponding to the service, the at least one public sub-configuration data corresponding to the service and the at least one designated sub-configuration data corresponding to the service, which are contained in the target file.
7. A device for configuring a business process, comprising:
the first determining module is used for determining the service of the service flow to be configured as a target service;
a second determining module, configured to determine at least one public sub-configuration data included in a service flow corresponding to the target service, where each public sub-configuration data corresponds to one sub-service flow of the target service;
the acquisition module is used for acquiring the at least one public sub-configuration data from the configuration files corresponding to other services;
a generating module, configured to generate a configuration file corresponding to the target service according to the acquired at least one public sub-configuration data and the acquired at least one specific sub-configuration data of the target service;
and the configuration module is used for configuring the business process of the target business according to the configuration file corresponding to the target business.
8. The apparatus according to claim 7, wherein before the obtaining module obtains the at least one piece of common sub-configuration data from the configuration files corresponding to other services, the first determining module is further configured to determine an original configuration file to which the target service belongs;
the obtaining module is specifically configured to obtain the at least one piece of public sub-configuration data from the original configuration file, where the original configuration file includes a configuration file corresponding to at least one other service.
9. A computer-readable storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, implements the method of any of the preceding claims 1 to 6.
10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any of claims 1 to 6 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149945.1A CN112286572A (en) | 2020-10-23 | 2020-10-23 | Configuration method and device of business process |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011149945.1A CN112286572A (en) | 2020-10-23 | 2020-10-23 | Configuration method and device of business process |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112286572A true CN112286572A (en) | 2021-01-29 |
Family
ID=74423841
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011149945.1A Withdrawn CN112286572A (en) | 2020-10-23 | 2020-10-23 | Configuration method and device of business process |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112286572A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116107561A (en) * | 2023-04-14 | 2023-05-12 | 湖南云畅网络科技有限公司 | Low-code-based action node rapid construction method, system and storage medium |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106354493A (en) * | 2016-08-24 | 2017-01-25 | 南昌码行科技有限公司 | Development mode implementation method for solving traditional software development pain points |
| CN107679700A (en) * | 2017-09-08 | 2018-02-09 | 阿里巴巴集团控股有限公司 | Business flow processing method, apparatus and server |
| CN110750267A (en) * | 2019-09-26 | 2020-02-04 | 浙江大搜车软件技术有限公司 | Service information updating method and device, computer equipment and storage medium |
-
2020
- 2020-10-23 CN CN202011149945.1A patent/CN112286572A/en not_active Withdrawn
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106354493A (en) * | 2016-08-24 | 2017-01-25 | 南昌码行科技有限公司 | Development mode implementation method for solving traditional software development pain points |
| CN107679700A (en) * | 2017-09-08 | 2018-02-09 | 阿里巴巴集团控股有限公司 | Business flow processing method, apparatus and server |
| CN110750267A (en) * | 2019-09-26 | 2020-02-04 | 浙江大搜车软件技术有限公司 | Service information updating method and device, computer equipment and storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116107561A (en) * | 2023-04-14 | 2023-05-12 | 湖南云畅网络科技有限公司 | Low-code-based action node rapid construction method, system and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107025559B (en) | Service processing method and device | |
| CN110008224B (en) | Database transaction processing method and device | |
| CN106796522A (en) | System and method for updating source code file | |
| CN108320071B (en) | Business risk management method, device and equipment | |
| CN109947643B (en) | A/B test-based experimental scheme configuration method, device and equipment | |
| CN108616361B (en) | Method and device for identifying uniqueness of equipment | |
| CN113079224A (en) | Account binding method and device, storage medium and electronic equipment | |
| CN115391337A (en) | Database partitioning method and device, storage medium and electronic equipment | |
| CN114510296A (en) | Applet storage and calling method, device and equipment | |
| CN111694992A (en) | Data processing method and device | |
| CN112286572A (en) | Configuration method and device of business process | |
| CN111311267B (en) | Multi-account risk prevention and control method, system and equipment | |
| CN112559346A (en) | Service testing method and device | |
| CN109409037B (en) | Method, device and equipment for generating data confusion rule | |
| CN110334031B (en) | Memory allocation code detection method and device, computer equipment and storage medium | |
| CN111338655A (en) | Installation package distribution method and system | |
| CN111242731B (en) | Service execution method and device | |
| CN112416444B (en) | Board switching control method, device, equipment and medium | |
| CN110704742B (en) | Feature extraction method and device | |
| CN112596781A (en) | Service execution and service configuration method and device | |
| CN114020211A (en) | Storage space management method, device, equipment and storage medium | |
| CN110245115B (en) | File processing method, engine and system | |
| CN111796864A (en) | Data verification method and device | |
| CN107391223B (en) | File processing method and device | |
| CN112749152A (en) | Data migration method and device of intelligent contract 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 | ||
| WW01 | Invention patent application withdrawn after publication | ||
| WW01 | Invention patent application withdrawn after publication |
Application publication date: 20210129 |