CN106251114B - Method and device for realizing approval in application - Google Patents
Method and device for realizing approval in application Download PDFInfo
- Publication number
- CN106251114B CN106251114B CN201610349262.8A CN201610349262A CN106251114B CN 106251114 B CN106251114 B CN 106251114B CN 201610349262 A CN201610349262 A CN 201610349262A CN 106251114 B CN106251114 B CN 106251114B
- Authority
- CN
- China
- Prior art keywords
- approval
- approver
- application
- user
- request packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The invention provides a method for realizing approval in application, which comprises the following steps: the server receives an application approval request packet sent by an application; obtaining an approval relation according to the identification information in the application approval request packet; obtaining role data according to the enterprise identification contained in the identification information, and obtaining an organization structure from the role data; carrying out recursive search on the relational approver in the organization framework, and generating approver data by the relational approver obtained by the recursive search; and responding to the application approval request packet according to the approver data, and automatically setting an approver in the application through the response. In addition, a device matched with the method for realizing approval in the enterprise social network is also provided. The method and the device for realizing the examination and approval in the application can set the approver in a self-adaptive manner in the realization of the examination and approval function, and further improve the self-adaptability of the setting of the approver.
Description
Technical Field
The invention relates to the technical field of internet application, in particular to a method and a device for realizing approval in application.
Background
With the rapid development of internet application technology, various enterprise management applications exist at present to network the daily office companies of the enterprise, and further facilitate communication and cooperative work among members in the enterprise.
The networking of the real working scene is increasingly realized through enterprise management application, and further more and more enterprise office functions are provided in the enterprise management application.
The provided enterprise office functions comprise an approval function, the approval function is used for networking approval processes such as reimbursement and the like, but most related approvers are fixed and unchangeable for the existing approval function, for example, for enterprise members applying for approval at will, the set approvers are specific personnel and cannot be set in a self-adaptive manner according to the enterprise members applying for approval, and further the setting of the approvers in the realization of the approval function is lack of adaptability.
Disclosure of Invention
Based on this, it is necessary to provide a method for implementing approval in an application, which can adaptively set an approver in implementing an approval function, thereby improving the adaptivity of the approver setting.
In addition, there is a need to provide a device for implementing approval in an application, which can adaptively set an approver in implementing an approval function, thereby improving the adaptivity of the approver setting.
A method for enabling approval in an application, comprising:
the server receives an application approval request packet sent by an application;
obtaining an approval relation according to the identification information in the application approval request packet;
obtaining role data according to the enterprise identification contained in the identification information, and obtaining an organization structure from the role data;
carrying out recursive search on the relational approver in the organization framework, and generating approver data by the relational approver obtained by the recursive search;
and responding to the application approval request packet according to the approver data, and automatically setting an approver in the application through the response.
A method for enabling approval in an application, comprising:
monitoring to obtain an application approval instruction triggered in an application;
responding to the application approval instruction to generate an application approval request packet, and sending the application approval request packet to a server;
receiving a response of the server to the application approval request packet to obtain approver data automatically matched with the server;
and automatically setting an approver in the application according to the approver data.
An apparatus for implementing approval in an enterprise social network, comprising:
the application receiving module is used for receiving an application approval request packet sent by an enterprise social network;
the relation obtaining module is used for obtaining an approval relation according to the identification information in the application approval request packet;
the role data acquisition module is used for acquiring role data according to the enterprise identification contained in the identification information and acquiring an organization architecture from the role data;
the recursion searching module is used for carrying out recursion searching on the relational approver in the organization framework and generating approver data by the relational approver obtained by the recursion searching;
and the response module is used for responding to the application approval request packet according to the approver data and automatically setting the approver in the application through the response.
An apparatus for enabling approval in an application, comprising:
the application interception module is used for intercepting an application approval instruction triggered in an application;
the application package module is used for responding to the application approval instruction to generate an application approval request package and sending the application approval request package to a server;
the response receiving module is used for receiving the response of the server to the application approval request packet to obtain the approver data automatically matched with the server;
and the automatic setting module is used for automatically setting the approver in the application through the approver data.
In order to solve the technical problems, the following technical scheme is adopted:
the server receives an application approval request packet sent by an application, acquires an approval relationship from identification information in the application approval request packet, further acquires role data according to an enterprise identification contained in the identification information, acquires an organization structure from the role data, performs recursive search of a relational approver in the organization structure, generates the relational approver data acquired by the recursive search into approver data, responds to the application approval request packet according to the approver data, and automatically sets the approver in the application through the response, so that automatic matching and setting of the approver can be realized in the application, that is, the approver can be adaptively set in the realization of an approval function, and the adaptability of setting of the approver is improved.
Drawings
FIG. 1 is a flow diagram that illustrates a method for performing an approval process in an application, according to one embodiment;
FIG. 2 is a flowchart of a method of FIG. 1 for obtaining approval relationships based on identification information in an application approval request package;
FIG. 3 is a flow chart of a method for performing approval in an application according to another embodiment;
FIG. 4 is a flowchart of a method for performing approval in an application according to another embodiment;
FIG. 5 is a flow diagram that illustrates a method for performing an approval process in an application, according to an embodiment;
FIG. 6 is a flowchart of a method for performing approval in an application according to another embodiment;
FIG. 7 is a diagram of a user add page of an application in one embodiment;
FIG. 8 is a flowchart of a method for performing approval in an application according to another embodiment;
FIG. 9 is a schematic diagram of a page implementing a full name application;
FIG. 10 is a flowchart of a method for trigger-based approver management, obtaining enterprise identification and approver setting information in the listening application of FIG. 8;
FIG. 11 is a timing diagram for implementing the approval for reimbursement in one embodiment;
FIG. 12 is a schematic diagram of an interface for an approver display in one embodiment;
FIG. 13 is a block diagram of an apparatus for performing approval in an exemplary application;
FIG. 14 is a schematic diagram of the structure of the relationship obtaining module of FIG. 13;
FIG. 15 is a schematic structural diagram of an apparatus for carrying out approval in application of another embodiment;
FIG. 16 is a schematic structural diagram of an apparatus for carrying out approval in application of another embodiment;
FIG. 17 is a block diagram of an apparatus for performing approval in an exemplary application;
FIG. 18 is a schematic structural diagram of an apparatus for carrying out approval in application of another embodiment;
FIG. 19 is a schematic structural diagram of an apparatus for carrying out approval in application of another embodiment;
FIG. 20 is a schematic diagram of the structure of an approver management interception module of FIG. 19;
fig. 21 is a schematic structural diagram of a server according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments that embody features and advantages of the invention are described in detail below in the specification. It is to be understood that the invention is capable of other embodiments and that various changes in form and details may be made therein without departing from the scope of the invention and the description and drawings are to be regarded as illustrative in nature and not as restrictive.
In one embodiment, the method for implementing approval in the application is shown in fig. 1, and includes:
and step 110, the server receives an application approval request packet sent by the application.
The application that sends the application approval request packet to the server is any application having an approval function, and is run on the terminal. The user can apply for approval through the approval function of the application at any time by triggering the application in the terminal to run. In one embodiment, the referenced application may be an enterprise social networking application.
The enterprise social network application is an office tool, namely an office communication tool, and the communication function and the office function inside an enterprise can be realized through the enterprise social network application by taking members inside the enterprise as users of the enterprise social network application.
The application approval request packet received by the server is generated and sent to the server when the user triggers an approval function in the application and applies for approval.
In a specific implementation, after receiving the application approval request packet sent by the application, the server further performs validity judgment on the application approval request packet, and may execute step 130 when the application approval request packet obtained by the judgment is a valid request.
And if the request packet for application examination and approval is judged to be not legal, namely the application examination and approval operation triggered in the application is illegal, refusing to execute and returning a corresponding error code in the packet.
It should be noted that the validity judgment includes (1) whether the encryption processing of the application approval request packet is correct; (2) and (4) verifying whether the user applying for approval is a legal authorized user or not through a session key.
And step 130, obtaining the approval relationship according to the identification information in the application approval request packet.
The application approval request packet at least carries identification information, and the identification information is used for uniquely marking enterprises and users.
It should be noted that, the application is specific to each enterprise, that is, the enterprise can implement the communication function and the office function between its internal members through the application. Therefore, in the application, the enterprise and the internal member of the enterprise, namely the user, need to be uniquely identified through the identification information.
The approval relationship is used for automatically setting an approver for a user applying for approval. The approval relationship comprises a designated approver and/or a relational approver, and the approval relationship is uniquely corresponding to the enterprise identifier in the identification information, namely for any enterprise, the approval relationship uniquely corresponds to the enterprise identifier.
Whereby the storage of the approval relationship in the server will be made dependent on the identification information. In a specific implementation, the storage of the approval relationship is implemented by unique identification of the enterprise by the identification information.
Therefore, the approval relationship can be obtained in the server according to the identification information in the application approval request packet, and the approval relationship is effective for the users in the corresponding enterprises, namely the users applying for approval.
And 150, obtaining role data according to the enterprise identification contained in the identification information, and obtaining an organization architecture from the role data.
The obtained approval relationships include relational approvers, and thus the storage by the server for the enterprise includes the approval relationships as described above, in addition to role data. The role data for the enterprise will also be stored indexed by the enterprise identification.
Therefore, after the server receives the application approval request packet, the role data can be obtained according to the enterprise identifier contained in the identification information in the application approval request packet.
The identification information includes a user identification in addition to the enterprise identification. And acquiring the organization structure related to the user identification in the role data of the related enterprise according to the user identification.
Wherein the user identification associated organizational structure is part of a corresponding enterprise organizational structure. Specifically, the project group where the user is located and the upper project group of the user form an organization structure related to the user identifier.
And 170, carrying out recursive search on the relational approver in the organization framework, and generating approver data by the relational approver obtained by the recursive search.
The designated approver and/or the designated relational approver can be obtained through the approval relationship. Therefore, the automatic matching of the approvers can be performed through the approval relationship, and the approver data capable of automatically setting the approvers for the user applying for approval can be obtained.
In the case where the approval relationship includes a designated relational approver, recursive search of the relational approver will be performed in the organizational framework provided by the role data.
The relational approver in the approval relationship is used for specifying the relationship between the user and the approver, and further, other users who have the relationship with the user can become the approver in the approval process applied by the user.
It should be noted that there may be a plurality of relational approvers in the approval relationship, and in the approval relationship in which a plurality of relational approvers are specified, a relationship hierarchy exists between the plurality of relational approvers. And obtaining a plurality of approvers according to a plurality of relational approvers appointed in the approval relationship, and carrying out multi-stage approval through the obtained plurality of approvers.
The role data of the enterprise records the project group in which each user in the enterprise is located and the identity of each user in the project group. In addition, the organizational structure of the enterprise is also recorded. The organizational structure of an enterprise includes multiple project groups of the enterprise.
It should be noted that the term group refers to a set formed by a plurality of users constructed according to an organization structure in an enterprise, and for example, the term group may correspond to a department or a group in the enterprise, and is not limited herein, and is flexibly set according to the needs of actual operation.
In the role data of the enterprise, the approval relationship calculation is carried out according to the relation type approver appointed in the approval relationship, so that other users of which the relative users can become the relation type approver appointed in the approval relationship can be obtained, and the approver data is obtained correspondingly.
Through the process, the server can adaptively match the approver for the user, and further obtain other users which are consistent with the specified relational approver in the approval relation, so that the approver becomes an approver automatically set in the application, and the automatic setting of the approver in the application is realized.
It can be understood that the approval relationship may include a designated approver and a relational approver, so as to automatically set a multi-level approval process including the existence of multiple types of approvers for a user applying for approval, thereby adapting to the requirement of implementing the approval process.
In a specific implementation, the relational approver includes a superordinate relational approver. The higher-level relation approver refers to an approver who can be a user by other users at the higher level of the user. Therefore, in the obtained organization structure, the direct superior level of the user is found by taking the item group where the user is located as the starting point.
In the searching process, if the user is the upper level of the project group, or all the users of the project group are not the 'upper level' identity, the user recurs to the upper level organization structure of the project group to search the direct upper level, and the recursion is carried out to the upper level organization structure until the upper level is found.
And after the recursive search of the superior relation approver is completed, generating the approver data by the superior relation approver obtained by the recursive search.
The recursive search process of the approver with the approval relationship including the plurality of superior relationships is similar to the search process, namely, the process is repeatedly executed until the recursive search of the last superior relationship approver in the approval relationship is completed.
Through the process, recursive search of the approver is realized, and the approver can be automatically set for the user in a self-adaptive manner in the organization architecture of the enterprise, so that the setting of the approver in application can be matched with the actual organization architecture of the enterprise, and the accuracy and the effectiveness of automatic setting of the approver are improved.
And 190, responding to the application approval request packet according to the approver data, and automatically setting the approver in the application according to the response.
And the server responds to the application approval request packet sent by the application according to the approver data so as to automatically set an approver for approval applied in the implementation of the application as an approval function.
Through the process, the server can adaptively provide the data of the approver for the application applying for approval, so that the automatic setting of the approver in the application is realized, and the automatically set approver is automatically matched according to the identification information of the user, so that the automatically set approver is adaptive to the user and is not fixed for all users, and the adaptability is greatly enhanced.
In one embodiment, step 130 is shown in FIG. 2, and further comprises:
and step 131, extracting the enterprise identification contained in the identification information in the application approval request packet.
The identification information carried by the application approval request contains enterprise identification, so that after the server receives the application approval request packet sent by the application, the enterprise identification contained in the identification information is extracted and obtained by the application approval request packet.
And step 133, searching the stored approval relationship according to the enterprise identifier to obtain the approval relationship corresponding to the enterprise identifier.
The server stores the approval relations of a plurality of enterprises, and the approval relations of each enterprise are stored by taking the enterprise identification as an index. Therefore, in the stored approval relationship, the approval relationship corresponding to the enterprise identifier is obtained by searching according to the enterprise identifier.
It can be seen that the approval relationship is uniquely corresponding to the corresponding enterprise, in other words, the approval relationship will be valid for all members, i.e., users, in the enterprise. The approval relationship provides a setting principle of an approver for approving all member applications of corresponding enterprises, so that the approver adapted to a user can be automatically obtained under the guidance of the approval relationship, and the possibility of realizing the automatic setting of the approver is provided.
In one embodiment, the obtained approval relationship includes a designated approver, and the method as described above further includes: and extracting data according to the approver appointed in the approval relationship to obtain approver data.
On one hand, the setting of the approver in the application can be a pre-designated approver, namely, the approver is included in the approval relationship obtained according to the identification information in the application approval request packet. The designated approver designates a specific user as the approver for the approval implementation in the enterprise.
And if the obtained approval relationship comprises the specified approver, directly taking out the approver data.
The obtained approval relationship may only include the designated approver, and on the other hand, the obtained approval relationship is not limited thereto, so that the server responds to the application request packet according to the approver data, including the approver data corresponding to the designated approver, and may further include other approver data.
In addition, if a plurality of designated approvers are included in the approval relationship, a relationship hierarchy exists in the designation of the plurality of approvers; therefore, correspondingly, the extracted approver data is also directly extracted according to the specified plurality of approvers, and the hierarchy among the plurality of approvers is established according to the existing relationship hierarchy.
For example, if the approval relationship includes user a, user B, and user C, user a, user B, and user C are designated as approvers in the approval relationship, and among the three approvers, user a will be used as a first-level approver, user B will be used as a second-level approver, and user C will be used as a third-level approver.
Therefore, by designating the approver in the approval relationship, the corresponding enterprise can provide the designated approver for the approval process of the user in the approval function, and the approval function in the application can meet the requirements of the enterprise in reality.
In one embodiment, the method as described above is illustrated in fig. 3, further comprising:
in step 210, the server receives a user addition request packet sent by an application.
The user adding request packet is initiated by the user adding a new user for the enterprise in which the user is located. In this process, the user referred to is the user of the administrator identity in the application.
In the application, an enterprise is provided with one or more users with administrator identities, and other users are used as common users in the enterprise.
The user of the administrator identity adds new users in the enterprise through the application operated by the terminal of the user; for the server, the new user addition it implements will be implemented by the user add request package.
In specific implementation, the user addition request packet includes identification information, a user identification for triggering user addition operation, an application identification, all information fields of a user, and an operation timestamp, and a final user addition request packet is obtained by encrypting the user addition request packet and is sent to the server.
Therefore, the server also performs validity judgment after receiving the user addition request packet, and a new user can be added after the validity judgment is passed. In a preferred embodiment, this process will additionally record the time of the last operation and the user that triggered the user add operation.
And step 230, executing user adding operation of the corresponding enterprise according to the user adding request packet.
After receiving the user adding request packet, the server executes user adding operation according to the content in the user adding request packet, so that the new user can realize the related functions of the enterprise where the new user is located in the application.
And step 250, after the user adding operation is completed, updating the role data of the corresponding enterprise according to the identity field in the user adding request packet.
The identity field is used for indicating the identity of the project group to which the user belongs in the enterprise. In one embodiment, the identity field includes a superior level and a common member, and the identity field of the user may be any one of these, which is not limited herein.
And after the new user is added, the server updates the role data of the corresponding enterprise according to the project group where the new user is located, and updates the identity of the new user in the role data according to the identity field in the user addition request packet.
In other words, the role data update performed by the identity field in the user addition request packet enables the server to add the new user and the identity of the new user to the role data stored by the enterprise.
In a specific actual operation, the identity field of the user may be extracted from all information fields of the user in the user addition request packet.
In one embodiment, the method as described above further comprises:
and judging whether an approval relationship corresponding to the identification information exists, if not, generating approver data according to the historical approver corresponding to the identification information, and if so, executing the step 130.
In the process of searching the approval relationship stored in the server according to the identification information, if the corresponding enterprise does not store the approval relationship in the server, the historical approver set by the user for approval can be obtained according to the identification information, so that the automatic setting of the approver in the application of the user is realized, and the validity of the automatic setting of the approver can be ensured.
In one embodiment, the method as above is shown in fig. 4, further comprising:
in step 310, the server receives an approval setting request packet sent by an application.
The examination and approval setting request packet is used for realizing the setting and updating of the examination and approval relationship in the enterprise. And sending the examination and approval setting request packet to the server by the application, triggering the management of the examination and approval people of the enterprise in the server, and further setting or updating the examination and approval relations which take effect on all members of the enterprise.
In the concrete implementation, the management of the approvers is the process of adding, deleting and changing the approvers.
In an embodiment, the approval setting request packet includes identification information, a user identification triggering the approval setting operation, an application identification, approver setting information, and an operation timestamp, in other words, the approval setting request packet is finally obtained after the contents are encrypted.
Therefore, in a preferred embodiment, the server performs a validity judgment on the received approval setting request packet, and step 330 may be performed after the validity judgment is passed.
The approval setting request packet sent by the user through the application carries the enterprise identification and the approval person setting information. The approver setting information is used for realizing generation and storage of the approver relationship corresponding to the corresponding enterprise.
Specifically, the approval setting information includes a designated approver and/or a set relational approver, and the designated approver and/or the set relational approver can obtain a mutual relation hierarchy. In one embodiment, the set relational approver is a superordinate relational approver.
For example, the approval setting information includes two higher-level relation approvers, and the corresponding relation hierarchy is two levels, so that for the user applying for approval, the directly higher level of the project group where the user is located serves as the first-level approver, and then the directly higher level of the first-level approver is found on the basis of the first-level approver and serves as the second-level approver;
on the basis, if the approval setting information further comprises the specified approver, and the corresponding relationship hierarchy is three levels, namely, the superior relationship approver and the specified approver are three levels, after the second-level approver is found, the specified approver is used as the third-level approver.
And 350, generating the approval relationship of the enterprise through the information set by the approver, and storing the approval relationship by taking the enterprise identification as an index.
And the server acquires the examination and approval setting information from the examination and approval setting request packet, and then generates examination and approval relations for corresponding enterprises according to the examination and approval setting information, and stores the examination and approval relations so as to take effect on all users in the enterprises.
Through the process, the server matched with the application with the approval function is realized, and further through the process, the server realizes the automatic setting of an approver in the enterprise social network application, and the realization of the approval function in the application is optimized.
In addition, a method for implementing approval in an application is correspondingly provided, and as shown in fig. 5, the method includes:
and step 410, intercepting and obtaining an application approval instruction triggered in the application.
As mentioned before, the enterprise-social network application will run on the terminal of each user himself. The user is the member of the enterprise that uses the application.
The application triggers the self-equipped approval function, and the approval function comprises the realization of an approval process, an approval setting process and the updating of role data related to the addition of a user.
For the realization of the approval process in the application, firstly, the approval application is triggered in the application, and an application approval instruction is generated.
On the user plane, in one embodiment, this process is implemented by triggering and clicking a corresponding button in the application, for example, a "i want to reimburse" button may be clicked in the application to initiate the application approval process, and then an application approval instruction is generated accordingly.
And 430, generating an application approval request packet in response to the application approval instruction, and sending the application approval request packet to a server.
The content of the application and approval request packet comprises fields such as a user identifier, an application identifier, an operation timestamp and the like of application and approval, so that when an application and approval instruction is responded, required fields are obtained to combine to obtain a packet body of the application and approval request packet, and then a final application and approval request packet is obtained and sent to a server.
And step 450, receiving the response of the server to the request packet for application and approval to obtain the data of the approver automatically matched with the server.
The application which sends the application approval request packet receives a response packet of the server, and the response packet is a response of the server to the application approval request packet, so that the approver data which is automatically matched with the server can be obtained.
And 470, automatically setting the approver in the application through the approver data.
Through the process, after the application is applied for approval, the application can automatically set an approver for the approval of the current application through interaction with the server, so that the intelligent degree and the adaptability of the approval function in the application are improved.
After the automatic setting of the approver in the application is completed, the subsequent approval process can be completed. Specifically, after the input and extraction of the approval information are completed in the application, the approval information is obtained and an approval request packet is generated corresponding to the automatically set approver, and the approval request packet is sent to the server.
And the server writes the examination and approval information in the examination and approval request packet into a storage, informs related approvers of examining and approving to obtain a final examination and approval result, and returns the final examination and approval result to the enterprise social network.
Taking the approval of reimbursement as an example, in the process of reimbursement and approval, the approval information includes information such as user identification of applying for approval, enterprise identification, application time, reimbursement type, reimbursement reason, reimbursement details, expense type, occurrence time, expense amount, expense description, certification material, and the like.
In one embodiment, as shown in fig. 6, the method as described above further comprises:
step 510, intercepting the identity settings in the user addition and the user addition triggered in the application, and obtaining the enterprise identification and all the information fields of the user.
As previously described, the application may initiate the addition of a new user. In other words, the user of the administrator identity in the application triggers the user adding operation, and the user adding page of the application inputs all the information fields of the user, where the process of inputting all the information fields of the user includes an identity setting process, that is, as shown in fig. 9, after the input is completed, the user adding operation is completed through storage, and the application obtains the enterprise identification and all the information fields of the user.
FIG. 7 illustrates a user add page 600 applied in one embodiment where the identity setting is a selection 610 of an identity item in the user add page 600.
Further, in this embodiment, step 510 includes: and triggering user addition in the interception application, perfecting and generating all information fields of the user according to the identity field setting and other fields in the user addition, and acquiring enterprise identification.
And 530, generating a user adding request packet according to the enterprise identification and all the information fields of the user, and sending the user adding request packet to the server.
And 550, executing user adding operation of the corresponding enterprise on the server through the user adding request packet, and updating the role data corresponding to the enterprise identifier.
Through the process, the addition of the user is realized in the application, and in the addition process of the user, the corresponding role data is updated, so that the automatic setting of the approver in the realization of the subsequent approval function can be optimized, and effective data support is provided for the automatic setting of the approver.
In another embodiment, as shown in fig. 8, the method as described above further comprises:
And step 730, generating an approval setting request packet according to the enterprise identification and the approver setting information, and sending the approval setting request packet to a server.
And step 750, generating the approval relationship of the enterprise in the server through the approval setting request packet.
Through the process, an independent setting inlet is arranged in the application, so that the examination and approval relationship of the enterprise can be conveniently set, and the set examination and approval relationship can take effect on all enterprise members, so as to configure the process in the application.
In a preferred embodiment, the administrator-identified user realizes the management of the approver of the enterprise through an application operated by the terminal.
As indicated in fig. 9, taking the reimbursement approval as an example, in the application page 810, by triggering the process setting to be performed and popping up an interface 830 for selecting an approver on the application page 810, the user with the administrator identity can complete the approver management of the enterprise through the interface 830 for selecting the approver.
Further, in this embodiment, step 710 is shown in fig. 10, and includes:
and 711, triggering the management of the approvers in the interception application to obtain the selected superior relation approver and/or the designated approver in the selection of the approvers.
And 713, forming approver setting information by the approver with the superior relationship and/or the specified approver, and acquiring the enterprise identification.
Through the process, the setting of the approver can be automatically realized in the application, namely, the approver and/or the specific approver with the higher-level relation is appointed for realizing the subsequent approval function.
The approval implementation in the application described above can be applied to any approval scene, for example, a leave-asking scene, a document review scene, and the like, and the specified approval relationship is not limited to the superordinate relationship approver, and may be other concepts similar to the superordinate relationship approver, for example, "main editing", and the like.
The following describes an implementation process of approval in the application described above with reference to a specific embodiment. In the present embodiment, the approval of reimbursement will be described as an example.
For convenience, the simple and clear description is carried out, the administrator identity is used for logging in an enterprise management page, and the reimbursement application management page is entered in the enterprise management page through the selected enterprise application, and is regarded as an reimbursement management end; the application which is run on the terminal and the user with the common membership logs in is regarded as the client.
For a server to cooperate with an application, it includes a reimbursement server and a database for storage.
FIG. 11 illustrates a timing sequence for implementing the approval for reimbursement in one embodiment, which real-time will be used to implement enterprise-related approval relationship settings and approval for reimbursement in an application.
Specifically, on the one hand, regarding the approval relationship setting related to an enterprise in the application, the steps 810 to 840 are performed.
On the other hand, the implementation of enterprise-related approval in the application will be realized by executing steps 850 to 891.
The approver returned in step 890 is displayed in the interface 900 as shown in fig. 12, that is, the approver item 910 is displayed in the interface 900, and the corresponding reimbursement information, such as reimbursement type, expense type, time of occurrence, expense amount and the like, is submitted in the interface 900, and then the reimbursement approval can be performed by executing step 891
The application described above is applicable to other processes related to approval besides the approval of reimbursement.
In addition, there is also correspondingly provided an apparatus for implementing approval in an application, which, as shown in fig. 13, includes an application receiving module 1010, a relationship obtaining module 1030, a role data obtaining module 1050, a recursive finding module 1070, and a response module 1090, where:
the application receiving module 1010 is configured to receive an application approval request packet sent by an enterprise social network.
And a relation obtaining module 1030, configured to obtain an approval relation according to the identification information in the application approval request packet.
And a role data obtaining module 1050, configured to obtain role data according to the enterprise identifier included in the identifier information, and obtain the organization structure from the role data.
The recursive search module 1070 is configured to perform recursive search on the relational approver in the organization structure, and generate approver data from the relational approver obtained through the recursive search.
And the response module 1090 is used for responding to the application approval request packet according to the approver data and automatically setting the approver in the application through response.
In one embodiment, the relationship obtaining module 1030 is shown in fig. 14 and includes an enterprise identification extracting unit 1031 and a lookup unit 1033, wherein:
and an enterprise identifier extracting unit 1031, configured to extract an enterprise identifier included in the identifier information in the application approval request packet.
The searching unit 1033 is configured to search for the stored approval relationship according to the enterprise identifier, so as to obtain an approval relationship corresponding to the enterprise identifier.
In one embodiment, the obtained approval relationship comprises a designated approver, and the apparatus as described above further comprises a data obtaining module. The data acquisition module is used for extracting data according to the approver appointed in the approval relationship to obtain approver data.
In one embodiment, the apparatus as described above is shown in fig. 15, and includes an addition request receiving module 1110, an addition operation executing module 1130, and a character data updating module 1150, wherein:
an add request receiving module 1110, configured to receive a user add request packet sent by an application.
The add operation execution module 1130 is configured to execute a user add operation of a corresponding enterprise according to the user add request packet.
And a role data updating module 1150, configured to update the role data of the corresponding enterprise according to the identity field in the user addition request packet after the user addition operation is completed.
In one embodiment, the apparatus as described above further comprises a determination module. The judging module is configured to judge whether an approval relationship corresponding to the identification information exists, if not, generate approver data according to a historical approver corresponding to the identification information, and if so, notify the relationship obtaining module 1030.
In another embodiment, the apparatus as described above is shown in fig. 16, and further includes a setting request receiving module 1210, a request information obtaining module 1230 and a logging module 1250, wherein:
a setting request receiving module 1210, configured to receive an approval setting request packet sent by an application.
A request information obtaining module 1230, configured to obtain the enterprise identifier and the approver setting information from the approval setting request packet.
And the storage module 1250 is configured to generate an approval relationship of the enterprise through the approver setting information, and store the approval relationship by using the enterprise identifier as an index.
Correspondingly, an apparatus for implementing approval in an application is also provided, as shown in fig. 17, including an application interception module 1310, an application package module 1330, a response receiving module 1350 and an automatic setting module 1370, where:
and an application interception module 1310 configured to intercept an application approval instruction triggered in the enterprise social network application.
The application package module 1330 is configured to generate an application approval request package in response to the application approval instruction, and send the application approval request package to the server.
The response receiving module 1350 is configured to receive a response from the server to the request packet for application and approval, so as to obtain approver data automatically matched with the server.
And the automatic setting module 1370 is used for automatically setting the approver in the application through the approver data.
In one embodiment, the apparatus as described above is shown in fig. 18, further comprising a user adding listening module 1410, a user adding group package module 1430, and an updating module 1450, wherein:
and the user adding and intercepting module 1410 is used for intercepting identity settings in user adding and user adding triggered in the application, and acquiring enterprise identifications and all information fields of the users.
And the user adding and packaging module 1430 is configured to generate a user adding request packet according to the enterprise identifier and all the information fields of the user, and send the user adding request packet to the server.
The updating module 1450 is configured to execute a user adding operation of a corresponding enterprise on the server through the user adding request packet and update the role data corresponding to the enterprise identifier.
Further, in this embodiment, the user adding interception module 1410 is further configured to intercept user addition triggered in the application, generate all information fields of the user according to identity field setting and perfection of other fields performed in the user addition, and acquire an enterprise identifier.
In another embodiment, the apparatus as described above is shown in fig. 19, further comprising an approver management listening module 1510, an approve setting request group package module 1530, and a relationship generation module 1550, wherein:
the approver management interception module 1510 is configured to intercept approver management triggered in the application, and acquire an enterprise identifier and approver setting information.
The approval setting request packaging module 1530 is configured to generate an approval setting request package according to the enterprise identifier and the approver setting information, and send the approval setting request package to the server.
And the relationship generation module 1550 is configured to generate an approval relationship of the enterprise in the server through the approval setting request packet.
Further, in this embodiment, the approver management listening module 1510 is shown in fig. 20, and includes an approver obtaining unit 1511 and a setting information forming unit 1513, where:
the approver obtaining unit 1511 is configured to trigger approver management in the interception application, and obtain the selected approver and/or the designated approver in the approver selection.
And a setting information forming unit 1513, configured to form approver setting information by the superordinate approver and/or the designated approver, and obtain the enterprise identifier.
Fig. 21 illustrates a structure of a server according to an embodiment of the present invention, where the server 1600 may have a relatively large difference due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 1610 (e.g., one or more processors) and a memory 1620, and one or more storage media 1630 (e.g., one or more mass storage devices) storing applications 1631 or data 1633. Memory 1620 and storage media 1630 may be transient or persistent storage, among others. The program stored on the storage medium 1630 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a server. Still further, the central processor 1610 may be configured to communicate with the storage medium 1630 and execute a series of instruction operations in the storage medium 1630 on the server 1600. The server 1600 may also include one or more power supplies 1650, one or more wired or wireless network interfaces 1670, one or more input-output interfaces 1680, and/or one or more operating systems 1635, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.
Furthermore, the present invention can be implemented by hardware circuitry or by a combination of hardware circuitry and software instructions, and thus, implementation of the present invention is not limited to any specific hardware circuitry, software, or combination of both.
It will be understood by those skilled in the art that all or part of the steps for implementing the above embodiments may be implemented by hardware, or may be implemented by a program instructing relevant hardware, where the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, etc.
While the present invention has been described with reference to several exemplary embodiments, it is understood that the terminology used is intended to be in the nature of words of description and illustration, rather than of limitation. As the present invention may be embodied in several forms without departing from the spirit or essential characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, but rather should be construed broadly within its spirit and scope as defined in the appended claims, and therefore all changes and modifications that fall within the meets and bounds of the claims, or equivalences of such meets and bounds are therefore intended to be embraced by the appended claims.
Claims (19)
1. A method for implementing approval in an application, comprising:
the server receives a user adding request packet sent by an application;
judging the legality of the user adding request packet;
when the user adding request packet is legal, executing user adding operation of a corresponding enterprise according to the user adding request packet, and recording operation time and a user identifier for triggering the user adding operation;
after the user adding operation is completed, updating the role data of the corresponding enterprise according to the identity field in the user adding request packet;
receiving an application approval request packet sent by an application;
when the application approval request packet is legal, judging whether an approval relation corresponding to the identification information in the application approval request packet exists or not, and if not, generating approver data according to a historical approver corresponding to the identification information; if the request packet exists, obtaining an approval relation according to the identification information in the application approval request packet;
obtaining role data according to the enterprise identification contained in the identification information, and obtaining an organization structure from the role data;
performing a recursive search of a relational approver in the organizational structure, the recursive search comprising: searching the direct superior of the user by taking the project group where the user is located as the initial, if the user is the superior of the project group where the user is located or the project group has no superior, recursion is carried out to the superior organizational structure of the project group to search the direct superior, and the recursion is repeated until the superior is found; generating approver data of the relation type approver obtained by recursive search;
and responding according to the application approval request packet sent by the application corresponding to the approver data so as to automatically set the approver in the application applying for approval.
2. The method of claim 1, wherein the step of obtaining approval relationships based on identification information in the application approval request packet comprises:
extracting enterprise identification contained in the identification information in the application approval request packet;
searching in the stored approval relationship according to the enterprise identification to obtain the approval relationship corresponding to the enterprise identification.
3. The method of claim 1, wherein the obtained approval relationship comprises a designated approver, the method further comprising:
and extracting data according to the approver appointed in the approval relationship to obtain approver data.
4. The method of claim 1, further comprising:
the server receives an approval setting request packet sent by the application;
obtaining enterprise identification and approver setting information from the approval setting request packet;
and generating an approval relationship of an enterprise through the approver setting information, and storing the approval relationship by taking the enterprise identification as an index.
5. A method for implementing approval in an application, comprising:
sending a user addition request packet to a server; so that the server judges the legality of the user adding request packet; when the user adding request packet is legal, executing user adding operation of a corresponding enterprise according to the user adding request packet, and recording operation time and a user identifier for triggering the user adding operation; after the user adding operation is completed, updating the role data of the corresponding enterprise according to the identity field in the user adding request packet;
monitoring to obtain an application approval instruction triggered in an application;
responding to the application approval instruction to generate an application approval request packet, and sending the application approval request packet to a server; when the application approval request packet is legal, judging whether an approval relation corresponding to the identification information in the application approval request packet exists or not, and if not, generating approver data according to a historical approver corresponding to the identification information;
receiving a response of a server to the application approval request packet, so that the server obtains role data according to the enterprise identification contained in the identification information and obtains an organization architecture from the role data; and performing a recursive search of a relational approver in the organizational structure, the recursive search comprising: searching the direct superior of the user by taking the project group where the user is located as the initial, if the user is the superior of the project group where the user is located or the project group has no superior, recursion is carried out to the superior organizational structure of the project group to search the direct superior, and the recursion is repeated until the superior is found; generating approver data by the relation type approver obtained by recursive search, and obtaining the approver data which is automatically matched when the server determines that the approval relation corresponding to the identification information in the application approval request packet exists;
and automatically setting an approver in the application according to the approver data.
6. The method of claim 5, further comprising:
monitoring user addition triggered in application and identity setting in the user addition to obtain enterprise identification and all information fields of the user;
generating a user adding request packet according to the enterprise identification and all the information fields of the user, and sending the user adding request packet to a server;
and executing user adding operation of corresponding enterprises on a server through the user adding request packet and updating role data corresponding to the enterprise identifications.
7. The method according to claim 6, wherein the steps of triggering user addition in the interception application and setting identity in the user addition, obtaining enterprise identification and all user information fields comprise:
and triggering user addition in the interception application, perfecting and generating all information fields of the user according to the identity field setting and other fields in the user addition, and acquiring enterprise identification.
8. The method of claim 5, further comprising:
monitoring the approver management triggered in the application, and acquiring enterprise identification and approver setting information;
generating an approval setting request packet according to the enterprise identification and the approver setting information, and sending the approval setting request packet to a server;
and generating an approval relationship of the enterprise in the server through the approval setting request packet.
9. The method of claim 8, wherein the step of triggering approver management in the listening application to obtain enterprise identification and approver setting information comprises:
monitoring the approver management triggered in the application to obtain the selected superior relation approver and/or the designated approver in the approver selection;
and forming approver setting information by the superior relation approver and/or the appointed approver, and acquiring an enterprise identifier.
10. An apparatus for enabling approval in an application, comprising:
the adding request receiving module is used for receiving a user adding request packet sent by the application;
a request packet validity judging module for judging the validity of the request packet added by the user;
the adding operation execution module is used for executing the user adding operation of the corresponding enterprise according to the user adding request packet when the user adding request packet is legal, and recording the operation time and the user identification for triggering the user adding operation;
the role data updating module is used for updating the role data of the corresponding enterprise according to the identity field in the user adding request packet after the user adding operation is completed;
the application receiving module is used for receiving an application approval request packet sent by an application;
the relation obtaining module is used for judging whether an approval relation corresponding to the identification information in the application approval request packet exists or not when the application approval request packet is legal, and if not, generating approver data according to a historical approver corresponding to the identification information; if the request packet exists, obtaining an approval relation according to the identification information in the application approval request packet;
the role data acquisition module is used for acquiring role data according to the enterprise identification contained in the identification information and acquiring an organization architecture from the role data;
a recursive search module for performing a recursive search of a relational approver in the organizational structure, the recursive search comprising: searching the direct superior of the user by taking the project group where the user is located as the initial, if the user is the superior of the project group where the user is located or the project group has no superior, recursion is carried out to the superior organizational structure of the project group to search the direct superior, and the recursion is repeated until the superior is found; generating approver data of the relation type approver obtained by recursive search;
and the response module is used for responding according to the application approval request packet sent by the corresponding application of the approver data so as to automatically set the approver for approval applied in the implementation of taking the application as an approval function.
11. The apparatus of claim 10, wherein the relationship obtaining module comprises:
the enterprise identification extracting unit is used for extracting enterprise identifications contained in the identification information in the application approval request packet;
and the searching unit is used for searching in the stored approval relationship according to the enterprise identification to obtain the approval relationship corresponding to the enterprise identification.
12. The apparatus of claim 10, wherein the obtained approval relationship comprises a designated approver, the apparatus further comprising:
and the data acquisition module is used for extracting data according to the approver appointed in the approval relationship to obtain approver data.
13. The apparatus of claim 10, further comprising:
the setting request receiving module is used for receiving an approval setting request packet sent by the application;
the request information obtaining module is used for obtaining enterprise identification and approver setting information from the approval setting request packet;
and the storage module is used for generating the approval relationship of the enterprise through the information set by the approver and storing the approval relationship by taking the enterprise identification as an index.
14. An apparatus for enabling approval in an application, comprising:
the adding request packet sending module is used for sending a user adding request packet to the server; so that the server judges the legality of the user adding request packet; when the user adding request packet is legal, executing user adding operation of a corresponding enterprise according to the user adding request packet, and recording operation time and a user identifier for triggering the user adding operation; after the user adding operation is completed, updating the role data of the corresponding enterprise according to the identity field in the user adding request packet;
the application interception module is used for intercepting an application approval instruction triggered in an application;
the application package module is used for responding to the application approval instruction to generate an application approval request package, and sending the application approval request package to a server so that the server can judge the legality of the application approval request package, and when the application approval request package is legal, judging whether an approval relation corresponding to the identification information in the application approval request package exists, if not, generating approver data according to a historical approval person corresponding to the identification information;
a response receiving module, configured to receive a response to the application approval request packet from the server, so that the server obtains role data according to the enterprise identifier included in the identifier information, and obtains an organization structure from the role data; and performing a recursive search of a relational approver in the organizational structure, the recursive search comprising: searching the direct superior of the user by taking the project group where the user is located as the initial, if the user is the superior of the project group where the user is located or the project group has no superior, recursion is carried out to the superior organizational structure of the project group to search the direct superior, and the recursion is repeated until the superior is found; generating approver data by the relation type approver obtained by recursive search, and obtaining the approver data which is automatically matched when the server determines that the approval relation corresponding to the identification information in the application approval request packet exists;
and the automatic setting module is used for automatically setting the approver in the application through the approver data.
15. The apparatus of claim 14, further comprising:
the system comprises a user adding and monitoring module, a user adding and monitoring module and a user adding and monitoring module, wherein the user adding and monitoring module is used for monitoring user adding triggered in application and identity setting in the user adding and obtaining enterprise identification and all information fields of a user;
the user adding and packaging module is used for generating a user adding request packet according to the enterprise identification and all the information fields of the user and sending the user adding request packet to a server;
and the updating module is used for executing user adding operation of corresponding enterprises on the server through the user adding request packet and updating the role data corresponding to the enterprise identifications.
16. The apparatus of claim 14, wherein the subscriber addition interception module is further configured to intercept subscriber additions triggered in an application, generate all subscriber information fields based on identity field settings and other field refinements performed in the subscriber additions, and obtain an enterprise identity.
17. The apparatus of claim 16, further comprising:
the approver management monitoring module is used for monitoring approver management triggered in the application and acquiring enterprise identification and approver setting information;
the approval setting request packaging module is used for generating an approval setting request package according to the enterprise identification and the approver setting information and sending the approval setting request package to a server;
and the relation generation module is used for generating the approval relation of the enterprise in the server through the approval setting request packet.
18. The apparatus of claim 17, wherein the approver management listening module comprises:
the approver obtaining unit is used for monitoring approver management triggered in the application to obtain the selected superior relation approver and/or the designated approver in the approver selection;
and the setting information forming unit is used for forming the setting information of the approver by the higher-level relation approver and/or the appointed approver and acquiring the enterprise identification.
19. A computer-readable storage medium, in which at least one instruction or at least one program is stored, which is loaded and executed by a processor to implement a method of performing an approval as in any one of claims 1 to 4 or any one of claims 5 to 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610349262.8A CN106251114B (en) | 2016-05-24 | 2016-05-24 | Method and device for realizing approval in application |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610349262.8A CN106251114B (en) | 2016-05-24 | 2016-05-24 | Method and device for realizing approval in application |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106251114A CN106251114A (en) | 2016-12-21 |
| CN106251114B true CN106251114B (en) | 2020-05-01 |
Family
ID=57626639
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610349262.8A Active CN106251114B (en) | 2016-05-24 | 2016-05-24 | Method and device for realizing approval in application |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106251114B (en) |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108573371B (en) * | 2018-04-18 | 2023-06-20 | 平安科技（深圳）有限公司 | Data approval method, device, computer equipment and storage medium |
| CN109034606A (en) * | 2018-07-23 | 2018-12-18 | 万翼科技有限公司 | The measures and procedures for the examination and approval, device and the computer readable storage medium of task based access control pause |
| CN109165856B (en) * | 2018-08-31 | 2023-08-08 | 平安科技（深圳）有限公司 | Dynamic configuration method, device and storage medium of approval chain |
| CN110163503A (en) * | 2019-05-22 | 2019-08-23 | 北京秦淮数据有限公司 | Processing method, device and the electronic equipment of modification application |
| CN110363537A (en) * | 2019-05-31 | 2019-10-22 | 平安科技（深圳）有限公司 | Long-range face label record screen transfers method, apparatus, storage medium and computer equipment |
| CN110310090A (en) * | 2019-06-26 | 2019-10-08 | 杭州天宽科技有限公司 | Dynamic electron approval process generation method, device, equipment and medium based on modularization |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102629346A (en) * | 2012-03-05 | 2012-08-08 | 浪潮集团山东通用软件有限公司 | Realization method of personnel assessment relation approval of human resource management information system |
| CN103475685A (en) * | 2012-06-08 | 2013-12-25 | 深圳中兴网信科技有限公司 | Service approval method and system thereof, and mobile approval platform |
| CN103873345A (en) * | 2012-12-14 | 2014-06-18 | 上海格尔软件股份有限公司 | Method for realizing mail approval based on rules |
| CN104318381A (en) * | 2014-10-21 | 2015-01-28 | 中国建设银行股份有限公司 | Background audit task distributing method and device |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105094854A (en) * | 2015-09-30 | 2015-11-25 | 北京恒华伟业科技股份有限公司 | Approval process configuration method and device |
-
2016
- 2016-05-24 CN CN201610349262.8A patent/CN106251114B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102629346A (en) * | 2012-03-05 | 2012-08-08 | 浪潮集团山东通用软件有限公司 | Realization method of personnel assessment relation approval of human resource management information system |
| CN103475685A (en) * | 2012-06-08 | 2013-12-25 | 深圳中兴网信科技有限公司 | Service approval method and system thereof, and mobile approval platform |
| CN103873345A (en) * | 2012-12-14 | 2014-06-18 | 上海格尔软件股份有限公司 | Method for realizing mail approval based on rules |
| CN104318381A (en) * | 2014-10-21 | 2015-01-28 | 中国建设银行股份有限公司 | Background audit task distributing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106251114A (en) | 2016-12-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106251114B (en) | Method and device for realizing approval in application | |
| JP7222036B2 (en) | Model training system and method and storage medium | |
| US10356094B2 (en) | Uniqueness and auditing of a data resource through an immutable record of transactions in a hash history | |
| WO2020029589A1 (en) | Model parameter acquisition method and system based on federated learning, and readable storage medium | |
| TWI798550B (en) | Method and device for multi-party joint risk identification | |
| US8838679B2 (en) | Providing state service for online application users | |
| US10929345B2 (en) | System and method of performing similarity search queries in a network | |
| US11669549B2 (en) | Identity mapping for cloud migrations | |
| US20110302277A1 (en) | Methods and apparatus for web-based migration of data in a multi-tenant database system | |
| CN106301978A (en) | The recognition methods of gang member account, device and equipment | |
| US10083061B2 (en) | Cloud embedded process tenant system for big data processing | |
| CN109241352A (en) | The acquisition methods and server of Profile information | |
| WO2020233014A1 (en) | Message sending method and apparatus, and computer device and storage medium | |
| CN111934899A (en) | Configuration method and device of user information of Internet of things and computer equipment | |
| CN111177481B (en) | User identifier mapping method and device | |
| CN111047434B (en) | Operation record generation method and device, computer equipment and storage medium | |
| CN105447342B (en) | script encryption method, decryption method and engine | |
| US11222309B2 (en) | Data processing systems for generating and populating a data inventory | |
| CN114595555A (en) | Carbon emission data processing method based on block chain | |
| CN114372291A (en) | Privacy joint reasoning method, device, equipment and storage medium | |
| CN113626863A (en) | Data processing method and device | |
| CN113836237A (en) | Method and device for auditing data operation of database | |
| US8069180B1 (en) | Systems and methods for automated employee resource delivery | |
| Liu et al. | Smart hardware hybrid secure searchable encryption in cloud with IoT privacy management for smart home system | |
| CN110362626A (en) | One kind being based on the convenience-for-people inquiry system of block chain network and application method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |