CN112330304A

CN112330304A - Contract approval method and device

Info

Publication number: CN112330304A
Application number: CN202011353102.3A
Authority: CN
Inventors: 潘娟; 马微; 周晓雨; 武桐
Original assignee: Taikang Insurance Group Co Ltd
Current assignee: Taikang Insurance Group Co Ltd
Priority date: 2020-11-27
Filing date: 2020-11-27
Publication date: 2021-02-05

Abstract

The application provides a contract approval method and a contract approval device, wherein the method comprises the following steps: acquiring a contract type change instruction in the process of target contract approval, wherein the contract type change instruction carries a target contract type; responding to the change instruction, and acquiring the current approved process of the target contract and the approved process of the target contract type; and performing node comparison on the approved process and the approval process of the target contract type, and determining the approval process after the target contract is changed. By the scheme, the problem that the contract approval efficiency is low due to the fact that rollback is needed when the contract type modification requirement exists in the existing contract approval is solved, and the technical effect of effectively improving the contract approval efficiency is achieved.

Description

Contract approval method and device

Technical Field

The application belongs to the technical field of internet, and particularly relates to a contract approval method and device.

Background

The contract approval process generally refers to the process of node-by-node approval according to a preset approval process, and the contract approval is determined to be completed after the approval of the last approval node is completed. For example: the approval process of the type A contract is as follows: the contract initiator-team supervisor-department supervisor-general manager-director of the board, and the approval process of the type B contract is as follows: contract initiator-team leader-finance staff-department leader-board leader.

That is, the approval processes and approval nodes of different contracts are different, and in the existing contract approval process, if the same type needs to be changed in the approval process, the whole contract needs to be returned and approval needs to be initiated again.

The existing contract approval is generally to customize the approval flow according to the personalized requirements of each organization, and at the same time, the flows of special contract types, sub-organizations and branch companies are customized, and the contract types are not allowed to be modified in the contract approval process. If the modification is needed, if the phenomena that a certain leader is omitted in the process link, examination and approval and the like are discovered, the process link needs to be returned to the end, the process link is returned to the sender initiating link, and the process link is restarted, so that the examination and approval efficiency is reduced, and the labor cost is increased.

In view of the above problems, no effective solution has been proposed.

Disclosure of Invention

The application aims to provide a contract approval method and device, which can improve contract approval efficiency.

The application provides a contract approval method and a contract approval device, which are realized as follows:

a method of contract approval, the method comprising:

acquiring a contract type change instruction in the process of target contract approval, wherein the contract type change instruction carries a target contract type;

responding to the change instruction, and acquiring the current approved process of the target contract and the approved process of the target contract type;

and performing node comparison on the approved process and the approval process of the target contract type, and determining the approval process after the target contract is changed.

In one embodiment, the node comparison between the approved process and the approval process of the target contract type is performed to determine the approval process after the target contract is changed, and the method includes:

determining whether an approval node which is the same as the approval process of the target contract type exists in the approved process;

and if the same examination and approval nodes exist, taking the process without the same examination and approval nodes in the examination and approval process of the target contract type as the modified examination and approval process.

acquiring a current approval node as a target node;

determining the position of a target node in the approval process of the target contract type, and determining a node set before and a node set after the target node in the approval process of the target contract type;

determining whether nodes which do not exist in the approved process exist in a previous node set;

taking nodes which do not exist in the approved process in the previous node set as nodes to be signed;

and taking the node to be signed and the subsequent node set as an approval process after the target contract is changed.

In one embodiment, in response to the modification instruction, obtaining an approval process of the target contract type includes:

calling a preset process rule engine;

acquiring identification information of the target contract type;

and calling an approval process of the target contract type from the preset process engine according to the identification information.

In one embodiment, the above method further comprises:

acquiring a modification instruction of a flow rule engine from a user, wherein the modification instruction comprises at least one of the following: adding contract types, deleting contract types, merging contract types, splitting contract types and modifying the approval process of the selected contract types;

modifying the flow rule engine according to the modification instruction;

and storing the modified flow rule engine.

In one embodiment, after determining the approval process after the target contract is modified, the method further includes:

acquiring a current approval node;

determining the position of the current approval node in the changed approval process;

and taking the current approval node as an initial node, and continuing to approve according to the changed approval process.

In one embodiment, obtaining contract type modification instructions includes:

receiving a change request of the same type from a user in a contract approval system;

receiving a contract type selected by a user on a change page;

taking the contract type selected on the changed page as a target contract type;

and generating the contract type change instruction according to the target contract type.

In another aspect, a contract approval apparatus is provided, including:

the first acquisition module is used for acquiring a contract type change instruction in the process of examining and approving a target contract, wherein the contract type change instruction carries a target contract type;

the second acquisition module is used for responding to the change instruction and acquiring the current approved process of the target contract and the approved process of the target contract type;

and the comparison module is used for carrying out node comparison on the approved process and the approval process of the target contract type to determine the approval process after the target contract is changed.

In one embodiment, the alignment module comprises:

the first determining unit is used for determining whether an approval node which is the same as the approval process of the target contract type exists in the approved process;

and the removing unit is used for taking the process of the target contract type after the same examination and approval node is removed in the examination and approval process as the modified examination and approval process under the condition that the same examination and approval node exists.

In one embodiment, the alignment module comprises:

the acquisition unit is used for acquiring the current approval node as a target node;

the second determining unit is used for determining the position of the target node in the approval process of the target contract type and determining a node set before and a node set after the target node in the approval process of the target contract type;

a third determining unit, configured to determine whether a node that does not exist in the approved process exists in a previous node set;

the system comprises a signature adding unit, a signature analyzing unit and a signature analyzing unit, wherein the signature adding unit is used for taking nodes which do not exist in the approved process in the previous node set as nodes to be signed;

and the generating unit is used for taking the node to be signed and the subsequent node set as the approval process after the target contract is changed.

In yet another aspect, a terminal device is provided, comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor implementing the steps of the method:

In yet another aspect, a computer-readable storage medium is provided having computer instructions stored thereon which, when executed, implement the steps of the method of:

According to the contract approval method and device, in the contract approval process, if the same type of modification requests occur, the contract does not need to be returned to a contract submitting party, the original contract type approval process is compared with the new type approval process, and the approved nodes do not need to be repeatedly approved. By the mode, the problem that the contract approval efficiency is low due to the fact that rollback is needed when the contract type modification requirement exists in the existing contract approval is solved, and the technical effect of effectively improving the contract approval efficiency is achieved.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.

FIG. 1 is a flow chart of a method of one embodiment of a method of contract approval provided herein;

FIG. 2 is a schematic diagram of an approval process for a pay-class-generic framework collaborative contract provided by the present application;

FIG. 3 is a schematic view of an approval process for a claim reimbursement agreement for an expenditure class-medical institution as provided herein;

FIG. 4 is an architecture diagram of a computer terminal provided herein;

FIG. 5 is a block diagram of an embodiment of a contract approval apparatus provided in the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Considering that the existing contract operator makes mistakes in the selection of the same type in the contract drafting stage, and in the subsequent legal review stage or the confirmation link of the presenter, if the same type needs to be adjusted according to the actual service scene, the contract needs to be backed off, and then approval is initiated again, so that the efficiency of contract approval is extremely low.

Based on this, in this example, a contract approval method is provided, as shown in fig. 1, which may include the following steps:

step 101: acquiring a contract type change instruction in the process of target contract approval, wherein the contract type change instruction carries a target contract type;

step 102: responding to the change instruction, and acquiring the current approved process of the target contract and the approved process of the target contract type;

step 103: and performing node comparison on the approved process and the approval process of the target contract type, and determining the approval process after the target contract is changed.

In the above example, in the process of contract approval, if a modification request for the same type occurs, the contract is not required to be returned to the contract submitting party, but the original contract type approval process is compared with the new type approval process, and the approved nodes are not required to be repeatedly approved. By the mode, the problem that the contract approval efficiency is low due to the fact that rollback is needed when the contract type modification requirement exists in the existing contract approval is solved, and the technical effect of effectively improving the contract approval efficiency is achieved.

Specifically, when the node comparison is performed between the approved process and the approval process of the target contract type, and the approval process after the target contract is changed is determined, a deduplication manner may be adopted, that is, for nodes that have already executed the approval operation in the preorder approval process, if the nodes also exist in the new type, the process nodes do not need to execute the approval operation again, specifically, the method may be: determining whether an approval node which is the same as the approval process of the target contract type exists in the approved process; and if the same examination and approval nodes exist, taking the process without the same examination and approval nodes in the examination and approval process of the target contract type as the modified examination and approval process.

For example: the type of the contract selected by the contract submitting node is type A, and the approval process of the type A contract is as follows: the process of submission of the presenter, group leader confirmation, minister confirmation, legal approval, financial approval, president approval and legal reexamination is as follows: presenter submission-group leader validation-legal approval-technical validation-director approval.

After the employee submits one-part contract and selects the type of the contract as type A, the system can match the approval process of the type A contract from the background (namely, submission of the submitter, confirmation of the group leader, confirmation of the organization leader, legal approval, financial approval, approval of the director and legal reexamination) as the approval process of the current contract, namely, the approval process is advanced layer by layer according to the matched approval process until the approval is finished. If the contract type is found to be selected wrongly in the middle of the examination and approval, for example, the type of the current contract is found to be B type in the legal examination and approval process, the background associates the examination and approval processes of the B type contract (i.e., submitter submission, group leader confirmation, legal examination and approval, technical confirmation and director examination and approval), compares the examination and approval processes of the two types of contracts, determines that the examination and approval steps corresponding to ' submitter submission and group leader confirmation ' are completed for the B type contract, and then performs the examination and approval process by using the examination and approval nodes of ' legal examination and approval, technical confirmation and director ' examination and approval '. Therefore, after determining to modify the type B contract, the current contract is switched from the previous subsequent flow "financial approval-president approval-legal review" to "legal approval-technical confirmation-president approval".

In actual implementation, not only the deduplication operation but also the tagging operation is sometimes required. Correspondingly, the node comparison between the approved process and the approval process of the target contract type is performed to determine the approval process after the target contract is changed, which may include: acquiring a current approval node as a target node; determining the position of a target node in the approval process of the target contract type, and determining a node set before and a node set after the target node in the approval process of the target contract type; determining whether nodes which do not exist in the approved process exist in a previous node set; taking nodes which do not exist in the approved process in the previous node set as nodes to be signed; and taking the node to be signed and the subsequent node set as an approval process after the target contract is changed.

The type of the contract selected by the contract submitting node is the type A, and the approval process of the type A contract is as follows: presenter submission-group leader validation-legal approval-technical validation-director approval. The type of the modified contract is B type, and the approval process of the B type contract is as follows: presenter submission-group leader confirmation-minister confirmation-legal approval-financial approval-director approval-legal reexamination.

When the A-type contract is approved to the legal approval node, the contract type is modified, the approval nodes of financial approval, president approval and legal review are added for the B-type contract, but the approval nodes before the legal approval are lacked for the president confirmation, so that the president confirmation, financial approval, president approval and legal review can be used as the subsequent approval process.

For the examination and approval processes of different types of contracts, the examination and approval processes can be set and stored in a process rule engine mode, so that after a contract submitting person selects a contract type, a background can automatically match the corresponding process rule, namely the examination and approval process. And then, according to the matched approval process, carrying out contract approval one by one on the nodes. Specifically, the obtaining of the approval process of the target contract type in response to the change instruction may include: calling a preset process rule engine; acquiring identification information of the target contract type; and calling an approval process of the target contract type from the preset process engine according to the identification information.

For the above flow rule engine, a user may modify as required, that is, may obtain a modification instruction of the flow rule engine from the user, where the modification instruction may include, but is not limited to, at least one of the following: adding contract types, deleting contract types, merging contract types, splitting contract types and modifying the approval process of the selected contract types; modifying the flow rule engine according to the modification instruction; and storing the modified flow rule engine.

After the approval process after the target contract is changed is determined, the current approval node can be obtained; determining the position of the current approval node in the changed approval process; and taking the current approval node as an initial node, and continuing to approve according to the changed approval process. Namely, the current approval node is used as an initial node for starting subsequent approval, then the subsequent nodes of the current approval node in the modified approval process are obtained, and the contract approval is carried out one by one through the subsequent nodes, so that the contract approval after the contract type is modified is completed.

The contract type modification method can be applied to a contract approval system, namely, multiple contract types can be gathered in the contract approval system, a user selects one contract type when the contract needs to be approved, then approval is triggered, in the approval process, a modification request of the same type in the contract approval system can be received, a contract type selection page can be displayed to the user based on the modification request, then the user can select the contract type to be modified on the page, the contract type selected on the modification page is used as a target contract type, and a contract type modification instruction is generated according to the selected target contract type, so that modification of the contract approval process is triggered.

The above method is described below with reference to a specific example, however, it should be noted that the specific example is only for better describing the present application and is not to be construed as limiting the present application.

Aiming at the problems that the selection of the same type is wrong in the contract drafting stage of the existing contract operator, and the subsequent legal review stage or the confirmation link of a presenter is adopted, if the same type needs to be adjusted according to the actual service scene, the contract needs to be backed off, and then the examination and approval are initiated again, so that the efficiency of contract examination and approval is extremely low.

Therefore, in the embodiment, it is considered that a contract approval system can be provided, in which an approval process of each contract type is set, and the approval processes of each type are associated, and the same part and the different part of the approval processes of different types of contracts are concerned, when the contracts are approved, if there is a requirement for contract type modification, only the different part is re-approved without contract rollback, and the same part in the preamble follows the approval result before contract type modification, so that when the contract types are modified, the link of contract submission is not required, thereby reducing the approval workload of the contracts under the condition of wrong type selection, and effectively improving the approval efficiency.

Specifically, in the contract approval system, the following nodes may be included: in order to realize centralized control of the same examination and approval, the contract submission nodes, the examination and approval link nodes and the system management nodes need to set examination and approval processes of each contract type in the background, and can perform association and differentiation judgment on different examination and approval processes, namely, a process engine and a rule engine need to be established.

For example, the type of the contract selected by the contract submitting node is type a, and the approval process of the type a contract is as follows: the process of submission of the presenter, group leader confirmation, minister confirmation, legal approval, financial approval, president approval and legal reexamination is as follows: presenter submission-group leader validation-legal approval-technical validation-director approval.

By the mode, the contract is not required to be returned to the contract submitting stage, the existing and overlapped nodes do not need to be examined and approved, and the examination and approval efficiency is improved.

That is, in the above example, the difference between the contract type before modification and the contract type after modification is compared, and the approval process that has been executed does not need to be executed any more, and only needs to be switched to the subsequent node of the contract type after modification.

Further, when the approval processes of the new and old contract types are matched, a signature adding mode can be adopted to adjust the modified approval process, for example, the contract type selected by the contract submission node is a type a, and the approval process of the type a contract is as follows: presenter submission-group leader validation-legal approval-technical validation-director approval. The type of the modified contract is B type, and the approval process of the B type contract is as follows: presenter submission-group leader confirmation-minister confirmation-legal approval-financial approval-director approval-legal reexamination.

That is, for the approval nodes before the current node, the original contract type does not exist, but some approval nodes in the new contract type can adopt a signing mode to add the approval nodes as signing nodes to the subsequent approval process.

A specific example is described as follows, in the process of contract approval, the current approval link can edit contract information, and then "contract type" is allowed to be modified, all valid contract types are popped up, and after a user selects to modify the contract type, the user clicks: and if the contract is stored, determining that the contract type is successfully modified, and after the contract type is modified, judging the flow trend again by the system according to the contract type. Wherein, in the process of process approval, the following nodes are involved: submission by the presenter, confirmation by the signed presenter, initial legal review, re-legal review, etc.

When the on-line contract submitting department contract submitting persons draft the contract and submit the examination and approval, in the examination and approval process, except the inner personnel link of the submitting department, other links can carry out signature adding examination and approval on the department responsible person of the relevant department submitting the model, the signature adding personnel can also send other personnel in the department to carry out signature adding, and finally, after the examination and approval of the contract is passed, the contract examination and approval process is completed.

Suppose, in the process of process approval, the links are involved: submission by the presenter, confirmation by the presenter, modification/confirmation by the signed presenter, initial legal review, re-legal review, etc. When the contract is approved, the buyer material control management approval node modifies the contract type of the expenditure-general framework cooperative contract into an expenditure-medical institution claim settlement direct payment agreement, and then the corresponding background approval flow changes correspondingly, and the changes are matched by the background.

As shown in fig. 2, the examination and approval process of the "payment class-general framework cooperative contract" is the examination and approval process of the "payment class-medical institution claims direct payment agreement" as shown in fig. 3, and after the purchase logistics management examination and approval node modifies the agreement type into the "payment class-medical institution claims direct payment agreement", the subsequent examination and approval process can be directly switched to the subsequent examination and approval process of the "payment class-medical institution claims direct payment agreement".

In the process of contract approval, the approval nodes can perform signature adding processing according to requirements and conditions, and can also perform operations such as modification on the same type according to conditions.

In the above example, because the contract approval rules and the process engine are set in the background, the contract type switching at the front end and the configuration logic at the background can be automatically identified, so that different approval process paths can be obtained, and thus, when the contract type needs to be increased or the background process needs to be modified, only the modification requirement needs to be given, the contract approval rules and the process engine can be automatically adjusted by the background, so that the efficiency of the whole contract approval system can be improved.

The method embodiments provided in the above embodiments of the present application may be executed in a mobile terminal, a computer terminal, or a similar computing device. Taking the operation on the computer terminal as an example, fig. 4 is a hardware structure block diagram of the computer terminal of the contract approval method according to the embodiment of the present invention. As shown in fig. 4, the computer terminal 10 may include one or more (only one shown) processors 102 (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions. It will be understood by those skilled in the art that the structure shown in fig. 4 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computer terminal 10 may also include more or fewer components than shown in FIG. 4, or have a different configuration than shown in FIG. 4.

The memory 104 may be used to store software programs and modules of application software, such as program instructions/modules corresponding to the contract approval method in the embodiment of the present invention, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, implementing the contract approval method of the application program. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission module 106 is used to receive or transmit data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission module 106 may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

At the software level, the contract approval apparatus may be as shown in fig. 5, and includes:

a first obtaining module 501, configured to obtain a contract type change instruction in a target contract approval process, where the contract type change instruction carries a target contract type;

a second obtaining module 502, configured to obtain, in response to the change instruction, a current approved process of the target contract and an approved process of the target contract type;

a comparison module 503, configured to perform node comparison on the approved process and the approval process of the target contract type, and determine the approval process after the target contract is changed.

In one embodiment, the alignment module 503 may include: the first determining unit is used for determining whether an approval node which is the same as the approval process of the target contract type exists in the approved process; and the removing unit is used for taking the process of the target contract type after the same examination and approval node is removed in the examination and approval process as the modified examination and approval process under the condition that the same examination and approval node exists.

In one embodiment, the alignment module 503 may include: the acquisition unit is used for acquiring the current approval node as a target node; the second determining unit is used for determining the position of the target node in the approval process of the target contract type and determining a node set before and a node set after the target node in the approval process of the target contract type; a third determining unit, configured to determine whether a node that does not exist in the approved process exists in a previous node set; the system comprises a signature adding unit, a signature analyzing unit and a signature analyzing unit, wherein the signature adding unit is used for taking nodes which do not exist in the approved process in the previous node set as nodes to be signed; and the generating unit is used for taking the node to be signed and the subsequent node set as the approval process after the target contract is changed.

In one embodiment, the second obtaining module 502 may be specifically configured to obtain a preset process rule engine; acquiring identification information of the target contract type; and calling an approval process of the target contract type from the preset process engine according to the identification information.

In one embodiment, the contract approval apparatus may be further configured to obtain a modification instruction of the process rule engine from the user, where the modification instruction includes at least one of: adding contract types, deleting contract types, merging contract types, splitting contract types and modifying the approval process of the selected contract types; modifying the flow rule engine according to the modification instruction; and storing the modified flow rule engine.

An embodiment of the present application further provides a specific implementation manner of an electronic device, which is capable of implementing all steps in the contract approval method in the foregoing embodiment, where the electronic device specifically includes the following contents: a processor (processor), a memory (memory), a communication Interface (Communications Interface), and a bus; the processor, the memory and the communication interface complete mutual communication through the bus; the processor is configured to call a computer program in the memory, and when executing the computer program, the processor implements all the steps in the contract approval method in the above embodiment, for example, when executing the computer program, the processor implements the following steps:

step 1: acquiring a contract type change instruction in the process of target contract approval, wherein the contract type change instruction carries a target contract type;

step 2: responding to the change instruction, and acquiring the current approved process of the target contract and the approved process of the target contract type;

and step 3: and performing node comparison on the approved process and the approval process of the target contract type, and determining the approval process after the target contract is changed.

As can be seen from the above description, in the contract approval process, if a modification request of the same type occurs, the contract approval process does not need to be returned to the contract submitting party, but the original contract type approval process is compared with the new type approval process, and the approved nodes do not need to be repeatedly approved. By the mode, the problem that the contract approval efficiency is low due to the fact that rollback is needed when the contract type modification requirement exists in the existing contract approval is solved, and the technical effect of effectively improving the contract approval efficiency is achieved.

Embodiments of the present application further provide a computer-readable storage medium capable of implementing all steps in the contract approval method in the above embodiments, where the computer-readable storage medium stores thereon a computer program, and when the computer program is executed by a processor, the computer program implements all steps of the contract approval method in the above embodiments, for example, when the processor executes the computer program, the processor implements the following steps:

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 hardware + program class embodiment, since it is substantially similar to the method embodiment, the description is simple, and the relevant points can be referred to the partial description of the method embodiment.

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Although the present application provides method steps as described in an embodiment or flowchart, additional or fewer steps may be included based on conventional or non-inventive efforts. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or client product executes, it may execute sequentially or in parallel (e.g., in the context of parallel processors or multi-threaded processing) according to the embodiments or methods shown in the figures.

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 vehicle-mounted human-computer interaction device, a cellular telephone, a camera phone, a smart phone, 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.

Although embodiments of the present description provide method steps as described in embodiments or flowcharts, more or fewer steps may be included based on conventional or non-inventive means. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual apparatus or end product executes, it may execute sequentially or in parallel (e.g., parallel processors or multi-threaded environments, or even distributed data processing environments) according to the method shown in the embodiment or the figures. 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, the presence of additional identical or equivalent elements in a process, method, article, or apparatus that comprises the recited elements is not excluded.

For convenience of description, the above devices are described as being divided into various modules by functions, and are described separately. Of course, in implementing the embodiments of the present description, the functions of each module may be implemented in one or more software and/or hardware, or a module implementing the same function may be implemented by a combination of multiple sub-modules or sub-units, and the like. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

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 therefore be considered as 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 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.

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, embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present 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 so forth) having computer-usable program code embodied therein.

The embodiments of this specification 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 described embodiments 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. In the description herein, references to the description of the term "one embodiment," "some embodiments," "an example," "a specific example," or "some examples," etc., mean that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of an embodiment of the specification. In this specification, the schematic representations of the terms used above are not necessarily intended to refer to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, various embodiments or examples and features of different embodiments or examples described in this specification can be combined and combined by one skilled in the art without contradiction.

The above description is only an example of the embodiments of the present disclosure, and is not intended to limit the embodiments of the present disclosure. Various modifications and variations to the embodiments described herein will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present specification should be included in the scope of the claims of the embodiments of the present specification.

Claims

1. A method of contract approval, the method comprising:

responding to the contract type change instruction, and acquiring the current approved process of the target contract and the approved process of the target contract type;

2. The method according to claim 1, wherein performing a node comparison between the approved process and the approval process of the target contract type to determine the approval process after the target contract is modified comprises:

3. The method according to claim 1, wherein performing a node comparison between the approved process and the approval process of the target contract type to determine the approval process after the target contract is modified comprises:

acquiring a current approval node as a target node;

4. The method of claim 1, wherein obtaining an approval process for the target contract type in response to the alteration instruction comprises:

calling a preset process rule engine;

acquiring identification information of the target contract type;

5. The method of claim 4, further comprising:

modifying the flow rule engine according to the modification instruction;

and storing the modified flow rule engine.

6. The method of claim 1, after determining the revised approval schedule for the target contract, further comprising:

acquiring a current approval node;

7. The method of claim 1, wherein obtaining contract type modification instructions comprises:

receiving a contract type selected by a user on a change page;

8. A contract approval apparatus, comprising:

9. A terminal device comprising a processor and a memory for storing processor-executable instructions, the instructions when executed by the processor implementing the steps of the method of:

performing node comparison on the approved process and the approval process of the target contract type, and determining the approval process after the target contract is changed;

and examining and approving the target contract according to the changed examination and approval process.

10. A computer readable storage medium having stored thereon computer instructions which, when executed, implement the steps of a method comprising: