Contract management methods, devices, equipment, and storage media based on multi-tenant collaboration
By deploying a shared resource library and contract integration module in the SaaS system, the problem of low efficiency in contract management among multiple tenants was solved, enabling collaborative contract management under information isolation and improving the efficiency and accuracy of contract management.
Patent Information
- Application Number
- CN202510019837.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-01-07
- Publication Date
- 2025-10-28
- Estimated Expiration
- 2045-01-07
AI Technical Summary
In multi-tenant SaaS systems, contract management is inefficient because data and communication between tenants are isolated, requiring contracts to be processed and handed over one by one, making efficient collaboration impossible.
By deploying a shared resource library in the SaaS system, multi-tenant collaborative management is achieved using the contract integration module. This allows the system to obtain tenants' contract editing information, automatically locate editing items based on content identifiers, and perform contract integration and collaborative editing while maintaining information isolation.
It achieves information isolation and contract collaboration management among multiple tenants, improves contract management efficiency, ensures information isolation among tenants and enables standardized editing, and ensures the accuracy and flexibility of contract collaboration management.
Smart Images

Figure CN119417658B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of SaaS technology, and in particular to a contract management method, apparatus, device, and storage medium based on multi-tenant collaboration. Background Technology
[0002] Currently, each property management company typically manages multiple residential communities or office buildings, and the information between each property is usually isolated. In order to improve management efficiency and achieve resource sharing, property management companies usually build SaaS systems based on Software as a Service (SaaS) systems, with each property being a tenant of the SaaS system, thereby achieving multi-tenant isolated management.
[0003] Contract management is a crucial component of property management. In related technologies, SaaS systems can already be used to manage contract drafting and review processes online, effectively improving efficiency. However, if a contract requires joint drafting and review by multiple tenants, the data and communication between each tenant are isolated. Only one tenant can independently complete their portion of the contract processing before transferring it to another tenant via the SaaS system for further processing, resulting in low contract management efficiency. Summary of the Invention
[0004] This invention aims to at least solve one of the technical problems existing in the prior art. To this end, this invention proposes a contract management method, apparatus, device, and storage medium based on multi-tenant collaboration, which can realize contract management based on multi-tenant collaboration and improve contract management efficiency.
[0005] In a first aspect, embodiments of the present invention provide a contract management method based on multi-tenant collaboration, applied to a SaaS system. The SaaS system includes a shared resource library and multiple preset tenants. The shared resource library is shared by each of the preset tenants. The shared resource library includes a contract integration module, and each preset tenant has a preset tenant identifier. The method includes:
[0006] Obtain a contract management request sent by any first tenant, wherein the contract management request carries a first identifier table and a second identifier table, the first identifier table records multiple tenant identifiers, and the second identifier table records multiple optional content identifiers;
[0007] Based on each of the optional content identifiers, construct corresponding optional edit items, determine multiple second tenants based on the first identifier table, send the second identifier table to the second tenants, and determine the second tenants and the first tenants as collaborating tenants;
[0008] Obtain contract editing information sent by each of the collaborating tenants, wherein the contract editing information includes at least one contract information unit, and the contract information unit includes a unit content identifier and a unit fill text;
[0009] Based on any of the contract information units, determine the corresponding target editing item based on the unit content identifier, and write the unit fill text into the target editing item;
[0010] The target contract is constructed based on the target fill text recorded in all the target edit items.
[0011] According to some embodiments of the present invention, the shared resource library further includes multiple shared information modules, each of which records different information. After obtaining the contract editing information sent by each of the collaborating tenants, the method further includes:
[0012] When the contract editing information contains a resource call instruction, the shared information module indicated by the resource call instruction is identified as the target information module;
[0013] Based on the resource call instruction, target shared information is obtained from the target information module, and the target shared information is determined as the text to be filled in the unit.
[0014] According to some embodiments of the present invention, after obtaining the contract editing information sent by each of the collaborating tenants, the method further includes:
[0015] When contract editing information is received from multiple collaborating tenants, a first unit set is constructed based on all the contract information units;
[0016] The first unit set is split into multiple second unit sets, wherein the unit content identifier carried by the contract information unit in the second unit set is the same, and each second unit set corresponds to one unit content identifier;
[0017] Merge all contract information units within the same second unit set, wherein the unit fill text of the merged contract information unit is the union of the unit fill texts of each unit before the merger.
[0018] According to some embodiments of the present invention, determining the corresponding target editing item based on the cell content identifier and writing the cell filling text into the target editing item includes:
[0019] When the content of the target edit item is empty, the cell fill text is written into the target edit item and determined as candidate fill text, and the cooperative tenant corresponding to the candidate fill text is recorded;
[0020] When the target edit item contains the candidate fill text, a semantic comparison result is obtained by performing a semantic comparison between the candidate fill text and the unit fill text.
[0021] When the semantic comparison result indicates that the candidate filled text and the unit filled text are different from each other, the unit filled text is written into the target edit item;
[0022] Alternatively, if the semantic comparison result indicates that there is overlapping text between the candidate filling text and the unit filling text, the overlapping text is removed from the unit filling text and then written into the target editing item.
[0023] According to some embodiments of the present invention, after obtaining the contract editing information sent by each of the collaborating tenants, the method further includes:
[0024] The unit content identifiers not recorded in the second identifier table are identified as new content identifiers;
[0025] Add the new content identifier to the second identifier table, add a new edit item based on the new content identifier, and write the cell fill text corresponding to the new content identifier into the new edit item;
[0026] The updated second identifier table is sent to each of the collaborating tenants.
[0027] According to some embodiments of the present invention, after obtaining the contract editing information sent by each of the collaborating tenants, the method further includes:
[0028] An editing prompt interface is constructed, in which the unit content identifier associated with each of the collaborative tenants is displayed;
[0029] The editing prompt interface is sent to each of the collaborating tenants.
[0030] According to some embodiments of the present invention, constructing a target contract based on the target-filled text recorded in all target edit items includes:
[0031] Based on the order of the optional content identifiers recorded in the second identifier table, each of the optional editable items is sorted.
[0032] When sorting and editing information is received from any of the collaborating tenants, the sorting of at least one of the optional editing items is adjusted based on the sorting and editing information, wherein the sorting and editing information includes a sorting content identifier and a target sorting position;
[0033] Upon receiving the edit completion instruction sent by each of the collaborating tenants, a target information unit is constructed based on each target edit item and the corresponding target fill text, and all the target information units are sent to the first tenant;
[0034] In response to the build complete instruction sent by the first tenant, the target contract is constructed based on the current sorting of each of the target edit items and all the target fill text.
[0035] In a second aspect, embodiments of the present invention provide a contract management device based on multi-tenant collaboration, including at least one control processor and a memory for communicatively connecting with the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enables the at least one control processor to perform the contract management method based on multi-tenant collaboration as described in the first aspect above.
[0036] Thirdly, embodiments of the present invention provide an electronic device including a contract management device based on multi-tenant collaboration as described in the second aspect above.
[0037] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions for performing the contract management method based on multi-tenant collaboration as described in the first aspect above.
[0038] The contract management method based on multi-tenant collaboration according to embodiments of the present invention has at least the following beneficial effects: Obtaining a contract management request sent by any first tenant, wherein the contract management request carries a first identifier table and a second identifier table, the first identifier table recording multiple tenant identifiers, and the second identifier table recording multiple optional content identifiers; constructing corresponding optional edit items based on each optional content identifier, determining multiple second tenants based on the first identifier table, sending the second identifier table to the second tenants, and determining the second tenants and the first tenants as collaborating tenants; obtaining contract editing information sent by each of the collaborating tenants, wherein the contract editing information includes at least one contract information unit, the contract information unit including a unit content identifier and unit fill text; determining a corresponding target edit item based on any contract information unit and the unit content identifier, and writing the unit fill text into the target edit item; constructing a target contract based on the target fill text recorded in all target edit items. According to the technical solution of the present invention, any tenant can designate a collaborative tenant to edit the contract, and deploy a contract integration module using a shared resource library. This enables each collaborative tenant to interact with the contract integration module, and automatically locates the editing item corresponding to the fill text through the content identifier carried by the contract editing information. This ensures information isolation between tenants, achieves collaborative contract management, and improves contract management efficiency. Attached Figure Description
[0039] Figure 1 This is a schematic diagram of a SaaS system provided in one embodiment of the present invention;
[0040] Figure 2 This is a flowchart of a contract management method based on multi-tenant collaboration provided in another embodiment of the present invention;
[0041] Figure 3 This is a complete flowchart of a contract management method based on multi-tenant collaboration provided in another embodiment of the present invention;
[0042] Figure 4 This is a structural diagram of a contract management device based on multi-tenant collaboration provided in another embodiment of the present invention. Detailed Implementation
[0043] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.
[0044] In the description of the present invention, it should be understood that descriptions involving orientations, such as up, down, front, back, left, right, etc., indicating orientations or positional relationships, are based on the orientations or positional relationships shown in the accompanying drawings. They are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, they cannot be understood as limitations on the present invention.
[0045] In the description of this invention, "several" means one or more, "more than" means two or more, "greater than," "less than," and "exceeding" are understood to exclude the stated number, while "above," "below," and "within" are understood to include the stated number. The use of "first" and "second" in the description is merely for distinguishing technical features and should not be construed as indicating or implying relative importance, or implicitly indicating the number of indicated technical features, or implicitly indicating the order of the indicated technical features.
[0046] In the description of the present invention, unless otherwise clearly defined, terms such as setting, installing, and connecting should be understood in a broad sense, and technicians in the relevant technical field can reasonably determine the specific meanings of the above terms in the present invention based on the specific content of the technical solution.
[0047] This invention provides a contract management method, apparatus, device, and storage medium based on multi-tenant collaboration. The multi-tenant collaboration-based contract management method includes: obtaining a contract management request sent by any first tenant, wherein the contract management request carries a first identifier table and a second identifier table, the first identifier table recording multiple tenant identifiers, and the second identifier table recording multiple optional content identifiers; constructing corresponding optional edit items based on each optional content identifier, determining multiple second tenants based on the first identifier table, sending the second identifier table to the second tenants, and determining the second tenants and the first tenants as collaborating tenants; obtaining contract editing information sent by each of the collaborating tenants, wherein the contract editing information includes at least one contract information unit, the contract information unit including a unit content identifier and unit fill text; determining a corresponding target edit item based on any contract information unit and the unit content identifier, and writing the unit fill text into the target edit item; and constructing a target contract based on the target fill text recorded in all target edit items. According to the technical solution of the present invention, any tenant can designate a collaborative tenant to edit the contract, and deploy a contract integration module using a shared resource library. This enables each collaborative tenant to interact with the contract integration module, and automatically locates the editing item corresponding to the fill text through the content identifier carried by the contract editing information. This ensures information isolation between tenants, achieves collaborative contract management, and improves contract management efficiency.
[0048] First, refer to Figure 1 , Figure 1This is a schematic diagram of a SaaS system provided in an embodiment of the present invention. The SaaS system in this embodiment includes a shared resource library 11 and multiple preset tenants. The shared resource library 11 is shared by each preset tenant. The shared resource library 11 includes a contract integration module 12. Each preset tenant has a preset tenant identifier. The shared resource library 11 also includes multiple shared information modules 13. The information recorded in each shared information module 13 is different from each other.
[0049] It should be noted that each preset tenant can be a property management system for a residential community or an office building. No restrictions are placed on the property entity corresponding to the preset tenant.
[0050] It should be noted that the SaaS system 10 can be shared by various pre-defined tenants. In this embodiment, a shared resource library 11 is deployed in the SaaS system 10. As those skilled in the art will know, the shared resource library 11 may include multiple shared information modules 13, such as... Figure 1 The personnel structure module, customer information module, electronic signature module, etc. shown, and the information in the shared information module 13 can be accessed and obtained by each preset tenant. For example, any preset tenant can obtain relevant personnel structure information from the personnel structure module.
[0051] It should be noted that in this embodiment, a contract integration module 12 is maintained in the shared resource library 11. The contract integration module 12 does not have any preset content and is used to integrate the contract editing information sent by each collaborating tenant. The contract integration module 12 can be used to build multiple target contracts at the same time. After each contract management request is obtained, an independent storage space is allocated in the contract integration module 12, and the contract editing information of the corresponding collaborating user can be obtained in the storage space.
[0052] The following is based on the appendix Figure 1 The SaaS system shown further illustrates the technical solution of this embodiment of the invention.
[0053] Reference Figure 2 , Figure 2 The flowchart illustrates a contract management method based on multi-tenant collaboration, as provided in an embodiment of the present invention. This method includes, but is not limited to, the following steps:
[0054] S11, obtain a contract management request sent by any first tenant, wherein the contract management request carries a first identifier table and a second identifier table, the first identifier table records multiple tenant identifiers, and the second identifier table records multiple optional content identifiers.
[0055] S12, construct corresponding optional edit items based on each optional content identifier, determine multiple second tenants based on the first identifier table, send the second identifier table to the second tenants, and determine the second tenants and the first tenants as collaborative tenants;
[0056] S13, obtain the contract editing information sent by each collaborating tenant, wherein the contract editing information includes at least one contract information unit, and the contract information unit includes a unit content identifier and a unit fill text;
[0057] S14. Based on any contract information unit, determine the corresponding target editing item based on the unit content identifier, and write the unit fill text into the target editing item;
[0058] S15, construct the target contract based on the target fill text recorded in all target edit items.
[0059] It should be noted that the first tenant is the preset tenant that initiates the contract management request. Any preset tenant can serve as the first tenant. After constructing the contract management request locally, it can be sent to the SaaS system. Each contract management request corresponds to one first tenant. A target contract is constructed in the contract integration module. The SaaS system in this embodiment can realize the joint management of multiple target contracts. Each time the SaaS system obtains a contract management request, it allocates a storage block in the contract integration module and opens the access rights of the storage block to the corresponding collaborating tenant. Each preset tenant can be identified as a collaborating tenant of multiple target contracts, thereby realizing the collaborative management of multiple tenants and multiple contracts.
[0060] It should be noted that the first identifier table records the identifiers of all tenants in the collaborative management target contract. The tenant identifiers of each preset tenant are different. Since the first tenant is the initiator of the contract management request, the first identifier table may not record the tenant identifier of the first tenant. The SaaS system will determine the first tenant as the collaborative tenant by default, and determine multiple second tenants from the remaining preset tenants through the first identifier table. Then, the first tenant and the second tenant will be determined as collaborative tenants, thus realizing the customization of collaborative tenants.
[0061] For example Figure 1 As shown, after tenant A initiates contract management request 1 to SaaS system 10, it is identified as the first tenant 21 of target contract 1, and tenants C and D are identified as the second tenants 22 of target contract 1. Tenants A, C, and D are then identified as collaborating tenants of target contract 1. If tenant B initiates contract management request 2 to SaaS system 10 and records tenants A and C in the first identifier table, then tenant B is the first tenant of target contract 2. Tenants A, B, and C are then identified as collaborating tenants of target contract 2. Tenants A and C can edit both target contract A and target contract B by adaptively adding contract identifiers to the contract editing information, thus improving the flexibility of prior contract collaboration management.
[0062] It should be noted that this embodiment does not enable communication and interaction between multiple collaborating tenants, as this contradicts and is not feasible due to the information isolation inherent in SaaS systems. To enable multiple tenants to collaboratively edit the same content, this embodiment utilizes the shared resource library of the SaaS system, which can interact with all preset tenants. A contract integration module is configured in the shared resource library, providing each collaborating tenant with the basis for interacting with the contract integration module. Each collaborating tenant independently sends contract editing information to the contract integration module. While maintaining information isolation among multiple tenants, the contract integration module integrates the contract editing information sent by multiple collaborating tenants to achieve collaborative contract management. Therefore, to ensure that the content sent by each collaborating tenant to the contract integration module conforms to the relevant format, the first tenant in this embodiment carries a second identifier table when initiating a contract management request. The second identifier table records optional content identifiers, enabling the contract integration module to assign an optional edit item based on each optional content identifier. The second identifier table is then sent to each second tenant. When a second tenant needs to edit the content of a target edit item, it determines the corresponding optional content identifier by querying the second identifier table. After editing the unit fill text, it constructs a contract information unit. The contract integration module locates the target edit item based on the unit content identifier and fills the target edit item with the unit fill text. Under information isolation, this ensures that multiple tenants can locate edit items using a unified standard, ensures that contract text of the same type is accurately filled with the correct edit item, and ensures the accuracy of contract collaboration management.
[0063] It should be noted that each collaborating tenant can edit through a relevant visual interface. For example, a table can be displayed in the collaborating tenant's system interface. One column of the table is used to input the unit content identifier, and the other column is used to input the unit fill text. Each contract information unit can be edited individually. Alternatively, multiple contract information units can be obtained in batches by importing a table. For example, an Excel spreadsheet can be imported into the collaborating tenant's system. One column of cells records the unit content identifier, and the other column records the unit fill text. This embodiment does not limit the specific input method.
[0064] For example, this embodiment uses different contract terms as optional content identifiers, such as "Contract Personnel," "Contract Amount," and "Contract Details." The contract integration module creates corresponding optional editable items for each optional content identifier. After obtaining the second identifier table, when tenant D needs to edit the "Contract Details," it constructs a contract editing information, with the corresponding unit content identifiers being "Contract Details" and "Detail A." The contract integration module locates the corresponding editable item A based on "Contract Details" and writes Detail A into editable item A, ensuring that the contract content is written into the correct editable item. Of course, collaborating tenants can record multiple contract information units in the form of a form within a single contract editing information, and the contract integration module can respond to each contract information unit individually.
[0065] It should be noted that, according to the technical solution of the above embodiments, each optional editable item can be a component of the target contract. After each optional editable item is determined as a target editable item and the corresponding target fill text is written, multiple collaborating tenants complete the collaborative management of the target contract based on their interaction with the contract integration module. The contract integration module can automatically construct the target contract based on the target fill text of each target editable item. For example, if each optional editable item is a clause in the contract template, the target fill text is filled into the contract template to generate the target contract. Given the text content of the target contract, those skilled in the art know how to automatically construct a standard format electronic contract, so no further details are provided here.
[0066] It is worth noting that this embodiment implements multi-tenant collaborative management based on the contract integration module. Since the information between collaborative tenants is isolated from each other, this embodiment uses text filling as a principle description. Of course, it is also possible to edit the existing filling text in the optional editable items. For example, the unit content identifier, prior text and replacement text are recorded in the contract information unit. It is sufficient to ensure that the optional editable items are located in the contract information unit with the unit content identifier. The specific editing method can be adaptively adjusted in the contract information unit according to actual needs.
[0067] Additionally, in one embodiment, reference is made to Figure 3 After step S13 is completed, the following steps are included, but are not limited to:
[0068] S21, when the contract editing information contains a resource call instruction, the shared information module indicated by the resource call instruction is identified as the target information module;
[0069] S22, based on the resource call instruction, obtain the target shared information from the target information module, and determine the target shared information as the cell filling text.
[0070] It should be noted that a SaaS system can be configured with multiple shared information modules. These shared information modules are system resources shared by various pre-defined tenants, such as... Figure 1 As shown, the shared information module may include a customer information module, an electronic signature module, a contract template module, a personnel structure module, etc. The customer information module is used to record the customer information of the property management company, the electronic signature module is used to record the electronic signature of the property management company, the contract template module records different types of contract templates, and the personnel structure module records the personnel structure information of different preset tenants. In this embodiment, the specific type of the shared information module is not limited, as long as it can be shared and called by various preset tenants.
[0071] It should be noted that the shared information module is used to record shared information. In this embodiment, the contract editing information is used to record resource call instructions. For example, the identification of the target information module and the description information of the target shared information are recorded in the contract editing information. After the SaaS system determines the target information module, it extracts the target shared information from it as a unit to fill text, thereby improving the flexibility of contract editing.
[0072] For example, such as Figure 1 As shown, the contract editing information initiated by tenant C contains content A and calling instruction A. The optional editing item corresponding to the content identifier of content A is the contract liability object. The corresponding SaaS system determines the target information module as personnel structure based on calling instruction A, and the target shared information is the name of the manager of level A. The names of all managers of level A are retrieved and written as target fill text into the corresponding target editing item to realize automatic content filling.
[0073] Additionally, in one embodiment, reference is made to Figure 3 After step S13 is completed, the following steps are included, but are not limited to:
[0074] S31, when contract editing information sent by multiple collaborating tenants is obtained, the first unit set is constructed based on all contract information units;
[0075] S32, the first unit set is split into multiple second unit sets, wherein the unit content identifiers carried by the contract information units in the second unit sets are the same, and each second unit set corresponds to a unit content identifier;
[0076] S33, merge all contract information units within the same second unit set, wherein the unit fill text of the merged contract information unit is the union of the unit fill texts of each unit before the merge.
[0077] It should be noted that this embodiment utilizes the shared attributes of the contract integration module to achieve multi-tenant collaborative editing. Since information is still isolated between multiple tenants, it is possible that multiple collaborating tenants may simultaneously input the same or different content for the same optional edit item. In this embodiment, after receiving contract editing information from multiple collaborating tenants, the contract integration module first places all contract editing information into a first unit set before writing the unit fill text. Because each optional content identifier corresponds to a contract clause or a type of content, the same collaborating tenant typically will not generate multiple contract information units based on the same unit content identifier. If multiple contract information units are identified corresponding to the same unit content identifier, it can be determined that multiple collaborating tenants have initiated editing based on the same content. To avoid content overlap, this embodiment constructs a second unit set based on the contract information units corresponding to the same unit content identifier. For ease of automation, even if the unit content identifier contains only one contract information unit, a separate second unit set is created. Since there are at least two collaborating tenants, the first unit set will be split into at least two second unit sets.
[0078] It should be noted that after splitting into multiple second unit sets, if a second unit set includes only one contract information unit, the subsequent writing steps can be directly executed, which will not be elaborated here. If the second unit set includes multiple contract information units, since the corresponding unit content identifiers are the same, this embodiment will take the union of the multiple unit fill texts to construct a merged fill text. The merged fill text and the unit content identifier will be used to construct a new contract information unit. This contract information unit records the fill text of all collaborating tenants based on the unit content identifier, and the subsequent target editing items can be filled in.
[0079] It's worth noting that when merging multiple unit fill texts, simple semantic recognition can be used to determine if the fill texts are duplicated. If they are not semantically duplicated, it can be determined that multiple collaborating tenants entered different parts of the content based on the same target editing item, such as multiple sub-clauses under a contract clause. In this case, the fill texts of the multiple units can be directly concatenated. If they are semantically duplicated, the semantically duplicated text can be extracted from any unit fill text and then concatenated with the remaining text. Alternatively, the duplicated part can be sent to the first tenant for manual review. The first tenant who initiated the contract editing is the reviewer of the duplicated content, and the fill text returned by the first tenant can be used as the fill text of the new contract information unit.
[0080] Additionally, in one embodiment, reference is made to Figure 3 Step S14 specifically includes, but is not limited to, the following steps:
[0081] S141, when the content of the target edit item is empty, write the cell filling text into the target edit item and determine it as the candidate filling text, and record the cooperating tenant corresponding to the candidate filling text;
[0082] S142, when the target edit item contains candidate fill text, a semantic comparison is performed based on the candidate fill text and the unit fill text to obtain the semantic comparison result;
[0083] S143, when the semantic comparison result indicates that the candidate padding text and the unit padding text are different from each other, write the unit padding text into the target editing item;
[0084] S144, when the semantic comparison result indicates that there is overlapping text between the candidate filling text and the unit filling text, the overlapping text is removed from the unit filling text and then written to the target editing item.
[0085] It should be noted that when multiple collaborating tenants simultaneously input content for a target editing item, they can refer to the above embodiment to merge contract information units. This embodiment only describes the filling method of the merged contract information unit.
[0086] It should be noted that when the content of the target editing item is empty, the cell fill text is directly written into the target editing item. Since the target editing item can be entered multiple times, or the entered content can be modified and deleted, the written cell fill text is first determined as the candidate fill text. When the editing is finally completed and the target contract is constructed, the candidate fill text saved in the target editing item is determined as the target fill text.
[0087] It should be noted that when the cell fill text is obtained, the target editing item already has candidate fill text, meaning that the target editing item has already had relevant text entered. This editing is a secondary editing. To ensure the correctness of the contract content, this embodiment performs simple semantic recognition on the candidate fill text and the cell fill text. Through semantic recognition, it can be determined whether the candidate fill text and the cell fill text involve the same content, such as whether they both involve the contract period or the contract subject. If the semantic recognition result indicates that the two are different, then the cell fill text is a further supplement to the target editing item. The cell fill text is written into the target editing item, and together with the prior candidate fill text, it serves as the content of the target editing item.
[0088] It should be noted that if there is overlapping text between the cell filling text and the candidate filling text, the overlapping text does not have to be exactly the same in words, but can also be semantically the same. For example, "the contract is valid for 3 years" and "the contract is valid from year A to year A+2" are different in words, but are semantically the same and are therefore identified as overlapping text. In this embodiment, the overlapping text is removed from the cell filling text and the remaining part is written into the target editing item.
[0089] It is worth noting that in step S144, if the semantics are similar but the text is different, it is not determined to be overlapping text. After the cell filling text is written to the target editing item, since this embodiment also records the collaborating tenant corresponding to each written text, the candidate filling text obtained after writing can be sent to the previous collaborating tenant and the collaborating tenant editing this time. If the two collaborating tenants are the same preset tenant, the cell filling content submitted by the collaborating tenant again will be used to overwrite the writing. If the two collaborating tenants are different preset tenants, the cell filling content submitted by the two collaborating tenants again will be compared. If they are the same, they will be written. If they are still different, a prompt message can be generated to prompt the two collaborating tenants to negotiate offline and initiate editing again.
[0090] Additionally, in one embodiment, reference is made to Figure 3 After step S13 is completed, the following steps are included, but are not limited to:
[0091] S41, the unit content identifier not recorded in the second identifier table is identified as the newly added content identifier;
[0092] S42, add a new content identifier to the second identifier table, add a new edit item based on the new content identifier, and write the cell fill text corresponding to the new content identifier into the new edit item;
[0093] S43 sends the updated second identifier table to each collaborating tenant.
[0094] It should be noted that, in this embodiment, after determining the second tenant, a second identifier table is sent to the second tenant, so that the second tenant can determine the optional editable items configured by the first tenant according to the second identifier table. During the contract editing process, any collaborating tenant can also add optional editable items, thereby improving the flexibility of contract collaborative editing.
[0095] It should be noted that, in order to add optional editable items, collaborating tenants, if they have a second identifier table, can record unit content identifiers that are not recorded in the second identifier table in the contract information unit. During the editing phase, the contract integration module only associates a piece of fill text with different unit content identifiers. Therefore, the unrecorded unit content identifiers can be identified as new content identifiers. New editable items are added based on the new content identifiers as new optional editable items. After the unit fill text is filled, the new content identifiers are updated to the second identifier table, and the second identifier table is synchronized to each collaborating tenant to ensure that the second identifier table of each collaborating tenant records the unit content identifiers corresponding to all optional editable items in the contract integration module.
[0096] Additionally, in one embodiment, reference is made to Figure 3 After step S13 is completed, the following steps are included, but are not limited to:
[0097] S51, Build an editing prompt interface, which displays the cell content identifier associated with each collaborating tenant;
[0098] S52 sends the editing prompts interface to each collaborating tenant.
[0099] It should be noted that this embodiment involves multiple collaborating tenants. After triggering editing, the contract integration module constructs an editing prompt interface, which displays the unit content identifier associated with each collaborating tenant. The editing prompt interface can record the unit content identifiers that each collaborating tenant is currently editing and that were previously edited. At the same time, the editing prompt interface is pushed to each collaborating tenant in real time, so that each collaborating tenant can know the content edited by other collaborating tenants while maintaining information isolation. This can avoid duplicate editing of the same content, identify the collaborating tenants corresponding to content with disputes in real time, and ensure the accuracy of the contract through timely offline communication, thereby improving the flexibility of collaborative contract editing.
[0100] For example, such as Figure 1 As shown, the editing prompt interface displays that tenant A is editing the target editing items corresponding to content A and content B, tenant C is editing the target editing items corresponding to content A and content C, and tenant D is editing the target editing items corresponding to content B and content D. The specific display method can be set according to actual needs.
[0101] Additionally, in one embodiment, reference is made to Figure 3 Step S15 specifically includes, but is not limited to, the following steps:
[0102] S151, sort each optional editable item according to the order of the optional content identifiers recorded in the second identifier table;
[0103] S152, when sorting editing information is received from any collaborating tenant, the sorting of at least one optional editing item is adjusted based on the sorting editing information, wherein the sorting editing information includes a sorting content identifier and a target sorting position;
[0104] S153, when the editing completion instruction sent by each collaborating tenant is obtained, a target information unit is constructed based on each target editing item and the corresponding target fill text, and all target information units are sent to the first tenant;
[0105] S154, in response to the build complete instruction sent by the first tenant, constructs the target contract based on the current order of each target edit item and all target fill text.
[0106] It should be noted that the second identifier table may correspond to a part of the target contract. The second identifier table is edited by the first tenant. The contract integration module sorts the optional editable items according to the order of the optional content identifiers recorded in the second identifier table, so that the optional editable items can be initially arranged into a contract framework.
[0107] It should be noted that sorting the optional editable items based on the second identifier table is a preliminary sort. According to the description of the above embodiment, the order and content of contract terms may be managed during the contract collaboration management process. Therefore, any collaborative tenant can send sorting and editing information to optimize and adjust the position of the optional editable items according to the sorting and editing information. The sorting and editing information uses the unit content identifier of the optional editable item that needs to be adjusted as the sorting content identifier and records the target sorting position.
[0108] For example, the cell content identifiers corresponding to the currently selectable editable items include content A, content B, content C, and content D. The sorting edit information initiated by tenant C records content B and position 3. The order of the selectable editable items can be adjusted to content A, content C, content B, and content D.
[0109] It should be noted that the information between collaborating tenants in this embodiment is isolated from each other. Therefore, collaborating tenants cannot communicate or interact online. After each collaborating tenant completes the content they need to edit, they can send an editing completion instruction to the contract integration module. When the contract integration module receives the editing completion instructions from all collaborating tenants, it determines the currently saved candidate fill text of the target edit item as the target fill text, thus obtaining the preliminary text content of the target contract. Since the first tenant is the initiator of editing the target contract, this embodiment sends all target information units to the first tenant. The first tenant performs a preliminary review of the target information units to determine whether the content of each target edit item conforms to the specifications, such as whether there is duplicate content. After confirming that there are no errors, the first tenant sends a construction completion instruction to the contract integration module. The contract integration module uses the currently sorted target edit items as the content sorting of the target contract and constructs the target contract as the final text content of the target contract, ensuring that the target contract is generated when each collaborating tenant has completed editing, thus ensuring the completeness of the target contract content.
[0110] like Figure 4 As shown, Figure 4 This is a structural diagram of a contract management device based on multi-tenant collaboration provided in one embodiment of the present invention. The present invention also provides a contract management device based on multi-tenant collaboration, comprising:
[0111] The processor 401 can be implemented using a general-purpose central processing unit (CPU), microprocessor, application specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application.
[0112] The memory 402 can be implemented as a read-only memory (ROM), static storage device, dynamic storage device, or random access memory (RAM). The memory 402 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the relevant program code is stored in the memory 402 and is called and executed by the processor 401 to implement the contract management method based on multi-tenant collaboration of the embodiments of this application.
[0113] Input / output interface 403 is used to implement information input and output;
[0114] The communication interface 404 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).
[0115] Bus 405 transmits information between various components of the device (e.g., processor 401, memory 402, input / output interface 403, and communication interface 404);
[0116] The processor 401, memory 402, input / output interface 403 and communication interface 404 are connected to each other within the device via bus 405.
[0117] This application also provides an electronic device, including the contract management device based on multi-tenant collaboration as described above.
[0118] This application embodiment also provides a storage medium, which is a computer-readable storage medium, storing a computer program that, when executed by a processor, implements the above-described contract management method based on multi-tenant collaboration.
[0119] Memory, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer-executable programs. Furthermore, memory may include high-speed random access memory, and may also include non-transitory memory, such as at least one disk storage device, flash memory device, or other non-transitory solid-state storage device. In some embodiments, memory may optionally include memory remotely located relative to the processor, and these remote memories can be connected to the processor via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof. The device embodiments described above are merely illustrative, and the units described as separate components may or may not be physically separate, and may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.
[0120] It will be understood by those skilled in the art that all or some of the steps and systems in the methods disclosed above can be implemented as software, firmware, hardware, and suitable combinations thereof. Some or all of the physical components can be implemented as software executed by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware, or as an integrated circuit, such as an application-specific integrated circuit. Such software can be distributed on a computer-readable medium, which can include computer storage media (or non-transitory media) and communication media (or transient media). As is known to those skilled in the art, the term computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disc (DVD) or other optical disc storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or any other medium that can be used to store desired information and is accessible to a computer. Furthermore, as is known to those skilled in the art, communication media typically include computer-readable instructions, data structures, program modules, or other data in modulated data signals such as carrier waves or other transmission mechanisms, and may include any information delivery medium.
[0121] The above provides a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the above embodiments. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of the present invention.
Claims
1. A contract management method based on multi-tenant collaboration, characterized in that, A contract integration module for a shared resource library in a SaaS system, wherein the SaaS system includes multiple pre-defined tenants, the shared resource library is shared by each of the pre-defined tenants, and each pre-defined tenant has a pre-defined tenant identifier; the method includes: Obtain any contract management request sent by a first tenant, and create a storage block associated with the contract management request, wherein the contract management request carries a first identifier table and a second identifier table, the first identifier table records multiple tenant identifiers, and the second identifier table records multiple optional content identifiers; Based on each of the optional content identifiers, construct corresponding optional edit items, determine multiple second tenants based on the first identifier table, send the second identifier table to the second tenants, determine the second tenants and the first tenants as cooperating tenants, and open the access permissions of the storage block to each of the cooperating tenants; Obtain the contract editing information sent by each of the collaborating tenants, and save the contract editing information to the storage block, wherein the contract editing information includes at least one contract information unit, and the contract information unit includes a unit content identifier and a unit fill text; After obtaining the contract editing information sent by each of the collaborating tenants, the method further includes: When contract editing information is received from multiple collaborating tenants, a first unit set is constructed based on all the contract information units; The first unit set is split into multiple second unit sets, wherein the unit content identifier carried by the contract information unit in the second unit set is the same, and each second unit set corresponds to one unit content identifier; Merge all contract information units within the same second unit set, wherein the unit fill text of the merged contract information unit is the union of the unit fill texts of each unit before the merger; Based on any of the contract information units, determine the corresponding target editing item based on the unit content identifier, and write the unit fill text into the target editing item; The target contract is constructed based on the target fill text recorded in all the target edit items.
2. The contract management method based on multi-tenant collaboration according to claim 1, characterized in that, The shared resource library also includes multiple shared information modules, each recording different information. After obtaining the contract editing information sent by each of the collaborating tenants, the method further includes: When the contract editing information contains a resource call instruction, the shared information module indicated by the resource call instruction is identified as the target information module; Based on the resource call instruction, target shared information is obtained from the target information module, and the target shared information is determined as the text to be filled in the unit.
3. The contract management method based on multi-tenant collaboration according to claim 2, characterized in that, Based on the cell content identifier, the corresponding target editing item is determined, and the cell filling text is written into the target editing item, including: When the content of the target edit item is empty, the cell fill text is written into the target edit item and determined as candidate fill text, and the cooperative tenant corresponding to the candidate fill text is recorded; When the target edit item contains the candidate fill text, a semantic comparison result is obtained by performing a semantic comparison between the candidate fill text and the unit fill text. When the semantic comparison result indicates that the candidate filled text and the unit filled text are different from each other, the unit filled text is written into the target edit item; Alternatively, if the semantic comparison result indicates that there is overlapping text between the candidate filling text and the unit filling text, the overlapping text is removed from the unit filling text and then written into the target editing item.
4. The contract management method based on multi-tenant collaboration according to claim 1, characterized in that, After obtaining the contract editing information sent by each of the collaborating tenants, the method further includes: The unit content identifiers not recorded in the second identifier table are identified as new content identifiers; Add the new content identifier to the second identifier table, add a new edit item based on the new content identifier, and write the cell fill text corresponding to the new content identifier into the new edit item; The updated second identifier table is sent to each of the collaborating tenants.
5. The contract management method based on multi-tenant collaboration according to claim 1, characterized in that, After obtaining the contract editing information sent by each of the collaborating tenants, the method further includes: An editing prompt interface is constructed, in which the unit content identifier associated with each of the collaborative tenants is displayed; The editing prompt interface is sent to each of the collaborating tenants.
6. The contract management method based on multi-tenant collaboration according to claim 5, characterized in that, The target contract is constructed based on the target fill text recorded in all target edit items, including: Based on the order of the optional content identifiers recorded in the second identifier table, each of the optional editable items is sorted. When sorting and editing information is received from any of the collaborating tenants, the sorting of at least one of the optional editing items is adjusted based on the sorting and editing information, wherein the sorting and editing information includes a sorting content identifier and a target sorting position; Upon receiving the edit completion instruction sent by each of the collaborating tenants, a target information unit is constructed based on each target edit item and the corresponding target fill text, and all the target information units are sent to the first tenant; In response to the build complete instruction sent by the first tenant, the target contract is constructed based on the current sorting of each of the target edit items and all the target fill text.
7. A contract management device based on multi-tenant collaboration, characterized in that, It includes at least one control processor and a memory for communicatively connecting to the at least one control processor; the memory stores instructions executable by the at least one control processor, which, when executed by the at least one control processor, enable the at least one control processor to perform the contract management method based on multi-tenant collaboration as described in any one of claims 1 to 6.
8. An electronic device, characterized in that, Includes the contract management device based on multi-tenant collaboration as described in claim 7.
9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions for causing a computer to perform the contract management method based on multi-tenant collaboration as described in any one of claims 1 to 6.
Citation Information
Patent Citations
Structured data interconnection method and server based on cloud computing service platform
CN113992736A
Automatic contract generation method and device, server, medium and product
CN114091415A