Service approval method, device and equipment based on corpus and medium

Abstract

The invention relates to a business approval method and device based on a corpus, equipment and a medium, and the method comprises the steps: configuring a role table, a user table and a user role association table, and generating a user role corpus; configuring the business item table, the auditing table, the label table and the online process table to generate an item corpus; and executing a service approval process based on the user role corpus and the item corpus. According to the method and the device, examination and approval requirements of cross-level and cross-department users and different business items can be effectively met, and examination and approval processes of the business items in different examination and approval scenes are more efficiently executed, so that the examination and approval processes of the business items are more flexible and convenient.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a corpus-based business approval method, device, equipment and medium. Background Art

[0002] The approval process of business matters is an important link in the collaborative work between different departments at the same level or between different departments at different levels in the public security industry. Through the transfer of approval flow, the approval flow of businesses that require approval from different departments at the same level or different departments at different levels can be transferred to complete the processes of viewing, editing, referencing, synchronizing, and regularizing business matters.

[0003] The approval and circulation requirements for business matters at different levels and in different related departments are not the same. Due to the differences in the daily processing requirements for business matters, and the mutual approval scenarios between different levels and departments are mostly conducted through offline communication, which brings about problems such as high communication costs and low work efficiency. At this time, there is an urgent need for a universal business process approval method that can not only meet the business process approval of departments at the same level, but also meet the process circulation requirements of multiple scenarios such as mutual approval of business matters between departments at different levels. Summary of the invention

[0004] In order to solve the above technical problems, the present disclosure provides a corpus-based business approval method, device, equipment and medium.

[0005] According to one aspect of the present disclosure, a corpus-based business approval method is provided, comprising:

[0006] The role table, user table and user role association table are configured to generate a user role corpus; wherein the role table is used to record the role information of users of multiple levels and multiple departments, the user table is used for the identity information of the users, and the user role association table is used to record the roles, management scopes and permissions corresponding to the users;

[0007] The business item table, the review table, the label table and the online process table are configured to generate an item corpus; wherein the business item table is used to record business items, the review table is used to record business items to be reviewed by the user, the label table is used to record label information of the business items, and the online process table is used to record the review status of parent and child items with a cascading relationship;

[0008] A business approval process is executed based on the user role corpus and the matter corpus.

[0009] According to another aspect of the present disclosure, there is also provided a corpus-based business approval device, comprising:

[0010] A user configuration module is used to configure the role table, user table and user role association table to generate a user role corpus; wherein the role table is used to record the role information of users of multiple levels and multiple departments, the user table is used for the identity information of the users, and the user role association table is used to record the roles, management scopes and permissions corresponding to the users;

[0011] The item configuration module is used to configure the business item table, the review table, the label table and the online process table to generate an item corpus; wherein the business item table is used to record business items, the review table is used to record business items to be reviewed by the user, the label table is used to record label information of the business items, and the online process table is used to record the review status of parent and child items with a cascading relationship;

[0012] The business approval module is used to execute the business approval process based on the user role corpus and the matter corpus.

[0013] According to another aspect of the present disclosure, an electronic device is provided, the electronic device comprising:

[0014] processor;

[0015] a memory for storing instructions executable by the processor;

[0016] The processor is used to read the executable instructions from the memory and execute the instructions to implement the above method.

[0017] According to another aspect of the present disclosure, a computer-readable storage medium is provided, wherein the storage medium stores a computer program, and the computer program is used to execute the above method.

[0018] Compared with the prior art, the technical solution provided by the embodiments of the present disclosure has the following advantages:

[0019] The technical solution provided by the embodiment of the present disclosure includes: configuring the role table, user table and user role association table to generate a user role corpus; configuring the business matter table, review table, label table and online process table to generate a matter corpus; executing the business approval process based on the user role corpus and the matter corpus. In this technical solution, the user role corpus uses multiple roles, multiple management scopes, and multiple permissions to record users of multiple levels and multiple departments, so that the creation, editing, approval, viewing and other permissions of users in different levels and departments are different, which can meet the needs of cross-level and cross-department users to approve business matters. On the basis of the user role corpus, combined with the matter corpus to record the review status of business matters and parent-child matters with cascading relationships, it can meet the needs of cross-level multi-copy synchronization update status in multiple business approval scenarios such as creating new business matters, editing business matters, and synchronizing business matters. The chain structure of the cascading relationship between parent-child matters is adopted to record the cascading relationship between parent node matters and child node matters in a series of approval links from creation to submission for review, to approval or rejection, and then to forward and reverse updates. The approval status of business matters is changed synchronously through tracing back the cascading relationship layer by layer. Therefore, this solution can effectively respond to the approval needs of users across levels and departments and different business matters, and more efficiently execute the approval process of business matters in different approval scenarios, making the approval process of business matters more flexible and convenient. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0021] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0022] Figure 1 A flowchart of a corpus-based business approval method provided in an embodiment of the present disclosure;

[0023] Figure 2 A schematic diagram of a model of a user role corpus provided in an embodiment of the present disclosure;

[0024] Figure 3 A schematic diagram of a model of a matter corpus provided in an embodiment of the present disclosure;

[0025] Figure 4 A schematic diagram of an approval interface for business matters provided in an embodiment of the present disclosure;

[0026] Figure 5 An example swimlane diagram of approval in the scenario of a newly added business item provided in an embodiment of the present disclosure;

[0027] Figure 6 An example swimlane diagram of approval and rejection in the scenario of a new business item provided in an embodiment of the present disclosure;

[0028] Figure 7 An example swimlane diagram for canceling a new business item in a scenario provided by an embodiment of the present disclosure;

[0029] Figure 8 An example swimlane diagram of approval in the scenario of editing / deleting business items provided in an embodiment of the present disclosure;

[0030] Fig. 9 An example swimlane diagram of approval rejection in the scenario of editing / deleting a business item provided in an embodiment of the present disclosure;

[0031] Fig.10 An example swimlane diagram for canceling a business item in a scenario of editing / deleting a business item provided in an embodiment of the present disclosure;

[0032] Fig.11 An example swimlane diagram of approval in the scenario of synchronous business items provided in an embodiment of the present disclosure;

[0033] Fig.12 A structural block diagram of a corpus-based business approval device provided in an embodiment of the present disclosure;

[0034] Fig.13 A schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0036] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0037] At present, there is an urgent need for a universal business process approval method to meet the business process approval of each department at the same level, as well as to meet the process flow requirements of multiple scenarios such as mutual approval of business matters between departments at different levels. Based on this, the disclosed embodiments provide a corpus-based business approval method, device, equipment and medium. This technical solution can approve business in multiple scenarios across departments at different levels. Since the scenario combination roles and user permissions are realized through corpus configuration, it can effectively deal with the problem of different management users, different business needs, and approval processes for business matters in different scenarios between departments, making the business approval process more flexible and convenient, with strong portability, simple and fast secondary development, and low performance loss.

[0038] Figure 1 This is a flowchart of a corpus-based business approval method provided in an embodiment of the present disclosure. The method can be applied to cross-level multi-scenario approval processes, such as the collaborative work between different levels and departments at the provincial, municipal, district and county levels in the public security industry. The method can be executed by a corpus-based business approval device configured on a terminal, which can be implemented using software and / or hardware.

[0039] Reference Figure 1 The corpus-based business approval method provided by the embodiment of the present disclosure may include the following steps.

[0040] S102, configuring the role table, user table and user role association table to generate a user role corpus; wherein the role table is used to record the role information of users in multiple levels and multiple departments, the user table is used for the user's identity information, and the user role association table is used to record the user's corresponding role, management scope and authority.

[0041] This embodiment can dynamically configure information such as users and their roles across levels and departments, and connect the user role corpus with the massive user data accessed by the user side. The user data may include the user's identity information, role information, management scope and authority, such as approval authority and viewing authority. Since the user data corresponding to users at different levels and departments (such as across provinces, cities, districts and counties) are different, it is possible to dynamically configure the role table, user table and user role association table to establish targeted personal data for each user in the user role corpus that conforms to their actual situation.

[0042] Reference Figure 2The model example of the user role corpus shown in the figure takes user A as an example. Role information such as role ID and role name are dynamically configured in the role table, and then the role table is associated with user A. The role relationship corresponding to user A is configured in the user role relationship table, including: ID, user relationship ID, role relationship ID, and management scope and authority of user A. Among them, the role ID and user ID unique identifiers are mapped one-to-one, and the management scope indicates the management scope specific to a certain role and a certain user. Different management scopes generally correspond to different permissions such as viewing, editing, reference, synchronization, and regularization. For example, the public security industry manages different tracks and handles business matters under different tracks.

[0043] S104, configure the business matter table, review table, label table and online process table to generate a matter corpus; wherein the business matter table is used to record business matters, the review table is used to record business matters to be reviewed by users, the label table is used to record label information of business matters, and the online process table is used to record the review status of parent-child matters with cascading relationships.

[0044] Reference Figure 3 The model example of the item corpus shown in the figure configures the item ID, specific item, item description and other information of the business item in the business item table, and distinguishes different business items through the above information. Figures 4 to 11 , the matter corpus can include: reference matter corpus (referred to as reference library) and the own matter corpus of each level or each department (referred to as own library), which records all matters, my operation matters, and my approval matters under its level or department. The level of the reference library is higher than that of the own library; specifically, the reference library corresponds to provincial users, and the own library corresponds to ordinary users in districts and counties, department users in districts and counties, and users in districts and counties. Since the initiation and approval of business matters are implemented by users, therefore, combined with Figure 2 , the business item table can be associated with the user table.

[0045] In this embodiment, the tag information such as the tag ID and the item ID of the business item is dynamically configured in the tag table. The business items to be reviewed by the user are recorded in the review table, that is, Figure 5 I review items in.

[0046] This embodiment records the review status of the parent-child items with a cascading relationship in the online process table; wherein, the parent-child items with a cascading relationship refer to that when the current business item is approved, the item copy is copied to obtain the child business item, the current business item is used as the parent node item (also called the original item), and the copied child business item is used as the child node item (also called the copy item), thereby establishing a cascading relationship between the parent and child items. This cascading relationship can facilitate dynamic tracing of the connection status between the parent node item and the child node item in the approval process. It can be understood that the parent node item and the child node item are relative concepts. In an approval process containing multiple approval nodes, the same business item may be both a child node item in its previous approval node and a parent node item in its next approval node.

[0047] S106, executing the business approval process based on the user role corpus and the matter corpus.

[0048] The approval process of business items involves reversal and approval between different levels, different roles, and different users. This embodiment supports the business approval process to flow through different levels, from item creation, reversal to formalization. For the same business item, a copy is retained to dynamically display the status of the item, so as to facilitate different users at different levels to track the approval process of business items.

[0049] The approval process of business items generally involves the initiator and the approver of the business items. As an example, the initiator of a business item can be an ordinary user at the provincial department, an ordinary user at the district and county level, a department administrator at the district and county level, and a district and county administrator at the district and county level. The business process approval generally goes from the initiator to the department administrator, and then to the district and county administrator. The specific user needs to be dynamically configured. After the business item is initiated, the initiator can revoke the item, and the status of the copy item of each approval node that the business item has reversed will also change accordingly. The approver can choose to approve or reject the business item; of course, there are many special scenarios in actual applications. For example, after the department administrator approves a business item, the district and county administrator executes a rejection operation. At this time, the department administrator can choose to agree to the rejection or continue to approve it.

[0050] The above is only a brief description. The following will describe in detail an embodiment of executing a business approval process based on a user role corpus and an event corpus.

[0051] In this embodiment, executing the business approval process based on the user role corpus and the matter corpus may include the following steps 1 to 3.

[0052] Step 1: The first user terminal initiates a review application message for the current business item to the second user terminal, and records the current business item in a review table.

[0053] Among them, the current business item can be a business item at the starting node in the approval process, such as a newly created business item, a business item to be edited, deleted or revoked in the business item table; the current business item can also be a business item from the intermediate approval node to the end of the approval process, such as my operation items to be reviewed in the process from department review, district and county review to the formalization of the matter, my approval items that have been approved, and all matters of formalization of the matter.

[0054] Correspondingly, the first user terminal and the second user terminal are terminals where users in the user role corpus have the processing authority to initiate, operate, view and approve the current business item, and the first user terminal and the second user terminal correspond to users across levels and departments. When the current business item is a business item at the start node in the approval process, the first user terminal is the initiator at the start node in the approval process. Ordinary users or administrators at multiple levels can be the initiators of the business item. Figure 5 The example is a county-level ordinary user; correspondingly, the second user end is an approval end at an intermediate approval node in the approval process, as shown in the following example. Figure 5 District and county department users in the example.

[0055] When the current business item is a business item of an intermediate approval node in the approval process, the first user end is the initiator end of the i-th intermediate approval node in the approval process, as shown in the following example: Figure 5 The district and county department user in the example; correspondingly, the second user end is the approval end at the i+1th intermediate approval node in the approval process, as shown in the following example. Figure 5 District and county users in the example.

[0056] In addition, it can be understood that, relative to the i-1th intermediate approval node in the approval process, the first user terminal is also the approval terminal, and, relative to the i+2th intermediate approval node in the approval process, the second user terminal is also the initiating terminal. In short, the first user terminal and the second user terminal are relative, indicating the user terminals corresponding to the two adjacent approval nodes in the approval process, and the same is true for the third user terminal described below.

[0057] In this embodiment, the first user terminal can select the second user terminal corresponding to the next approval node in the approval process in the user role corpus; or it may not select the second user terminal. In this case, the second user terminal with processing authority for the current business matter can be determined in the user role corpus based on information such as the user's role, management scope and authority.

[0058] Then, the first user terminal initiates an audit application message for the current business item to the second user terminal corresponding to the next approval node in the approval process, and records the current business item in the audit table. Specifically, when the first user terminal submits an audit application for any operation such as creating, editing, deleting and revoking the current business item, an audit application message will be generated. At the same time, the first user terminal will record the current business item in the audit table as my operation item. The audit application message reminds the second user terminal to approve the current business item in the audit table. After approving or rejecting the current business item, the second user terminal will record the current business item in the audit table as my approval item.

[0059] Step 2, the second user terminal receives the current business item to be approved from the review table, and, by performing an approval operation on the current business item, establishes a sub-business item with a cascade relationship of parent and child items with the current business item, and changes the approval status of the current business item and the sub-business item.

[0060] In this embodiment, the second user terminal performs an approval operation on the current business item. In response to the approval operation, the following actions are performed: approving or rejecting the current business item, performing a copy based on the current business item, and changing the item status.

[0061] In the specific example, from the initiation of the current business item, department review, district and county review to the formalization of the item, a copy of the business item at each process node will be retained and the status will be displayed. Among them, the copy refers to the sub-business item that has a cascade relationship of parent-child items with the current business item. A cascade relationship will be formed between the current business items and their sub-business items under multiple process nodes. For example: after approval operations such as submission for review, approval, and rejection, a copy is executed on the basis of the business item table and written into the review table, starting from the parent node item (current business item) to the next level of child node items (sub-business items), forming a chain structure cascade relationship.

[0062] In addition, the approval status of each parent and child item is changed synchronously through tracing back through the cascading relationship, and displayed synchronously on the list page. Once the approval status of a child node item changes during the approval process, the parent node item is synchronously changed according to the cascading relationship.

[0063] In one embodiment, it also includes the creation and editing of event labels and online process tables. Since the business event table is associated with the label table and the online process table, when performing a copy, the label table and the online process table can also be copied synchronously, and the changes before and after the current business event are compared and recorded in the online process table. The changes before and after include but are not limited to: the approval status of the change, the re-edited business event, and the draft retained after the business event is revoked.

[0064] Step 3, the second user terminal takes the sub-business item as the new current business item, and initiates a new current business item review application message to the third user terminal; and so on, until the approval process of the current business item is completed. Among them, the first user terminal, the second user terminal and the third user terminal are terminals where users of different levels and / or different departments in the user role corpus are located.

[0065] Based on the above embodiments, this embodiment can support business item approval in various scenarios such as creation, editing, deletion, and revocation. Here, the following examples of business item approval processes are provided.

[0066] Example 1 of the approval process: adding a new business item. In this embodiment, the first user terminal sends a review application message of the current business item to the second user terminal, including: the first user terminal creates the current business item according to the new operation, and submits the review application message of the current business item to the second user terminal.

[0067] exist Figure 5 In the example, the first user terminal corresponds to an ordinary user in a county or district, creates a current business item according to a new creation operation, and initiates a review application message for the current business item to the second user terminal according to a submit review operation.

[0068] The second user terminal corresponds to the district and county department user. The second user terminal receives the current business item from the review table based on the review application message and performs an approval operation on the current business item. Through the approval operation, a sub-business item with a cascade relationship of parent and child items with the current business item is established, and the approval status of the current business item and the sub-business item is changed.

[0069] The above-mentioned embodiment of changing the approval status of the current business item and sub-business item may include: when the second user terminal is approving the current business item, changing the approval status of the current business item and sub-business item to a pending review status; when the second user terminal approves the current business item, changing the approval status of the current business item and sub-business item to a passed status; when the second user terminal approves and rejects the current business item, changing the approval status of the current business item and sub-business item to a rejected status.

[0070] Specifically, the current business item is a newly created business item by the first user end, which is recorded as my operation item under the district and county ordinary user, and the my operation item under the district and county ordinary user is the parent node item; the child business item is recorded as my approval item under the district and county department user, and the my approval item under the district and county department user is the child node item. When the second user end is approving my approval item, the approval status of my approval item is pending review, and the approval status of the parent node item is synchronously changed according to the cascading relationship, and the approval status of my operation item under the district and county ordinary user is changed to the department review status.

[0071] When the second user terminal approves my approval item, the approval status of my approval item is passed. At this time, if further approval is required, the second user terminal will use my approval item as the new current business item, and initiate a review application message for the new current business item to the third user terminal, and the third user terminal corresponds to the district and county user. In this case, the approval status of my approval item in the second user terminal is changed to passed, and my operation items under the ordinary users of the district and county are its parent node items, and the approval status will be changed synchronously to the district and county review status according to the cascading relationship, and my approval items under the district and county users are their child node items, and the approval status will be changed synchronously to the pending review status according to the cascading relationship.

[0072] According to the above method, the current business items are approved across levels and departments until they are finally approved or rejected. Figure 5 It shows the final approval of the current business item, including: when the current business item is approved, the current business item is formalized and written into the business item table. After approval, the current business item is formalized and the approval process ends. In this case, the approval status of the parent node item and the child node item is synchronized according to the cascading relationship, including: the approval status of the district and county users is synchronized to the approved status, the approval status of the district and county department users is synchronized to the approved status, and the approval status of the district and county ordinary users is synchronized to the completed status.

[0073] as well as, Figure 6 It shows the final approval and rejection of the current business item. After the district and county user approves and rejects it, the district and county department user agrees to reject it, and the current business item returns to the "My Operation Item" under the district and county ordinary user, and the district and county ordinary user re-edits the "My Operation Item". After re-editing, the approval process can be ended directly, or the re-edited current business item can be resubmitted for review. In this case, the approval status synchronization changes of the parent node item and the child node item according to the cascading relationship include: the approval status under the district and county user is the rejected status, the approval status under the district and county department user is synchronized to the rejected status, and the approval status under the district and county ordinary user is synchronized to the draft status.

[0074] At each approval node of the entire approval process above, an approval status change will be executed. Then, in this embodiment, each time the approval status is changed, the approval status of all business items with a cascade relationship is changed, and the changed approval status of the current business item and the sub-business item is recorded in the online process table. Specifically, each time the approval status is changed, the parent node items and sub-node items in the approval process are traced back layer by layer according to the cascade relationship, and the approval status of the parent node items and the sub-node items is changed synchronously. And the approval status of the parent node items and the sub-node items is recorded in the online process table.

[0075] This embodiment also includes revoking the current business item during the approval process of the current business item. In this scenario, the first user terminal initiates a review application message of the current business item to the second user terminal, including: after the current business item is approved, the first user terminal performs a revocation operation on the current business item in the business item table, and submits a review application message of revoking the current business item to the second user terminal. The first user terminal generally corresponds to the user who initiated the current business item.

[0076] like Figure 7 For example, after the second user terminal corresponding to the district and county department user approves the current business item, the first user terminal corresponding to the district and county general user reserves a cancel button for the original business item, and cancels the current business item through the cancel button, and then ends the approval process. In this scenario of canceling the business item, the approval status of the parent and child items is changed synchronously according to the cascading relationship, so that users at all levels of roles can view the status of the business item.

[0077] In this example, since the revocation operation occurred after the approval was passed on the second user side, and the third user side corresponding to the county user has not yet approved this node, the approval status under the county general user is changed from "under review" to "draft", and the approval status of the county department user is "passed", and the approval status under the county user will be changed from "pending review" to "revoked". It can be seen that in the scenario of revoking business items, each time the approval status is changed, the approval status of all business items with cascading relationships is changed, and the changed approval status of the current business item and sub-business items is recorded in the online process table.

[0078] Example 2 of the approval process: Editing a business item. In this embodiment, the first user terminal initiates a review application message of the current business item to the second user terminal, including: the first user terminal performs an editing operation on the current business item in the business item table, and submits a review application message of the edited business item to the second user terminal.

[0079] exist Figure 8In the example, the first user terminal corresponds to an ordinary user in the county and district. Among all the items recorded in the business item table, the current business item to be edited is determined, and the editing operation is performed on the current business item. The edited business item enters the my operation items. Then, according to the submission review operation, a review application message for the edited business item is initiated to the second user terminal. The subsequent approval process may include, for example: the second user terminal corresponding to the county and district department user reviews and approves, the third user terminal corresponding to the county and district user reviews and approves, and the first user terminal corresponding to the ordinary user in the county and district formalizes the edited business item and records it in all the items in the own item corpus. The specific process can refer to the new business item scenario described in the aforementioned example one. Figure 5 The corresponding final approval is passed through the implementation example of the current business matter.

[0080] exist Fig. 9 In the example, it shows the final approval and rejection of the current business item in the editing business item scenario. The approval process can refer to the new business item scenario described in the previous example 1. Figure 6 The corresponding final approval rejects the implementation example of the current business item.

[0081] like Fig.10 As shown, in the scenario of editing a business item, after the current business item is approved, the first user terminal can also perform a cancellation operation on the current business item in the business item table and submit a review application message for canceling the current business item to the second user terminal. The approval process can refer to the scenario of creating a new business item described in the above example 1. Figure 7 The corresponding implementation example of canceling the current business item.

[0082] Example 3 of the approval process: deleting a business item. In this embodiment, the first user terminal sends a review application message of the current business item to the second user terminal, including: the first user terminal performs a deletion operation on the current business item in the business item table, and submits a review application message of deleting the current business item to the second user terminal.

[0083] The approval process for deleting business items is basically the same as the approval process for business items shown in the above example 2. For details, please refer to the above embodiments and Figures 8 to 10 content.

[0084] Example 4 of the approval process: Synchronizing business items. In this embodiment, the first user terminal initiates a review application message of the current business item to the second user terminal, including: the first user terminal performs a synchronization operation on the current business item in the reference item corpus, and submits a review application message of synchronizing the current business item to the second user terminal; wherein the reference item corpus is included in the item corpus.

[0085] exist Fig.11In the example, the first user terminal corresponds to an ordinary user in the county and district. Among the business items recorded in the reference item corpus, the current business item to be synchronized is determined, and the synchronization operation is performed on the current business item. The current business item to be synchronized enters the my operation items. Then, according to the submission review operation, an audit application message for the current business item to be synchronized is initiated to the second user terminal. The subsequent approval process may include, for example: the second user terminal corresponding to the county and district department user approves the approval, the third user terminal corresponding to the county and district user approves the approval, and the first user terminal corresponding to the ordinary user in the county and district formalizes the current business item and records it in all items in its own item corpus. The specific process can refer to the aforementioned multiple embodiments and Fig.11 content.

[0086] According to the above embodiment, the reference item corpus is for users of all levels and departments. Considering that multiple administrators with the same role edit and copy the same business item in the reference item corpus and submit them for review, the same business item will go through different business approval processes, causing confusion. To address this problem, this embodiment can set the following scheme when executing the business approval process based on the user role corpus and the item corpus:

[0087] After the first user terminal initiates the review application message of the current business item, approval restrictions are implemented on the current business item to block the authority of other users to submit the current business item; among them, there are multiple users with the same role information in the user role corpus, and among the multiple users with the same role information, the terminal of the user who first initiates the review application message of the current business item is taken as the first user terminal.

[0088] In this embodiment, after the first-post user terminal initiates the review application message of the current business item, approval restrictions are implemented on the current business item, thereby shielding the authority of other users to submit it for review, avoiding confusion caused by the same business item going through different business approval processes, and improving the rationality of business item approval.

[0089] The corpus-based business approval method provided in the above embodiment includes: configuring a role table, a user table and a user role association table to generate a user role corpus; configuring a business matter table, an audit table, a label table and an online process table to generate a matter corpus; and executing a business approval process based on the user role corpus and the matter corpus. In this technical solution, the user role corpus uses multiple roles, multiple management scopes, and multiple permissions to record users of multiple levels and multiple departments, so that the creation, editing, approval, viewing and other permissions of users in different levels and departments are different, which can meet the needs of cross-level and cross-department users to approve business matters. On the basis of the user role corpus, combined with the matter corpus to record the review status of business matters and parent-child matters with cascading relationships, it can meet the needs of cross-level multi-copy synchronization update status in multiple business approval scenarios such as creating new business matters, editing business matters, and synchronizing business matters. The chain structure of the cascading relationship between parent-child matters is adopted to record the cascading relationship between parent node matters and child node matters in a series of approval links from creation to submission for review, to approval or rejection, and then to forward and reverse updates. The approval status of business matters is changed synchronously through tracing back the cascading relationship layer by layer. Therefore, this solution can effectively respond to the approval needs of users across levels and departments and different business matters, and more efficiently execute the approval process of business matters in different approval scenarios, making the approval process of business matters more flexible and convenient.

[0090] Fig.12 This is a structural block diagram of a corpus-based business approval device provided in an embodiment of the present disclosure. The device can be used to implement the above-mentioned corpus-based business approval method. The device can be implemented by software and / or hardware. Fig.12 The corpus-based business approval device may include the following modules:

[0091] The user configuration module 210 is used to configure the role table, the user table and the user role association table to generate a user role corpus; wherein the role table is used to record the role information of users of multiple levels and multiple departments, the user table is used for the identity information of the users, and the user role association table is used to record the roles, management scopes and permissions corresponding to the users;

[0092] The item configuration module 220 is used to configure the business item table, the review table, the label table and the online process table to generate an item corpus; wherein the business item table is used to record business items, the review table is used to record business items to be reviewed by the user, the label table is used to record label information of the business items, and the online process table is used to record the review status of parent and child items with a cascading relationship;

[0093] The business approval module 230 is used to execute the business approval process based on the user role corpus and the matter corpus.

[0094] In some embodiments, the business approval module 230 is further used to:

[0095] A first review application unit, used for the first user terminal to initiate a review application message of the current business item to the second user terminal, and record the current business item in the review table;

[0096] An approval operation unit, used for the second user end to receive the current business item to be approved from the review table, and to establish a sub-business item having a cascade relationship of parent and child items with the current business item by performing an approval operation on the current business item, and to change the approval status of the current business item and the sub-business item;

[0097] The second review application unit is used for the second user terminal to take the sub-business item as a new current business item and initiate a review application message for the new current business item to the third user terminal; wherein the first user terminal, the second user terminal and the third user terminal are terminals where users of different levels and / or different departments in the user role corpus are located.

[0098] In some embodiments, the first review application unit is further used to:

[0099] The first user terminal creates a current business item according to the creation operation, and submits a review application message of the current business item to the second user terminal;

[0100] The first user terminal performs an editing operation on the current business item in the business item table, and submits a review application message of the edited business item to the second user terminal;

[0101] The first user terminal performs a deletion operation on the current business item in the business item table, and submits a review application message for deleting the current business item to the second user terminal;

[0102] The first user terminal performs a synchronization operation on the current business item in the reference item corpus, and submits a review application message for synchronizing the current business item to the second user terminal; wherein the reference item corpus is included in the item corpus.

[0103] In some embodiments, the first review application unit is further used to:

[0104] After the current business item is approved, the first user terminal performs a cancellation operation on the current business item in the business item table, and submits a review application message for canceling the current business item to the second user terminal.

[0105] In some embodiments, the approval operation unit is further used to:

[0106] When the second user terminal is approving the current business item, changing the approval status of the current business item and the sub-business item to a pending approval status;

[0107] When the second user terminal approves the current business item, the approval status of the current business item and the sub-business item is changed to the approved status;

[0108] When the second user terminal approves and rejects the current business item, the approval status of the current business item and the sub-business item is changed to a rejected status.

[0109] In some embodiments, the apparatus further comprises:

[0110] Each time the approval status is changed, the approval status of all business items having the cascade relationship is changed, and the changed approval status of the current business item and the sub-business items is recorded in the online process table.

[0111] In some embodiments, the apparatus further comprises:

[0112] When the current business item is approved, the current business item is formalized and written into the business item table.

[0113] In some embodiments, the business approval module 230 is further used to:

[0114] After the first user terminal initiates the review application message of the current business matter, approval restrictions are implemented on the current business matter to block the authority of other user terminals to submit the current business matter; wherein, there are multiple users with the same role information in the user role corpus, and among the multiple users with the same role information, the terminal of the user who first initiates the review application message of the current business matter is taken as the first user terminal.

[0115] The implementation principle and technical effects of the device provided in this embodiment are the same as those of the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference may be made to the corresponding contents in the aforementioned method embodiment.

[0116] Fig.13 The structure diagram of an electronic device provided by the embodiment of the present disclosure is shown in FIG. Fig.13 As shown, the electronic device 300 includes one or more processors 301 and a memory 302 .

[0117] The processor 301 may be a central processing unit (CPU) or other forms of processing units having data processing capabilities and / or instruction execution capabilities, and may control other components in the electronic device 300 to perform desired functions.

[0118] The memory 302 may include one or more computer program products, and the computer program product may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, a random access memory (RAM) and / or a cache memory (cache), etc. The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 301 may run the program instructions to implement the corpus-based business approval method of the embodiment of the present disclosure described above and / or other desired functions. Various contents such as input signals, signal components, noise components, etc. may also be stored in the computer-readable storage medium.

[0119] In one example, the electronic device 300 may further include: an input device 303 and an output device 304 , and these components are interconnected via a bus system and / or other forms of connection mechanisms (not shown).

[0120] In addition, the input device 303 may also include, for example, a keyboard, a mouse, and the like.

[0121] The output device 304 can output various information to the outside, including the determined distance information, direction information, etc. The output device 304 can include, for example, a display, a speaker, a printer, a communication network and a remote output device connected thereto, and the like.

[0122] Of course, to simplify, Fig.13 Only some of the components related to the present disclosure in the electronic device 300 are shown, and components such as a bus, an input / output interface, etc. are omitted. In addition, according to specific application situations, the electronic device 300 may also include any other appropriate components.

[0123] Furthermore, this embodiment also provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is used to execute the above-mentioned corpus-based business approval method.

[0124] The computer program product of a corpus-based business approval method, device, electronic device and medium provided in the embodiments of the present disclosure includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the method described in the previous method embodiments. The specific implementation can be found in the method embodiments, which will not be repeated here.

[0125] It should be noted that, in this article, relational terms such as "first" and "second" are only 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 these entities or operations. Moreover, the terms "include", "comprise" 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 includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0126] The above description is only a specific embodiment of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A corpus-based business approval method, It is characterized in that include: The role table, user table and user role association table are configured to generate a user role corpus; wherein the role table is used to record the role information of users of multiple levels and multiple departments, the user table is used for the identity information of the users, and the user role association table is used to record the roles, management scopes and permissions corresponding to the users; The business item table, the review table, the label table and the online process table are configured to generate an item corpus; wherein the business item table is used to record business items, the review table is used to record business items to be reviewed by the user, the label table is used to record label information of the business items, and the online process table is used to record the review status of parent and child items with a cascading relationship; A business approval process is executed based on the user role corpus and the matter corpus.

2. The method according to claim 1, It is characterized in that The executing the business approval process based on the user role corpus and the matter corpus includes: The first user terminal initiates a review application message of the current business item to the second user terminal, and records the current business item in the review table; The second user terminal receives the current business item to be approved from the review table, and, by performing an approval operation on the current business item, establishes a sub-business item having a cascade relationship of a parent and a child with the current business item, and changes the approval status of the current business item and the sub-business item; The second user terminal takes the sub-business item as a new current business item and initiates an audit application message for the new current business item to the third user terminal; wherein the first user terminal, the second user terminal and the third user terminal are terminals where users of different levels and / or different departments in the user role corpus are located.

3. The method according to claim 2, It is characterized in that The first user terminal initiates a review application message of the current business matter to the second user terminal, including: The first user terminal creates a current business item according to the creation operation, and submits a review application message of the current business item to the second user terminal; The first user terminal performs an editing operation on the current business item in the business item table, and submits a review application message of the edited business item to the second user terminal; The first user terminal performs a deletion operation on the current business item in the business item table, and submits a review application message for deleting the current business item to the second user terminal; The first user terminal performs a synchronization operation on the current business item in the reference item corpus, and submits a review application message for synchronizing the current business item to the second user terminal; wherein the reference item corpus is included in the item corpus.

4. The method according to claim 2, It is characterized in that The first user terminal initiates a review application message of the current business matter to the second user terminal, including: After the current business item is approved, the first user terminal performs a cancellation operation on the current business item in the business item table, and submits a review application message for canceling the current business item to the second user terminal.

5. The method according to claim 2, It is characterized in that The changing of the approval status of the current business item and the sub-business item includes: When the second user terminal is approving the current business item, changing the approval status of the current business item and the sub-business item to a pending approval status; When the second user terminal approves the current business item, the approval status of the current business item and the sub-business item is changed to the approved status; When the second user terminal approves and rejects the current business item, the approval status of the current business item and the sub-business item is changed to a rejected status.

6. The method according to claim 2, It is characterized in that The method further comprises: Each time the approval status is changed, the approval status of all business items having the cascade relationship is changed, and the changed approval status of the current business item and the sub-business items is recorded in the online process table.

7. The method according to claim 2, It is characterized in that The method further comprises: When the current business item is approved, the current business item is formalized and written into the business item table.

8. The method according to claim 1 or 2, It is characterized in that The executing the business approval process based on the user role corpus and the matter corpus includes: After the first user terminal initiates the review application message of the current business matter, approval restrictions are implemented on the current business matter to block the authority of other user terminals to submit the current business matter; wherein, there are multiple users with the same role information in the user role corpus, and among the multiple users with the same role information, the terminal of the user who first initiates the review application message of the current business matter is taken as the first user terminal.

9. A business approval device based on corpus, It is characterized in that include: A user configuration module is used to configure the role table, user table and user role association table to generate a user role corpus; wherein the role table is used to record the role information of users of multiple levels and multiple departments, the user table is used for the identity information of the users, and the user role association table is used to record the roles, management scopes and permissions corresponding to the users; The item configuration module is used to configure the business item table, the review table, the label table and the online process table to generate an item corpus; wherein the business item table is used to record business items, the review table is used to record business items to be reviewed by the user, the label table is used to record label information of the business items, and the online process table is used to record the review status of parent and child items with a cascading relationship; The business approval module is used to execute the business approval process based on the user role corpus and the matter corpus.

10. An electronic device, It is characterized in that The electronic device comprises: processor; a memory for storing instructions executable by the processor; The processor is used to read the executable instructions from the memory and execute the instructions to implement the method described in any one of claims 1-8.

11. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores instructions, and when the instructions are executed on a terminal device, the terminal device implements the method according to any one of claims 1 to 8.

Images