Approval flow template configuration method, approval flow center, system and electronic device

Abstract

The application provides an approval flow template configuration method, an approval flow center, a system and an electronic device, and belongs to the computer field. The approval flow template configuration method comprises the following steps: in response to a configuration operation of a user for each element in an approval process, completing the configuration of the element, obtaining configuration data of the element, and the configuration operation is used for configuring an element type of the element and a position of the element in the approval process, wherein the element type in the approval process at least comprises an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event and an approval condition; and obtaining a target approval flow template according to the configuration data of each element in the approval process. According to the scheme, the approval flow template does not need to be configured from the perspective of business demand analysis, the configuration of the approval flow template is completed through the combination of simple elements, the process of the approval flow configuration is simplified, and the difficulty of user operation and understanding is reduced.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computers, in particular to an approval flow template configuration method, an approval flow center, a system and an electronic device. BACKGROUND

[0002] At present, there are many approval flow related systems on the market. These systems basically think and construct the approval flow from the role, approval relationship, report relationship, approval level, approval scheme, etc. Or, according to the different needs, the approval flow is customized and developed. The typical solution is to design and implement the entire approval flow from the business requirement analysis, which leads to the complexity of the configurable implementation and operation of the approval flow. SUMMARY

[0003] The present application provides an approval flow template configuration method, an approval flow center, a system and an electronic device to solve the problem of the complexity of the configurable implementation and operation of the approval flow in the prior art.

[0004] In a first aspect, the present application provides an approval flow template configuration method, comprising: in response to a user's configuration operation on each element in an approval process, completing the configuration of the element to obtain configuration data of the element, the configuration operation being used to configure an element type of the element and a position of the element in the approval process, wherein the element type in the approval process at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event and an approval condition; and obtaining a target approval flow template according to the configuration data of each element in the approval process.

[0005] In the embodiment of the present application, the element type of each element in the approval process and the position of the element in the approval process are configured, and then the target approval flow template is obtained based on the configuration data of each element in the approval process. The approval flow template is obtained by combining the four element types of the approval node, the approver, the event and the approval condition, without configuring the approval flow template from the perspective of business requirement analysis. Therefore, the configuration of the approval flow template is completed by combining simple elements, the process of the approval flow configuration is simplified, and the difficulty of user operation and understanding is reduced.

[0006] In combination with the technical solution of the above first aspect, in some possible implementation manners, after the target approval flow template is obtained, the method further comprises: determining that there is no old version of the approval flow template corresponding to the target approval flow template of the approval matter; generating a target approval component corresponding to the target approval flow template and generating version information of the target approval flow template, and associating the version information with the target approval component, wherein the target approval component is used to generate an approval application based on the target approval flow template when the target approval component is triggered.

[0007] In the embodiments of the present application, when there is no old version of the approval flow template corresponding to the target approval matter in the target approval flow template, the target approval component corresponding to the target approval flow template and version information are generated, and the target approval component and the version information are associated, so that when the target approval component is triggered, an approval application based on the target approval flow template is generated, so that the user can intuitively and conveniently submit the approval application.

[0008] In combination with the technical solutions provided in the above first aspect, in some possible implementation manners, before the target approval component corresponding to the target approval flow template is generated, the method further includes: in response to an operation of the user configuring an application form based on a preset application form component library, generating a target application form, the target application form being used to record data related to the approval application; and establishing an association relationship between the target application form and the target approval flow template, wherein when the target approval component is triggered, the target application form is displayed, and the approval application is generated based on the target application form filled by the user.

[0009] In the embodiments of the present application, by establishing the association relationship between the target application form and the target approval flow template, when the target approval component is triggered, the target application form is displayed, and the approval application is generated based on the target application form filled by the user. Meanwhile, when the target approval component corresponding approval flow template is updated, the target application form needs to be updated synchronously due to the association relationship between the target application form and the target approval flow template, so that the target application form and the target approval flow template always correspond, and the inconsistency of versions does not occur, so as to avoid the approval error.

[0010] In combination with the technical solutions provided in the above first aspect, in some possible implementation manners, the method further includes: when the approval application based on the target approval flow template submitted by the user is received, recording the version information of the target approval flow template; and after the target approval flow template corresponding to the approval application is approved, generating and storing the approval flow approval data corresponding to the approval application, the approval flow approval data including the version information of the target approval flow template corresponding to the approval application.

[0011] In the embodiments of the present application, since the approval flow approval data includes the version information of the target approval flow template corresponding to the approval application, when the approval flow approval data is queried subsequently, the corresponding approval flow template can be selected for display according to the version information, so as to prevent the situation that the current version of the approval flow template cannot display the approval flow approval data corresponding to the previous version of the approval flow template.

[0012] With the technical solution provided in the first aspect above, in some possible implementation manners, each approval flow template corresponds to an approval component, and the approval component is configured to generate an approval application of the approval flow template corresponding to the approval component when the approval component is triggered. The method further includes: when there is an old version of the approval flow template corresponding to the target approval flow template, replacing the old version of the approval flow template with the target approval flow template, generating version information of the target approval flow template, and associating the version information with an approval component corresponding to the old version of the approval flow template, so that the approval component corresponding to the old version of the approval flow template generates an approval application based on the target approval flow template when the approval component is triggered.

[0013] In the embodiments of the present application, the old version of the approval flow template corresponding to the target approval component is updated to the target approval flow template, the version information of the target approval flow template is generated, and the version information is associated with the approval component corresponding to the old version of the approval flow template, so that the approval component generates an approval application based on the target approval flow template when the approval component is triggered, thereby realizing the updating of the approval flow template corresponding to the approval component.

[0014] With the technical solution provided in the first aspect above, in some possible implementation manners, after the target approval flow template is obtained, the method further includes: in response to a user configuring an application corresponding to the target approval flow template, configuring an application domain name and a target application data type corresponding to the target approval flow template, and obtaining application basic information of a third-party application corresponding to the application domain name; obtaining target application data corresponding to the target application data type from the third-party application corresponding to the application domain name, so that the approver determines whether to approve the approval application according to the target application data.

[0015] In the embodiments of the present application, the application domain name and the target application data type corresponding to the target approval flow template are configured, so that the target application data corresponding to the target application data type can be obtained from the third-party application corresponding to the application domain name, so that the approver determines whether to approve the approval application according to the target application data, and the third-party application provides an approval function.

[0016] In the second aspect, the present application provides an approval flow center, including a configuration module, the configuration module is configured to respond to a user's configuration operation on each element in an approval process, complete the configuration of the element, and obtain configuration data of the element, the configuration operation is used to configure an element type of the element and a position of the element in the approval process, wherein the element type in the approval process at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition; the configuration module is further configured to obtain a target approval flow template according to the configuration data of each element in the approval process.

[0017] In a third aspect, the present application provides an approval flow system, comprising an approval flow center and a client, the approval flow center being configured to, in response to a user's configuration operation on each element in an approval flow, complete the configuration of the element, and obtain configuration data of the element, the configuration operation being configured to configure an element type of the element and a position of the element in the approval flow, wherein the element type in the approval flow comprises at least an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition; the approval flow center is further configured to obtain a target approval flow template according to the configuration data of each element in the approval flow; and the client is configured to generate an approval component according to the target approval flow template, and generate an approval application based on the target approval flow template when the approval component is triggered.

[0018] In a fourth aspect, an electronic device is provided, comprising a memory and a processor, the memory and the processor being connected; the memory is configured to store a program; and the processor is configured to invoke the program stored in the memory to execute the method in the first aspect and / or any possible implementation manner in combination with the first aspect.

[0019] In a fifth aspect, a computer readable storage medium is provided, and the computer readable storage medium stores a computer program, and the computer program is run by a computer to execute the method in the first aspect and / or any possible implementation manner in combination with the first aspect. BRIEF DESCRIPTION OF DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following will briefly introduce the drawings needed to be used in the embodiments. It should be understood that the following drawings only show some of the embodiments of the present application, and therefore should not be considered as a limitation to the scope. For those skilled in the art, other related drawings can also be obtained without creative labor.

[0021] Figure 1 A flowchart of an approval flow template configuration method according to an embodiment of the present application is shown;

[0022] Figure 2 A flowchart of an approval flow template approval flow according to an embodiment of the present application is shown;

[0023] Figure 3 A schematic diagram of a data structure corresponding to an approval flow template according to an embodiment of the present application is shown;

[0024] Figure 4 A structural block diagram of an approval flow system according to an embodiment of the present application is shown;

[0025] Figure 5 A structural block diagram of an electronic device is shown in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0027] It should be noted that similar reference numerals and letters refer to like items in the accompanying drawings, and thus, once an item is defined in one drawing, it is not necessary to further define and explain it in subsequent drawings. Meanwhile, in the description of the present application, the relationship terms such as "first", "second", etc. are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Furthermore, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the phrase "including a" does not exclude the presence of another identical element in the process, method, article or device including the element.

[0028] Furthermore, the term "and / or" in the present application merely describes an association relationship of associated objects, and indicates that there can be three relationships, for example, A and / or B can represent the three cases of A existing alone, A and B existing together, and B existing alone.

[0029] The technical solutions of the present application will be described clearly and completely below in conjunction with the drawings.

[0030] Please refer to Figure 1 , Figure 1 A flowchart of a method for configuring an approval flow template is provided in an embodiment of the present application, and the steps contained therein will be described below. Figure 1

[0031] S100: In response to a user's configuration operation on each element in an approval flow, the configuration of the element is completed, and configuration data of the element is obtained, the configuration operation being used to configure the element type of the element and the position of the element in the approval flow.

[0032] Among them, the element type in the approval flow at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition. The approval flow is a specific process for realizing the approval of a certain approval matter. ​

[0033] Optionally, when the element type is an approval node, it indicates that the element has approval functionality and configures the position of the element in the approval process.

[0034] When configuring an element with the element type "Approver", one or more approvers can be configured for that element. The specific number of approvers configured in this element can be set according to actual needs and is not limited here. The element with the element type "Approver" needs to be associated with an element with the element type "Approval Node" to indicate that the approval node is approved by the configured approver.

[0035] Optionally, when the element type is event, configure the event to be executed for the element, such as sending a notification message or sending an email. The specific event type configured in the element can be set according to actual needs, and there are no restrictions here.

[0036] Optionally, when the element type of an element is an approval condition, an approval condition is configured for that element. The approval condition needs to be associated with an element whose element type is an approval node. This means that the approval application will only be approved by the approval node associated with the approval condition if the approval condition is met. For example, when the approval item corresponding to the approval process is leave approval, the element whose element type is an approval condition is configured with "leave time less than 8 hours" and associated with the approval node. Then, when the leave time included in the approval application is less than 8 hours, the element whose element type is an approval node associated with this element will be used for approval.

[0037] In one implementation, the configuration data of each element in the target approval flow template can be stored in the form of an approval flow element relationship table and an approval flow element table. The approval flow element relationship table indicates the position of the element in the approval process, and the approval flow element table indicates the element type. The approval flow element relationship table includes a primary key, element ID, next element ID, approval flow template version ID, status, and creation time. The primary key represents the unique identifier of the approval flow element relationship table; the element ID represents the unique identifier of the element corresponding to the approval flow element relationship table; the next element ID represents the element ID of the element to be executed after the current element in the target approval flow template is executed; the approval flow template version ID indicates that the element corresponding to the approval flow element relationship table belongs to the approval flow template version corresponding to the approval flow template version ID; the status includes two types: normal and deleted, representing the status of the approval flow element table. Optionally, one implementation of the approval flow element relationship table is shown in Table 1:

[0038] Table 1

[0039]

[0040]

[0041] The approval flow element table includes a primary key, an approval flow template version id, an element type, a state, attributes required for element generation, and a creation time. The primary key represents a unique number of the approval flow element table. The approval flow template version id represents that the element corresponding to the approval flow element table belongs to the approval flow template version corresponding to the approval flow template version id. The element type represents the element type of the element corresponding to the approval flow element table. The state includes normal and delete, and represents the state of the approval flow element table. The attributes required for element generation include stored conditions, judgments, and specified object template data, and the attributes required for element generation are used when the approval flow is generated. Optionally, one embodiment of the approval flow element table is shown in Table 2.

[0042] Table 2

[0043]

[0044] S200: Obtain a target approval flow template according to the configuration data of each element in the approval process.

[0045] After obtaining the configuration data of each element in the approval process, a target approval flow template can be obtained according to the configuration data of each element in the approval process. The approval flow template is used to execute the approval process.

[0046] When the configuration data of each element in the target approval flow template is stored in the form of an approval flow element relationship table and an approval flow element table, the process of generating the target approval template according to the approval flow element relationship table and the approval flow element table can be that the approval flow element relationship table and the approval flow element table of each element corresponding to the target approval flow template are first obtained, and then all elements are assembled into a tree structure according to the approval flow element relationship table representing the position of the element in the approval process.

[0047] In one embodiment, after obtaining the target approval flow template, the basic information of the approval flow template representing the approval matter corresponding to the target approval flow template is generated and stored. Optionally, the basic information of the approval flow template is stored in the form of an approval flow template table, which includes a primary key, a business code, an approval flow name, a state, a restriction type, a specified id list, a creator id, and a creation time. The primary key represents a unique number of the approval flow template table. The approval flow name represents the name of the approval flow template corresponding to the approval flow template table. The state includes normal and delete, and represents the state of the approval flow element table. The business code is a short description of the approval flow. Optionally, one embodiment of the approval flow template table is shown in Table 3.

[0048] Table 3

[0049]

[0050]

[0051] In an implementation, after obtaining the target approval flow template, the target approval flow template can be modified, and corresponding modification information is generated and stored. Optionally, the modification information can be stored in the form of an operation record table, and the operation record table includes a primary key, a corresponding record id, a type, an operation type, modified data, modified data, and a creation time. The primary key represents the unique number of the operation record table. The modified data represents the target approval flow template before the operation corresponding to the operation record table is executed. The modified data represents the target approval flow template after the operation corresponding to the operation record table is executed. The creation time represents the time when the operation corresponding to the operation record table is executed. The corresponding record id represents the id of the object operated by the operation record table. The type represents which type of table the object operated by the operation record table is, such as tbl_process_template and tbl_process_template_version. Optionally, an implementation of the operation record table is shown in Table 4:

[0052] Table 4

[0053]

[0054] In an implementation, after S200, it is also necessary to determine whether the target approval flow template corresponding to the approval matter exists an old version of the approval flow template.

[0055] Optionally, since each approval flow template corresponds to an approval component, the approval component is used to generate an approval application of the approval flow template corresponding to the approval component when the approval component is triggered. When the target approval flow template corresponding to the approval matter exists an old version of the approval flow template, the old version of the approval flow template is replaced by the target approval flow template, the version information of the target approval flow template is generated, and the version information is associated with the approval component corresponding to the old version of the approval flow template, so that the approval component corresponding to the old version of the approval flow template is triggered to generate an approval application based on the target approval flow template.

[0056] The version information can be stored by means of an approval flow template version table, which includes a primary key, an approval flow template id, a version name, whether to merge an approval flow, a state, a creator id, a creation time, an editing time, and an operator id. The primary key represents the unique number of the approval flow template version table. The approval flow template version id represents the number of the approval flow template corresponding to the approval flow template version table. The version name represents the name of the approval flow template corresponding to the approval flow template version table. The state includes normal and deleted, and represents the state of the approval flow element table. The creator id represents the number of the object that creates the approval flow template version table. The creation time represents the creation time of the approval flow template version table. The editing time represents the editing time of the approval flow template corresponding to the approval flow template version table. Whether to merge an approval flow represents whether to automatically approve when the same approver appears in the node of the back door after the approver agrees once. The operator id is used to record the operation user that last operates the version. Optionally, one embodiment of the approval flow template version table is shown in Table 5:

[0057] Table 5

[0058]

[0059]

[0060] Optionally, the target approval flow template can be created under the old version of the approval flow template, and the target approval flow template is obtained according to the above S100 and S200. Then, in response to the operation of the user publishing the target approval flow template, the old version of the approval flow template is replaced with the target approval flow template, and the version information is associated with the approval component corresponding to the old version of the approval flow template. After receiving the operation instruction of the user publishing the target approval flow template, the target approval flow template can also be submitted to the super manager (a user who has the right to audit the target approval flow template) for auditing. After the super manager audits and passes, the old version of the approval flow template is replaced with the target approval flow template. If the super manager audits and does not pass, the operation of replacing the old version of the approval flow template with the target approval flow template is not performed. Correspondingly, at this time, an audit information representing the audit state of the super manager auditing the target approval flow template can be generated.

[0061] Optionally, the audit information can be stored in the form of an approval flow template approval record table, which includes a primary key, an approval state, an approval flow template version id, a creator id, a creation time, an editing time, and an operator id. The primary key represents the unique number of the approval flow template approval record table. The approval state is one of approval pass, approval rejection, and pending audit. The approval flow template version id indicates that the element corresponding to the approval flow template approval record table belongs to the approval flow template corresponding to the approval flow template version id. The creator id represents the number of the object that created the approval flow template approval record table. The creation time represents the creation time of the approval flow template approval record table. The editing time represents the editing time of the approval flow template corresponding to the approval flow template approval record table. The operator id represents the number of the super administrator who audits the approval flow template. Optionally, one embodiment of the approval flow template version table is shown in Table 6:

[0062] Table 6

[0063]

[0064] Optionally, replacing the old version of the approval flow template with the target approval flow template can be setting the old version of the approval flow template as withdrawn and setting the target approval flow template as in use, so that when the approval component is triggered, an approval application based on the target approval flow template is generated, and the old version of the approval flow template is replaced with the target approval flow template.

[0065] Optionally, the old version of the approval flow template can also be used to replace the currently used approval flow template, realizing version rollback.

[0066] Optionally, when there is no old version of the approval flow template corresponding to the target approval flow template, a target approval component corresponding to the target approval flow template is generated, and version information of the target approval flow template is generated and associated with the target approval component, wherein the target approval component is used to generate an approval application based on the target approval flow template when it is triggered.

[0067] In one embodiment, before generating the target approval component corresponding to the target approval flow template, the approval flow template configuration method further includes: in response to the user configuring an application form based on the preset application form component library, generating a target application form, the target application form being used to record data related to the approval application, and then establishing an association between the target application form and the target approval flow template, wherein when the target approval component is triggered, the target application form is displayed, and an approval application is generated based on the target application form filled by the user.

[0068] The target approval form is different when the target approval flow template corresponds to different approval matters. For example, when the approval matter is leave approval, the target approval form can include the following contents that need to be filled in by the user: leave personnel, leave type (e.g., annual leave, casual leave, sick leave), leave start time, leave end time, and the like. After the user fills in the above contents, a leave approval application is generated based on the target approval form filled in by the user. At this time, the leave approval application includes leave personnel, leave type, leave start time, and leave end time. The specific configuration content of the target approval form can be configured according to actual needs, which is not limited here.

[0069] Optionally, after the target approval form is generated, the version information of the target approval flow template includes the target approval form. For example, the approval flow template version table can also include form template data, which indicates the approval form corresponding to the approval flow template corresponding to the approval flow template version table.

[0070] Optionally, after the target approval form is generated, the version information of the target approval flow template includes the target approval form. For example, the approval flow template version table can also include form template data, which indicates the approval form corresponding to the approval flow template corresponding to the approval flow template version table.

[0071] Optionally, after the target approval form is generated, the version information of the target approval flow template includes the target approval form. For example, the approval flow template version table can also include form template data, which indicates the approval form corresponding to the approval flow template corresponding to the approval flow template version table.

[0072] In an implementation, when the user submits an approval application based on the target approval flow template, the version information of the target approval flow template is recorded, and after the target approval flow template corresponding to the approval application is approved, approval flow approval data corresponding to the approval application is generated and stored. The approval flow approval data includes the version information of the target approval flow template corresponding to the approval application.

[0073] Optionally, the approval flow approval data can include an approval flow table, an approval flow template version table (tbl_process_node), an approver table, and a form data cache table. The approval flow table includes a primary key, form data, an approval state, an application number, an applicant ID, an approval flow template version ID, a source, an application category, a creator ID, a creation time, an editing time, and an operator ID. The primary key represents a unique number of the approval flow table. The form data represents data filled in an application form by a user. The approval state includes to-be-approved, approval passed, approval rejected, and approval in progress. The application number represents a number of an approval application corresponding to the approval flow table. The applicant ID represents a number of an object that initiates the approval application. The approval flow template version ID represents that an element corresponding to the approval flow table belongs to an approval flow template corresponding to the approval flow template version ID. The source represents a source of the approval flow table. The application category represents a category of the approval application corresponding to the approval flow table. The creator ID represents a number of an object that creates the approval flow table. The creation time represents a creation time of the approval flow table. The editing time represents an editing time corresponding to the approval flow table. The operator ID is used to record an operation user that last operates the version. Optionally, one embodiment of the approval flow table is shown in Table 7:

[0074] Table 7

[0075]

[0076]

[0077] The approval flow template version table (tbl_process_node) includes a primary key, an actual approver, an approval node state, an approval opinion, an approval node order, the approval flow ID, a type, an element template ID, an editing time, and a creation time. The primary key represents a unique number of the approval flow template version table. The actual approver represents an approver that approves the approval application in the approval node corresponding to the approval flow template version table. The approval node state includes approval passed, approval rejected, and approval in progress. The approval opinion is an opinion input by the actual approver for the approval application. The approval node order includes an order of all approval nodes in the approval flow template corresponding to the approval flow template version table. The approval flow ID represents that the approval flow template version table belongs to the approval flow approval data corresponding to the approval flow ID. The creation time represents a creation time of the approval flow template version table. The editing time represents an editing time corresponding to the approval flow template version table. The type represents a type of the node, including two types of approval and event. The element template ID is used to mark that the approval node is generated according to which element. Optionally, one embodiment of the approval flow template version table is shown in Table 8:

[0078] Table 8

[0079]

[0080]

[0081] The approver table includes a primary key, an approver id, and an approval node id, wherein the primary key represents a unique number of the approver table; the approver id represents a number of the approver; and the approval node id represents a number of the approval node corresponding to the approver table. Optionally, one embodiment of the approver table is shown in Table 9:

[0082] Table 9

[0083]

[0084] The form data cache table includes a primary key, an approval flow template version id, a user id, stored content, a creation time, and an editing time. The primary key represents a unique number of the form data cache table; the approval flow template version id represents that the application form corresponding to the form data cache table belongs to the approval flow template corresponding to the approval flow template version id; the user id represents a number of the object that submits the approval application corresponding to the form data cache table; the stored content includes the data filled in the application form by the object that submits the approval application corresponding to the form data cache table; the creation time represents a creation time of the form data cache table; and the editing time represents an editing time of the form data cache table. Optionally, one embodiment of the form data cache table is shown in Table 10:

[0085] Table 10

[0086]

[0087] Optionally, after receiving the approval application submitted by the user based on the target approval flow template, the process of performing the approval operation according to the target approval flow template can be that the element type of the first element in the approval flow template is judged, if the element type of the first element in the approval flow template is an approval node, the approval information is sent to the approver configured in the element with the element type of the approver associated with the approval node, and after the approval of the approver, the approval data is received. When the approval data represents the rejection of the approval application, it is judged whether the element type of the next element is an event. If yes (i.e., the element type of the next element is an event), the event configured in the element is executed, and if the element type of the next element is not an event, the approval is ended. When the approval data represents the approval of the approval application, it is judged whether the element type of the next element is an event. If yes (i.e., the element type of the next element is an event), the event configured in the element is executed, and after the execution of the event, it is again judged whether the next element is an event. If the element type of the next element is not an event, it is judged whether the current element is the last element. If yes (i.e., the current element is the last element), the approval is ended, and if no (i.e., the current element is not the last element), the next element is executed. For better understanding, please refer toFigure 2 .

[0088] If the element type of the first element in the approval flow template is an approval condition, it is determined whether the approval application meets the approval condition. If not, the approval is ended. If yes, the approval operation is performed by the element type associated with the element, which is an approval node.

[0089] If the element type of the element is an event, the event configured in the element is executed, and then the element type of the next element is determined.

[0090] In one embodiment, after S200, the approval flow template configuration method further comprises: firstly, in response to the operation of the user configuring the target approval flow template corresponding application, configuring the application domain name and the target application data type corresponding to the target approval flow template, and obtaining the application basic information of the third-party application corresponding to the application domain name, and then obtaining the target application data corresponding to the target application data type from the third-party application corresponding to the application domain name, so that the approver determines whether the approval application passes the approval according to the target application data, thereby providing the approval function for the third-party application.

[0091] Optionally, after configuring the application domain name and the target application data type corresponding to the target approval flow template, the basic information of the approval flow template representing the approval matter corresponding to the target approval flow template further includes the application corresponding to the application domain name, for example, the application id is included in the approval flow template table, which represents the number of the application corresponding to the application domain name configured in the application domain name of the approval flow template table.

[0092] Optionally, after configuring the application domain name and the target application data type corresponding to the target approval flow template, the application information is generated and stored, which includes the application information table and the application user association table. The application information table includes the primary key, the application name, the domain name, the state, the specified id list, the creator id, the creation time, and the modification time. The primary key represents the unique number of the application information table; the application name represents the name of the application corresponding to the application domain name; the domain name is the application domain name; the specified id list represents the id of the user in the list as the manager; the creator id represents the id of the user creating the application information table; the creation time represents the creation time of the application information table; the editing time represents the editing time of the application information table; the state is used to mark the state of the application, including enabled and disabled. Optionally, one embodiment of the application information table is shown in Table 11.

[0093]

[0094] The primary key represents the unique number of the application information table; the application name represents the name of the application corresponding to the application domain name; the domain name is the application domain name; the specified id list represents the id of the user in the list as the manager; the creator id represents the id of the user creating the application information table; the creation time represents the creation time of the application information table; the editing time represents the editing time of the application information table; the state is used to mark the state of the application, including enabled and disabled. Optionally, one embodiment of the application information table is shown in Table 11.

[0095] Table 11

[0096] ​

[0097]

[0098] The application user association table represents the manager information, which includes a primary key, a user id, an application id, a state, a creation time, and a modification time. The primary key represents a unique number of the application user association table; the user id represents a user number corresponding to the application user association table; the application id represents an application number corresponding to the application user association table; the creation time represents a creation time of the application user association table; and the modification time represents a modification time of the application user association table. Optionally, an embodiment of the application user association table is shown in Table 12.

[0099] Table 12

[0100]

[0101] In an embodiment, the data structures of the approval flow element relationship table, the approval flow element table, the approval flow template version record table, the approval flow template version table, the approval flow table, the approval flow template table, the approval flow template table (tbl_process_node), the approver table, the form data cache table, the application information table, the application user association table, and the operation record table are as shown in Table 13. Figure 3

[0102] The embodiments of the application further provide an approval flow center, which includes a configuration module. The approval flow center can be an electronic device with data processing capability, such as a server, a computer, and the like.

[0103] The configuration module is configured to respond to a configuration operation of a user on each element in an approval process, complete the configuration of the element, and obtain configuration data of the element. The configuration operation is configured to configure an element type of the element and a position of the element in the approval process. The element type in the approval process at least includes an approval node and an approver. The element type of the element is any one of an approval node, an approver, an event, and an approval condition.

[0104] The configuration module is further configured to obtain a target approval flow template according to the configuration data of each element in the approval process.

[0105] The approval flow center further includes a processing module. The processing module is configured to, after obtaining the target approval flow template, determine that there is no old version of an approval flow template corresponding to an approval matter of the target approval flow template, generate a target approval component corresponding to the target approval flow template, and generate version information of the target approval flow template, and associate the version information with the target approval component. The target approval component is configured to generate an approval application based on the target approval flow template when the target approval component is triggered.

[0106] ​The processing module is further configured to, in response to an operation of a user configuring an application form based on a preset application form component library before the generating of the target approval flow component corresponding to the target approval flow template, generate a target application form for recording data related to an approval application; and establish an association between the target application form and the target approval flow template, wherein when the target approval flow component is triggered, the target application form is displayed, and the approval application is generated based on the target application form filled by the user.

[0107] The processing module is further configured to, when receiving an approval application submitted by a user based on the target approval flow template, record the version information of the target approval flow template; and after the approval of the target approval flow template corresponding to the approval application is completed, generate and store approval flow approval data corresponding to the approval application, wherein the approval flow approval data includes the version information of the target approval flow template corresponding to the approval application.

[0108] The processing module is further configured to, when there is an old version of an approval flow template corresponding to the approval matter of the target approval flow template, replace the old version of the approval flow template with the target approval flow template, generate version information of the target approval flow template, and associate the version information with an approval component corresponding to the old version of the approval flow template, so that when the approval component corresponding to the old version of the approval flow template is triggered, an approval application based on the target approval flow template is generated.

[0109] The processing module is further configured to, after obtaining the target approval flow template, in response to an operation of a user configuring an application corresponding to the target approval flow template, configure an application domain name and a target application data type corresponding to the target approval flow template, and obtain application basic information of a third-party application corresponding to the application domain name; and obtain target application data corresponding to the target application data type from the third-party application corresponding to the application domain name, so that the approver determines whether the approval application is approved based on the target application data.

[0110] The approval flow center provided by the embodiment has the same implementation principle and technical effects as the foregoing approval flow template configuration method embodiment, and for brevity of description, the part of the approval flow center embodiment not mentioned can refer to the corresponding content in the foregoing approval flow template configuration method embodiment.

[0111] Please refer to Figure 4 , Figure 4 An approval system 100 is provided in the embodiment, and the approval system 100 includes an approval flow center 110 and a client 120.

[0112] The approval flow center 110 is configured to complete configuration of each element in the approval flow in response to a configuration operation of a user, obtain configuration data of the element, and the configuration operation is used to configure an element type of the element and a position of the element in the approval flow, wherein the element type in the approval flow at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition;

[0113] The approval flow center 110 is further configured to obtain a target approval flow template according to the configuration data of each element in the approval flow.

[0114] The client 120 is configured to generate an approval component according to the target approval flow template, and generate an approval application based on the target approval flow template when the approval component is triggered.

[0115] The approval flow center 110 has the same working mode and working principle as the approval flow center described above, and will not be described again for brevity.

[0116] The client 120 is further configured to provide at least one function of submitting an approval application, viewing an approval flow list, an operation (agreement, rejection, withdrawal, comment, forwarding) of the approval flow, viewing application form details, and an approval progress.

[0117] The function of submitting an approval application indicates that the user can submit an approval application through the client 120.

[0118] The client 120 displays all approval applications proposed by the user after receiving a viewing instruction of the user on the approval flow list, including all approval applications in the approval process and completed approval applications.

[0119] The client 120 performs corresponding operations when receiving an operation of the user on the approval flow, such as agreement, rejection, withdrawal, comment, and forwarding, wherein the agreement and rejection are only operations executable by the approver, and the withdrawal is only an operation executable by the proposer of the approval application.

[0120] The client 120 displays the application form details of the approval application and the progress of the approval application when receiving a viewing operation of the user on the application form details and the approval progress of an approval application, wherein the progress of the approval application includes the approval process, the approval to be processed, and the approval completed.

[0121] Optionally, the approval flow center 110 configures each approval flow template, and the client 120 correspondingly creates a corresponding approval component, and the approval component is triggered to generate an approval application based on the approval flow template corresponding to the approval component.

[0122] Optionally, the client 120 provides a list and query conditions to help the user quickly locate the approval application.

[0123] Optionally, after the user fills in the application form, the client 120 generates the form structure through the template data configured by the application form, generates the application details page of the submitted application, and realizes the display of the details of the application.

[0124] Please refer to Figure 5 The electronic device 200 provided by the embodiment of the present application. The electronic device 200 includes: a transceiver 210, a memory 220, a communication bus 230, a processor 240.

[0125] The transceiver 210, the memory 220, and the processor 240 are directly or indirectly electrically connected to each other to realize data transmission or interaction. For example, these elements can be electrically connected to each other through one or more communication buses 230 or signal lines. Among them, the transceiver 210 is used for transceiving data. The memory 220 is used for storing a computer program, which includes at least one software function module in the form of software or firmware stored in the memory 220 or solidified in the operating system (OS) of the electronic device 200. The processor 240 is used for executing the executable modules stored in the memory 220.

[0126] For example, the processor executes the software function module or computer program corresponding to the above-mentioned approval flow template configuration method. At this time, the processor 240 is used to respond to the configuration operation of the user for each element in the approval process, complete the configuration of the element, obtain the configuration data of the element, and the configuration operation is used to configure the element type of the element and the position of the element in the approval process, wherein the element type in the approval process includes at least approval node and approver, and the element type of the element is any one of approval node, approver, event and approval condition; according to the configuration data of each element in the approval process, the target approval flow template is obtained.

[0127] The memory 220 can 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 Electric Erasable Programmable Read-Only Memory (EEPROM), and the like.

[0128] The processor 240 can be an integrated circuit chip with processing capability. The processor can be a general purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; or can be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps, and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed by the processor. The general purpose processor can be a microprocessor or the processor 240 can also be any conventional processor or the like.

[0129] The electronic device 200 can be the approval flow center, and can include, but is not limited to, a personal computer, a server, and the like.

[0130] The embodiments of the present application further provide a non-volatile computer readable storage medium (hereinafter referred to as a storage medium) having a computer program stored thereon. When the computer program is run by a computer such as the electronic device 200, the approval flow template configuration method shown in the above embodiments is executed. The computer readable storage medium includes a U disk, a mobile hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and the like.

[0131] The above descriptions are only the preferred embodiments of the present application, and are not intended to limit the present application. The present application can have various modifications and changes for those skilled in the art. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. An approval flow template configuration method, characterized by, The method comprises the following steps: in response to a user's configuration operation on each element in an approval process, completing the configuration of the element to obtain configuration data of the element, wherein the configuration operation is used to configure an element type of the element and a position of the element in the approval process, wherein the element type in the approval process at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition; obtaining a target approval flow template according to the configuration data of each element in the approval process; when the configuration data of each element is stored in the form of an approval flow element relationship table and an approval flow element table, generating the target approval template according to the approval flow element relationship table and the approval flow element table, comprising: obtaining the approval flow element relationship table and the approval flow element table of each element corresponding to the target approval flow template; the approval flow element relationship table indicates the position of the element in the approval process, and the approval flow element table indicates the element type of the element; assembling all elements into a tree structure according to the approval flow element relationship table representing the position of the element in the approval process to obtain the target approval flow template.

2. The method of claim 1, wherein, After obtaining the target approval flow template, the method further comprises: determining that there is no old version of the approval flow template corresponding to the target approval flow template of the approval matter; generating a target approval component corresponding to the target approval flow template, and generating version information of the target approval flow template, and associating the version information with the target approval component, wherein the target approval component is used to generate an approval application based on the target approval flow template when the target approval component is triggered.

3. The method of claim 2, wherein, Before generating the target approval component corresponding to the target approval flow template, the method further comprises: in response to a user's operation of configuring an application form based on a preset application form component library, generating a target application form, wherein the target application form is used to record data related to the approval application; establishing an association relationship between the target application form and the target approval flow template, wherein when the target approval component is triggered, the target application form is displayed, and the approval application is generated based on the target application form filled by the user.

4. The method of claim 3, wherein, The method further comprises: when receiving an approval application based on the target approval flow template submitted by a user, recording the version information of the target approval flow template; and after the target approval flow template corresponding to the approval application is approved, generating and storing approval flow approval data corresponding to the approval application, wherein the approval flow approval data includes the version information of the target approval flow template corresponding to the approval application.

5. The method of claim 1, wherein, Each approval flow template corresponds to an approval component, and the approval component is used to generate an approval application of the approval flow template corresponding to the approval component when the approval component is triggered, and the method further comprises: When an old version of the approval flow template corresponding to the target approval matter exists, the old version of the approval flow template is replaced by the target approval flow template, version information of the target approval flow template is generated, and the version information is associated with an approval component corresponding to the old version of the approval flow template, so that when the approval component corresponding to the old version of the approval flow template is triggered, an approval application based on the target approval flow template is generated.

6. The method of claim 1, wherein, After the target approval flow template is obtained, the method further includes: In response to a user configuring an application corresponding to the target approval flow template, configuring an application domain name and a target application data type corresponding to the target approval flow template, and obtaining application basic information of a third-party application corresponding to the application domain name; Obtaining target application data corresponding to the target application data type from the third-party application corresponding to the application domain name, so that the approver determines whether to approve the approval application according to the target application data.

7. An approval flow center, characterized by Comprise: The configuration module is configured to respond to a user's configuration operation on each element in an approval process, complete the configuration of the element, obtain configuration data of the element, and the configuration operation is used to configure an element type of the element and a position of the element in the approval process, wherein the element type in the approval process at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition; The configuration module is further configured to obtain a target approval flow template according to the configuration data of each element in the approval process; When the configuration data of each element is stored in the form of an approval flow element relationship table and an approval flow element table, the configuration module is specifically configured to obtain the approval flow element relationship table and the approval flow element table of each element corresponding to the target approval flow template; the approval flow element relationship table represents the position of the element in the approval process, and the approval flow element table represents the element type of the element; all elements are assembled into a tree structure according to the approval flow element relationship table representing the position of the element in the approval process, and the target approval flow template is obtained.

8. An approval flow system, characterized by Comprise: The approval flow center is configured to respond to a user's configuration operation on each element in an approval process, complete the configuration of the element, obtain configuration data of the element, and the configuration operation is used to configure an element type of the element and a position of the element in the approval process, wherein the element type in the approval process at least includes an approval node and an approver, and the element type of the element is any one of an approval node, an approver, an event, and an approval condition; The approval flow center is further configured to obtain a target approval flow template according to configuration data of each element in the approval flow; wherein the configuration data of each element is stored in the form of an approval flow element relationship table and an approval flow element table, the approval flow center is specifically configured to obtain the approval flow element relationship table and the approval flow element table of each element corresponding to the target approval flow template; the approval flow element relationship table indicates the position of an element in the approval flow, and the approval flow element table indicates the element type of the element; all elements are assembled into a tree structure according to the approval flow element relationship table representing the position of an element in the approval flow, and the target approval flow template is obtained; a client configured to generate an approval component according to the target approval flow template, and generate an approval application based on the target approval flow template when the approval component is triggered.

9. An electronic device, comprising: comprising: a memory and a processor, the memory and the processor being connected; the memory is configured to store a program; the processor is configured to call the program stored in the memory to execute the method according to any one of claims 1-6.

10. A computer-readable storage medium, characterized in that, a computer program is stored thereon, and the computer program is run by a computer to execute the method according to any one of claims 1-6.

Images