Table processing method and device, electronic equipment and storage medium

Abstract

The invention relates to a table processing method and device, electronic equipment and a storage medium, and the method comprises the steps that in response to merging operation on at least two continuous cells in a table, the at least two continuous cells are merged to obtain corresponding merged cells, and at least part of the cells are configured with cooperation permission; and configuring a cooperation permission for the merged cell. According to the method provided by the embodiment of the invention, the cooperation permission is reconfigured for the merged cells when the cells originally having the cooperation permission are merged, so that the security and smoothness of team cooperation can be ensured.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a table processing method, device, electronic device and storage medium. Background Art

[0002] Merging cells means merging two or more cells in the same row or column in a table into one cell in office software.

[0003] In actual applications, there is a special application scenario when merging cells: the multiple cells to be merged are originally configured with different collaboration permissions for different users, such as editing, commenting, or viewing only permissions.

[0004] In such scenarios, if you simply merge cells without considering the permission configuration of the merged cells, the originally protected cell contents may be exposed to users who should not have access to the contents, thereby undermining the collaborative security of the table. Summary of the invention

[0005] The present application provides a table processing method, device, electronic device and storage medium to solve the technical problem in the prior art that when merging cells, cells are only merged without considering the permission configuration of the merged cells, which is likely to destroy the collaborative security of the table.

[0006] In a first aspect, the present application provides a table processing method, the method comprising:

[0007] In response to a merge operation on at least two consecutive cells in the table, the at least two consecutive cells are merged to obtain corresponding merged cells, wherein at least some of the cells are configured with collaboration permissions;

[0008] Configure collaboration permissions for the merged cell.

[0009] In a possible implementation, in response to a merge operation on at least two consecutive cells in the table, merging the at least two consecutive cells to obtain a corresponding merged cell includes:

[0010] In response to a merge operation on at least two consecutive cells in a table, if it is determined that the current account has permission to perform the merge operation on the at least two consecutive cells, the at least two consecutive cells are merged to obtain a corresponding merged cell.

[0011] In a possible implementation, the method further includes:

[0012] In response to a merge operation on at least two consecutive cells in the table, obtaining collaboration permission configuration information of each of the cells;

[0013] The determining whether the current account has permission to perform the merge operation on the at least two consecutive cells includes:

[0014] When it is determined that the current account has the editing permission for each of the cells according to the collaboration permission configuration information of each of the cells, it is determined that the current account has the permission to perform the merging operation on the at least two consecutive cells.

[0015] In a possible implementation, configuring collaboration permissions for the merged cell includes:

[0016] Get the merged cell content in the merged cell;

[0017] Determine a source cell corresponding to the merged cell content, wherein the merged cell content includes the original cell content in the corresponding source cell;

[0018] Obtaining collaboration permission configuration information of the source cell;

[0019] The collaboration permission is configured for the merged cell according to the collaboration permission configuration information of the source cell.

[0020] In a possible implementation manner, merging the at least two consecutive cells to obtain a corresponding merged cell includes:

[0021] Merging the at least two consecutive cells into one cell, and using original cell contents in some of the cells as merged cell contents of the merged cell, to obtain a corresponding merged cell;

[0022] Alternatively, the at least two continuous cells are merged into one cell, and the original cell contents in each of the cells are used as the merged cell contents of the merged cell to obtain a corresponding merged cell.

[0023] In a possible implementation manner, merging the at least two consecutive cells to obtain a corresponding merged cell includes:

[0024] Inputting the cell contents of the at least two consecutive cells into a trained content generation model to obtain generated content of the content generation model;

[0025] The at least two continuous cells are merged into one cell, and the generated content is used as the merged cell content of the merged cell to obtain a corresponding merged cell.

[0026] In a possible implementation, configuring collaboration permissions for the merged cell includes:

[0027] Obtaining collaboration permission configuration information of each of the cells;

[0028] The collaboration permission is configured for the merged cell according to the collaboration permission configuration information of each of the cells.

[0029] In a possible implementation, configuring the collaboration permission for the merged cell according to the collaboration permission configuration information of each of the cells includes:

[0030] According to the collaboration permission configuration information of each of the cells, the collaboration account of each of the cells is obtained; a target collaboration account is selected from the collaboration accounts of each of the cells and configured as the collaboration account of the merged cell, wherein the collaboration account has the collaboration permission of the corresponding cell;

[0031] Alternatively, target collaboration permission configuration information satisfying a set condition is selected from the collaboration permission configuration information of each of the cells, and collaboration permission is configured for the merged cell according to the target collaboration permission configuration information.

[0032] In a possible implementation, configuring collaboration permissions for the merged cell includes:

[0033] In response to a permission configuration operation on the merged cell, the collaboration permission indicated by the permission configuration operation is configured for the merged cell.

[0034] In a possible implementation manner, after configuring the collaboration permission for the merged cell, the method further includes:

[0035] According to the merged cell and the collaboration permission of the merged cell, the area permission rule related to the merged cell is updated.

[0036] In a second aspect, the present application provides a table processing device, the device comprising:

[0037] A cell merging module, configured to, in response to a merging operation on at least two consecutive cells in a table, merge the at least two consecutive cells to obtain corresponding merged cells, wherein at least some of the cells are configured with collaboration permissions;

[0038] The permission configuration module is used to configure the collaboration permission for the merged cell.

[0039] In a possible implementation, the cell merging module is specifically used to:

[0040] In response to a merge operation on at least two consecutive cells in a table, if it is determined that the current account has permission to perform the merge operation on the at least two consecutive cells, the at least two consecutive cells are merged to obtain a corresponding merged cell.

[0041] In a possible implementation, the device further includes:

[0042] The original permission acquisition module is used to obtain the collaboration permission configuration information of each of the cells in response to a merge operation on at least two consecutive cells in the table;

[0043] The cell merging module is used to determine whether the current account has the permission to perform the merging operation on the at least two consecutive cells when it is determined that the current account has the editing permission for each of the cells based on the collaboration permission configuration information of each of the cells.

[0044] In a possible implementation, the permission configuration module includes:

[0045] A content acquisition unit, used to acquire the merged cell content in the merged cell;

[0046] A source cell determining unit, configured to determine a source cell corresponding to the merged cell content, wherein the merged cell content includes the original cell content in the corresponding source cell; and obtain the collaboration permission configuration information of the source cell;

[0047] The permission configuration unit is used to configure the collaboration permission for the merged cell according to the collaboration permission configuration information of the source cell.

[0048] In a possible implementation, the cell merging module is specifically used to:

[0049] Merging the at least two consecutive cells into one cell, and using original cell contents in some of the cells as merged cell contents of the merged cell, to obtain a corresponding merged cell;

[0050] Alternatively, the at least two continuous cells are merged into one cell, and the original cell contents in each of the cells are used as the merged cell contents of the merged cell to obtain a corresponding merged cell.

[0051] In a possible implementation, the cell merging module is specifically used to:

[0052] Inputting the cell contents of the at least two consecutive cells into a trained content generation model to obtain generated content of the content generation model;

[0053] The at least two continuous cells are merged into one cell, and the generated content is used as the merged cell content of the merged cell to obtain a corresponding merged cell.

[0054] In a possible implementation, the permission configuration module includes:

[0055] The original permission acquisition unit is used to acquire the collaboration permission configuration information of each of the cells;

[0056] The permission configuration unit is used to configure the collaboration permission for the merged cell according to the collaboration permission configuration information of each of the cells.

[0057] In a possible implementation manner, the permission configuration unit is specifically used to:

[0058] According to the collaboration permission configuration information of each of the cells, the collaboration account of each of the cells is obtained; a target collaboration account is selected from the collaboration accounts of each of the cells and configured as the collaboration account of the merged cell, wherein the collaboration account has the collaboration permission of the corresponding cell;

[0059] Alternatively, target collaboration permission configuration information satisfying a set condition is selected from the collaboration permission configuration information of each of the cells, and collaboration permission is configured for the merged cell according to the target collaboration permission configuration information.

[0060] In a possible implementation, the permission configuration module is specifically used to:

[0061] In response to a permission configuration operation on the merged cell, the collaboration permission indicated by the permission configuration operation is configured for the merged cell.

[0062] In a possible implementation, the device further includes:

[0063] The area authority updating module is used to update the area authority rules related to the merged cell according to the merged cell and the collaboration authority of the merged cell after configuring the collaboration authority for the merged cell.

[0064] In a third aspect, the present application provides an electronic device, comprising: a processor and a memory, wherein the processor is used to execute a table processing program stored in the memory to implement the table processing method described in any one of the first aspects.

[0065] In a fourth aspect, the present application provides a storage medium storing one or more programs, wherein the one or more programs can be executed by one or more processors to implement the table processing method described in any one of the first aspects.

[0066] The above-mentioned technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application, by responding to a merging operation on at least two consecutive cells in a table, merges at least two consecutive cells to obtain a corresponding merged cell, and configures collaboration permissions for the merged cell, thereby effectively managing the collaboration permissions of the merged cells. Moreover, the technical solution provided by the embodiment of the present application, when processing the merging of cells that originally have collaboration permissions, reconfigures collaboration permissions for the merged cells, thereby ensuring the security and smoothness of team collaboration. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

[0069] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.

[0070] Figure 1 A flowchart of an embodiment of a table processing method provided in an embodiment of the present application;

[0071] Figure 2 is an example diagram of at least two consecutive cells to be merged in an embodiment of the present application;

[0072] Figure 3 An example diagram of merging cells in an embodiment of the present invention;

[0073] Figure 4 A flowchart of another table processing method provided in an embodiment of the present application;

[0074] Figure 5 A flowchart of another table processing method provided in an embodiment of the present application;

[0075] Figure 6 A block diagram of an embodiment of a table processing device provided in an embodiment of the present application;

[0076] Figure 7A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0078] The disclosure below provides many different embodiments or examples to realize the different structures of the present application. In order to simplify the disclosure of the present application, the parts and settings of specific examples are described below. Of course, they are only examples, and the purpose is not to limit the present application. In addition, the present application can repeat reference numbers and / or letters in different examples. This repetition is for the purpose of simplification and clarity, and does not itself indicate the relationship between the various embodiments and / or settings discussed.

[0079] In order to solve the technical problem in the prior art that when merging cells, only the cells are merged without considering the permission configuration of the merged cells, which is likely to destroy the collaborative security of the table, the present application provides a table processing method, device, electronic device and storage medium, which can effectively manage the collaborative permissions of merged cells and ensure the security and smoothness of team collaboration.

[0080] Figure 1 A flowchart of an embodiment of a table processing method provided in an embodiment of the present application.

[0081] like Figure 1 As shown, the process includes the following steps:

[0082] Step 101: In response to a merge operation on at least two consecutive cells in a table, at least two consecutive cells are merged to obtain corresponding merged cells, wherein different cells have different collaboration permissions.

[0083] Step 102: Configure collaboration permissions for merged cells.

[0084] For ease of understanding, step 101 and step 102 are described in a unified manner as follows:

[0085] The above-mentioned table can be any table, which can be a table in a traditional format, such as a table in .xls, .xlsx and other formats, or a new generation of smart table, online table, and the embodiment of the present application does not limit this.

[0086] From the perspective of access methods, the above-mentioned table belongs to a collaborative document, that is, a document that allows multiple users to collaboratively edit it. There are currently two different ways of document collaboration, namely online collaborative documents and collaborative documents within a local area network. Among them, online collaborative documents are a way of sharing and editing documents through the Internet, storing documents on a cloud server, allowing multiple users to access, edit and comment on documents at the same time, and providing real-time collaboration and communication functions. A collaborative document within a local area network refers to a method in which multiple users can edit and modify the same document within a local area network through a shared folder or using professional collaborative editing software. The table in the embodiment of the present application can be any of the above-mentioned collaborative documents, and the embodiment of the present application does not limit this.

[0087] At least two consecutive cells in the table may include cells in two or more adjacent rows, and / or cells in two or more adjacent columns. Figure 2 (a) is an example of at least two consecutive cells in a table including cells in two or more adjacent rows; see Figure 2 (b) is an example of at least two consecutive cells in a table including cells in two or more adjacent columns; see Figure 2 (c) is an example in which at least two consecutive cells in a table include cells in more than two adjacent rows and adjacent columns.

[0088] In one embodiment, the user can select at least two consecutive cells in the table by operating the mouse or by inputting cell position information, and then trigger a merge operation on the selected cells, for example, by triggering a merge cell icon in the table toolbar to trigger the merge operation on the selected cells. Typically, in response to the merge operation on at least two consecutive cells in the table, the at least two consecutive cells are merged to obtain a corresponding merged cell.

[0089] For example, if the cell location information entered by the user is (B7:B10), it means that the selected cells include the cells in row 7 of column B to row 10 of column B. Figure 2 (a) Example. Then, in response to the merge operation on the selected cell, the selected cell is merged to obtain the corresponding merged cell. Figure 3 Example of (a).

[0090] Assuming that the cell location information entered by the user is (B7:E7), it means that the selected cells include the cells in row 7 of column B to row 7 of column E. Figure 2 (b) Example. Then, in response to the merge operation on the selected cell, the selected cell is merged to obtain the corresponding merged cell. Figure 3 (b) Example.

[0091] Assuming that the cell location information entered by the user is (B7:E10), it means that the selected cells include the cells in row 7 of column B to row 10 of column E. Figure 2 (c) Example. Then, in response to the merge operation on the selected cell, the selected cell is merged to obtain the corresponding merged cell. Figure 3 (c) Example.

[0092] Furthermore, in the technical solution of the embodiment of the present application, different permission collaboration areas can be set for different collaboration accounts in the table, that is, different collaboration accounts can edit the corresponding permission collaboration areas in the table respectively. In other words, different areas in the table can have different collaboration permissions. Here, the area in the table can be an area formed by one or more cells. For example, a cell in a table can form an area, and for another example, cells in a row (or column) or certain rows (or columns) in a table can form an area. The embodiment of the present application does not limit the division of areas in the table. Collaboration on the table includes but is not limited to: editing, commenting or viewing, etc.

[0093] On this basis, as an exemplary application scenario, the cells to be merged are at least partially configured with collaboration permissions, and different cells are configured with different collaboration permissions. Here, different collaboration permissions include different collaboration accounts, and the same collaboration account but different collaboration permissions for the same collaboration account. Among them, different collaboration accounts mean that the collaboration accounts are not exactly the same, that is, the collaboration accounts can be partially the same, but even if the collaboration accounts are partially the same, they are considered to be different collaboration accounts. For example, the collaboration permissions configured for cell 1 are: user A can edit, user B can view (read-only); the collaboration permissions configured for cell 2 are: user A can edit, user C can edit, and user B can edit. It can be seen that the collaboration accounts of the two cells are different, and the collaboration permissions of the same collaboration account are also different. Specifically, the collaboration accounts of cell 1 include user A and user B, and the collaboration accounts of cell 2 include user A, user B and user C; the same user B has read-only collaboration permissions for cell 1 and editable collaboration permissions for cell 2. It can be seen that different collaboration accounts and the same collaboration accounts but different collaboration permissions for the same collaboration account can both be considered to be different configured collaboration permissions.

[0094] In the above exemplary application scenario, if you simply merge cells without considering the permission configuration of the merged cells, the originally protected cell contents may be exposed to users who should not have access to these contents, thereby undermining the collaborative security of the table. For example, the cells to be merged include cell 1 and cell 2, and the collaborative permissions configured for cell 1 are: editable by all users, and the collaborative permissions configured for cell 2 are only allowed to be viewed by user A. At this point, assuming that the cell content of the merged cell retains the content of cell 2, and no permission configuration is made for the merged cell, the content in cell 2 will be leaked.

[0095] In this regard, it can be seen from the description of steps 101 and 102 that in the technical solution of the embodiment of the present application, after merging cells that were originally configured with collaboration permissions to obtain a merged cell, the collaboration permissions are reconfigured for the merged cell. In this way, after the cells are merged, the collaboration access to the merged cell can be reasonably controlled, thereby ensuring the security and smoothness of team collaboration.

[0096] As for how to configure collaboration permissions for merged cells, illustrative explanations are given below through different embodiments, which will not be described in detail here.

[0097] The technical solution provided in the embodiment of the present application merges at least two consecutive cells in a table in response to a merge operation to obtain a corresponding merged cell, and configures collaboration permissions for the merged cell, thereby effectively managing the collaboration permissions of the merged cells. In addition, when processing a merge of cells that originally had collaboration permissions, the technical solution provided in the embodiment of the present application reconfigures collaboration permissions for the merged cells, thereby ensuring the security and smoothness of team collaboration.

[0098] Figure 4 A flowchart of another table processing method provided in an embodiment of the present application. Figure 4 The process shown in Figure 1 Based on the process shown in the figure, this paper mainly describes an implementation scheme for configuring collaboration permissions for merged cells based on the cell contents in the merged cells. Figure 4 As shown, the following steps are included:

[0099] Step 401: In response to a merge operation on at least two consecutive cells in a table, at least two consecutive cells are merged to obtain corresponding merged cells, wherein at least some of the cells have collaboration permissions.

[0100] In some cases, each of the at least two consecutive cells has cell content (for the convenience of description, the cell content before the cells are merged is referred to as the original cell content). Figure 2 As shown in (a), the original cell contents of the four cells to be merged are "1", "2", "3" and "4" respectively.

[0101] In this case, in one embodiment, the specific implementation of merging at least two consecutive cells to obtain the corresponding merged cell includes: merging at least two consecutive cells into one cell, and using the original cell content in some of the cells as the merged cell content of the merged cell to obtain the corresponding merged cell.

[0102] In this embodiment, the merged cell content is composed of the original cell content of some cells in the cells to be merged. Here, some cells in the cells to be merged can be one of the cells, or two or more of the cells, which is not limited in this embodiment of the present application.

[0103] For example, if some of the cells to be merged are one of the cells, as an optional implementation, the one cell is a default designated cell, such as a cell located in the first row and first column of the cells to be merged. Figure 2 (a) to Figure 2 In the example of (c), the cell at position B7 is the cell located in the first row and first column of the cells to be merged. That is to say, the original cell content of the cell located in the first row and first column of the cells to be merged is used as the merged cell content. For example, see Figure 3 For example (a), Figure 2 After the four cells shown in (a) are merged, the content of the merged cell is "1".

[0104] As another optional implementation, the one cell is a cell specified by the user. That is, when merging cells, the user can specify the original cell content that needs to be retained in the merged cell. This can flexibly set the merged cell content to meet user needs.

[0105] An exemplary implementation of the above implementation includes: when the merge operation is about to be performed, a dialog box pops up to ask the user which cell content the user wants to keep, and the user can select the cell content to be kept in the dialog box by selecting or inputting information. In addition, in the above information input method, the user can enter the location information of the cell to be selected, or enter a certain selection logic to select the cell. The selection logic is, for example: the longest content length, the largest value, the content appears the most times in the table, etc.

[0106] In another embodiment, the specific implementation of merging at least two consecutive cells to obtain the corresponding merged cell includes: merging at least two consecutive cells into one cell, and using the cell content in each cell as the merged cell content of the merged cell to obtain the corresponding merged cell.

[0107] In this embodiment, the merged cell content is composed of the original cell content in all cells to be merged, which can achieve complete retention of the content in the table and maintain the traceability of the original cell content.

[0108] For example, the original cell contents of the three cells to be merged are "1", "2", and "3" respectively, and the merged cell content of the merged cell obtained by merging the three cells is "123".

[0109] For further description of step 401, please refer to the above Figure 1 The relevant description in the illustrated embodiment will not be repeated here.

[0110] Step 402: Get the merged cell content in the merged cell.

[0111] Step 403: Determine the source cell corresponding to the merged cell content, wherein the merged cell content includes the original cell content in the corresponding source cell.

[0112] It should be noted here that the source cell corresponding to the merged cell content does not refer to the cell on which the merge operation is performed, but to the cell from which the merged cell content comes. For example, if cell 1 and cell 2 are merged, and the original cell content in cell 1 is retained in the merged cell, then the source cell corresponding to the merged cell content in the merged cell is cell 1.

[0113] Step 404: Obtain the collaboration permission configuration information of the source cell.

[0114] Step 405: Configure collaboration permissions for the merged cell according to the collaboration permission configuration information of the source cell.

[0115] From the description of step 404 and step 405, it can be seen that the technical solution of the embodiment of the present application supports configuring the collaboration permission for the merged cell, that is, the merged cell content, according to the collaboration permission of the original cell content. This processing can maintain the collaboration security of the original cell content.

[0116] In one embodiment, when the number of source cells corresponding to the merged cell content is 1, the collaboration permission of the source cell can be directly configured as the collaboration permission of the merged cell.

[0117] For example, the cells to be merged include cell 1 and cell 2. The collaboration permission configured for cell 1 is: editable by all users, and the collaboration permission configured for cell 2 is: viewable by user A only. If cell 1 and cell 2 are merged, and the original cell content in cell 1 is used as the merged cell content of the merged cell, the collaboration permission configured for the merged cell is: editable by all users. If cell 1 and cell 2 are merged, and the original cell content in cell 2 is used as the merged cell content of the merged cell, the collaboration permission configured for the merged cell is: viewable by user A only.

[0118] It can be seen that by configuring the collaboration permissions of the original cell content as the collaboration permissions of the merged cell, the collaboration security of the original cell content and the consistency of the collaboration permissions can be maintained.

[0119] In another embodiment, when the number of source cells corresponding to the merged cell content is two or more, since different source cells may have different collaboration permissions, the collaboration permissions of the merged cell need to be reasonably configured.

[0120] As an optional implementation method, according to the collaboration permission configuration information of each source cell, the collaboration account of each source cell is obtained. The collaboration account mentioned here refers to a user account with collaboration permission for the source cell, wherein the collaboration permission may be editing permission or read-only permission. Then, the target collaboration account is selected from the collaboration accounts of each source cell and configured as the collaboration account of the merged cell. In this case, the original collaboration permission of the collaboration account of the merged cell can be retained.

[0121] Further optionally, the target collaboration account refers to the collaboration account of each source cell. In other words, the collaboration account of each source cell is configured as the collaboration account of the merged cell.

[0122] For example, the source cells corresponding to the merged cell content include cell 1 and cell 2. The collaboration permission configured for cell 1 is: editable by all users, and the collaboration permission configured for cell 2 is that only user A is allowed to edit. If cell 1 and cell 2 are merged, and the original cell contents in cell 1 and cell 2 are used as the merged cell content of the merged cell, then the collaboration accounts configured for the merged cell include all users, and the original collaboration permission of each collaboration account is retained: editable. In other words, the collaboration permission configured for the merged cell is: editable by all users.

[0123] For another example, the source cells corresponding to the merged cell content include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user B is allowed to edit, and the collaboration permission configured for cell 2 is: only user A is allowed to edit. If cell 1 and cell 2 are merged, and the original cell contents in cell 1 and cell 2 are used as the merged cell content of the merged cell, then the collaboration accounts configured for the merged cell include user A and user B, and the collaboration permission of user A and user B is retained for the merged cell: editable. In other words, the collaboration permissions configured for the merged cell are: user A can edit, user B can edit.

[0124] For another example, the source cells corresponding to the merged cell content include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user B is allowed to edit, and the collaboration permission configured for cell 2 is: user B can view. If cell 1 and cell 2 are merged, and the original cell contents in cell 1 and cell 2 are used as the merged cell content of the merged cell, then the collaboration accounts configured for the merged cell include user A and user B, and the collaboration permission of user A and user B is retained for the merged cell: editable. In other words, the collaboration permissions configured for the merged cell are: user A can edit, user B can view.

[0125] Optionally, the target collaboration account refers to a portion of the collaboration accounts of each source cell. That is, the portion of the collaboration accounts of each source cell is configured as the collaboration account of the merged cell. Here, the portion of the collaboration account may be any one or several of the collaboration accounts. In the case where the portion of the collaboration account includes multiple accounts, the portion of the collaboration account may correspond to the same source cell or to different source cells.

[0126] For example, the source cells corresponding to the merged cell content include cell 1 and cell 2. The collaboration permissions configured for cell 1 are: editable by user A, editable by user B, and editable by user C. The collaboration permissions configured for cell 2 are: editable by user D only. If a merge operation is performed on cell 1 and cell 2, and the original cell contents in cell 1 and cell 2 are used as the merged cell contents of the merged cell, then when user A, the collaboration account of source cell 1, is selected as the target collaboration account, user A is configured as the collaboration account of the merged cell, and the original collaboration permissions of user A are retained. In other words, the collaboration permissions configured for the merged cell are: editable by user A. When user D, the collaboration account of source cell 2, is selected as the target collaboration account, user D is configured as the collaboration account of the merged cell, and the original collaboration permissions of user D are retained. In other words, the collaboration permissions configured for the merged cell are: editable by user D.

[0127] An exemplary implementation of the above implementation includes: when the merge operation is about to be executed, a dialog box pops up to ask the user which collaboration account he wants to keep, and the user can select which collaboration account to be kept in the dialog box by selecting or inputting information.

[0128] As another optional implementation, target collaboration permission configuration information that meets set conditions is selected from the collaboration permission configuration information of each source cell, and collaboration permissions are configured for the merged cell according to the target collaboration permission configuration information.

[0129] The above setting conditions are, for example, the highest level of authority or the lowest level of authority. Here, the level of authority can be defined by the scope of authority.

[0130] For example, the source cells corresponding to the merged cell content include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user B is allowed to edit, and the collaboration permission configured for cell 2 is: only user B is allowed to view. Assuming the above setting condition is the highest level of permission, the collaboration permission configured for the merged cell is: only user B is allowed to edit. And assuming the above setting condition is the lowest level of permission, the collaboration permission configured for the merged cell is: only user B is allowed to view.

[0131] As another optional implementation, the user can select the collaboration permission configured for the merged cell from the collaboration permission configuration information of the source cell. For example, when the merge operation is about to be executed, a dialog box pops up to ask the user which source cell collaboration permission configuration information the user wants to keep. The user can select which source cell collaboration permission configuration information will be kept in the dialog box. The retained collaboration permission configuration information will be applied to the merged cell.

[0132] For example, the source cells corresponding to the merged cell content include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user A is allowed to view, and the collaboration permission configured for cell 2 is: only user B is allowed to view. If the user chooses to keep the permission configuration information of cell 2, the collaboration permission configured for the merged cell is: only user B is allowed to view. At this time, even if the original cell content in cell 1 is retained in the merged cell content, user A cannot view the merged cell content.

[0133] In addition, in one embodiment, when the merge operation is about to be performed, a dialog box may pop up to ask the user which of the above methods he / she wants to use to configure the collaboration permission for the merged cell. At this time, the collaboration permission for the merged cell will be configured according to the method selected by the user. In this way, a more flexible merged cell permission configuration scheme can be implemented.

[0134] Figure 4The process shown in Figure 1 On the basis of the process shown, by determining the source cell corresponding to the merged cell content, obtaining the collaboration permission configuration information of the source cell, and configuring the collaboration permission for the merged cell according to the collaboration permission configuration information of the source cell, a scheme is implemented to configure collaboration permissions for the merged cell according to the collaboration permissions of the original cell content, that is, the merged cell content. This implementation scheme can realize automated permission management for the merged cells on the one hand, and maintain the collaboration security of the original cell content on the other hand.

[0135] In the above step 401, a scheme is described for directly retaining the original cell content of a cell as the merged cell content. In another embodiment, the merged cell content can also be obtained in the following manner: inputting the cell content in at least two consecutive cells into a trained content generation model, obtaining the generated content of the content generation model, and using the generated content as the merged cell content of the merged cell. That is to say, in another embodiment, the specific implementation of merging at least two consecutive cells to obtain the corresponding merged cell includes: inputting the cell content in at least two consecutive cells into a trained content generation model, obtaining the generated content of the content generation model; merging at least two consecutive cells into one cell, and using the generated content as the merged cell content of the merged cell to obtain the corresponding merged cell.

[0136] Optionally, the generated content is a summary of the cell contents in at least two consecutive cells. By using the summary of the original cell contents as the merged cell contents, redundant information in the table can be reduced, so that readers can grasp key information more quickly, improve reading efficiency, and reduce the storage space occupied by the table.

[0137] Figure 5 A flowchart of another embodiment of a table processing method provided in an embodiment of the present application. Figure 5 The process shown in Figure 1 Based on the process shown in the figure, this paper mainly describes an implementation scheme for configuring collaboration permissions for merged cells based on the original collaboration permissions of the cells before merging. Figure 5 As shown, the following steps are included:

[0138] Step 501: In response to a merge operation on at least two consecutive cells in a table, obtain collaboration permission configuration information of each cell, and merge at least two consecutive cells to obtain corresponding merged cells, wherein at least some of the cells have collaboration permissions.

[0139] In one embodiment, the collaboration permissions originally configured for the cell are recorded, as well as the history of changes to the permissions of the cell, so as to facilitate auditing or backtracking when necessary.

[0140] Based on this, in response to a merge operation on at least two consecutive cells in the table, the collaboration permission configuration information of each cell is obtained.

[0141] Step 502: Configure collaboration permissions for the merged cells according to the collaboration permission configuration information of each cell.

[0142] In one embodiment, according to the collaboration permission configuration information of each cell, the specific implementation of configuring the collaboration permission for the merged cell includes: according to the collaboration permission configuration information of each cell, obtaining the collaboration account of each cell; selecting a target collaboration account from the collaboration accounts of each cell and configuring it as the collaboration account of the merged cell, wherein the collaboration account has the collaboration permission of the corresponding cell. In this case, the collaboration account of the merged cell retains the original collaboration permission.

[0143] Further optionally, the target collaboration account refers to each collaboration account of the cells to be merged. In other words, the collaboration account of each cell is configured as the collaboration account of the merged cell.

[0144] For example, the cells to be merged include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user B is allowed to edit, and the collaboration permission configured for cell 2 is: only user A is allowed to edit. If cell 1 and cell 2 are merged, regardless of the content of the merged cell, user A and user B will be configured as the collaboration account of the merged cell, and the original collaboration permissions of user A and user B will be retained for the merged cell. In other words, the collaboration permissions configured for the merged cell are: user A can edit, user B can edit.

[0145] For another example, the cells to be merged include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user B is allowed to edit, and the collaboration permission configured for cell 2 is: user A can view. If cell 1 and cell 2 are merged, regardless of the content of the merged cell, user A and user B will be configured as the collaboration account of the merged cell, and the original collaboration permissions of user A and user B will be retained for the merged cell. In other words, the collaboration permissions configured for the merged cell are: user B can edit, user A can view.

[0146] Optionally, the target collaboration account refers to a portion of the collaboration accounts of the cells to be merged. That is, the portion of the collaboration accounts of each cell is configured as the collaboration account of the merged cell. Here, the portion of the collaboration account may be any one or several of the collaboration accounts. In the case where the portion of the collaboration account includes multiple, the portion of the collaboration account may correspond to the same cell or to different cells.

[0147] For example, the cells to be merged include cell 1 and cell 2. The collaboration permissions configured for cell 1 are: editable by user A, editable by user B, and editable by user C. The collaboration permissions configured for cell 2 are: only editable by user D. If cell 1 and cell 2 are merged, and user A, the collaboration account of cell 1, is selected as the target collaboration account, user A is configured as the collaboration account of the merged cell, and the original collaboration permissions of user A are retained. In other words, the collaboration permissions configured for the merged cell are: editable by user A. If user D, the collaboration account of cell 2, is selected as the target collaboration account, user D is configured as the collaboration account of the merged cell, and the original collaboration permissions of user D are retained. In other words, the collaboration permissions configured for the merged cell are: editable by user D.

[0148] An exemplary implementation of the above implementation includes: when the merge operation is about to be executed, a dialog box pops up to ask the user which collaboration account he wants to keep, and the user can select which collaboration account to be kept in the dialog box by selecting or inputting information.

[0149] In another embodiment, the specific implementation of configuring collaboration permissions for merged cells according to the collaboration permission configuration information of each cell includes: selecting target collaboration permission configuration information that meets the set conditions from the collaboration permission configuration information of each cell, and configuring collaboration permissions for the merged cell according to the target collaboration permission configuration information.

[0150] The above setting conditions are, for example, the highest level of authority or the lowest level of authority. Here, the level of authority can be defined by the scope of authority.

[0151] For example, the cells to be merged include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user B is allowed to edit, and the collaboration permission configured for cell 2 is: only user B is allowed to view. Assuming that the above setting condition is the highest level of permission, the collaboration permission configured for the merged cell is: only user B is allowed to edit. And assuming that the above setting condition is the lowest level of permission, the collaboration permission configured for the merged cell is: only user B is allowed to view.

[0152] In another embodiment, the specific implementation of configuring collaboration permissions for merged cells according to the collaboration permission configuration information of each cell includes: in response to a selection operation on the collaboration permission configuration information of any cell, configuring collaboration permissions for the merged cell according to the selected collaboration permission configuration information.

[0153] That is to say, in this embodiment, the user can select the collaboration permission configured for the merged cell from the collaboration permission configuration information of the cells to be merged. For example, when the merge operation is about to be performed, a dialog box pops up to ask the user which cell's collaboration permission configuration information he wants to keep. The user can select the cell in the dialog box in a selected manner or directly select the collaboration permission configuration information of the cell. The collaboration permission configuration information of the selected cell or the selected collaboration permission configuration information will be retained, and the retained collaboration permission configuration information will be applied to the merged cell.

[0154] For example, the cells to be merged include cell 1 and cell 2. The collaboration permission configured for cell 1 is: only user A is allowed to view, and the collaboration permission configured for cell 2 is: only user B is allowed to view. If the user chooses to keep the permission configuration information of cell 2, the collaboration permission configured for the merged cell is: only user B is allowed to view. At this time, even if the original cell content in cell 1 is retained in the merged cell content, user A cannot view the merged cell content.

[0155] In addition, in one embodiment, when the merge operation is about to be performed, a dialog box may pop up to ask the user which of the above methods he / she wants to use to configure the collaboration permission for the merged cell. At this time, the collaboration permission for the merged cell will be configured according to the method selected by the user. In this way, a more flexible merged cell permission configuration scheme can be implemented.

[0156] Figure 5 The process shown in Figure 1 On the basis of the process shown, by obtaining the collaboration permission configuration information of each cell, the collaboration permissions are configured for the merged cells according to the collaboration permission configuration information of each cell, and a solution for configuring collaboration permissions for merged cells according to the original collaboration permissions of the cells is implemented. On the one hand, this implementation scheme can realize automated permission management for merged cells, and on the other hand, it can maintain the controllability of the collaboration permissions of merged cells, thereby contributing to the collaboration security of the table.

[0157] Figure 4 and Figure 5 The illustrated process proposes two different solutions for configuring collaboration permissions for merged cells. In practical applications, other solutions may also exist. For example, in one embodiment, the specific implementation of configuring collaboration permissions for merged cells includes: in response to a permission configuration operation on the merged cell, configuring the collaboration permissions indicated by the permission configuration operation for the merged cell.

[0158] It should be noted that this embodiment is Figure 4 and Figure 5The difference between configuring collaboration permissions for merged cells based on user selection in the process shown is that here the scope of the user's permission configuration operation is not limited to the collaboration permissions of the source cell, nor is it limited to the collaboration permissions of the cells to be merged, but rather has a wider range of permission configuration options.

[0159] As an optional implementation method, after merging cells, a dialog box pops up automatically or triggered by the user to ask the user for the collaboration permissions that the user wants to apply to the merged cells. The dialog box can be provided with flexible permission configuration options, such as selecting permission configuration options for designated personnel to view / edit / comment. Thus, the user can configure collaboration permissions for the merged cells by selecting permission configuration options.

[0160] This embodiment provides flexible permission configuration options and an extended permission configuration range, so that users can more accurately control the collaboration permissions of merged cells, thereby meeting diverse collaboration needs and collaboration security requirements.

[0161] Based on any of the above embodiments, the present application also provides the following embodiments:

[0162] In one embodiment, in response to a merge operation on at least two consecutive cells in a table, the at least two consecutive cells are merged to obtain a corresponding merged cell. The specific implementation includes: in response to a merge operation on at least two consecutive cells in a table, when it is determined that the current account has the authority to perform the merge operation on at least two consecutive cells, the at least two consecutive cells are merged to obtain the corresponding merged cell.

[0163] The current account refers to the currently logged in account, that is, the account initiating the merge operation. It can be seen that in this embodiment, the merge cell operation triggered by the user is also subject to permission verification. If it is determined that the current account has permission to perform a merge operation on at least two consecutive cells, the at least two consecutive cells are merged to obtain a corresponding merged cell. On the contrary, if it is determined that the current account does not have permission to perform a merge operation on at least two consecutive cells, the merge operation on the at least two consecutive cells is refused.

[0164] As an optional implementation method, in response to a merging operation on at least two consecutive cells in a table, the collaboration permission configuration information of each cell is obtained, and on this basis, the specific implementation of determining whether the current account has the permission to perform the merging operation on at least two consecutive cells includes: determining that the current account has the permission to perform the merging operation on at least two consecutive cells when the current account has the editing permission for each cell is determined based on the collaboration permission configuration information of each cell.

[0165] In the above implementation, the current account is allowed to perform the merge operation on the cells to be merged only when the current account has the editing permission for each cell to be merged.

[0166] Optionally, the current account has editing permissions for each cell, including but not limited to the following situations: the current account is the creator of the table. Normally, the creator of the table has all permissions to the table and can perform all reasonable operations on the table; the current account is granted editing permissions for any cell in the table by the creator of the table; the current account is granted editing permissions for each cell to be merged; the current account is granted editing permissions for each cell to be merged, and the collaboration permission configuration information of each cell to be merged is consistent; the current account is granted the permission for the collaborative account that manages the document to have collaboration permissions on the document, that is, the current account can set the collaboration permissions for the collaborative account of the document.

[0167] The above embodiments help prevent unauthorized users from making inappropriate modifications to the table, and help maintain the integrity of the table data, especially in a team collaboration environment where different users may have different roles and permissions. Through the permission verification mechanism in the above embodiments, it can be ensured that users can only operate on the table within their permissions, thereby avoiding work conflicts and unnecessary coordination costs. This helps to improve the smoothness of team collaboration.

[0168] In one embodiment, the regional permission function can also be enabled for the above table. Here, the regional permission function can set collaboration permissions for a specified area, such as some people can edit, some people can only view, etc., which can be used to manage regional data for the table. For example, see Figure 2 In the example of (a), assume that the user enables the area permission function for the table and selects cells B7:B8 as the designated area to set collaboration permissions. For example, the collaboration permissions set for the cell area B7:B8 are: user A can edit, others can only view. At this time, a area permission rule can be generated: only user A can edit the cell area B7:B8, others can only view.

[0169] Afterwards, when a merge operation is performed on the cell area B7:B10, B7:B10 will be merged into one cell, and the merged cell (i.e., the merged cell) is usually recorded as B7. In addition, it can be seen from the above embodiment that after the cell area B7:B10 is merged into one cell, the collaboration permissions of the merged cell will also be reset. It can be seen that in the merged cell scenario, the area permission rules of the original cell area related to the merged cell need to be updated synchronously. Here, the original cell area related to the merged cell refers to: the merged cell is obtained by merging the cells in the original cell area.

[0170] In this regard, in the technical solution of the embodiment of the present application, after configuring the collaboration permission for the merged cell, the area permission rules related to the merged cell are updated according to the merged cell and the collaboration permission of the merged cell. The area permission rules related to the merged cell refer to: the area permission rules of the original cell area related to the merged cell.

[0171] For example, suppose that the cell range B7:B10 is merged to obtain the merged cell B7, and the area permission rule set for the merged cell B7 is: only users A and B can edit the cell range B7, and others can only view it. Then, the above area permission rule: only user A can edit the cell range B7:B8, and others can only view it will be updated to: only users A and B can edit the cell range B7, and others can only view it.

[0172] The above embodiment realizes synchronous updating of the area permission rules related to the merged cells in the merged cell scenario, which can avoid the conflict between the area permission rules and the collaboration permissions of the merged cells, thereby ensuring the security and smoothness of team collaboration.

[0173] Figure 6 This is a block diagram of an embodiment of a table processing device provided in an embodiment of the present application. Figure 6 As shown, the device comprises:

[0174] A cell merging module 61 is used for merging at least two consecutive cells in a table in response to a merging operation on the at least two consecutive cells to obtain corresponding merged cells, wherein at least some of the cells have collaboration permissions;

[0175] The permission configuration module 62 is used to configure the collaboration permission for the merged cell.

[0176] In a possible implementation manner, the cell merging module 61 is specifically used for:

[0177] In response to a merge operation on at least two consecutive cells in a table, if it is determined that the current account has permission to perform the merge operation on the at least two consecutive cells, the at least two consecutive cells are merged to obtain a corresponding merged cell.

[0178] In a possible implementation, the device further includes:

[0179] The original permission acquisition module is used to obtain the collaboration permission configuration information of each of the cells in response to a merge operation on at least two consecutive cells in the table;

[0180] The cell merging module 61 is used to determine whether the current account has the permission to perform the merging operation on the at least two consecutive cells when it is determined that the current account has the editing permission for each of the cells according to the collaboration permission configuration information of each of the cells.

[0181] In a possible implementation, the permission configuration module 62 includes:

[0182] A content acquisition unit, used to acquire the merged cell content in the merged cell;

[0183] A source cell determining unit, configured to determine a source cell corresponding to the merged cell content, wherein the merged cell content includes the original cell content in the corresponding source cell; and obtain the collaboration permission configuration information of the source cell;

[0184] The permission configuration unit is used to configure the collaboration permission for the merged cell according to the collaboration permission configuration information of the source cell.

[0185] In a possible implementation manner, the cell merging module 61 is specifically used for:

[0186] Merging the at least two consecutive cells into one cell, and using original cell contents in some of the cells as merged cell contents of the merged cell, to obtain a corresponding merged cell;

[0187] Alternatively, the at least two continuous cells are merged into one cell, and the original cell contents in each of the cells are used as the merged cell contents of the merged cell to obtain a corresponding merged cell.

[0188] In a possible implementation manner, the cell merging module 61 is specifically used for:

[0189] Inputting the cell contents of the at least two consecutive cells into a trained content generation model to obtain generated content of the content generation model;

[0190] The at least two continuous cells are merged into one cell, and the generated content is used as the merged cell content of the merged cell to obtain a corresponding merged cell.

[0191] In a possible implementation, the permission configuration module 62 includes:

[0192] The original permission acquisition unit is used to acquire the collaboration permission configuration information of each of the cells;

[0193] The permission configuration unit is used to configure the collaboration permission for the merged cell according to the collaboration permission configuration information of each of the cells.

[0194] In a possible implementation manner, the permission configuration unit is specifically used to:

[0195] According to the collaboration permission configuration information of each of the cells, the collaboration account of each of the cells is obtained; a target collaboration account is selected from the collaboration accounts of each of the cells and configured as the collaboration account of the merged cell, wherein the collaboration account has the collaboration permission of the corresponding cell;

[0196] Alternatively, target collaboration permission configuration information satisfying a set condition is selected from the collaboration permission configuration information of each of the cells, and collaboration permission is configured for the merged cell according to the target collaboration permission configuration information.

[0197] In a possible implementation, the permission configuration module 62 is specifically used to:

[0198] In response to a permission configuration operation on the merged cell, the collaboration permission indicated by the permission configuration operation is configured for the merged cell.

[0199] In a possible implementation, the device further includes:

[0200] The area authority updating module is used to update the area authority rules related to the merged cell according to the merged cell and the collaboration authority of the merged cell after configuring the collaboration authority for the merged cell.

[0201] like Figure 7 As shown, an embodiment of the present application provides an electronic device, including a processor 111, a communication interface 112, a memory 113 and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0202] Memory 113, used for storing computer programs;

[0203] In one embodiment of the present application, the processor 111 is used to execute the program stored in the memory 113 to implement the table processing method provided by any of the above method embodiments, including:

[0204] In response to a merge operation on at least two consecutive cells in the table, the at least two consecutive cells are merged to obtain corresponding merged cells, wherein at least some of the cells have collaboration permissions;

[0205] Configure collaboration permissions for the merged cell.

[0206] An embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the table processing method provided in any of the aforementioned method embodiments are implemented.

[0207] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0208] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a general hardware platform, and of course, by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the relevant technology can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0209] It should be understood that the terms used herein are only for the purpose of describing specific example embodiments and are not intended to be limiting. Unless the context clearly indicates otherwise, the singular forms "one", "an" and "said" as used herein may also be meant to include plural forms. The terms "include", "comprise", "contain", and "have" are inclusive, and therefore specify the existence of stated features, steps, operations, elements and / or parts, but do not exclude the existence or addition of one or more other features, steps, operations, elements, parts, and / or combinations thereof. The method steps, processes, and operations described herein are not interpreted as necessarily requiring them to be performed in the specific order described or illustrated, unless the execution order is clearly indicated. It should also be understood that additional or alternative steps may be used.

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

Claims

1. A table processing method, characterized in that: The method comprises: In response to a merge operation on at least two consecutive cells in the table, the at least two consecutive cells are merged to obtain corresponding merged cells, wherein at least some of the cells are configured with collaboration permissions; Configure collaboration permissions for the merged cell.

2. The method according to claim 1, characterized in that In response to the merging operation on at least two consecutive cells in the table, merging the at least two consecutive cells to obtain a corresponding merged cell includes: In response to a merge operation on at least two consecutive cells in a table, if it is determined that the current account has permission to perform the merge operation on the at least two consecutive cells, the at least two consecutive cells are merged to obtain a corresponding merged cell.

3. The method according to claim 2, characterized in that The method further comprises: In response to a merge operation on at least two consecutive cells in the table, obtaining collaboration permission configuration information of each of the cells; The determining whether the current account has permission to perform the merge operation on the at least two consecutive cells includes: When it is determined that the current account has the editing permission for each of the cells according to the collaboration permission configuration information of each of the cells, it is determined that the current account has the permission to perform the merging operation on the at least two consecutive cells.

4. The method according to claim 1, characterized in that: The configuring collaboration permissions for the merged cell includes: Get the merged cell content in the merged cell; Determine a source cell corresponding to the merged cell content, wherein the merged cell content includes the original cell content in the corresponding source cell; Obtaining collaboration permission configuration information of the source cell; The collaboration permission is configured for the merged cell according to the collaboration permission configuration information of the source cell.

5. The method according to claim 1, characterized in that The step of merging the at least two consecutive cells to obtain a corresponding merged cell includes: Merging the at least two consecutive cells into one cell, and using original cell contents in some of the cells as merged cell contents of the merged cell, to obtain a corresponding merged cell; Alternatively, the at least two continuous cells are merged into one cell, and the original cell contents in each of the cells are used as the merged cell contents of the merged cell to obtain a corresponding merged cell.

6. The method according to claim 1, characterized in that The step of merging the at least two consecutive cells to obtain a corresponding merged cell includes: Inputting the cell contents of the at least two consecutive cells into a trained content generation model to obtain generated content of the content generation model; The at least two continuous cells are merged into one cell, and the generated content is used as the merged cell content of the merged cell to obtain a corresponding merged cell.

7. The method according to claim 1, characterized in that The configuring collaboration permissions for the merged cell includes: Obtaining collaboration permission configuration information of each of the cells; The collaboration permission is configured for the merged cell according to the collaboration permission configuration information of each of the cells.

8. The method according to claim 7, characterized in that The configuring the collaboration permission for the merged cell according to the collaboration permission configuration information of each of the cells includes: According to the collaboration permission configuration information of each of the cells, the collaboration account of each of the cells is obtained; a target collaboration account is selected from the collaboration accounts of each of the cells and configured as the collaboration account of the merged cell, wherein the collaboration account has the collaboration permission of the corresponding cell; Alternatively, target collaboration permission configuration information satisfying a set condition is selected from the collaboration permission configuration information of each of the cells, and collaboration permission is configured for the merged cell according to the target collaboration permission configuration information.

9. The method according to claim 1, characterized in that: The configuring collaboration permissions for the merged cell includes: In response to a permission configuration operation on the merged cell, the collaboration permission indicated by the permission configuration operation is configured for the merged cell.

10. The method according to claim 1, characterized in that After configuring the collaboration permission for the merged cell, the method further includes: According to the merged cell and the collaboration permission of the merged cell, the area permission rule related to the merged cell is updated.

11. A table processing device, characterized in that: The device comprises: A cell merging module, configured to, in response to a merging operation on at least two consecutive cells in a table, merge the at least two consecutive cells to obtain a corresponding merged cell, wherein different cells have different collaboration permissions; The permission configuration module is used to configure the collaboration permission for the merged cell.

12. An electronic device, characterized in that: include: A processor and a memory, wherein the processor is used to execute a table processing program stored in the memory to implement the table processing method according to any one of claims 1 to 10.

13. A storage medium, characterized in that: The storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement the table processing method according to any one of claims 1 to 10.

Images