Multi-system service approval process configuration method, device, equipment and medium

Abstract

The invention relates to a multi-system service approval process configuration method, device and equipment and a medium, and is applied to the technical field of process configuration. The method comprises the following steps: obtaining an approval node and approval logic; creating a standard process configuration file based on the approval node and the approval logic, the standard process configuration file including an approval process, the approval process including the approval node, an approval node code, a role name and a role code; creating a standard role configuration table, wherein the standard role configuration table comprises role names and role codes; establishing a mapping relation between the standard process configuration file and the standard role configuration table based on the role code; performing batch configuration of the approvers in the approval process based on the mapping relation; generating an ID number of the approval process; and issuing the approval process and the corresponding ID number to an application system. The method has the effects of improving the configuration efficiency of the approval process and reducing the operation and maintenance workload.

Description

Technical Field

[0001] The present application relates to the technical field of process configuration, and in particular to a method, device, equipment and medium for configuring a multi-system business approval process. Background Art

[0002] Currently, more and more large enterprises use multiple system software to implement daily management and operations. Using multiple systems can better meet the needs of the company's continuous development and improve the company's operating efficiency. The multi-system working mode can also better help the company achieve refined and automated management, thereby improving the company's management level.

[0003] Process approval is an essential part of large enterprises. For processes that are numerous and complex, especially those that cross organizational levels, more than three organizational levels are often involved. The departments and positions at different organizational levels are not the same, and the differences are even huge. As a result, each node of each approval process in each system needs to have a separate approver. At the same time, when personnel change, the adjustment of the corresponding process approvers is also very cumbersome, which greatly increases the workload of operation and maintenance and increases the cost of process maintenance. Summary of the invention

[0004] In order to improve the configuration efficiency of the approval process and reduce the operation and maintenance workload, the present application provides a multi-system business approval process configuration method, device, equipment and medium.

[0005] In the first aspect, the present application provides a multi-system business approval process configuration method, which adopts the following technical solution: A multi-system business approval process configuration method, applied to the process management middle platform, includes: Get the approval node and approval logic; Creating a standard process configuration file based on the approval node and the approval logic, wherein the standard process configuration file includes an approval process, and the approval process includes an approval node, an approval node code, a role name, and a role code; Creating a standard role configuration table, wherein the standard role configuration table includes a role name and a role code; Establishing a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code; Perform batch configuration of approvers in the approval process based on the mapping relationship; Generate an ID number for the approval process; The approval process and the corresponding ID number are published to the application system.

[0006] By adopting the above technical solution, a standard role configuration table is created, and the role names in the standard role configuration table are consistent with the role names corresponding to the approval nodes in all standard process configuration files, so that a mapping relationship is established between the two. After the approvers are configured in the standard role configuration table, they are pushed to all processes synchronously through the mapping relationship, and batch configuration of approvers corresponding to approval nodes in multiple approval processes can be completed, which improves the configuration efficiency of the approval process and reduces the operation and maintenance workload.

[0007] Optionally, the creating a standard process configuration file based on the approval node and the approval logic includes: The approval nodes in the standard process configuration file are encoded based on a first preset rule to obtain a plurality of approval node codes, wherein the approval node codes correspond to the approval nodes one by one.

[0008] Optionally, the step of creating a standard role configuration table includes: Acquire management organization hierarchy information, wherein the management organization hierarchy information includes multiple management organizations, management hierarchies corresponding to the management organizations, and upper-lower level correspondences between the multiple management organizations; Based on the management organization hierarchy information and the second preset rule, a plurality of administrator configuration tables are created, and an administrator table code is generated, wherein the administrator configuration table includes administrator information, and the administrator information includes administrator information of the current level and administrator information of the lower level, and the administrator information of the lower level is configured by the administrator of the current level; Creating a standard role configuration table based on a third preset rule, and generating a role table code and a role code, wherein the standard role configuration table corresponds to the administrator configuration table in a one-to-one manner; Acquire approver information based on the administrator information; Configuring the standard role configuration table based on the approver information; Based on the administrator configuration table, a plurality of the standard role configuration tables are linked through role table coding.

[0009] By adopting the above technical solution, an administrator configuration table is created for each management organization, which can more clearly determine the responsibilities of administrators at all levels. In addition, since the management organization corresponds one-to-one with the standard role configuration table and the administrator configuration table, when the management organization changes, only the corresponding configuration table needs to be modified, which improves the flexibility and scalability of the configuration.

[0010] Optionally, the establishing a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code includes: Determining the correspondence between the role code and the approval node code based on the standard process configuration file; A mapping relationship between the approver and the approval node is determined based on the corresponding relationship.

[0011] By adopting the above technical solution, the standard role configuration table and the standard process configuration file are set with the same role name, and the mapping relationship between the standard process configuration file and the standard role configuration table can be more conveniently established according to the role code corresponding to the role name.

[0012] In the second aspect, the present application provides a multi-system business approval process configuration method, which adopts the following technical solution: A multi-system business approval process configuration method, applied to an application system, includes: Receive the approval process and the corresponding ID number, wherein the approval process includes an approval node, an approval node code, a role name, and a role code; Get the newly added approval nodes and approval logic; Establishing a process association between the newly added approval node and the approval node based on the newly added approval logic; The newly added approval node is inserted into the approval process based on the process association.

[0013] By adopting the above technical solution, users can quickly and conveniently initiate the approval process by calling the ID number through the application system. When the user needs to add a new approval node, a process association is established between the new approval node code and the approval node code, and the ID number of the approval process is called. During the process flow, the new approval node can be inserted into the standard approval process according to the process association, so that the approval node can be flexibly added without affecting the operation of the main process.

[0014] Optionally, establishing a process association between the newly added approval node and the approval node based on the newly added approval logic includes: Creating a new process configuration file based on the new approval node and the new approval logic, wherein the new process configuration file includes a new approval node, a new approval node code, a new role name, and a new role code; Create a new role configuration table, the new role configuration table includes a new role name and a new role code; Establishing a new mapping relationship between the new process configuration file and the new role configuration table based on the new role code; Perform batch configuration of approvers based on the newly added mapping relationship; The newly added approval node code is associated with the approval node code based on the newly added approval logic.

[0015] By adopting the above technical solution, it is more convenient to configure the approver for the newly added approval node by creating a new role configuration table, and by associating the newly added approval node code with the approval node code, it is more convenient to insert the new node into the approval process.

[0016] In a third aspect, the present application provides a multi-system business approval process configuration device, which adopts the following technical solution: A multi-system business approval process configuration device, applied to a process management middle platform, includes: The first acquisition module is used to obtain the approval node and approval logic; A first creation module is used to create a standard process configuration file based on the approval node and the approval logic, wherein the standard process configuration file includes an approval process, and the approval process includes an approval node, an approval node code, a role name, and a role code; A second creation module is used to create a standard role configuration table, wherein the standard role configuration table includes a role name and a role code; A mapping establishment module, used to establish a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code; A batch configuration module, used for batch configuration of approvers in the approval process based on the mapping relationship; A number generation module, used to generate an ID number for the approval process; The process publishing module is used to publish the approval process and the corresponding ID number to the application system.

[0017] By adopting the above technical solution, a standard role configuration table is created, and the role names in the standard role configuration table are consistent with the role names corresponding to the approval nodes in all standard process configuration files, so that a mapping relationship is established between the two. After the approvers are configured in the standard role configuration table, they are pushed to all processes synchronously through the mapping relationship, and batch configuration of approvers corresponding to approval nodes in multiple approval processes can be completed, which improves the configuration efficiency of the approval process and reduces the operation and maintenance workload.

[0018] In a fourth aspect, the present application provides a multi-system business approval process configuration device, which adopts the following technical solution: A multi-system business approval process configuration device, applied to an application system, comprising: A process receiving module, used to receive the approval process and the corresponding ID number, wherein the approval process includes an approval node, an approval node code, a role name and a role code; The second acquisition module is used to acquire the newly added approval node and the newly added approval logic; An association establishing module, used to establish a process association between the newly added approval node and the approval node based on the newly added approval logic; A node insertion module is used to insert the newly added approval node into the approval process based on the process association.

[0019] By adopting the above technical solution, users can quickly and conveniently initiate the approval process by calling the ID number through the application system. When the user needs to add a new approval node, a process association is established between the new approval node code and the approval node code, and the ID number of the approval process is called. During the process flow, the new approval node can be inserted into the standard approval process according to the process association, so that the approval node can be flexibly added without affecting the operation of the main process.

[0020] In a fifth aspect, the present application provides an electronic device, which adopts the following technical solution: An electronic device comprises a processor, wherein the processor is coupled to a memory; The memory stores a computer program that can be loaded by the processor and executes the multi-system business approval process configuration method described in any one of the first aspect or the second aspect.

[0021] In a sixth aspect, the present application provides a computer-readable storage medium, which adopts the following technical solution: A computer-readable storage medium stores a computer program that can be loaded by a processor and execute the multi-system business approval process configuration method described in any one of the first aspect or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a flowchart of a multi-system business approval process configuration method applied to a process management middle platform in an embodiment of the present application.

[0023] Figure 2 It is a flowchart of a multi-system business approval process configuration method applied to an application system in an embodiment of the present application.

[0024] Figure 3 It is a structural block diagram of a multi-system business approval process configuration device applied to a process management middle station in an embodiment of the present application.

[0025] Figure 4 It is a structural block diagram of a multi-system business approval process configuration device applied to an application system in an embodiment of the present application.

[0026] Figure 5 It is a structural block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0027] The present application is further described in detail below in conjunction with the accompanying drawings.

[0028] The embodiment of the present application provides a multi-system business approval process configuration method, which can be executed by an electronic device, which can be a server or a terminal device, wherein the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services. The terminal device can be a smart phone, a tablet computer, a desktop computer, etc., but is not limited thereto.

[0029] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0030] In addition, the term "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article, unless otherwise specified, generally indicates that the associated objects before and after are in an "or" relationship.

[0031] like Figure 1 As shown, a multi-system business approval process configuration method is applied to the process management middle platform. The main process of the method is described as follows (steps S101 to S107): Step S101: Acquire approval nodes and approval logic.

[0032] Obtain the approval nodes and approval logic of the process in each organizational level from the business management personnel or project management personnel. The approval logic is the process relationship between the approval nodes. For example, when approval node 1 is approved, it jumps to approval node 2; when approval node 1 is not approved, it jumps to approval node 3.

[0033] Step S102: Create a standard process configuration file based on the approval node and approval logic.

[0034] The standard process configuration file includes an approval process, and the approval process includes an approval node, an approval node code, a role name, and a role code.

[0035] The approval nodes are organized into multiple approval processes according to the approval logic, and multiple approval processes are jointly determined as standard process configuration files. A standard process database is created, and the standard process configuration files are stored in the standard process database. Each approval node corresponds to a role name, and each role name corresponds to a role code. It is worth noting that the standard process configuration files are encrypted and tamper-proof, and the approval nodes contained therein cannot be deleted, and the role names cannot be modified.

[0036] Specifically, creating a standard process configuration file based on approval nodes and approval logic includes: encoding the approval nodes in the standard process configuration file based on a first preset rule to obtain multiple approval node codes, and the approval node codes correspond to the approval nodes one by one.

[0037] The first preset rule is a rule for approval node coding. Each approval node is coded according to the first preset rule to obtain an approval node code corresponding to each approval node.

[0038] Step S103: Create a standard role configuration table.

[0039] The standard role configuration table includes role name and role code.

[0040] Specifically, creating a standard role configuration table includes: obtaining management organization hierarchy information, the management organization hierarchy information includes multiple management organizations, management hierarchies corresponding to the management organizations, and the superior-subordinate correspondence between the multiple management organizations; creating multiple administrator configuration tables based on the management organization hierarchy information and the second preset rule, and generating administrator table codes, the administrator configuration table includes administrator information, the administrator information includes administrator information at this level and administrator information at lower levels, and the administrator information at lower levels is configured by the administrator at this level; creating a standard role configuration table based on the third preset rule, and generating role table codes and role codes, the standard role configuration table corresponds to the administrator configuration table one by one; obtaining approver information based on the administrator information; configuring the standard role configuration table based on the approver information; and linking multiple standard role configuration tables through role table codes based on the administrator configuration table.

[0041] In this embodiment, management organization hierarchy information is obtained from the management personnel or the database. The management organization hierarchy information includes the name of the management organization (for example: Company A, Subsidiary B), the management level corresponding to the management organization (for example: second level, third level), the name of the subordinate management organization and the administrator information at this level. The second preset rule is obtained from the database. The second preset rule includes the creation rule of the administrator configuration table and the generation rule of the administrator table code. The administrator table code is the code corresponding to the administrator configuration table. According to the second preset rule, an administrator configuration table is created for each management organization in the management organization hierarchy information, and the corresponding administrator table code is generated. After the administrator configuration table is created, the subordinate administrator information is obtained from the administrator at this level and configured into the administrator configuration table at this level. An administrator configuration database is created, all configured administrator configuration tables are stored in the administrator configuration database, and each administrator configuration table in the administrator configuration database is mounted according to the superior-subordinate relationship of the management organization. The mounting method is to mount the administrator table code.

[0042] A third preset rule is obtained from the database. The third preset rule includes a generation rule for a standard role configuration table and a generation rule for a role table code. According to the third preset rule, a standard role configuration table is created for each management organization and a corresponding role table code is generated. The standard role configuration table includes a role name, a role code and approver information. The approver information includes the approver's name, the approver's department name and the approver's job title. It is worth noting that the role name and role code in the standard role configuration table are the same as those in the standard process configuration file. The standard role configuration table and the standard process configuration file are associated with each other through the role code. The rules for encoding each role name are not specifically limited here. The role name is not a job name, but an independent abstract entity, such as: A1, A2, B1, etc. Each management organization corresponds to an administrator configuration table and a standard role configuration table, that is, the standard role configuration table and the administrator configuration table also correspond one to one.

[0043] According to the administrator information, the approver information is obtained from the administrator at the same level, that is, the correspondence between the role name and the approver, and the approver information is configured into the standard role configuration table, a role configuration database is created, and the standard role configuration table with the configured approver information is stored in the role configuration database. Multiple standard role configuration tables in the role configuration database are mounted according to the superior-subordinate relationship indicated by the corresponding administrator configuration table. The mounting method is to mount the role table code.

[0044] Step S104: Establish a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code.

[0045] The mapping relationship between the standard process configuration file and the standard role configuration table is the mapping relationship between the role name in the standard process configuration file and the approver information in the standard role configuration table.

[0046] Specifically, a mapping relationship between a standard process configuration file and a standard role configuration table is established based on the role code, including: determining a corresponding relationship between a role code and an approval node code based on the standard process configuration file; and determining a mapping relationship between an approver and an approval node based on the corresponding relationship.

[0047] In this embodiment, the correspondence between the role code and the approval node code is searched from the standard process configuration file, and the mapping relationship between the approver and the approval node is determined according to the correspondence and the same role code in the standard process configuration file and the standard role configuration table.

[0048] Step S105: batch configuration of approvers in the approval process based on the mapping relationship.

[0049] According to the mapping relationship, the approver information is batch configured to each approval node in the standard process configuration file, thereby completing the batch configuration of approvers in each approval process.

[0050] When personnel changes occur, you only need to modify the approver information corresponding to the role name in the standard role configuration table, and then re-configure the batch of approvers in the approval process, which reduces the operation and maintenance workload and thus reduces the process maintenance cost.

[0051] Step S106: Generate an ID number for the approval process.

[0052] According to the preset numbering rules (pre-set, no specific restrictions are made here), a separate ID number is generated for each approval process that has been configured with the approver information.

[0053] Step S107: Publish the approval process and the corresponding ID number to the application system.

[0054] The approval process and the corresponding ID number are published to all application systems. Users can initiate the approval process by calling the ID number in the application system.

[0055] like Figure 2 As shown, a multi-system business approval process configuration method is applied to the application system. The main process of the method is described as follows (steps S201 to S204): Step S201, receiving the approval process and the corresponding ID number.

[0056] The approval process includes approval nodes, approval node codes, role names, and role codes.

[0057] The application system receives the standard approval process and the corresponding ID number from the process management center, so that it can initiate the approval process by calling the ID number.

[0058] Step S202: Acquire a newly added approval node and a newly added approval logic.

[0059] The approval nodes of the approval process at the process management center cannot be increased. When an approval node needs to be added, the new approval node and the new approval logic are obtained from the user. The new approval logic includes the logical order between the new approval nodes. For example, the new approval node 4 needs to be inserted between approval node 5 and approval node 6.

[0060] Step S203: Establish a process association between the newly added approval node and the approval node based on the newly added approval logic.

[0061] Specifically, a process association between a newly added approval node and an approval node is established based on the newly added approval logic, including: creating a new process configuration file based on the newly added approval node and the newly added approval logic, the new process configuration file includes the newly added approval node, the newly added approval node code, the new role name and the new role code; creating a new role configuration table, the new role configuration table includes the new role name and the new role code; establishing a new mapping relationship between the new process configuration file and the new role configuration table based on the new role code; batch configuring approvers based on the new mapping relationship; and associating the new approval node code with the approval node code based on the new approval logic.

[0062] In this embodiment, each newly added approval node is encoded according to the first preset rule to obtain a newly added approval node code corresponding to each newly added approval node, each newly added approval node corresponds to a newly added role name, and each newly added role name corresponds to a newly added role code (the encoding rules are not specifically limited here), and the newly added approval node, the newly added approval node code, the newly added role name, the newly added role code and the newly added approval logic are jointly formed into a newly added process configuration file, and a newly added configuration file database is established to store the newly added process configuration file.

[0063] According to the third preset rule, a new role configuration table is created and the corresponding new role table code is generated. The new role configuration table includes the correspondence between the role name and the approver information. The approver information is obtained from the user and configured into the new role configuration table, thereby completing the creation of the new role configuration table and establishing a new role configuration database to store the configured new role configuration table.

[0064] A new mapping relationship is established between the new process configuration file and the new role configuration table according to the same new role code. According to the new mapping relationship, the approver information in the new role configuration table can be batch configured into the new process configuration file to complete the batch configuration of the approvers corresponding to the new approval nodes. The association between the new approval node and the approval node is found from the new approval logic, and the new approval node code is associated with the approval node code through the association.

[0065] It is worth noting that each application system can create multiple new process configuration files and multiple new role configuration tables according to needs.

[0066] Step S204: inserting a new approval node into the approval process based on process association.

[0067] The approval nodes of the approval process at the process management center cannot be increased. When the user needs to add a new approval node, a process association is established between the new approval node code and the approval node code, and the ID number of the approval process is called. During the process flow, the new approval node can be inserted into the corresponding position of the standard approval process according to the process association. In this way, approval nodes can be flexibly added without affecting the operation of the main process.

[0068] Figure 3 This is a structural block diagram of a multi-system business approval process configuration device 300 applied to a process management middle station in an embodiment of the present application.

[0069] like Figure 3 As shown, the multi-system business approval process configuration device 300 applied to the process management middle station mainly includes: The first acquisition module 301 is used to acquire the approval node and approval logic; The first creation module 302 is used to create a standard process configuration file based on the approval node and the approval logic. The standard process configuration file includes the approval process. The approval process includes the approval node, the approval node code, the role name and the role code; The second creation module 303 is used to create a standard role configuration table, which includes a role name and a role code; A mapping establishment module 304 is used to establish a mapping relationship between a standard process configuration file and a standard role configuration table based on the role code; Batch configuration module 305, used for batch configuration of approvers in the approval process based on the mapping relationship; The number generation module 306 is used to generate an ID number for the approval process; The process publishing module 307 is used to publish the approval process and the corresponding ID number to the application system.

[0070] As an optional implementation of this embodiment, the first creation module 302 is also specifically used to create a standard process configuration file based on the approval node and the approval logic, including: encoding the approval nodes in the standard process configuration file based on the first preset rule to obtain multiple approval node codes, and the approval node codes correspond to the approval nodes one by one.

[0071] As an optional implementation of this embodiment, the second creation module 303 is also specifically used to create a standard role configuration table, including: obtaining management organization hierarchy information, the management organization hierarchy information includes multiple management organizations, management hierarchies corresponding to the management organizations, and the upper and lower correspondences between multiple management organizations; creating multiple administrator configuration tables based on the management organization hierarchy information and the second preset rule, and generating administrator table codes, the administrator configuration table includes administrator information, the administrator information includes administrator information at this level and lower-level administrator information, and the lower-level administrator information is configured by the administrator at this level; creating a standard role configuration table based on the third preset rule, and generating role table codes and role codes, the standard role configuration table corresponds to the administrator configuration table one by one; obtaining approver information based on the administrator information; configuring the standard role configuration table based on the approver information; and linking multiple standard role configuration tables through role table codes based on the administrator configuration table.

[0072] As an optional implementation of this embodiment, the mapping establishment module 304 is also specifically used to establish a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code, including: determining the correspondence between the role code and the approval node code based on the standard process configuration file; determining the mapping relationship between the approver and the approval node based on the correspondence.

[0073] Figure 4 This is a structural block diagram of a multi-system business approval process configuration device 400 applied to an application system according to an embodiment of the present application.

[0074] like Figure 4 As shown, the multi-system business approval process configuration device 400 applied to the application system mainly includes: The process receiving module 401 is used to receive the approval process and the corresponding ID number. The approval process includes the approval node, the approval node code, the role name and the role code; The second acquisition module 402 is used to acquire the newly added approval node and the newly added approval logic; The association establishment module 403 is used to establish a process association between the newly added approval node and the approval node based on the newly added approval logic; The node insertion module 404 is used to insert a new approval node into the approval process based on process association.

[0075] As an optional implementation of this embodiment, the association establishment module 403 is also specifically used to establish a process association between a newly added approval node and an approval node based on the newly added approval logic, including: creating a new process configuration file based on the newly added approval node and the newly added approval logic, the new process configuration file including the newly added approval node, the newly added approval node code, the newly added role name and the newly added role code; creating a new role configuration table, the new role configuration table including the new role name and the new role code; establishing a new mapping relationship between the new process configuration file and the new role configuration table based on the new role code; batch configuring approvers based on the new mapping relationship; and associating the new approval node code with the approval node code based on the new approval logic.

[0076] In one example, the module in any of the above devices can be one or more integrated circuits configured to implement the above methods, such as: one or more application specific integrated circuits (ASICs), or, one or more digital signal processors (DSPs), or, one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms.

[0077] For another example, when the modules in the device can be implemented in the form of a processing element scheduling program, the processing element can be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call a program. For another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0078] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and modules can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0079] Figure 5 A structural block diagram of an electronic device 500 provided in an embodiment of the present application.

[0080] like Figure 5 As shown, the electronic device 500 includes a processor 501 and a memory 502 , and may further include an information input / information output (I / O) interface 503 , one or more of communication components 504 , and a communication bus 505 .

[0081] The processor 501 is used to control the overall operation of the electronic device 500 to complete all or part of the steps of the multi-system business approval process configuration method described above; the memory 502 is used to store various types of data to support the operation of the electronic device 500, and these data may include, for example, instructions for any application or method used to operate on the electronic device 500, and data related to the application. The memory 502 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0082] The I / O interface 503 provides an interface between the processor 501 and other interface modules, and the above-mentioned other interface modules can be keyboards, mice, buttons, etc. These buttons can be virtual buttons or physical buttons. The communication component 504 is used for wired or wireless communication between the electronic device 500 and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or a combination of one or more of them, so the corresponding communication component 504 can include: Wi-Fi components, Bluetooth components, NFC components.

[0083] The electronic device 500 can be implemented by one or more application specific integrated circuits (ASIC), digital signal processors (DSP), digital signal processing devices (DSPD), programmable logic devices (PLD), field programmable gate arrays (FPGA), controllers, microcontrollers, microprocessors or other electronic components to execute the multi-system business approval process configuration method given in the above embodiment.

[0084] The communication bus 505 may include a path to transmit information between the above components. The communication bus 505 may be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, etc. The communication bus 505 may be divided into an address bus, a data bus, a control bus, etc.

[0085] The electronic device 500 may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc., and may also be servers, etc.

[0086] The present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the above-mentioned multi-system business approval process configuration method are implemented.

[0087] The computer-readable storage medium may include: 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, and other media that can store program codes.

[0088] The terms "comprises," "comprising," or any other variations thereof are intended to cover non-exclusive inclusion such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not expressly listed, or also includes elements inherent to such process, method, article, or apparatus.

[0089] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of application involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the aforementioned application concept. For example, the above features are replaced with (but not limited to) technical features with similar functions applied in the present application.

Claims

1. A multi-system business approval process configuration method, characterized in that: Applied to process management platform, including: Get the approval node and approval logic; Creating a standard process configuration file based on the approval node and the approval logic, wherein the standard process configuration file includes an approval process, and the approval process includes an approval node, an approval node code, a role name, and a role code; Creating a standard role configuration table, wherein the standard role configuration table includes a role name and a role code; Establishing a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code; Perform batch configuration of approvers in the approval process based on the mapping relationship; Generate an ID number for the approval process; The approval process and the corresponding ID number are published to the application system.

2. The method according to claim 1, characterized in that The creating a standard process configuration file based on the approval node and the approval logic includes: The approval nodes in the standard process configuration file are encoded based on a first preset rule to obtain a plurality of approval node codes, wherein the approval node codes correspond to the approval nodes one by one.

3. The method according to claim 1, characterized in that The step of creating a standard role configuration table includes: Acquire management organization hierarchy information, wherein the management organization hierarchy information includes multiple management organizations, management hierarchies corresponding to the management organizations, and upper-lower level correspondences between the multiple management organizations; Based on the management organization hierarchy information and the second preset rule, a plurality of administrator configuration tables are created, and an administrator table code is generated, wherein the administrator configuration table includes administrator information, and the administrator information includes administrator information of the current level and administrator information of the lower level, and the administrator information of the lower level is configured by the administrator of the current level; Creating a standard role configuration table based on a third preset rule, and generating a role table code and a role code, wherein the standard role configuration table corresponds to the administrator configuration table in a one-to-one manner; Acquire approver information based on the administrator information; Configuring the standard role configuration table based on the approver information; Based on the administrator configuration table, a plurality of the standard role configuration tables are linked through role table coding.

4. The method according to claim 1, characterized in that: The establishing of a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code includes: Determining the correspondence between the role code and the approval node code based on the standard process configuration file; A mapping relationship between the approver and the approval node is determined based on the corresponding relationship.

5. A multi-system business approval process configuration method, characterized in that: Applied to application systems, including: Receive the approval process and the corresponding ID number, wherein the approval process includes an approval node, an approval node code, a role name, and a role code; Get the newly added approval nodes and approval logic; Establishing a process association between the newly added approval node and the approval node based on the newly added approval logic; The newly added approval node is inserted into the approval process based on the process association.

6. The method according to claim 5, characterized in that The establishing of a process association between the newly added approval node and the approval node based on the newly added approval logic includes: Creating a new process configuration file based on the new approval node and the new approval logic, wherein the new process configuration file includes a new approval node, a new approval node code, a new role name, and a new role code; Create a new role configuration table, the new role configuration table includes a new role name and a new role code; Establishing a new mapping relationship between the new process configuration file and the new role configuration table based on the new role code; Perform batch configuration of approvers based on the newly added mapping relationship; The newly added approval node code is associated with the approval node code based on the newly added approval logic.

7. A multi-system business approval process configuration device, characterized in that: Applied to process management platform, including: The first acquisition module is used to obtain the approval node and approval logic; A first creation module is used to create a standard process configuration file based on the approval node and the approval logic, wherein the standard process configuration file includes an approval process, and the approval process includes an approval node, an approval node code, a role name, and a role code; A second creation module is used to create a standard role configuration table, wherein the standard role configuration table includes a role name and a role code; A mapping establishment module, used to establish a mapping relationship between the standard process configuration file and the standard role configuration table based on the role code; A batch configuration module, used for batch configuration of approvers in the approval process based on the mapping relationship; A number generation module, used to generate an ID number for the approval process; The process publishing module is used to publish the approval process and the corresponding ID number to the application system.

8. A multi-system business approval process configuration device, characterized in that: Applied to application systems, including: A process receiving module, used to receive the approval process and the corresponding ID number, wherein the approval process includes an approval node, an approval node code, a role name and a role code; The second acquisition module is used to acquire the newly added approval node and the newly added approval logic; An association establishing module, used to establish a process association between the newly added approval node and the approval node based on the newly added approval logic; A node insertion module is used to insert the newly added approval node into the approval process based on the process association.

9. An electronic device, characterized in that: comprising a processor coupled to a memory; The processor is configured to execute a computer program stored in the memory, so that the electronic device executes the method according to any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: The method comprises a computer program or an instruction, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 6.

Images