Examination and approval path generation method and device, equipment and storage medium

Abstract

The invention relates to the technical field of information management, and discloses an approval path generation method and device, equipment and a storage medium, and the method comprises the steps: determining the node hierarchy number of a project to which a target service belongs in an organization structure tree and the function classification of the target service; determining a target preset approval link based on the node hierarchy number and the function classification; and determining the approval path corresponding to the target service according to the target preset approval link, the organization structure tree and the personnel information. The method can be suitable for complex management organization structures in the building industry and the like, and automatic and large-scale generation of the approval path is realized.

Description

Technical Field

[0001] The present application relates to the field of information management technology, and in particular to an approval path generation method, device, equipment and storage medium. Background Art

[0002] In the prior art, the organizational structure tree usually only includes two levels: company and department. In the construction industry, there are many projects involved, and these projects are often independent of the organizational structure tree, which leads to information not being exchanged between projects and companies or departments. In addition, the current design of the approval process usually adopts a static approval path design, that is, users need to manually add approvers from the approval roles, which makes the approval process design more cumbersome. Due to the separation of the organizational structure tree and the project in the construction industry, the approval path design for tasks in each project in the construction industry is even more complicated. Summary of the invention

[0003] In view of this, the embodiments of the present application provide an approval path generation method, device, equipment and storage medium, which can be applicable to complex management organizational structures such as the construction industry, and realize automatic and large-scale generation of approval paths.

[0004] In a first aspect, an embodiment of the present application provides a method for generating an approval path, including:

[0005] Determine the number of node levels in the organizational structure tree of the project to which the target business belongs and the functional classification of the target business;

[0006] Determine a target preset approval link based on the number of node levels and the functional classification;

[0007] The approval path corresponding to the target business is determined according to the target preset approval link, the organizational structure tree and personnel information.

[0008] In some embodiments, determining the approval path corresponding to the target business according to the target preset approval link, the organizational structure tree and personnel information includes:

[0009] The number of approval levels and the approval role corresponding to each approval node in each approval level are determined according to the target preset approval link.

[0010] A target node corresponding to each approval level is determined based on the number of approval levels and the organizational structure tree.

[0011] The approving personnel corresponding to each approval node in the approval hierarchy are obtained from the personnel information corresponding to each target node.

[0012] The approval path is generated according to the approval personnel of each approval node in each approval level and each approval node in each approval level.

[0013] In some embodiments, after acquiring the approval personnel corresponding to each approval node in the approval hierarchy from the personnel information corresponding to each target node, the method further includes:

[0014] If the current target node cannot match the approver of the approval role required by the approval node, an alarm message is issued to enable the user to manually match the approver; or

[0015] According to the preset matching rule of no approving personnel, the approval node that has not matched the approving personnel is re-matched with the approving personnel; wherein the preset matching rule of no approving personnel is to match the approving personnel who meet the approval role required by the current approval node from the superior target node of the current target node that has not matched the approving personnel.

[0016] In some embodiments, the generation of the organizational structure tree includes:

[0017] Generate company nodes based on company information;

[0018] Based on the department information, determine the company to which each department belongs, and mount each department under the corresponding company node to generate a department node;

[0019] Based on the project information, the department or company to which the project belongs is determined, and each of the projects is mounted under the corresponding department node or company node, and a project node is generated.

[0020] In some embodiments, it further includes: if the organizational structure tree is changed, updating the corresponding approval path according to the changed organizational structure tree.

[0021] In some embodiments, the change in the organizational structure tree includes a personnel change;

[0022] Then, all the approval paths are updated according to the changed organizational structure tree, including:

[0023] The approving personnel corresponding to the approval role associated with the personnel change in the approval path is changed to form the updated approval path.

[0024] In some embodiments, the change of the organizational structure tree also includes a change of node level;

[0025] Then, all the approval paths are updated according to the changed organizational structure tree, including:

[0026] Determining the target business associated with the node level change;

[0027] Determine the target preset approval link based on the number of node levels of the project to which the target business associated with the node level change belongs in the organizational structure tree after the change, and the functional classification of the target business associated with the level change;

[0028] The approval path corresponding to the target business associated with the hierarchical change is determined according to the target preset approval link, the changed organizational structure tree and personnel information.

[0029] In a second aspect, an embodiment of the present application provides an approval path generation device, including:

[0030] The first determination module is used to determine the number of node levels of the project to which the target business belongs in the organizational structure tree and the functional classification of the target business;

[0031] A second determination module, configured to determine a target preset approval link based on the number of node levels and the functional classification;

[0032] The third determination module is used to determine the approval path corresponding to the target business according to the target preset approval link, the organizational structure tree and personnel information.

[0033] In a third aspect, an embodiment of the present application provides a terminal device, comprising a processor and a memory, wherein the memory stores a computer program, and the processor is used to execute the computer program to implement the above-mentioned approval path generation method.

[0034] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, which, when executed on a processor, implements the above-mentioned approval path generation method.

[0035] The embodiments of the present application have the following beneficial effects: the present application pre-sets the corresponding target preset approval chain based on the functional classification of the business at the node level level. Therefore, after determining the number of node levels in the organizational structure tree of the project where the target business is located and the functional classification of the target business, the corresponding preset approval chain can be determined. According to the approval role of each approval node in the preset approval chain, combined with the organizational structure tree and the personnel information corresponding to each node of the organizational structure tree, the approval path of the target task can be directly generated, thereby achieving the efficiency of approval path generation, and batch generation of approval paths can be achieved. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0037] Figure 1 A schematic diagram of a process for generating an organizational structure tree in an embodiment of the present application is shown;

[0038] Figure 2 A schematic diagram of an organizational structure tree according to an embodiment of the present application is shown;

[0039] Figure 3 A first flow chart of the method for generating an approval path according to an embodiment of the present application is shown;

[0040] Figure 4 A second flow chart of the approval path generation method according to an embodiment of the present application is shown;

[0041] Figure 5 A structural schematic diagram of an approval path generation device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0042] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0043] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0044] Hereinafter, the terms "including", "having" and their cognates that can be used in various embodiments of the present application are intended only to indicate specific features, numbers, steps, operations, elements, components or a combination of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or a combination of the foregoing items or increasing the possibility of one or more features, numbers, steps, operations, elements, components or a combination of the foregoing items. In addition, the terms "first", "second", "third" and the like are only used to distinguish descriptions and cannot be understood as indicating or implying relative importance.

[0045] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present application belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present application.

[0046] In conjunction with the accompanying drawings, some embodiments of the present application are described in detail below. In the absence of conflict, the following embodiments and features in the embodiments can be combined with each other.

[0047] In the existing technology, organizational structure management and approval process design are widely used in enterprise information management systems (such as ERP systems and project management systems). Its main technical features are as follows:

[0048] 1. The organizational structure tree usually contains two types of nodes: "company" and "department". Among them, the company node is the top-level node, and the department node is mounted at the lower level. The hierarchical relationship between nodes is fixed, and the node type cannot be dynamically expanded. For example, it is impossible to directly mount a project node under the company node, so the existing organizational structure tree cannot support complex project management requirements.

[0049] 2. Project management is generally a separate module, which is logically separated from the organizational structure tree, resulting in the incompatibility of project management information with organizational structure tree information. Since the construction industry usually involves multiple types of nodes (such as group companies, first-level companies, second-level companies... first-level departments, second-level departments, projects, etc.), the existing organizational structure tree management cannot meet the needs of multi-level dynamic management in the construction industry.

[0050] 3. Due to the isolation of the existing organizational structure tree from project management, it is difficult to achieve multi-level approval for the approval path of each task in construction industry projects.

[0051] Based on this, the present application proposes an approval path generation method, device, equipment and storage medium to dynamically and automatically generate approval paths for each task in the multi-level management of the construction industry. Before describing the approval path generation method of this embodiment, the organizational structure tree of this embodiment is first described.

[0052] Figure 1 A schematic diagram of a process for generating an organizational structure tree in an embodiment of the present application is shown. Exemplarily, the generation of the organizational structure tree includes:

[0053] Step S10, generating a company node according to company information.

[0054] Step S20, based on the department information, determine the company to which each department belongs, and mount each department under the corresponding company node to generate a department node.

[0055] Step S30, based on the project information, determine the department or company to which the project belongs, mount each of the projects under the corresponding department node or company node, and generate a project node.

[0056] like Figure 2 As shown, this embodiment is mainly aimed at the organizational structure management of the construction industry. For the construction industry, it not only includes company nodes and department nodes, but also project nodes. It can be understood that the organizational structure tree for the construction industry includes three types of nodes:

[0057] 1. Company nodes (including group company (head office) nodes, subsidiary (first-level company, second-level company, etc.) nodes. This node supports mounting subordinate company nodes, department nodes, and project nodes.

[0058] 2. Department node (department node under the group company, department node under the subsidiary), this node can mount the project node.

[0059] 3. Project nodes can mount project-level departments.

[0060] It can be understood that the organizational structure of this embodiment integrates companies, departments and projects, so that an intuitive management link is formed between projects, departments and companies, which can reduce data redundancy and avoid the problem of project information islands caused by the independence of projects from companies and departments in the prior art. In addition, by integrating companies, departments and projects, a unified management logic is adopted between companies, departments and projects, which facilitates the subsequent generation of approval paths for tasks in projects.

[0061] When there is no organizational structure tree in the system, the organizational structure tree is first generated based on the company information, department information and project information. First, the company information is obtained, where the company information includes but is not limited to the company name, hierarchical relationship (such as head office / subsidiary), location, company code, etc. If it is a subsidiary, it also includes the parent company to which the subsidiary belongs. After obtaining the company information, a company node can be generated based on the company information and used as the root node of the organizational structure tree.

[0062] After the company node is determined, the department information is obtained, where the department information includes but is not limited to the department name, department code, affiliated company, department function description, etc. The affiliated company of each department can be determined through the department information, and then each department node can be mounted under the corresponding company node. It can be understood that the department can be mounted under the head office node or the subsidiary node.

[0063] After the department node is determined, the project information is obtained, wherein the project information includes but is not limited to the company or department to which the project belongs and the project code, etc. The project is mounted under the corresponding company node or department node according to the company or department to which the project belongs.

[0064] If the project node also includes project departments, each project department will be mounted under the corresponding project node according to the project department information.

[0065] For example, the company information obtained is: Company A, the head office; Company B, which belongs to Company A.

[0066] The department information obtained is: Finance Department C, belonging to Company A; Technology Department D, belonging to Company B.

[0067] The project information obtained is: Project X, belongs to Company A; Project Y belongs to Technology Department D.

[0068] The organizational structure tree generated according to the above information is: "Finance Department C", "Project X" and "Company B" are mounted under the "Company A" node; "Technology Department D" is mounted under the "Company B" node, and "Project Y" is mounted under the "Technology Department D" node.

[0069] It should be noted that the above-mentioned method of obtaining company information, department information and project information can be the information directly input by the user through an input device, or can be the information uploaded to the system in the form of a table.

[0070] After the organizational structure tree is generated, this embodiment also needs to perform repeated detection on each node to avoid repeated generation of nodes.

[0071] If changes are made to an existing organizational structure tree, such as node level changes, the node level changes may include adding new project nodes, changing the node positions of existing project nodes, deleting existing project nodes, or deleting department nodes.

[0072] If a new project node is added, the new project will be mounted under the corresponding company node or department node according to the new project information (project name, project code, company / department, etc.). It should be noted that when adding a new project node, it is necessary to determine whether the new project is repeated with an existing project, which can be checked according to the project code.

[0073] If the node position of an existing project node changes, the project node that needs to be changed will be updated according to the input project node change information. For example, "Project Y" was originally mounted under Technology Department D, and now Project Y needs to be directly mounted under the node of Company B, then according to the information of Project Y change, Project Y will be mounted under the node of Company B in the organizational structure tree.

[0074] If you want to delete an existing project node or department node, etc., you can delete the node to be deleted in the organizational structure tree based on the information of the deleted node.

[0075] It should be noted that when mounting a department or project, if the obtained department information or project information does not have a clear belonging node, the system will issue a reminder. In this case, after receiving the reminder, you can mount the department or project under the target node, or adjust the input information.

[0076] Since each node in the organizational structure tree has a corresponding person, the corresponding personnel information is stored in the personnel information table, which includes but is not limited to name, number, node, role (such as safety officer, project manager, financial director, etc.). If there is a change in personnel, the approval path including the changed personnel will be updated synchronously.

[0077] In the case where an organizational structure tree is already available, the approval path generation method is described below in conjunction with some specific embodiments.

[0078] Figure 3 A schematic diagram of a process flow of the approval path generation method of an embodiment of the present application is shown. Exemplarily, the approval path generation method includes the following steps:

[0079] Step S100, determining the number of node levels of the project to which the target business belongs in the organizational structure tree and the functional classification of the target business.

[0080] In the process of company management, there are various businesses, such as construction organization design business, drawing review business, infrastructure inspection business, excellence acceptance business, etc. Each business needs to be reviewed, and different business review paths may also be different. The review path is related to the number of node levels of the project to which the business belongs in the organizational structure tree and the functional classification of the business.

[0081] The number of node levels of a business project in the organizational structure tree refers to the node of the business project in the organizational structure tree, and how many levels are above it, such as Figure 2 As shown in the figure, the business in project O includes project O, construction department K, company G, company F and company A, and the number of node levels is 5; the business in project P includes project P, company F and company A, and the number of node levels is 3.

[0082] For functional classification, each business has its own functional classification label, and the functional classification can be construction-related functions, acceptance-related functions, staffing functions, etc.

[0083] Step S200, determining a target preset approval link based on the number of node levels and functional classification.

[0084] The preset approval links are pre-set, and each preset approval link is designed according to the number of node levels and functional classification. Each preset approval link includes at least one approval node, and each approval node is set with a corresponding approver role.

[0085] Each approval level in the preset approval chain includes at least one approval role. For example, if a certain business requires three levels of approval, the first level is the project-level approval to which the current business belongs (the approval process is the project technical person in charge and the project manager), the second level is the upper functional organization of the project (if the upper functional organization of the project is a department, the approval process can be the department manager), and the third level is the approval of the upper two functional organizations of the project (if the upper two functional organizations of the project are companies, the approval process can be the safety management manager and the chief engineer). This embodiment can avoid the need for each business approval process in the prior art to select a separate approver by designing a preset approval chain. This embodiment uses a preset approval chain, which is equivalent to each business being able to find a corresponding approval path template, so that the approval path of each business can be efficiently determined later.

[0086] Step S300, determining the approval path corresponding to the target business according to the target preset approval chain, organizational structure tree and personnel information.

[0087] After determining the target preset approval chain corresponding to the target task, that is, determining how many levels of approval are required and what the roles of the approvers are at each level of approval, and because we also know which project node the target task is on in the organizational structure tree, we can also determine the nodes in the organizational structure tree corresponding to each approval level of the target preset approval chain. In addition, the personnel information corresponding to each node in the organizational structure tree is also determined, so the approval role required for each approval level can be determined based on the personnel information corresponding to the node in the corresponding organizational structure tree. Figure 2 For a business in project O, the corresponding preset approval chain includes three approval levels. The approval roles corresponding to each approval level are project manager, department manager and company manager respectively. This means that the business needs to be approved by the project manager of the corresponding node of project O, the department manager of the corresponding node of construction department K, and finally the company manager of the corresponding node of company G.

[0088] For example, Figure 4 As shown, step S300 includes:

[0089] Step S310, determining the number of approval levels and the approval role corresponding to each approval node in each approval level according to the target preset approval link.

[0090] After determining the target preset approval chain, it is also possible to determine how many levels of approval are required for the target task, how many approval nodes are required in each level of approval, and the approval role required for each approval node. Among them, the approval nodes in each level of approval can be parallel (that is, there are two or more parallel approval nodes in the same approval level) or serial (that is, each approval node in the same approval level is executed in sequence).

[0091] Step S320 , determining the target node corresponding to each approval level based on the number of approval levels and the organizational structure tree.

[0092] After determining the number of approval levels, since task approval is usually carried out level by level according to the organizational structure, and the project to which the target task belongs is also determined, the first target node of the target task in the organizational structure tree is known, and then combined with the number of approval levels, each target node of the target task in the organizational structure tree can be determined.

[0093] Step S330: acquiring the approval personnel corresponding to each approval node in the corresponding approval hierarchy from the personnel information corresponding to each target node.

[0094] Since each node of the organizational structure tree corresponds to the personnel information of the node, and the personnel information includes the role of each person, the approver of each approval node can be determined based on the personnel information of each target node. If there are two or more personnel who meet the role of the approver when matching the approver of the approval node, any one of them can be selected as the approver of the current approval node of the current target task, or selected by polling, or selected by setting a priority. If the approver of the corresponding role is not matched at a certain approval node, an alarm will be issued. After receiving the alarm information, the user can manually match the corresponding approver for the approval node; or pre-set rules for unmatched approvers, such as setting that if the approver cannot be matched at the current node, the corresponding approver will be matched from the parent node of the current target node by default.

[0095] Step S340: generating an approval path according to the approvers of each approval node in each approval level and each approval node in each approval level.

[0096] After determining the approvers for each approval node, the approval path for the current target task can be directly generated by arranging the approval nodes in order at each approval level in the preset approval chain.

[0097] In some embodiments, after obtaining the approving personnel that meet the requirements of each approval node in the corresponding approval hierarchy from the personnel information corresponding to each target node, it also includes: determining whether the approving personnel of each approval node corresponding to the current target business are repeated; if repeated, matching the approving personnel again for the approval nodes corresponding to the repeated approving personnel.

[0098] In some implementations, if the organizational structure tree is changed, the corresponding approval path is updated according to the changed organizational structure tree. It is understood that if the organizational structure tree is changed, the approval path involved in the organizational structure tree change is changed synchronously, and there is no need to manually change the corresponding approval path.

[0099] As shown in the organizational structure tree generation part, the organizational structure tree change may be a node level change or a personnel change.

[0100] If the personnel information corresponding to the node of the organizational structure tree has changed, such as the project manager of project Z has changed from a to b, the approval path involving the node in the approval path needs to be updated to form an updated approval path. This can avoid the situation where the corresponding approval path is not updated when the personnel resign or transfer, and the approval process will be unapproved when it reaches the approval of the change person, causing business delays. For example, for a task under project Z, its original approval path is project manager a in project Z. After project manager a approves it, the safety manager in the company's B node approves it. After the project manager of the project Z node changes from a to b, the approval path will be automatically updated according to the change in personnel information, and the updated approval path will be project manager b and safety manager.

[0101] If the node level of the organizational structure tree has changed, all approval paths are updated according to the changed organizational structure tree, including: determining the target business associated with the node level change; determining the target preset approval chain based on the number of node levels of the project to which the target business associated with the node level change belongs in the changed organizational structure tree, and the functional classification of the target business associated with the level change; determining the approval path corresponding to the target business associated with the level change based on the target preset approval chain, the changed organizational structure tree and personnel information.

[0102] It can be understood that when the node level of the organizational structure tree changes, the approval path related to the changed node can be determined based on the node of the changed organizational structure tree, and then these approval paths can be regenerated according to the generation process of the approval path. If some approval nodes in the new approval path have been reviewed and are consistent with the approval roles corresponding to the approval nodes of the original approval path, the approval node can be marked. When the approval is subsequently carried out according to the updated approval path, the marked approval node can be directly skipped. For example, for a business of Project Z, the previous approval path is Project Manager A of the Project Z node and Marketing Manager B of the Company B node. If Project Z is changed to the node under Operation Department J, the target preset approval link is re-determined according to the functional type of the business at the node level tree level after the change, and then the approval path can be re-generated for the business according to the above-mentioned approval path generation method.

[0103] In some implementations, when adjusting the approval path or the organizational structure tree, the adjustment can be made directly by dragging in the interface to achieve visualization and convenience of the operation.

[0104] In this application, by combining projects with companies and departments in the organizational structure tree, it is more in line with the actual needs of the construction industry, so that projects can be mounted under a certain department or company according to actual conditions, avoiding the situation of project information islands in the prior art, realizing dynamic associations between companies, departments, and projects, and improving the consistency and integrity of organizational structure management data. In addition, when generating approval paths, this application pre-sets the corresponding target preset approval links based on the functional classification of the business at the node level level. Therefore, after determining the number of node levels in the organizational structure tree where the project where the target business is located and the functional classification of the target business, the corresponding preset approval link can be determined. According to the approval role of each approval node in the preset approval link, combined with the organizational structure tree and the personnel information corresponding to each node of the organizational structure tree, the approval path of the target task can be directly generated, thereby achieving the efficiency of approval path generation, and batch generation of approval paths can be achieved. In addition, for the construction industry, complex scenarios involving multi-level, multi-role, and multi-node approvals are often involved. Through the path generation method of this application, the target preset approval link can be set according to the functional classification of the target business and the number of node levels in the organizational structure tree where the target business is located. It can set several parallel approval roles in the same approval level, that is, it can achieve cross-departmental, cross-project, and cross-company collaborative approval. Furthermore, when the organizational structure tree changes, this application can also achieve synchronous update and adjustment of the approval path, thereby ensuring the synchronization of the organizational structure tree and the approval path.

[0105] Figure 5A schematic diagram of the structure of the approval path device of the embodiment of the present application is shown. Exemplarily, the approval path device includes:

[0106] The first determination module 100 is used to determine the number of node levels of the project to which the target business belongs in the organizational structure tree and the functional classification of the target business.

[0107] The second determination module 200 is used to determine a target preset approval link based on the number of node levels and functional classification.

[0108] The third determination module 300 is used to determine the approval path corresponding to the target business according to the target preset approval link, the organizational structure tree and the personnel information.

[0109] It can be understood that the device of this embodiment corresponds to the approval path generation method of the above embodiment, and the options in the above embodiment are also applicable to this embodiment, so they will not be described repeatedly here.

[0110] The present application also provides a terminal device. Exemplarily, the terminal device includes a processor and a memory, wherein the memory stores a computer program, and the processor runs the computer program to enable the terminal device to execute the functions of the various modules in the above-mentioned approval path generation method or the above-mentioned approval path device.

[0111] Among them, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including a central processing unit (CPU), a graphics processing unit (GPU) and a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or at least one of other programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., which can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application.

[0112] The memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The memory is used to store a computer program, and the processor may execute the computer program accordingly after receiving an execution instruction.

[0113] The present application also provides a computer-readable storage medium for storing the computer program used in the above-mentioned terminal device. For example, the computer-readable storage medium may include, but is not limited to, various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0114] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, a program segment or a part of a code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0115] In addition, the functional modules or units in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0116] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application.

[0117] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A method for generating an approval path, characterized in that: include: Determine the number of node levels in the organizational structure tree of the project to which the target business belongs and the functional classification of the target business; Determine a target preset approval link based on the number of node levels and the functional classification; The approval path corresponding to the target business is determined according to the target preset approval link, the organizational structure tree and personnel information.

2. The approval path generation method according to claim 1, characterized in that: The determining the approval path corresponding to the target business according to the target preset approval link, the organizational structure tree and the personnel information includes: Determine the number of approval levels and the approval role corresponding to each approval node in each approval level according to the target preset approval link; Determine a target node corresponding to each approval level based on the number of approval levels and the organizational structure tree; Acquire the approval personnel corresponding to each approval node in the approval hierarchy from the personnel information corresponding to each target node; The approval path is generated according to the approval personnel of each approval node in each approval level and each approval node in each approval level.

3. The approval path generation method according to claim 2, characterized in that: After acquiring the approval personnel corresponding to each approval node in the approval hierarchy from the personnel information corresponding to each target node, the method further includes: If the current target node cannot match the approver of the approval role required by the approval node, an alarm message is issued to enable the user to manually match the corresponding approver; or According to the preset matching rule of no approving personnel, the approval node that has not matched the approving personnel is re-matched with the approving personnel; wherein the preset matching rule of no approving personnel is to match the approving personnel who meet the approval role required by the current approval node from the superior target node of the current target node that has not matched the approving personnel.

4. The approval path generation method according to claim 1, characterized in that: The generation of the organizational structure tree includes: Generate company nodes based on company information; Based on the department information, determine the company to which each department belongs, and mount each department under the corresponding company node to generate a department node; Based on the project information, the department or company to which the project belongs is determined, and each of the projects is mounted under the corresponding department node or company node, and a project node is generated.

5. The approval path generation method according to claim 2, characterized in that: Also includes: If the organizational structure tree is changed, the corresponding approval path is updated according to the changed organizational structure tree.

6. The approval path generation method according to claim 5, characterized in that: Changes to the organizational structure tree include personnel changes; Then, all the approval paths are updated according to the changed organizational structure tree, including: The approving personnel corresponding to the approval role associated with the personnel change in the approval path is changed to form the updated approval path.

7. The approval path generation method according to claim 5, characterized in that: The change of the organizational structure tree also includes a change of node level; Then, all the approval paths are updated according to the changed organizational structure tree, including: Determining the target business associated with the node level change; Determine the target preset approval link based on the number of node levels of the project to which the target business associated with the node level change belongs in the organizational structure tree after the change, and the functional classification of the target business associated with the level change; The approval path corresponding to the target business associated with the hierarchical change is determined according to the target preset approval link, the changed organizational structure tree and personnel information.

8. An approval path generation device, characterized in that: include: The first determination module is used to determine the number of node levels of the project to which the target business belongs in the organizational structure tree and the functional classification of the target business; A second determination module, configured to determine a target preset approval link based on the number of node levels and the functional classification; The third determination module is used to determine the approval path corresponding to the target business according to the target preset approval link, the organizational structure tree and personnel information.

9. A terminal device, characterized in that: The terminal device includes a processor and a memory, the memory stores a computer program, and the processor is used to execute the computer program to implement the approval path generation method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The device stores a computer program, which, when executed on a processor, implements the approval path generation method according to any one of claims 1 to 7.

Images