Business approval method and system

Abstract

The disclosed embodiment discloses a business approval method and system. The business approval method includes: obtaining a business request instruction; calling the corresponding business type data based on the business request instruction; generating an approval business form based on the business type data; and completing business approval based on the approval business form. The business approval is completed by calling the business type data through the obtained business request instruction to generate an approval business form. The business type data can be automatically configured according to different businesses to build a corresponding approval process. When building a new business process, only the corresponding business type data needs to be called without reconfiguring the entire business process, thereby achieving the purpose of strong scalability.

Description

Technical Field

[0001] The present disclosure relates to the field of data processing, and in particular to a business approval method and system. Background Art

[0002] With the rapid development of global information technology and increasingly fierce business competition, enterprises need collaborative, comprehensive and integrated solutions to improve their efficiency and promote their long-term development. With the popularization of the Internet, office automation has become the best way to solve the office bottleneck problem of poor information exchange and inconvenient negotiation and communication caused by physical distance.

[0003] The current office automation generally uses independently developed software, and its approval business processes are pre-configured. If a new business process is needed, the new business process needs to be reconfigured. And the business process application and approval often require a specially developed client. In summary, in the process of implementing the embodiments of the present disclosure, the inventor found that the existing technology has the problem of poor scalability of existing business approval. Summary of the invention

[0004] In view of this, the embodiments of the present disclosure provide a business approval method and system, which at least partially solve the problem of poor scalability of business approval in the prior art.

[0005] In a first aspect, an embodiment of the present disclosure provides a business approval method, including:

[0006] Get business request instructions;

[0007] Calling corresponding business type data based on the business request instruction;

[0008] Generate an approval business form based on the business type data;

[0009] Complete business approval based on the approval business order.

[0010] Optionally, the service request instruction is transmitted based on TCP, and the service type data is transmitted based on TCP.

[0011] Optionally, completing the business approval based on the approval business form includes:

[0012] Send approval notifications to corresponding approvers or requesters.

[0013] Optionally, the approval notification is pushed based on UDP point-to-point.

[0014] Optionally, before the step of calling corresponding service type data based on the service request instruction, the step includes:

[0015] The sequence ID of the process reversal order and the operating user ID of the corresponding node are added to the business type data.

[0016] Optionally, before the step of calling corresponding service type data based on the service request instruction, the step further includes:

[0017] Define the operation file for binary type data conversion;

[0018] A corresponding mapping relationship is defined in the first mapping file based on the operation file.

[0019] Optionally, before the step of generating an approval business form based on the business type data, the step further includes:

[0020] Configure the second mapping file of the database type, configure the database sql query and the abstract class query file.

[0021] In a second aspect, the embodiment of the present disclosure further provides a business approval system, including a user end, a business service end and an approval service end;

[0022] The user terminal is used to initiate a service request instruction;

[0023] The business service end is used to call corresponding business type data based on the received business request instruction;

[0024] The approval service end is used to generate an approval business form based on the business type data, and complete business approval based on the approval business form.

[0025] Optionally, the user end and the business server end communicate based on TCP, and the business server end and the approval server end communicate based on TCP.

[0026] Optionally, the approval server is used to push the approval notification to the corresponding user terminal based on UDP point-to-point when completing the business approval based on the approval business form.

[0027] The business approval method and system provided by the embodiments of the present disclosure, wherein the business approval method, through the acquired business request instruction, calls the business type data to generate an approval business form, thereby completing the business approval, can automatically configure the business type data according to different businesses, thereby building a corresponding approval process, and when building a new business process, only the corresponding business type data needs to be called, without reconfiguring the entire business process, thereby achieving the purpose of strong scalability.

[0028] The data in the business process is transmitted based on TCP, and the scalability is further enhanced due to the versatility of TCP.

[0029] Send approval notices to relevant personnel and promptly notify them to complete the corresponding approval work, thereby improving approval efficiency while avoiding missing business approvals.

[0030] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the following preferred embodiments are specifically cited and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0032] Figure 1 A flowchart of a business approval method provided in an embodiment of the present disclosure;

[0033] Figure 2 An approval business flow chart of a business approval system provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0034] The embodiments of the present disclosure are described in detail below with reference to the accompanying drawings.

[0035] It should be clear that the following embodiments of the present disclosure are described by specific specific examples, and those skilled in the art can easily understand other advantages and effects of the present disclosure from the contents disclosed in this specification. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all of the embodiments. The present disclosure can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present disclosure. It should be noted that the following embodiments and features in the embodiments can be combined with each other in the absence of conflict. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present disclosure.

[0036] It should be noted that various aspects of the embodiments within the scope of the appended claims are described below. It should be apparent that the aspects described herein may be embodied in a wide variety of forms, and any specific structure and / or function described herein is merely illustrative. Based on the present disclosure, it should be understood by those skilled in the art that an aspect described herein may be implemented independently of any other aspect, and two or more of these aspects may be combined in various ways. For example, any number of aspects described herein may be used to implement the device and / or practice the method. In addition, other structures and / or functionalities other than one or more of the aspects described herein may be used to implement this device and / or practice this method.

[0037] It should also be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present disclosure. The drawings only show components related to the present disclosure rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0038] Additionally, in the following description, specific details are provided to facilitate a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects described may be practiced without these specific details.

[0039] Existing business approvals are configured separately according to business needs. For example, business A only needs to initiate business A request, and the approval can be completed in sequence according to the pre-configured process. For example, the approval process of business A includes: requester initiates → A1 → A2 → A3 → A4 → A5 → requester. The approval process of business B includes: requester initiates → B1 → B2 → B3 → B4 → B5 → requester. If there is an approval process involving two businesses, it is necessary to build a new approval process in the system: requester initiates → A1 → A2 → A3 → A4 → A5 → B1 → B2 → B3 → B4 → B5 → requester, or requester initiates → B1 → B2 → B3 → B4 → B5 → A1 → A2 → A3 → A4 → A5 → requester.

[0040] For ease of understanding, Figure 1 As shown, this embodiment discloses a business approval method, including:

[0041] Step S101: Obtaining a service request instruction;

[0042] The business request instruction includes the business type data to be called and the business process to be generated. The business type data is such as process A and process B, and the process to be generated is A+B.

[0043] Step S102: calling corresponding service type data based on the service request instruction;

[0044] The corresponding business request instruction calls the corresponding business type data in the business server, such as A process data and B process data.

[0045] Step S103: Generate an approval business form based on the business type data;

[0046] Based on the above business type data and instructions, an approval business form is generated from requester to A1 → A2 → A3 → A4 → A5 → B1 → B2 → B3 → B4 → B5 → requester, without reconfiguring the entire business process. Based on the instructions, the existing configured business process is called, and the configured business process is integrated to realize the business process corresponding to the instruction. The approval order of each node of the new business process in the prior art and the approver on each node need to be reconfigured, while this embodiment directly calls the approval order and node approver data originally configured on the server.

[0047] Step S104: completing business approval based on the approval business form.

[0048] Complete the approval of each node based on the above approval business order.

[0049] The business request instruction in this embodiment is initiated by the requester based on the client, which can be a mobile phone, computer, etc. The business type data runs in the business server, the approval business form is generated and runs in the work order server, and the business approval is completed based on the approval business form and runs in the approval server. In a specific embodiment, the transmission of data between each server is based on TCP transmission. The use of TCP transmission can ensure that the business processes running on each server are not a system and data transmission can be completed.

[0050] For example, if the business server is a CEMS service and the work order server is a CEMSUP service, the two servers run different approval procedures, and approval business can also be implemented.

[0051] Based on the above application scenarios, after adopting the technical solution of the present invention, if the approval process involves two businesses A and B, there is no need to reconfigure the business process. It is only necessary to call the original A process and B process, and then generate the corresponding A+B process or B+A process in the work order service based on the command, and the original A process and B process are saved in the business server.

[0052] Optionally, the service request instruction is transmitted based on TCP, and the service type data is transmitted based on TCP.

[0053] Optionally, completing the business approval based on the approval business form includes:

[0054] Send approval notifications to corresponding approvers or requesters.

[0055] Optionally, the approval notification is pushed based on UDP point-to-point.

[0056] Optionally, before the step of calling corresponding service type data based on the service request instruction, the step includes:

[0057] The sequence ID of the process reversal order and the operating user ID of the corresponding node are added to the business type data.

[0058] Optionally, before the step of calling corresponding service type data based on the service request instruction, the step further includes:

[0059] Defines the operation file for binary type data conversion; implements compatibility with distributed databases.

[0060] A corresponding mapping relationship is defined in the first mapping file based on the operation file.

[0061] The core engine package source code of the approval workflow supports the stand-alone database by default. When using a distributed database, an error will occur. When using the distributed database DBLE, the binary data type conversion rules of the native binary data table of the workflow have changed, and the normal insertion operation of the table cannot be performed. Therefore, a class is redefined to implement the conversion operation of binary type data, and the mapping relationship of the class is added to the source code mapping xml file in the engine package. The mapping xml file is the first mapping file. The mapping relationship is compatible with the new binary conversion rules, thereby achieving the purpose of compatibility with distributed databases.

[0062] Optionally, before the step of generating an approval business form based on the business type data, the step further includes:

[0063] Configure the second mapping file of the database type, configure the database sql query and abstract class query file. In addition, in order to be compatible with domestic databases, the limitAfter attribute of the database must also be configured.

[0064] The proportion of domestic databases such as DAMO, Jincang and Shentong in some projects is expanding year by year, but the activiti workflow does not support domestic databases. If you want to be compatible with domestic databases such as DAMO and Jincang, first of all, you need to configure the domestic database type, because the approval service will read the jdbc configuration file on the server at the beginning of startup and then create the database type of the program. Therefore, on the basis of the original supported database, you need to add a custom configuration database type mapping, that is, configure the second mapping file; secondly, put the core engine framework package source code of the workflow into the database sql query and abstract class query for expansion and transformation, mainly for the compatible transformation of the core methods of the core query class; then, the precautions for sql table creation, introduce the domestic database configuration file to configure the limitAfter attribute of each database, so that the domestic database can also create a normal workflow, so as to achieve the purpose of compatibility with domestic databases.

[0065] A business approval system includes a user end, a business service end and an approval service end;

[0066] The user terminal is used to initiate a service request instruction;

[0067] The business service end is used to call corresponding business type data based on the received business request instruction;

[0068] The approval service end is used to generate an approval business form based on the business type data, and complete business approval based on the approval business form.

[0069] Optionally, the user end and the business server end communicate based on TCP, and the business server end and the approval server end communicate based on TCP.

[0070] Optionally, the approval server is used to push the approval notification to the corresponding user terminal based on UDP point-to-point when completing the business approval based on the approval business form.

[0071] Optionally, the business service end is further used to add a sequence ID of the process reversal order and an operation user ID of the corresponding node to the business type data.

[0072] Optionally, on the business server side, define an operation file for binary data conversion;

[0073] A corresponding mapping relationship is defined in the first mapping file based on the operation file.

[0074] System approval Figure 2 As shown, step 1: build the main service A (business server) and set the approval policy for the corresponding business type, set the approval switch, set the terminal user, and create the required approval process definition;

[0075] Step 2: Build TCP forwarding service, set up service forwarding mechanism, and determine the forwarding request size function number;

[0076] Step 3: Determine to build a unified database and set the corresponding table creation statements to create tables;

[0077] Step 4: Download client M, update the policy, and log in using the specified terminal user;

[0078] Step 5: Build the work order service C (work order server) to ensure the normal display of the work order list and approval rejection;

[0079] Step 6: Start the UDP service to ensure the normal use of the UDP service function;

[0080] Step 7: Build approval service B (approval server), introduce UDP message push method, and establish TCP request forwarding between service A and approval service B, client M and approval service B, and work order service C and approval service B.

[0081] In business approval, different servers in the existing technology share the same database, but different servers require different user permissions for control. For example, the CEMS service requires specific configuration permissions to view the approval process definition page and allow the creation of approval process definitions, while the corresponding CEMSUP server requires a specific terminal installed device user to be responsible for the approval of the work order generated by the approval process. Although the approval service as a logical processing is an independent service, the existing technology is only the operation of the traditional activiti workflow, which only supports one business type for approval. The approval service as an intermediate business logic processing greatly wastes resources, so it is very necessary to transform and expand the approval process;

[0082] Therefore, in order to realize the technical solution of the present disclosure, first

[0083] 1. Expand business types: expand the approval process definition table and approval process definition record log table, add business types, state status, etc.;

[0084] At the same time, the columns of the work order table are expanded, adding the number of message outbound transmissions, work order validity period, business type, title, file information, etc., and the columns of the work order history table are also expanded, adding business type, sequence ID of process reversal order, process reversal ID of the previous node, and operator user ID of the previous node. On the basis of the original document encryption application approval, it can also be compatible with the "message approval" and "DLP document outbound application approval" processes;

[0085] 2. Added UDP message push: Embed the cems point-to-point message sending function in the approval service to directly call the UDP service, send a request to the client's public class SendPtpUtil, configure and agree on the corresponding size function number and the fixed json format for the client to normally receive UDP messages, judge whether the device is online, obtain the device cache, call the interface for cleaning offline device information, etc. Ensure normal UDP point-to-point message sending;

[0086] 3. The core engine package source code of the approval workflow supports the stand-alone database by default. When using a distributed database, an error will occur. When using the distributed database DBLE, the binary data type conversion rules of the workflow's native binary data table have changed, and normal insertion operations on the table cannot be performed. Therefore, it is necessary to redefine an additional class to rewrite the conversion operation of binary type data, and add the mapping relationship of the newly defined class to the source code mapping xml file in the engine package to be compatible with the new binary conversion rules, thereby achieving compatibility with distributed databases;

[0087] 4. The proportion of domestic databases such as DAMO, Jincang and Shentong in some projects is expanding year by year, but the activiti workflow does not support domestic databases. If you want to be compatible with domestic databases such as DAMO and Jincang, first of all, you need to configure the domestic database type, because the approval service will read the jdbc configuration file on the server at the beginning of startup and then create the database type of the program. Therefore, on the basis of the original supported database, it is necessary to increase the mapping of custom configuration database type; secondly, put the core engine framework package source code of the workflow into the database sql query and abstract class query for expansion and transformation. Here we mainly make compatible transformations to the core methods of the core query class; then, the precautions for sql table creation, introduce the domestic database configuration file to configure the limitAfter attribute of each database, so that the domestic database can also create normal workflows, so as to achieve the purpose of compatibility with domestic databases.

[0088] The basic principles of the present disclosure are described above in conjunction with specific embodiments. However, it should be noted that the advantages, strengths, effects, etc. mentioned in the present disclosure are only examples and not limitations, and it cannot be considered that these advantages, strengths, effects, etc. are required by each embodiment of the present disclosure. In addition, the specific details disclosed above are only for the purpose of illustration and ease of understanding, and are not limitations. The above details do not limit the present disclosure to the necessity of adopting the above specific details to be implemented.

[0089] In the present disclosure, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. The block diagrams of the devices, devices, equipment, and systems involved in the present disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagram. As will be appreciated by those skilled in the art, these devices, devices, equipment, and systems can be connected, arranged, and configured in any manner. Words such as "including", "comprising", "having", etc. are open words, referring to "including but not limited to", and can be used interchangeably with them. The words "or" and "and" used here refer to the words "and / or" and can be used interchangeably with them, unless the context clearly indicates otherwise. The words "such as" used here refer to the phrase "such as but not limited to", and can be used interchangeably with them.

[0090] Additionally, as used herein, "or" used in a list of items beginning with "at least one" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Furthermore, the word "exemplary" does not mean that the example described is preferred or better than other examples.

[0091] It should also be noted that in the system and method of the present disclosure, each component or each step can be decomposed and / or recombined. Such decomposition and / or recombination should be regarded as equivalent solutions of the present disclosure.

[0092] Various changes, substitutions, and modifications of the techniques described herein may be made without departing from the teachings defined by the appended claims. Furthermore, the scope of the claims of the present disclosure is not limited to the specific aspects of the processes, machines, manufactures, compositions of events, means, methods, and actions described above. Currently existing or later to be developed processes, machines, manufactures, compositions of events, means, methods, or actions that perform substantially the same functions or achieve substantially the same results as the corresponding aspects described herein may be utilized. Thus, the appended claims include such processes, machines, manufactures, compositions of events, means, methods, or actions within their scope.

[0093] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the aspects shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

[0094] The above description has been given for the purpose of illustration and description. In addition, this description is not intended to limit the embodiments of the present disclosure to the forms disclosed herein. Although multiple example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims

1. A business approval method, characterized in that: include: Obtaining a service request instruction, wherein the service request instruction includes service type data to be called and a service process to be generated; Calling corresponding business type data based on the business request instruction; Generate an approval business form based on the business type data; Before the step of calling the corresponding service type data based on the service request instruction, the method includes: Adding a sequence ID of the process reversal order and an operation user ID of the corresponding node to the business type data; Before the step of calling the corresponding service type data based on the service request instruction, the method further includes: Define the operation file for binary type data conversion; Defining a corresponding mapping relationship in the first mapping file based on the operation file; Complete business approval based on the approval business order; Before the step of generating an approval business form based on the business type data, the method further includes: Configure the second mapping file of the database type, configure the database sql query and the abstract class query file.

2. The business approval method according to claim 1, characterized in that: The service request instruction is transmitted based on TCP, and the service type data is transmitted based on TCP.

3. The business approval method according to claim 1, characterized in that: The completing the business approval based on the approval business order includes: Send approval notifications to corresponding approvers or requesters.

4. The business approval method according to claim 3, characterized in that: The approval notification is pushed based on UDP point-to-point.

5. A business approval system, characterized in that: Including user side, business service side and approval service side; The user terminal is used to initiate a service request instruction, wherein the service request instruction includes the service type data to be called and the service process to be generated; The business service end is used to call corresponding business type data based on the received business request instruction; The business service end is also used to add a sequence ID of the process reversal order and an operation user ID of the corresponding node to the business type data; On the business service side, define an operation file for binary type data conversion; Defining a corresponding mapping relationship in the first mapping file based on the operation file; The approval service end is used to generate an approval business form based on the business type data, and complete business approval based on the approval business form; On the approval service side, a second mapping file of the database type is configured, and a database sql query and an abstract class query file are configured.

6. The business approval system according to claim 5, characterized in that: The user end and the business service end communicate based on TCP, and the business service end and the approval service end communicate based on TCP.

7. A business approval system according to claim 5, characterized in that: The approval service end is used to push the approval notification to the corresponding user end based on UDP point-to-point when the business approval is completed based on the approval business order.

Images