Report management method and device, terminal, medium and program product

Abstract

The embodiment of the invention discloses a report management method and device, a terminal, a medium and a program product. The method comprises the following steps: displaying a report document in a social application program; according to report items in the report document, editing the report document to obtain sub-report documents; and reporting and submitting the sub-report document. By adopting the embodiment of the invention, the report efficiency of the target enterprise can be improved.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a reporting management method, a reporting management device, a terminal, a computer-readable storage medium, and a computer program product. Background Technology

[0002] With the development of technology, reporting by target companies (such as any company) has gradually shifted from face-to-face reporting to online reporting, that is, using the Internet to enable internal reporting by company members.

[0003] Currently, employees within the target company have limited skills in editing reporting documents, and their editing methods are relatively simple and limited. For example, when editing reporting documents, employees only support basic text editing, such as editing plain text. This limits the target company's reporting capabilities in terms of reporting management, collaborative communication, and user experience, resulting in low reporting efficiency and increased difficulty in team collaboration. Summary of the Invention

[0004] This application provides a reporting management method, device, terminal, medium, and program product that can improve the reporting efficiency of target enterprises.

[0005] On the one hand, embodiments of this application provide a reporting management method, the method comprising:

[0006] Displaying a report document in a social application, the report document includes one or more report items, which are in a structured data format;

[0007] Edit the report document according to the report items to obtain a sub-report document; the editing operation includes at least one of the following: rich text insertion operation and annotation operation of document content in the report document;

[0008] Submit the report document.

[0009] On the other hand, embodiments of this application provide a reporting management device, which includes:

[0010] Display unit for displaying report documents in social applications, the report documents including one or more report items, the report items being in a structured data format;

[0011] The processing unit is used to edit the report document according to the report items in the report document to obtain a sub-report document; the editing operation includes at least one of the following: rich text insertion operation and annotation operation of document content in the report document;

[0012] The processing unit is also used to submit reports of sub-report documents.

[0013] On the other hand, embodiments of this application provide a terminal, which includes:

[0014] A processor, adapted to execute computer programs;

[0015] A computer-readable storage medium storing a computer program that, when executed by a processor, implements the reporting management method described above.

[0016] On the other hand, embodiments of this application provide a computer-readable storage medium storing a computer program adapted to be loaded by a processor and executed as described above in the reporting management method.

[0017] On the other hand, embodiments of this application provide a computer program product or computer program that includes computer instructions stored in a computer-readable storage medium. The processor of a terminal reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the terminal to perform the aforementioned reporting management method.

[0018] In this embodiment, if a target object logged into the social application (i.e., a reporting object that needs to fill out a report document) needs to make a report, the target object can open the corresponding report document through the social application. The report document includes one or more reporting items, and the reporting items are structured data structures. That is, the report document includes one or more reporting items with a fixed structure, and the reporting items are matters that the target object needs to edit to realize the report. Compared with the reporting object having to create the report document itself, this structured report document method can save the creation time of the report document and can ensure the uniformity of the document format of the report documents submitted by multiple reporting objects, which greatly facilitates the downstream operations of reporting (such as report summarization and report viewing). Furthermore, when editing a report document, the recipient can edit it according to the reporting items to create sub-reports. On one hand, the reporting items guide the editing process; for example, if a recipient needs to report today's work, they only need to edit the corresponding reporting item, improving efficiency. On the other hand, the system provides rich editing capabilities, such as inserting rich text or annotating the document, making reports more intuitive and detailed, and facilitating a better presentation of work results and plans. In summary, this embodiment combines structured report documents with rich editing capabilities, significantly enhancing reporting capabilities in social applications and improving internal reporting efficiency within enterprises. Attached Figure Description

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a schematic diagram of an interface for a reporting document provided in an exemplary embodiment of this application;

[0021] Figure 2 This is a schematic diagram of a reporting scenario provided by an exemplary embodiment of this application;

[0022] Figure 3 This is a flowchart illustrating a reporting management method provided in an exemplary embodiment of this application;

[0023] Figure 4 This is a schematic diagram illustrating a display of a reporting document provided in an exemplary embodiment of this application;

[0024] Figure 5 This is a schematic diagram illustrating a reporting reminder provided in an exemplary embodiment of this application;

[0025] Figure 6 This is a schematic diagram of a mobile terminal interface provided in an exemplary embodiment of this application;

[0026] Figure 7 This is a schematic diagram of a reporting item provided in an exemplary embodiment of this application;

[0027] Figure 8a This is a schematic diagram illustrating the insertion of an image into a reporting document, provided by an exemplary embodiment of this application.

[0028] Figure 8b This is a schematic diagram illustrating image editing in an inserted report document, provided by an exemplary embodiment of this application.

[0029] Figure 8c This is a schematic diagram illustrating four upload states of an image provided in an exemplary embodiment of this application;

[0030] Figure 9 This is a schematic diagram illustrating the insertion of a document into a reporting document, provided by an exemplary embodiment of this application.

[0031] Figure 10 This is a schematic diagram illustrating the insertion of a table into a reporting document, provided by an exemplary embodiment of this application;

[0032] Figure 11 This is a schematic diagram illustrating the insertion of a file into a report document, provided by an exemplary embodiment of this application.

[0033] Figure 12 This is a schematic diagram illustrating the insertion of a schedule into a reporting document, provided by an exemplary embodiment of this application.

[0034] Figure 13 This is a schematic diagram illustrating the insertion of meeting links into a presentation document, provided by an exemplary embodiment of this application.

[0035] Figure 14 This is a schematic diagram illustrating an annotation operation on reporting information in a reporting document, provided by an exemplary embodiment of this application;

[0036] Figure 15 This is a schematic diagram illustrating an annotation operation on template information in a reporting document, provided by an exemplary embodiment of this application.

[0037] Figure 16a This is a schematic diagram illustrating a commenting operation on the entire report document, provided by an exemplary embodiment of this application;

[0038] Figure 16b This is a schematic diagram illustrating a batch deletion of filled content in a report document, provided by an exemplary embodiment of this application.

[0039] Figure 17 This is a schematic diagram illustrating a collaborative editing of a report document, provided in an exemplary embodiment of this application.

[0040] Figure 18 This is an illustration of a method for prompting the submission of a report document when a rich text file is being uploaded, as provided in an exemplary embodiment of this application.

[0041] Figure 19 This is a flowchart illustrating another reporting management method provided in an exemplary embodiment of this application;

[0042] Figure 20 This is a schematic diagram illustrating a document import implementation for report editing, provided by an exemplary embodiment of this application;

[0043] Figure 21 This is a schematic diagram illustrating an exemplary embodiment of this application, showing a method for voluntarily selecting and covering certain content.

[0044] Figure 22a This is a schematic diagram illustrating a method for merging multiple historical sub-report documents and displaying them over an overlay, provided by an exemplary embodiment of this application;

[0045] Figure 22bThis is a schematic diagram illustrating an exemplary embodiment of this application, showing a method of merging and overlaying partial content from multiple historical sub-report documents;

[0046] Figure 23 This is a schematic diagram illustrating a method for displaying a list of submitted report versions in a service interface that displays report documents, as provided in an exemplary embodiment of this application.

[0047] Figure 24a This is a schematic diagram of an application architecture provided in an exemplary embodiment of this application;

[0048] Figure 24b This is a schematic diagram of a storage layer structure provided in an exemplary embodiment of this application;

[0049] Figure 25 This is a schematic diagram illustrating the flow of reporting documents and sub-reporting documents between various business roles, provided by an exemplary embodiment of this application.

[0050] Figure 26a This is a schematic diagram illustrating the management permissions of an enterprise administrator as provided in an exemplary embodiment of this application;

[0051] Figure 26b This is a schematic diagram illustrating the creation of a reminder task and the sending of a reminder, provided in an exemplary embodiment of this application.

[0052] Figure 26c This is a schematic diagram of a summary reminder task processing method provided in an exemplary embodiment of this application;

[0053] Figure 26d This is a schematic diagram illustrating the process of a document creator creating a report template, provided in an exemplary embodiment of this application.

[0054] Figure 27a This is a schematic diagram illustrating a process for a reporting object to submit a sub-reporting document, provided in an exemplary embodiment of this application.

[0055] Figure 27b This is a schematic diagram illustrating the submission of a collection form when the sub-report document is a collection form, provided in an exemplary embodiment of this application;

[0056] Figure 27c This is a schematic diagram illustrating the permissions of various services provided in an exemplary embodiment of this application;

[0057] Figure 28a This is a schematic diagram of a summarization process provided in an exemplary embodiment of this application;

[0058] Figure 28b This is a schematic diagram of the main method flow of a reporting management method provided in an exemplary embodiment of this application;

[0059] Figure 29 This is a schematic diagram of the structure of a reporting management device provided in an exemplary embodiment of this application;

[0060] Figure 30 This is a schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application. Detailed Implementation

[0061] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0062] This application proposes a reporting management scheme. The technical terms and related concepts involved in this reporting management scheme are briefly introduced below:

[0063] (1) Social applications.

[0064] A social application can refer to a computer program with social functions, that is, a social interaction between multiple objects that can be realized in the social application. In the embodiments of this application, the social application can be called an enterprise communication application, which is an enterprise-level communication and office tool. Specifically, it is an application that supports communication and office work among enterprise members within a target enterprise (such as any enterprise). This social application meets the internal management needs of the enterprise and is a product oriented towards the enterprise-level market. In practical applications, each enterprise member in the target enterprise can log in to the social application through their respective member account Vid (such as the unique identity of an enterprise member in the social application, used to identify the account of the enterprise member in the target enterprise), and join the corresponding enterprise account Corpid (such as the unique identifier of the target enterprise in the social application, used to identify the unique account subject of the target enterprise) through their respective member accounts. In this way, enterprise members belonging to the same target enterprise do not need to add each other as friends, but can also communicate through the social application to realize enterprise office and communication. For example, if multiple users are assigned member accounts to log in to a social application, then these multiple users can search for the target company's corporate account through the social application where they are logged in with the corresponding member account, so as to join the same target company. In this case, it is determined that each user who joins the same target company is a member of that target company, that is, the members of the company are colleagues.

[0065] The social application deploys multiple sub-applications (referred to as business sub-applications), each corresponding to a specific application function provided by the social application. These sub-applications may include, but are not limited to, calendar sub-applications, meeting sub-applications, document sub-applications, and file sub-applications. The calendar sub-application provides schedule management functionality for enterprise members. Members can rely on this sub-application to create or receive schedules, which purposefully allocate time each day, clearly define the start and end times of each task, promptly identify any delays in work progress, and utilize reminders to prevent delays or omissions, thereby helping enterprise members better manage their time and improve work efficiency. The meeting sub-application provides meeting functionality for multiple enterprise members within the target enterprise. Specifically, multiple members can use this sub-application to schedule and conduct meetings, avoiding the need to switch to a dedicated meeting application for online meetings. The document sub-application provides document functionality for enterprise members, specifically supporting document creation, editing, and sharing. The document sub-application also has rich document editing capabilities, including rich text insertion and text annotation. The file sub-application provides file functionality for enterprise members, specifically enabling them to browse and download files within the target enterprise and synchronize files within the target enterprise. It should be understood that social applications offer more than just the sub-applications mentioned above, and their functionalities are not limited to those listed.

[0066] (2) Report.

[0067] Reporting is an important communication tool within a target company. It allows the company to convey information about its operations, project progress, and financial status to its members (such as leadership). Reporting within a target company primarily involves the reporting party and the reported party. Specifically, the reporting party needs to report information about the company's operations, project progress, and financial status to the reported party. For example, the reported party typically includes senior management, department heads, and project managers, while the reporting recipients are usually ordinary employees.

[0068] This application does not limit the type and frequency of reports within the target enterprise. Specifically: ① The types of reports may include, but are not limited to: work reports, customer visit reports, visitor request reports, sales reports, and self-reports. Work reports refer to the reporting entity reporting on its work content over a period of time to the reporting entity; customer visit reports refer to the reporting entity reporting on the names of customers who visited the target enterprise and the matters discussed during the visit; visitor request reports refer to the reporting entity reporting on the names of customers who submitted visit requests to the target enterprise and the application dates during the visit; sales reports refer to the reporting entity reporting on the sales performance of a specific product of the target enterprise over a period of time; and self-reports refer to the reporting entity reporting on its personal situation based on its individual reporting needs. ② The frequency of reports can be called the reporting cycle, which refers to the frequency / period at which the reporting entity reports to the reporting entity. For example, if the frequency of work reports from the reporting entity to the reporting entity is daily, weekly, or monthly, it means that the reporting entity may submit a work report to the reporting entity once a day / weekly / monthly.

[0069] In practical applications, corporate members who log in to social applications using their member accounts often have a need to report within the target company. For example, team members in a project group within the target company need to report project progress to their project manager. In this case, team members can edit the report document, adding the content they want to report, and then submit the document to the recipient. Currently, the report editing capabilities provided by relevant applications to the recipients (i.e., corporate members within the target company who need to report) are limited, such as only supporting plain text editing within the report document. This limited editing capability restricts report editing, content display, project management integration, team collaboration, and the overall reporting experience within the target company, reducing reporting efficiency and increasing the difficulty of team collaboration.

[0070] To facilitate rapid reporting by employees within a target enterprise using social applications and enhance report editing capabilities, this application's proposed reporting management solution introduces a novel reporting tool within the social application. This allows enterprise members to utilize this sub-application for various reporting functions related to their business. This enables employees to report while using the social application without needing to switch to a dedicated reporting application, avoiding frequent app hopping and improving internal reporting efficiency. Furthermore, the reporting tool introduced within the social application leverages the capabilities of other sub-applications (such as document and calendar sub-applications) to provide powerful report editing capabilities for reporting recipients. This ensures that recipients can quickly create rich sub-report documents for submission, improving both reporting efficiency and quality.

[0071] The following describes the rich report editing functions provided by the report management solution: When a reporting recipient within the target company (such as a member of the target company who needs to report, referred to as the target recipient, i.e., the member of the target company who serves as the recipient of the report document) needs to report, they can open the corresponding report document from a social application. For example, when reporting a weekly report, the recipient can open the weekly report; when reporting a daily report, they can open the daily report, etc. The opened report document is then displayed in the social application. This report document is a structured document, specifically, it includes one or more reporting items with a fixed structure. Each reporting item is in a structured data format, meaning that each reporting item in the report document is organized and displayed according to a predefined data format. Then, the reporting recipient can edit the report document according to the reporting items to obtain sub-report documents. The reporting recipient can then submit the edited sub-report documents, specifically submitting them to the corresponding recipient within the target company.

[0072] In this embodiment, during the editing process of the reporting document by the recipient, advanced editing capabilities and intuitive content display capabilities are provided. Specifically, the reporting tools provided by the social application support the insertion of rich text and the annotation of document content in the reporting document. The rich text can come from other sub-applications within the social application; that is, by leveraging the capabilities of other sub-applications within the social application, the rich content formats provided by each sub-application can be edited in the reporting document. For example, a calendar sub-application can be used to insert a calendar, and a document sub-application can be used to insert a document or table. Annotation of document content in the reporting document can specifically include underlining, commenting, annotating, or highlighting the document content.

[0073] Compared to mainstream solutions, the report management solution provided in this application has more powerful report editing capabilities. The main advantages of the report management solution in terms of report editing capabilities provided in this application are explained below:

[0074] Current mainstream reporting documents can be plain text documents, such as... Figure 1 The report document 101 shown in (1) is completely open to the reporting recipient. It is a blank Word document in which the reporting recipient customizes the reporting items and content. This completely open report document requires the reporting recipient to spend a significant amount of time writing and formatting the reporting items and content, reducing reporting efficiency and failing to standardize the document format of sub-report documents submitted by different reporting recipients. However, the report document provided in this embodiment is a structured document, such as... Figure 1 As shown in (2) of the report document 102, the report document 102 contains a framework of report content to be filled in, namely one or more report items in a fixed data format. For example, the data format of report item 103 is a report prompt message and a report input box, with the report prompt message located above the report input box. This method, which defines the report content to be filled in by the reporting object in the report document through report items in a fixed data format, such as the project progress, sales volume, and work details to be reported by the reporting object, eliminates the need for the reporting object to write report items and report content independently, saving time on report writing and format adjustment, and improving reporting efficiency.

[0075] Existing mainstream reporting documents also include structured documents. However, these structured documents currently lack powerful editing tools, supporting only basic text editing. For example, editing plain text within a reporting document leads to a uniform format in the sub-reports submitted by the reporting party, resulting in a lack of intuitiveness in the reporting content. However, the reporting tool provided in this application embodiment can leverage the application functions of other sub-applications within a social application to provide powerful editing tools. For instance, utilizing the robust document editing capabilities of the document sub-application within the social application allows for document editing within the reporting document, avoiding the additional overhead of relying on external tools. Furthermore, the reporting party can utilize these powerful editing capabilities to edit richer reporting content within the reporting document, such as inserting rich text (e.g., tables, schedules, or meeting minutes), annotating the document content, etc., ensuring that the completed sub-reports contain more comprehensive, professional, and richer content.

[0076] The reporting management solution described in this application provides advanced reporting editing capabilities, making it applicable to a wide range of application scenarios with varying reporting editing needs, effectively expanding the scope of reporting usage scenarios. Specifically, it not only meets the advanced needs of knowledge-based enterprise employees for editing and managing report documents, improving job satisfaction and productivity, but also caters to the needs of manual labor employees for information collection through reports; thus, the reporting management solution provided in this application has a broad range of application scenarios.

[0077] For example, the use case is a document-writing reporting scenario. This scenario can include, but is not limited to, scenarios where project teams report using written reports (or project reporting scenarios), and scenarios where operations teams report using written reports. Taking the document-writing reporting scenario as an example, project team members in the IT and manufacturing industries are knowledge workers who often possess strong editing skills and need to periodically report on project status (such as project progress and important project events), such as submitting weekly reports to report on the release status of a product version. When the reporting management solution provided in this application is applied to this project reporting scenario, it ensures that project team members can combine a large amount of rich text, documents, schedules, and files to complete project reports. This allows the completed sub-report documents to contain richer and more comprehensive reporting information, meeting the editing needs of knowledge workers for rich content formats.

[0078] For example, the use case is an information collection and reporting scenario. This scenario can include, but is not limited to, scenarios where stores collect sales information (or store reporting scenarios) and communities collect personnel information. Taking the scenario of stores collecting sales information as an example, the members in the store (such as retail store managers or salespersons) are manual labor employees who often only need to report some simple and clear data. When the reporting management solution provided in this application is applied to this store reporting scenario, it supports manual labor employees in simple text editing, image uploading, and document addition, which can meet their needs for simple and clear reporting content.

[0079] It should be noted that the above are only two exemplary application scenarios provided by the embodiments of this application; in practical applications, the reporting management scheme provided by the embodiments of this application can be applied to any scenario that requires reporting, and the above two exemplary scenario descriptions will not limit the applicable scenarios of the embodiments of this application.

[0080] To facilitate a better understanding of the reporting management scheme proposed in the embodiments of this application, the following is combined with... Figure 2Taking a project reporting scenario as an example, a scenario diagram of a project reporting scenario is given. Figure 2 This is a schematic diagram of the architecture of a reporting management system provided in an exemplary embodiment of this application. The reporting management system includes a terminal 201, a terminal 202, and a server 203. This embodiment of the application does not limit the number, type, or naming of the terminals and servers. Wherein:

[0081] (1) Terminal 201 refers to the terminal held by a member of the target enterprise who has reporting needs. In this case, the member can be called the reporting object of the reporting document. Terminal 201 refers to the member of the target enterprise who needs to receive the sub-reporting document corresponding to the reporting document. In this case, the member can be called the reporting object corresponding to the reporting document. The terminal (such as terminal 201 or terminal 202) may include, but is not limited to: smartphones (such as smartphones running Android or smartphones running Internet Working Operating System (IOS), tablet computers, portable personal computers, mobile Internet Devices (MID), in-vehicle devices, head-mounted devices, etc. This application embodiment does not limit the type of terminal device, which is stated here. Both terminal 201 and terminal 202 are equipped with social applications. In this way, the reporting object corresponding to the reporting document can download, edit, and submit the reporting document through the social applications deployed on its terminal. Similarly, the reporting object corresponding to the reporting document can receive the sub-reporting document submitted by the reporting object through the social applications deployed on its terminal.

[0082] (2) Server 203 is the server corresponding to terminals 201 and 202. Specifically, it is the backend server corresponding to the social applications deployed in terminals 201 and 202, used to interact with terminals 201 and 202 to provide computing and application service support for the social applications deployed in terminals 201 and 202. Server 203 can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms. Terminals 201, 202 and server 203 can be directly or indirectly connected through wired or wireless communication, which is not limited herein.

[0083] The member management scheme provided in this application embodiment can be jointly executed by terminal 201, terminal 202, and server 203 in the aforementioned member management system; specifically, it is jointly executed by the social application deployed in terminal 201, the social application deployed in terminal 202, and server 203. In specific implementation, when a reporting object in the target enterprise has a reporting need, a document retrieval operation can be performed in the social application. At this time, terminal 201, in response to the document identifier indicated by the document retrieval operation, downloads the reporting document corresponding to the document identifier from server 203 and renders and displays the reporting document. The reporting document can be a pre-set reporting template in the social application or a reporting template created by the enterprise administrator in the target enterprise, etc. Then, the reporting recipient can use a variety of reporting editing methods to edit the report document, filling in the report content. Specifically, the report document includes one or more structured reporting items, each corresponding to a reporting event, such as reporting item 1 for reporting today's work plan and reporting item 2 for reporting tomorrow's work arrangements. The reporting recipient can then edit all or part of the reporting items according to their reporting event needs using these methods. Editing of the document content (including reporting items and other document information) is also supported, such as comments / highlighting. Furthermore, if the reporting recipient submits the edited content in the report document, the terminal responds by returning the edited sub-report document to server 203, which then synchronizes the sub-report document to the corresponding reporting recipient. This reporting recipient can be chosen by the reporting recipient or pre-set during the creation or configuration of the report document.

[0084] Based on the above brief introduction of the reporting management scheme and reporting management system provided in the embodiments of this application, the following points should also be noted:

[0085] ①The embodiments of this application mentioned above Figure 2 The system architecture shown is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. Those skilled in the art will understand that, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems. That is to say, Figure 2 The schematic diagram of the reporting management system shown is an exemplary schematic diagram; in actual applications, the number and distribution of devices (such as terminals and servers) included in the reporting management system may change, and the schematic diagram of the reporting management system in this application embodiment is not limited.

[0086] ② The reporting management solution deployed in this embodiment supports being integrated into social applications as a business sub-application; it also supports being deployed as a plugin within any business sub-application of a social application. In other words, the reporting management solution can be an application-level plugin, which can be deployed within a social application and invoked by the social application to implement the reporting management solution provided in this embodiment. This embodiment does not limit the specific form in which the reporting tool is integrated into the social application.

[0087] ③ The data collection and processing in this application embodiment should strictly comply with the requirements of relevant laws and regulations. Obtaining personal information requires the knowledge or consent of the individual (or a legal basis for information acquisition), and subsequent data use and processing should be carried out within the scope of laws, regulations, and the authorization of the personal information subject. For example, when this application embodiment is applied to specific products or technologies, such as when a sub-report document is submitted to the reporting recipient, the permission or consent of the person completing the sub-report document is required, i.e., the permission or consent of the reporting recipient is required. Furthermore, the collection, use, and processing of relevant data (such as the synchronization of already completed reporting content) must comply with relevant national and regional laws, regulations, and standards.

[0088] Based on the above description of the reporting management scheme, this application proposes an embodiment of a... Figure 3 The reporting management method shown primarily concerns the editing of reporting documents by target individuals within the target enterprise. This method can be executed by the aforementioned terminal 201; see [link to documentation]. Figure 3 As shown, this reporting management method may include the following steps S301-S303:

[0089] S301: Display reporting documents in social applications.

[0090] In practical implementation, when a target object (such as any member of the target enterprise) has a reporting need, such as a member of a project department wanting to report project progress to the project leader, the target object can select a reporting document, such as a daily work report, for the social application. The terminal responds to the target object's selection of the reporting document by displaying the document, specifically by displaying a service interface and showing the document content within that document, such as the content included in a daily work report. The reporting document can be pre-configured by the social application developers or created and published to the target object by a member of the target enterprise with document creation permissions; this embodiment does not limit the source of the reporting document.

[0091] like Figure 4As shown, assuming the social application is the aforementioned application containing multiple business sub-applications, and the reporting function is deployed in the target business sub-application; if a target object belonging to the target enterprise logs into the social application and wants to report, the target object can open the main service interface 401 of the social application. This main service interface 401 displays the application identifiers of each sub-application in the multiple business sub-applications, including the application identifier 402 of the target business sub-application. When the application identifier 402 is selected, the tool identifiers of various tools provided by the target business sub-application are displayed in the main service interface 401, including the tool identifier 403 of the reporting tool. Then, the target object can perform a trigger operation on the tool identifier 404, at which time the tool interface 404 of the reporting tool is displayed. This tool interface 404 displays one or more candidate reporting documents for which the target object has reporting or editing permissions. Thus, the target object can select a reporting document from one or more candidate reporting documents according to its reporting needs. The terminal then displays a service interface 405 containing the reporting document, and the document content of the reporting document is displayed in this service interface 405.

[0092] It should be noted that the embodiments of this application do not limit the interface flow process of opening a report document from a social application; Figure 4 This is merely an exemplary diagram illustrating how to open a report document from a social application, and does not limit the method of opening a report document from a social application.

[0093] For example, when the reporting document is pre-configured by the developers of a social application, the target audience can use... Figure 4 The method shown illustrates how to open a report document from a social application. This same approach can be used when the report document was created and published to the target audience by a document creator within the target company. Figure 4 The method shown can be used to trigger the opening of the report document, but other methods can also be used. For example... Figure 5 As shown, the creator of a report document can configure reporting reminders when creating the document. For example, once the report document is published, it can remind the recipients configured to submit it, ensuring they are promptly aware of the required report. In this case, the reminder can be displayed in relevant business sub-applications within the social application. For instance, a reminder message 501 can be displayed in the document sub-application (or conversation sub-application, etc.). The recipient can then trigger this reminder message 501 from the relevant business sub-application to access the service interface 502 containing the report document. This method of quickly triggering the display of the report document via a reminder message not only provides reporting reminders to recipients but also enables rapid triggering of the report document, improving the convenience of displaying the report document.

[0094] It should also be noted that when a social application is installed and runs on different devices, the interface style of each screen within the social application will change depending on the device. (The aforementioned...) Figure 4 and Figure 5 The examples all use the installation and running of social applications on a computer as an example to introduce the schematic diagrams of each interface in the social application. When the social application is installed and running on a mobile device, the schematic diagrams of each interface in the social application will change accordingly. Figure 6 This illustrates an exemplary interface flow where a target user actively opens and displays a report document within a social application installed and running on a mobile device. It's important to note that the content of each interface within the social application remains identical regardless of whether it's installed and running on a desktop or mobile device, ensuring that the reporting functionality is available on both platforms.

[0095] Furthermore, the report document includes one or more reporting items, each corresponding to a reporting event type. This reporting event type indicates the type of reporting event to be reported when the target object fills in the reporting item. For example, the reporting event type may include, but is not limited to, work summary type, work plan type, sales result type, project progress type, and product grayscale result type, etc., which are not limited in this embodiment. In other words, the reporting items in the report document can be understood as a fixed-structured reporting item. The target object reports the reporting event by editing (e.g., filling in) each reporting item in the report document. The reporting event here is the content that the target object needs to report, such as a work summary, work plan, or sales amount. It can be seen that the report document provided in this embodiment is a structured document content, specifically, each reporting item in the report document is a structured data structure. Compared with a report document that provides the target object with completely open editing capabilities, the target object only needs to edit the report document according to each reporting item to achieve the reporting, saving the target object time and workload in writing different reporting items, and improving the efficiency of report editing to a certain extent. Furthermore, by providing reporting documents with a unified structure and format to different reporting recipients, it is beneficial for them to carry out downstream business processing based on the unified format and structure of the reporting documents, such as statistics, sharing, and viewing, thereby improving the reporting recipients' reporting editing experience.

[0096] The following is in conjunction with the appendix Figure 7 The accompanying report document will elaborate on the report items in detail, such as... Figure 7As shown, the report document includes at least report item 701, report item 702, and report item 703. Each report item is a structured data format, specifically a pre-defined data structure. For example, report item 701's data structure is represented by report title information 7011 and report area 7012; report item 702's data structure is represented by report title information 7021 and report area 7022; similarly, report item 703's data structure is represented by report title information 7031 and report area 7022. The presentation of the report area varies depending on the report event type to which the report item belongs. For instance, if report item 703 belongs to the report event type of uploading attachments, then the report area 7032 in the data structure of report item 703 will appear as an upload component. Conversely, if report item 702 belongs to the report event type of filling in sales data, then the report area 7022 in the data structure of report item 702 will appear as an input box that supports editing. It should be noted that the embodiments of this application do not limit the number of reporting items included in the reporting document or the reporting event type to which the reporting items belong.

[0097] S302: Edit the report document according to the report items in the report document to obtain a sub-report document.

[0098] After the target user opens the report document from the social application, they can edit the report document to fill in the events they want to report, creating a sub-report document. This sub-report document is then submitted to the corresponding recipient of the report document, thus achieving the reporting of the events. Specifically, the target user can edit the document content to fill in the events they want to report. The document content can include all the information in the original report document; more specifically, it can include reporting information and template information. The reporting information consists of reporting items and rich text filled in by the recipient for each item. Template information refers to all information in the report document other than the reporting information itself; this information is generally pre-set by the document creator (such as a member of the target company or the developer of the social application).

[0099] In this embodiment, the target object is allowed to edit one or more of the reporting information and template information; that is, editing of a reporting document may include, but is not limited to, editing of the reporting information in the reporting document and editing of the template information in the reporting document. The specific implementation process of the target object performing reporting editing in the reporting document is described below, wherein:

[0100] (1) Edit the reporting information in the reporting document.

[0101] Specifically, the target object can find the target reporting item corresponding to the target reporting event that the target object needs to report in the report document. Optionally, all reporting items in the report document correspond to the target reporting events that the target object needs to report, and in this case, each reporting item in all reporting items is a target reporting item. Optionally, some reporting items in the report document correspond to the target reporting events that the target object needs to report, and in this case, each reporting item in that part of the reporting items is a target reporting item; wherein, the part of the reporting items that the target object needs to report in the report document can be pre-set by the document creator when creating the report document, or it can be selected by the target object in the report document according to its own reporting needs. Then, the target object edits the target reporting item in the report document according to the reporting event type to which the target reporting event belongs, to obtain a sub-report document. The editing operations performed on the target reporting item can include at least one of the following: rich text insertion operations, and annotation operations on the document content in the report document, etc.; rich text is a special text format that is more colorful than ordinary text, and rich text can include at least one of the following elements: text, images, documents, files, schedules, meetings, tables, and videos. This application supports the insertion of rich text into structured reporting documents, greatly enriching the content formats that can be inserted into reporting documents. This allows the target object to use rich text to more clearly and intuitively present the details of the content to be reported, thereby improving the reporting quality of sub-reporting documents.

[0102] The following describes the editing operations for target reporting items; these operations include inserting rich text and annotating document content.

[0103] 1) Editing operations for target reporting items are insertion operations for rich text.

[0104] Specifically, the target object can perform an insertion operation in the reporting area corresponding to the target reporting item according to the reporting event type to which the target reporting event belongs. The terminal then responds to this insertion operation by displaying the inserted rich text in the reporting area corresponding to the target reporting item. At this time, the data format of the inserted rich text matches the reporting event type to which the target reporting event belongs. This matching of the data format of the inserted rich text to the reporting event type can be understood as follows: since different reporting events belong to different reporting event types, their data formats differ. The difference in data formats between different reporting events is reflected in the difference in the data format of the rich text used to express the reporting event. For example, if the reporting event type is "work plan," considering that work plans are reported using text, the data format of reporting events belonging to the work plan type can include text. That is, when performing an insertion operation on a target reporting item corresponding to the work plan type, the inserted rich text often includes text, and the data format of the inserted rich text "text" matches the work plan type to which the target reporting event "work plan" belongs. For example, if the reporting event belongs to the project progress result type, considering that using tables, text, and charts to report project progress results usually ensures that the project progress results are better displayed, then the data format of the reporting event belonging to the project progress result type can include tables, text, and charts. That is, when inserting the target reporting item corresponding to the project progress result type, the inserted rich text can often include tables, text, and charts at the same time, and the data format of the inserted rich text "table", "text", and "chart" matches the work plan type to which the target reporting event "work plan" belongs.

[0105] As described above, the social application provided in this application embodiment includes at least one business sub-application. Each business sub-application corresponds to an application function provided by the social application, such as a meeting sub-application, a calendar sub-application, and a document sub-application, etc. This application embodiment supports selecting rich text from within the social application when inserting rich text for a target reporting item. That is, the rich text inserted into the reporting area corresponding to the target reporting item can originate from the corresponding business sub-application found in the social application. By connecting the various business sub-applications and reporting functions within the social application, the reporting function can rely on each business sub-application to achieve reporting related to business within the application, greatly facilitating data reporting within the target enterprise and expanding the usage rate of the reporting function to a certain extent. Of course, this application embodiment also supports inserting rich text from outside the social application into the reporting area corresponding to the target reporting item, such as rich text from the local terminal, rich text from the cloud, or rich text from the Internet; this application embodiment does not limit the source of the rich text.

[0106] The following, with reference to the accompanying diagrams, describes the specific implementation process of inserting rich text into the reporting area corresponding to the target reporting item when the rich text is an image (or picture), document, table, file, schedule, or meeting; among which:

[0107] ① Rich text as images enables mixed text and image layout in report documents, enriching the content presentation. Specifically, when using rich text as images, the following points need to be explained:

[0108] a) Supports inserting images into the reporting area of ​​the target reporting item. For example... Figure 8aAs shown, assuming the target reporting item is "Today's Work Summary" in a report document, this target reporting item corresponds to a reporting area 801. Reporting area 801 is used by the target object to edit the report for the reporting event "Today's Work Summary" to report their work summary for the day. Reporting area 801 displays a toolbar 802, which includes one or more editing components (or options, buttons, controls) required for report editing, including but not limited to the insertion component 8021, font type component 8022, and font bold component 8023, etc. The target object can use one or more editing components in the toolbar 802 to edit the report in reporting area 801. The report editing process is as follows: If the target object wants to insert an image while editing the report in the report area 801, the target object can trigger the insertion component 8021 in the toolbar 802. In response to this trigger, the terminal invokes its local file selector. This file selector retrieves at least one candidate image from local storage and outputs a display interface 803 to show at least one candidate image. The target object can then select one or more candidate images from the display interface 803. In response to the target object's confirmation of the selected candidate images, the selected candidate images are uploaded to the report area 801, specifically to the cursor position within the report area 801.

[0109] It is worth noting that, Figure 8a This description merely illustrates the process of inserting images into the reporting area and does not limit the scope of the embodiments in this application. For example, when displaying one or more candidate images in the display interface 803, the image format of the candidate images that can be selected by the target object must be compatible with the document format of the reporting document. Candidate images whose image formats are not compatible with the document format of the reporting document are unselectable in the display interface 803, such as being grayed out. Furthermore, in addition to invoking the local file selector to insert an image, it also supports inserting the image to be inserted into the reporting area 801 by copying the image to be inserted to the clipboard and pasting the image from the clipboard. Also, when the insertion component 8021 is triggered, it does not directly invoke the local file selector, but instead displays an options window that includes an image insertion option. This image insertion option can then be triggered to invoke the local file selector and execute the candidate process.

[0110] b) Supports image editing of images inserted into the reporting area. Image editing can include, but is not limited to, enlarging or reducing the image area, rotating, compressing, stretching, etc. For example... Figure 8bAs shown, if the target object wants to edit the image in the reporting area, it can first click on the image in the reporting area to select it; then, the target object can edit the selected image. It should be noted that... Figure 8b This description is merely illustrative of the process of editing inserted images in the reporting area and does not limit the embodiments of this application. For example, when the terminal is a mobile device, it also supports zooming in on the images inserted in the reporting area to overcome the problem of unclear image display due to the small screen size of mobile devices.

[0111] c) After an image is inserted into the reporting area, there are four image states: uploading, successful upload, failed upload, and retry. For example... Figure 8c As shown, after an image is inserted into the reporting area, a first status prompt 8041 is displayed in the reporting area. This first status prompt 8041 indicates that the image is in the uploading state, meaning that the image is being uploaded or inserted into the reporting area. During the image uploading process, the same background image element, upload icon, and upload progress (such as the percentage of upload progress) can be displayed in the image's display area, allowing the target audience to intuitively perceive the image upload progress and improving their image uploading experience.

[0112] Furthermore, if the image is successfully uploaded to the reporting area, a proportionally scaled thumbnail of the image is displayed in the reporting area to indicate that the image has been successfully uploaded. For example, when the terminal is a computer, the maximum width of the proportionally scaled thumbnail is the width of the reporting area; when the terminal is a mobile device, the maximum width of the proportionally scaled thumbnail is 400 pixels. If the image upload fails, a second status message 8042 and a third status message 8043 are displayed in the reporting area based on the image path and whether the image file can be indexed. The second status message 8042 indicates that the image upload has failed, and the third status message 8043 indicates that the image is in a retry state. Specifically, when uploading an image in the reporting area, the image path and file are cached locally on the terminal, and the server executes the image upload task. If the server fails to upload the image, it marks the upload task based on the task identifier and rereads the image path stored locally on the terminal for a "retry". If the server can reread the image path stored locally on the terminal, a third prompt message 8043 is displayed in the reporting area; if the server cannot reread the image path stored locally on the terminal, a second prompt message 8042 is displayed in the reporting area. Furthermore, when the image is in a retry state, the target object can trigger the third retry prompt message 8043 in the reporting area to automatically re-upload the image.

[0113] ② Rich text is used as a document to add content to the report document, thereby expanding the amount of content that the report document can hold.

[0114] Specifically, embodiments of this application support inserting documents into the reporting area of ​​a target reporting item. For example... Figure 9As shown, when the insert component in the toolbar of the reporting area of ​​the target report item is triggered, an options window is displayed, which includes document options. In response to the target object's selection of this document option, an input field 901 and a candidate window 902 are displayed at the cursor position in the reporting area. The input field 901 allows the target object to directly enter the document name to search for and insert documents. The candidate window 902 displays relevant document names searched based on the information entered by the target object in the input field using the local file selector. Thus, the target object can enter keywords of the document name to be inserted in the input field 901 and select the document to be inserted into the reporting area from one or more candidate documents searched based on the keywords displayed in the candidate window 902. The selected candidate document is inserted at the cursor position in the reporting area as a document hyperlink (identifying the document name and type; the link represents the document name and type), allowing the user to quickly open the document by triggering the link. This link can be deleted as a whole. The candidate document can be a document independent of the social application, or a document stored in a storage sub-application of the social application, or a document opened in a document sub-application; the embodiments of this application do not limit the source of the candidate document.

[0115] Therefore, the document insertion method provided in this application, which allows for real-time searching of candidate documents based on keywords while inputting the document name, only requires the target object to remember the keywords in the document name to achieve fast document search, greatly improving the speed and efficiency of document insertion.

[0116] ③ Rich text is presented as tables, allowing the addition of table content to the report document, thus expanding the amount of content the report document can hold.

[0117] Specifically, embodiments of this application support inserting tables into the reporting area of ​​target reporting items; these tables can originate from business sub-applications within social applications, such as document sub-applications or email sub-applications, or they can originate from the local storage space of the terminal. Figure 10 As shown, when the insert component in the toolbar of the reporting area of ​​the target report item is triggered, an options window is displayed, which includes table options. In response to the cursor falling on the location of this table option, a table definition window 1001 is output. The target object can define the number of rows and columns of the inserted table through this table definition window 1001, such as inserting a table with 2 rows and 3 columns; the table with the defined number of rows and columns is directly inserted at the cursor position in the reporting area.

[0118] ④ Rich text files are used to add content from the files to the report documents, thereby expanding the amount of content that the report documents can hold.

[0119] Specifically, embodiments of this application support inserting files into the reporting area of ​​a target reporting item; these files can originate from a business sub-application within a social application, such as a file sub-application, or from the terminal's local storage space. Figure 11 As shown, when the insert component in the toolbar of the reporting area of ​​the target report item is triggered, an options window is displayed, which includes file options. In response to triggering the file options in the options window, similar to inserting a document in the reporting area, an input field and a candidate window are displayed at the cursor position in the reporting area. The input field allows the target object to directly enter the file name to search for and insert files. The candidate window displays relevant file names searched based on the information entered by the target object in the input field using the local file selector. Files selected from the candidate window are inserted into the reporting area as hyperlinks, with the hyperlink displaying the file name and type (e.g., text, table, etc.).

[0120] ⑤ Rich text is used as a schedule to enable the addition of schedules to report documents. This allows users to easily view the corresponding sub-report documents and grasp the project's schedule information directly based on the schedule in the sub-report document, greatly facilitating project management and making it more centralized and efficient.

[0121] Specifically, embodiments of this application support inserting a schedule into the reporting area of ​​a target reporting item; this schedule is provided by a schedule sub-application within a social application. For example... Figure 12 As shown, when the insert component in the toolbar of the reporting area of ​​the target report item is triggered, an options window is displayed, which includes schedule options. When the cursor falls on the location of the schedule option in the options window, a schedule window 1201 is output; the target object can use the schedule window 1201 to select existing schedules or create new schedules. Further, optionally, the selected or created schedule is also inserted into the report document in the form of a document hyperlink, specifically inserted at the cursor position in the report document; optionally, the selected or created schedule can be inserted into the report document in the form of a card; the presentation of the inserted schedule is not limited in this embodiment.

[0122] ⑥ Rich text for meetings allows users to add meeting entry points to report documents, making it convenient for users to view the corresponding sub-report documents and quickly enter the meeting directly from the sub-report documents. This greatly facilitates meeting participation and increases meeting attendance.

[0123] Specifically, embodiments of this application support inserting meeting links into the reporting area of ​​a target report item; the meeting indicated by the meeting link can be pre-set in a meeting sub-application provided by a social application, or it can be temporarily created by the target object when editing a report in the reporting area. Figure 13 As shown, when the insert component in the toolbar of the reporting area of ​​the target report item is triggered, an options window is displayed, which includes meeting options. When the cursor falls on the location of the meeting option in the options window, the meeting window is output; the target object can use this meeting window to select existing meetings or create new meetings. Further, optionally, the selected or created meeting is also inserted into the report document as a hyperlink, specifically inserted at the cursor position in the report document; optionally, the selected or created meeting can be inserted into the report document as a card; this embodiment does not limit the presentation of the inserted meeting.

[0124] It should be understood that ①-⑥ above are only a few exemplary ways of inserting rich text given in the embodiments of this application; in actual applications, the specific implementation of the insertion operation of inserting rich text into the reporting area varies depending on the type of rich text, which is hereby explained.

[0125] 2) Editing operations for target reporting items are annotation operations for document content, specifically annotation operations for reporting information in document content. As mentioned above, the reporting information consists of the reporting item and the rich text filled in by the reporting object for the reporting item. When the reporting item is the target reporting item in the reporting document, the reporting information in the reporting document includes the reporting information consisting of the target reporting item and the rich text filled in by the reporting object for the target reporting item.

[0126] Specifically, if a target entity needs to report a target reporting event, it can annotate the target reporting item in the reporting document according to the reporting event type to which the target reporting event belongs. Annotation operations for target reporting items include at least one of the following: underlining, commenting, and revising the reporting information within the target reporting item. In other words, if a target entity needs to annotate reporting information in the reporting document (e.g., an enterprise administrator needs to comment on the content reported by the reporting entity, or the reporting entity needs to underline the reported content to indicate the content that the reported entity needs to focus on when viewing the sub-reporting document), then it is determined that the target reporting event it needs to report is likely important information in the reporting document. Therefore, the target entity can annotate the corresponding reporting information in the reporting document according to the reporting event type to which the target reporting event belongs (e.g., annotate event type).

[0127] like Figure 14As shown, the report document includes report information 1401, which consists of report items and rich text 1402 filled in for those report items. The rich text 1402 contains text. If the target object wants to annotate the text in the rich text 1402 of the report information 1401, it can select the text to be annotated. At this time, a toolbar 1403 is output for the selected text, which includes a highlighting option 14031. The target object can then trigger the highlighting option 14031 to highlight the selected text. Similarly, the toolbar 1403 also includes a comment option 14032. In response to the target object's triggering of the comment option 14032, a comment box 1404 is output. The target object can then comment on the selected text in the comment box 1404. Similarly, toolbar 1403 also includes revision option 14033. In response to the target object's trigger operation on revision option 14033, all revision traces can be retained in the target report item during the process of the target object revising the selected text (such as replacing, deleting, and adding).

[0128] Therefore, the embodiments of this application support the target object to annotate the reporting information according to its own needs. In addition to enriching the target object's operation methods for the reporting document, it also helps the target object to mark important content in the reporting document to attract the attention of the reporting object, thereby strengthening the reporting connection between the reporting object and the reporting object. In the project reporting scenario, it helps the project team to collaborate.

[0129] It should be noted that, Figure 14 This paper introduces various annotation operations by taking the example of performing a single annotation operation (such as underlining, commenting, or revising) on ​​selected text in a report. In practical applications, multiple annotation operations can be performed on the same content, such as underlining and commenting on selected text. Furthermore, in addition to the three mentioned above, annotation operations for report information can also include other operations, such as highlighting, adding text boxes, etc. The specific operations of annotation operations are not limited in this embodiment.

[0130] (2) Edit the template information in the report document.

[0131] As mentioned above, the document content in the report document includes not only the report information but also template information. This template information is edited by the document creator during configuration, or, in the case of a report document as a sub-report document (such as a report document obtained by the target object being a sub-report document submitted by another report object), the template information can be edited by the report object. In addition to supporting the reporting editing of the report information (report items and rich text filled in for the report items) in the report document as shown in (1) above, this application embodiment also supports the reporting editing of the template information in the report document. This reporting editing is specifically a annotation operation. Specifically, it supports the target object to perform annotation operations on the template information in the report document to obtain a sub-report document; wherein, the annotation operations performed on the template information include at least one of the following: underlining operation, comment operation, and revision operation on the template information.

[0132] like Figure 15 As shown, the report document includes template information 1501. In response to the selection of all or part of the information in the template information 1501, a toolbar 1502 corresponding to the selected information is output. This toolbar 1502 includes options for different functions, such as underlining, commenting, and revision options. In this way, the target object can trigger the corresponding options to underline, comment on, and revise the selected information. It should be noted that the specific implementation process of annotating the template information in the report document is similar to the aforementioned implementation process of annotating the report information in the report document; the above only considers... Figure 15 The specific implementation process of performing annotation operations on template information is briefly explained. For detailed operation procedures, please refer to the aforementioned description of annotation operations, which will not be repeated here.

[0133] Furthermore, this application embodiment also supports commenting on a report document as a whole to obtain a sub-report document. That is, it supports the target object to treat the entire report document as a whole and comment on it; for example, a project leader can comment / evaluate the reporting quality of a sub-report submitted by a project team member. This method of directly commenting on the report document as a whole enables report editing to adapt to a wider range of reporting scenarios, providing powerful report editing capabilities for the reporting object, and improving the reporting experience and quality.

[0134] For example, a diagram illustrating the commenting process on the entire report document can be found here. Figure 16a ;like Figure 16aAs shown, a comment component 1601 is displayed in the report document, which is used to comment on the entire report document. If the target object wants to comment on the entire report document, the target object can perform a trigger operation on the comment component 1601. At this time, the terminal responds to the trigger operation on the comment component 1601 and outputs a comment window 1602. The comment window 1602 can be displayed in a floating form at a specific position on the terminal screen (such as the top position of the report document, the bottom corner position, etc.) to indicate to the target object that the current comment is on the entire report document. Of course, in order to avoid the comment window 1602 displayed in a floating form from obscuring the display content on the terminal screen, this embodiment of the application also supports the target object to drag the comment window 1602 on the terminal screen to change the position of the comment window 1602 according to their own visual needs.

[0135] The above (1) and (2) respectively introduce the editing of reporting information and template information in the reporting document; it should be understood that the specific editing methods for the reporting document are not limited to the above-mentioned methods. For example, the embodiments of this application also support batch deletion of the content already filled in the reporting document, realizing quick clearing of the reporting document and facilitating the target object to start editing the reporting document again. For example, the implementation process of batch deletion of the content already filled in the reporting document can be found in Figure 16b The report document displays a delete control 1603; when the delete control 1603 is triggered, the content already entered in the report document is cleared.

[0136] Furthermore, this application embodiment also supports multiple members within the target enterprise to collaboratively edit the same report document. This method of supporting multi-person collaborative editing has significant advantages in scenarios involving editing report documents. For example, project tasks are often completed by multiple project team members. When reporting on a project, if only a single project team member reports, the results are often inaccurate. Supporting multiple project team members to collaboratively edit the same report document not only improves the quality of the report but also greatly increases the speed and efficiency of the report.

[0137] In the specific implementation, the report document includes a collaborative editing component. If the target object wants other objects to participate in the reporting process while it is editing the report document, the target object can trigger the collaborative editing component. In response to this trigger, the terminal displays the target company's corporate address book. This address book includes member identifiers of each member of the target company, partial identifiers of each department within the target company, or the session identifier of the chat room where the target object is located. The target object can then select one or more member identifiers from the corporate address book. Upon confirmation of the selected member identifiers, the target object displays these member identifiers in the report document, indicating that the company member corresponding to each of these member identifiers is allowed to collaboratively edit the report document.

[0138] An exemplary diagram of collaboratively editing a report document can be found here. Figure 17 ;like Figure 17 As shown, the report document includes a collaborative editing component 1701. When a target object wants to invite other objects to edit the report document together, it can trigger an operation on the collaborative editing component 1701. In response to the trigger operation on the collaborative editing component 1701, the terminal outputs a member selection window 1702. This member selection window 1702 includes member identifiers of each member in the target enterprise, department identifiers of departments within the target enterprise, and the session identifier of the chat room where the target object is located, etc. Thus, the target object can perform an identifier selection operation in the member selection window 1702. For example, if the selection operation selects the session identifier of a group chat session, it means that the target object wants every group member in that group chat session to participate in the report document presentation. If the target object performs a confirmation operation on the selected session identifier (such as a trigger operation on the confirmation option), the report document displays the member identifiers of each group chat member in the group chat session corresponding to the session identifier (e.g., member identifier 1703 for member 1), indicating that every group chat member in the group chat session can perform real-time collaborative editing in the report document.

[0139] S303: Submit the report document.

[0140] In specific implementation, the report document includes a submission component. After the target object finishes editing the report document, it can trigger an operation on the submission component to submit the target object to the report document's recipients. The recipients of the report document can be selected by the target object from the target company's address book, pre-configured by the document creator when creating the report document, or a subset of recipients configured by the document creator while the target object selects the remainder. This application embodiment does not limit the method for determining the recipients.

[0141] It's worth noting that if, when the submission component is triggered, the terminal detects that rich text is still being uploaded in the report document, then for the submission of the corresponding sub-report document, a target prompt message is output. This message informs the target object that rich text is still being uploaded and the sub-report document cannot be submitted temporarily; submission should wait until the rich text upload is complete. Figure 18 As shown, if the image in the reporting area corresponding to reporting item 1801 is in an uploading state, and the target object performs a trigger operation on the submission component 1802, then the target prompt information 1803 can be displayed in the display area where reporting item 1801 is located. On the one hand, it reminds the target object that there is still a rich text in the reporting document that is in an uploading state and cannot be submitted. On the other hand, it informs the target object of the display position of the rich text in the uploading state in the reporting document, so that the target object can perform subsequent processing in a timely manner (such as waiting for the upload, or deleting the rich text in the uploading state, etc.).

[0142] In summary, the advantages of the powerful report editing capabilities provided by the report management solution in this application embodiment can be summarized as follows: ① Improved reporting efficiency and enhanced content expression: The report sub-applications introduced in the social application have powerful editing capabilities, supporting the use of the application capabilities of other sub-applications in the social application, greatly enriching the content formats that can be edited into the report document; such as supporting the insertion of rich text, tables and documents from the document sub-application, and calendars from the schedule sub-application, etc. By combining text and images in the report document, the completed sub-report document can present complex information more intuitively, making it easier for the recipient to understand the report content. ② Enhanced team collaboration and optimized project management: On the one hand, when filling out the report document, the recipient can use the application capabilities of other sub-applications in the social application to directly insert schedules, documents, files, and meeting content into the report document, which helps the recipient understand the sub-report document. For example, integrating a schedule into the sub-report document can help the project team better track project progress and important events using schedule management functions. On the other hand, it supports interactive features such as text annotation, like underlining, and comments, in the reporting document or sub-reporting document, which promotes communication and collaboration among members of the target company and improves the quality and speed of feedback.

[0143] Please see Figure 19 , Figure 19 This is a flowchart illustrating another reporting management method provided in an exemplary embodiment of this application; the reporting management method mainly concerns the editing of reporting documents by target objects within a target enterprise. This method can be executed by the aforementioned terminal 201; see [link to documentation]. Figure 19 As shown, this reporting management method may include the following steps S1901-S1906:

[0144] S1901: Display reporting documents in social applications.

[0145] S1902: Edit the report document according to the report items in the report document to obtain a sub-report document.

[0146] It should be noted that the specific implementation process shown in steps S1901-S1902 is the same as that described above. Figure 3 The specific implementation process shown in steps S301-S302 in the example is the same. Please refer to the relevant description of the specific implementation process shown in steps S301-S302 above. It will not be repeated here.

[0147] S1903: Add annotations to the template information in the report document to obtain a sub-report document.

[0148] S1904: Perform comment operations on the report document as a whole to obtain a sub-report document.

[0149] It should be noted that the reporting editing performed by the target object on the report document includes not only the editing operation shown in step S1902, but also the annotation operation on the template information shown in step S1903, and the comment operation on the report document shown in step S1904, to obtain the final sub-report document. The specific implementation process shown in steps S1903-S1904 can be found in the relevant description of the content shown in step S302 above, and will not be repeated here.

[0150] In addition to supporting the target object to write report documents using the report editing methods shown in steps S1902-S1903 above, this embodiment of the application also supports the target object to quickly edit report documents by importing the document content from previously edited historical sub-report documents into the current report document to be edited. The specific details of editing report documents via document import can be found in step S1905.

[0151] S1905: By importing documents, the report document can be edited to obtain a sub-report document.

[0152] Considering the periodicity of sub-report document submissions, and that some reporting event types require the same or similar reporting events across different reporting periods—for example, work summary reports require the target object to complete and submit sub-report documents in each reporting period, with the reporting events in daily sub-report documents potentially being the same or largely similar—this application embodiment supports importing edited (or submitted) historical sub-report documents into the currently edited report document to improve the efficiency of reporting different sub-report documents corresponding to the same report document. This enables rapid editing of report documents and improves the speed and efficiency of report editing.

[0153] In the specific implementation, the report document includes an import component. If the target object wants to use a historical sub-report document to overwrite the current report document, it can trigger an operation on the import component. The terminal responds to this trigger operation by the target object and outputs / displays a report list window. This report list window displays one or more historical sub-report documents corresponding to the currently edited report document. These historical sub-report documents can be those submitted by the target object within a historical reporting period, or they can be sub-report documents that the target object edited in the current reporting period but saved as drafts. Then, the target object can select a historical sub-report document in the report list window whose content is similar to the content they want to report. Thus, based on the document selection operation performed by the target object in the report list window, the terminal can select a target historical sub-report document from one or more historical sub-report documents. This target historical sub-report document can be any one of the one or more historical sub-report documents. The terminal then uses the content of this target historical sub-report document to overwrite the corresponding content in the current report document to obtain the sub-report document. The overlay display here can refer to replacing the edited rich text in the reporting area corresponding to the reporting item in the target historical sub-report document with the rich text in the reporting area corresponding to the corresponding reporting item in the report document (the reporting area corresponding to the corresponding reporting item can be empty).

[0154] To prevent accidental operation by the target user, this embodiment supports prompting the target user before displaying the corresponding document content in the report document using the document content from the target historical sub-report document. This prompts the target user to reconfirm whether they need to complete the report document using the document import method, thus avoiding accidental operation and improving the accuracy of report document editing. Specifically, before displaying the corresponding document content in the report document using the document content from the target historical sub-report document, a content overwrite prompt is output. This prompt indicates whether to use the document content from the target report document to overwrite the corresponding document content in the report document. If the target user wants to use the document content from the target report document to overwrite the corresponding document content in the report document, they perform a confirmation operation on the content overwrite prompt. At this time, based on the target user's confirmation operation on the content overwrite prompt, the terminal triggers the step of displaying the corresponding document content in the report document using the document content from the target historical sub-report document.

[0155] The following is in conjunction with the appendix Figure 20 This section describes the process of using the content of a target historical sub-report document to overlay and display the corresponding document content in the report document; for example... Figure 20As shown, the report document includes an import component 2001. In response to a trigger operation on the import component 2001, a report list window 2002 is output. This report list window 2002 includes one or more historical sub-report documents submitted by the target object within a historical time period, such as historical sub-report document 1, historical sub-report document 2, historical sub-report document 3, etc. To facilitate the target object's understanding of the general content of each historical sub-report document, this embodiment supports displaying the submission time of each historical sub-report document in the report list window 2002, making it easier for the target object to select a historical sub-report document. Assuming the target object wants to use historical sub-report document 2 as the report content for this report, the target object performs an identifier selection operation on historical sub-report document 2 in the report list window 2002. In response to the identifier selection operation on historical sub-report document 2, the terminal outputs a content overwrite prompt message 2003. This content overwrite prompt message 2003 is used to allow the target object to confirm whether to replace the corresponding document in the displayed report document with the corresponding document content from historical sub-report document 2. If the target object confirms the content overwrite prompt 2003, the terminal uses the document content from historical sub-report document 2 to overwrite the corresponding document content in the report document. For example, the report document includes report item 2004, report item 2005, and report item 2006; if report item 2004 contains rich text 1, and the corresponding report item in historical sub-report document 2 contains rich text 2, then rich text 2 will replace rich text 1 in report item 2004; similarly, if the report area corresponding to report item 2005 is empty, but the report area corresponding to the corresponding report item in historical sub-report document 2 is not empty, then the content of the report area corresponding to the corresponding report item in historical sub-report document 2 will be filled into the report area corresponding to report item 2005; similarly, if the attachment in the report area corresponding to report item 2006 is empty, then the attachment in the report area corresponding to the corresponding report item in historical sub-report document 2 will be added to the report area corresponding to report item 2006.

[0156] In addition to supporting, the embodiments of this application also support, Figure 20 As shown, in addition to using the rich text filled in for all reporting items in the target historical sub-reporting document to cover the rich text in the reporting area corresponding to the reporting item in the reporting document, this application embodiment also supports the target object to independently select the reporting items that need to be covered from the target historical sub-reporting document; this method of allowing the target object to independently select the reporting items that need to be copied meets the target object's personalized overlay display needs and improves the target object's reporting experience.

[0157] In practice, after the target object selects a target historical sub-report document from the report list window, the document content of that target historical sub-report document can be displayed in the social application; for example, a preview window can be output in the social application to display the document content of the target historical sub-report document. In this way, the target object can select target content from the document content of the target historical sub-report document according to its needs; the target content includes rich text entered for one or more reporting items. In response to the target object's selection operation of target content in the target historical sub-report document, the terminal uses the target content to overlay the rich text in the reporting area corresponding to the corresponding reporting item in the report document.

[0158] like Figure 21 As shown, in response to the target object's selection operation of the historical sub-report document 2 in the report list window, a preview window 2101 is output on the terminal screen of the terminal. The preview window 2101 displays the document content of the historical sub-report document 2, including but not limited to each report item and corresponding rich text in the historical sub-report document 2. The document structure of the historical sub-report document is the same as the document structure of the report document to be edited, specifically, the report event type to which each report item belongs and its display position in the document are the same. In this way, the target object can select the target content that it wants to copy into the report document in the preview window 2101, such as selecting the rich text in the report area corresponding to the report item "Today's Work Summary" and the rich text in the report area corresponding to the report item "Sales Change List". This embodiment of the application does not limit the selection method of selecting target content in the preview window. In this way, the terminal can use the rich text in the reporting area corresponding to the reporting item "Today's Work Summary" in the historical sub-report document 2 to overlay the edited rich text in the reporting area corresponding to the reporting item "Today's Work Summary" in the report document, and display the rich text in the reporting area corresponding to the reporting item "Sales Change List" in the historical sub-report document 2 in the reporting area corresponding to the reporting item "Sales Change List" in the report document.

[0159] Furthermore, this application embodiment also supports merging rich text entries for the same reporting item in at least two historical sub-report documents corresponding to a reporting document, and then displaying them overlaid in the reporting area corresponding to the reporting item in the reporting document; this satisfies the target object's need to merge multiple reporting contents from historical reports, improves the reporting efficiency of the reporting document, and enhances the target object's reporting editing experience. Specifically, the target object selects at least two target historical sub-report documents from the reporting list window, taking as an example a set of two target historical sub-report documents, including a first historical sub-report document and a second historical sub-report document.

[0160] Optionally, it supports merging the rich text in the corresponding reporting areas of all reporting items in the first and second historical sub-report documents to achieve content coverage of the entire reporting document. For example... Figure 22a As shown, after the target object selects the first historical sub-report and the second historical sub-report from the report list window, it can trigger an operation on the merge option 2201 in the report list window, indicating that the target object wants to merge the first historical sub-report and the second historical sub-report. Then, the terminal merges the rich text entered for each report item in the first historical sub-report document with the rich text entered for the corresponding report item in the second historical sub-report document, obtaining the rich text in the report area corresponding to each report item after merging; and uses the rich text in the report area corresponding to each report item after merging to overwrite the rich text in the report area corresponding to the corresponding report item in the report document.

[0161] Optionally, it supports customizing the merging of rich text in the corresponding reporting areas of some reporting items in the first and second historical sub-report documents for the target object, achieving personalized content coverage. For example... Figure 22b As shown, after the target object selects the first and second historical sub-reports from the report list window, a preview window is output. This preview window displays the document content of the first historical sub-report document by default, or the document content of the second sub-report document by default, or allows the target object to switch between displaying the document content of the first and second historical sub-report documents in the preview window. Then, the target object selects the rich text in the corresponding report area of ​​the report item in the document content displayed in the preview window. For example, if the rich text in the report area corresponding to the report item "Today's Work Summary" in the first historical sub-report document is selected, then the rich text in the report area corresponding to the report item "Today's Work Summary" in the first historical sub-report document is merged by default. In this way, the rich text in the report area corresponding to the merged report item "Today's Work Summary" will cover the already edited rich text in the report area corresponding to the report item "Today's Work Summary" in the current report document.

[0162] Therefore, the embodiments of this application support merging the document content of multiple historical sub-report documents. Especially in content summary reporting scenarios, compared with the requirement for the target object to manually summarize the content of multiple reporting cycles, it greatly improves reporting efficiency and enhances the reporting editing experience of the target object.

[0163] It should be noted that: ① The above is merely an exemplary process for implementing report editing using the document import method in this application embodiment, and does not limit the scope of this application embodiment. For example, this application embodiment also supports using the document content from the historical sub-report document previously filled out for the report document by default to overwrite the corresponding document content in the report document. ② This application embodiment supports importing the document content of the historical sub-report document into the report document to be edited using the above method, and then using the aforementioned rich report editing capabilities to perform secondary report editing on the imported report document, such as inserting rich text, annotating report information, and annotating template information on the imported document content, to form the final sub-report document.

[0164] Furthermore, the preceding content primarily describes the process of inserting rich text and performing annotation operations in a report document from an interface perspective; the following section describes the backend implementation of inserting rich text and performing annotation operations in a report document from a backend technology perspective. Specifically, after the target object performs an editing operation on a report item in the report document, the terminal can create a change instruction (e.g., a changeset) based on the editing operation in the report document. The change instruction describes the operation attributes of the editing operation in the report document, which may include, but are not limited to, at least one of the following: operation position, operation type, operation content, and operation target. Specifically, the operation position indicates the position of the report item operated on in the report document; the operation type indicates the type of operation, such as inserting rich text or rotating rich text; the operation content indicates the edited content, such as the inserted rich text; and the operation target indicates the purpose of the editing operation, such as inserting rich text at the cursor position in the report area corresponding to the report item. Then, the terminal binds the created change instruction to the report document and renders and displays the document content generated by the editing operation based on the change instruction.

[0165] Furthermore, considering that the sub-report documents created by inserting rich text will be submitted to the reported object or a temporary associated party (i.e., an object that is not the reporting object or the reported object of the report document, but has the permission to view the sub-report document), this application embodiment also supports sharing change instructions to the reported object (or temporary associated party) corresponding to the report document to achieve content synchronization of the sub-report documents. This allows the reported object to synchronously render and display the document content generated by the editing operation based on the change instructions. In this way, the content of the sub-report documents can be synchronized across multiple devices, thereby ensuring the consistency of information within the team and helping to ensure team collaboration capabilities.

[0166] It should be noted that the background technical processes executed by the terminal based on the editing operation vary depending on the specific operation procedure. The following details the background technical implementation for editing operations such as inserting rich text (images or pictures), documents, files, schedules, and meetings into the reporting area, as well as performing annotation operations in the reporting document; among them:

[0167] (1) Rich text is an image or a table.

[0168] The process of uploading images or tables to the reporting area is similar. The following example illustrates the process of uploading an image to the reporting area, using rich text inserted in the reporting area corresponding to a reporting item as an example. This process includes: After the target object selects the image to be inserted / uploaded, the image is finally uploaded to the static resource file storage service. In this service, the image is stored as a file, and an image file browsing address (or browsing URL (uniform resource location)) and a file identifier (FileID) are generated. The social application in the terminal uses this file identifier to retrieve the image's browsing URL from the static resource file storage service and writes the browsing URL into the document content of the reporting document, specifically into the location where the target object wants to insert the image. The social application in the terminal then notifies the file sub-application's write content command interface to write the image's FileID to the file, thus achieving image file storage. The terminal also generates a change set based on the operation attributes of the image insertion editing operation performed in the report document. After binding the change set to the report document, it triggers the terminal to use the image's FileID to exchange for image stream data. Specifically, it triggers the terminal to render the image into the report file based on the image stream data, thus realizing the insertion of the image into the report document for the object to view.

[0169] The process by which the terminal generates a change instruction based on the operation attributes of inserting an image into the reporting document can roughly include: pasting the image as a link into the reporting document based on the editing operation (specifically, the insertion operation) performed on the image by the target object; the reporting document then detects the pasting event and identifies the pasted image link; and finally, it structures the image link, specifically by identifying, understanding, and parsing the content included in the image link (such as image elements included in the image), and generates a change instruction based on the structured linked data.

[0170] A changeset is a data structure of instructions used to detect and apply changes to a document. When applied to editing reports, changesets help understand how a report changes from one state to another, such as from a state without rich text to a state with rich text inserted. Specifically, a reports' changeset starts from a particular state and describes how to reach the new state. By applying a series of changesets to a report, its history can be recorded, allowing for rollback to any previous state when needed. Changeets are particularly effective for editing online collaborative reports because they allow multiple users to edit simultaneously. Each user's changes can be recorded as a changeset, and then these changes are merged into a single report containing all user changes.

[0171] Changesets can include the following operations: ① Insert: Inserts rich text at a specific location in the report document. For example, to insert an image into the report area corresponding to a report item, an insert operation can be created, specifying that the rich text to be inserted is the image and the insertion location is the report area corresponding to the report item. ② Delete: Removes content from a specific location in the report document. For example, if target text is edited in the report area corresponding to a report item, a delete operation can be created, specifying that the text to be deleted is the report area corresponding to the report item and the document length of the text to be deleted (such as the number of characters in the text). ③ Retain: Retains some content in the report document without making any changes; this is usually used to indicate that the content should remain unchanged between insert and delete operations.

[0172] (2) Rich text is a document.

[0173] Specifically, when the target object performs an insert operation in the report document, the report document can recognize the insert operation. If the report document recognizes that the inserted content includes links with specific domain names and path characteristics, it determines that the inserted content is a document link. The terminal structures this document link in the report document to insert the document as a link at the location of the insert operation, allowing the target object to quickly open the relevant document by clicking the link in the report document.

[0174] The process of structuring and rendering document links can include, but is not limited to: ① Link identification and structuring: When a link is inserted into a report document, it is first checked whether the link conforms to specific domain name and path characteristics. If so, the link is determined to be a document link, and it will be structured. Specifically, the document link is structured into a special object containing the document link information and a function to open the document link. ② Creating a changeset: After identifying and structuring the document link, a changeset is created to represent the insertion operation for that document link in the report document. This changeset contains the position of the insertion operation and the inserted content (i.e., the structured document link), so the insertion operation and its position in the report document can be recorded based on the changeset. ③ Applying the changeset: Applying the changeset to the report document means inserting the structured document link at a specified position in the report document (such as the report area corresponding to the report item). This document link, as part of the report document, can be opened by clicking on the object. ④Storing and sharing changesets: Store this changeset on the server and share it with all users who are viewing a report document or sub-report document that contains this changeset; in this way, all users can see the newly inserted document link and can click to open the document link.

[0175] (3) Rich text is a file.

[0176] Specifically, when the target object performs a file insertion operation in the report document, the report document can recognize this operation. If the report document recognizes that the inserted content includes links with specific domain names and path characteristics, it determines that the inserted content is a file link. The terminal creates an object representing the file reference relationship. This object contains information about the inserted file link (such as the file name and ID) and a function that can open the file (such as a Uniform Resource Locator URL for a file sub-application in a social application that jumps from the report function to open the file). Then, the terminal creates a changeset to represent the file link insertion operation. This changeset contains the location of the insertion operation and the inserted content (i.e., the reference relationship object). In this way, the insertion operation and its location in the report document can be recorded based on the changeset. Next, the changeset can be applied to the report document, meaning that a reference relationship object is inserted at a specified location in the report document. This reference is part of the report document and can be clicked and opened by the object. Finally, the changeset can be stored on a server and shared with all users viewing the report document or sub-report document to ensure that all users can see the newly inserted file reference and can click to open it.

[0177] (4) Rich text for schedules or meetings.

[0178] The process of uploading schedules or meetings to the reporting area is similar. Below, we'll use a rich text file inserted into the reporting area corresponding to a report item as an example to illustrate the process of uploading a schedule to the reporting area. This process can include: ① Creating a schedule: When the target object selects to insert a new or existing schedule in the reporting document, first, an object representing this schedule is created. This object contains schedule information (such as title, time, location, and participants), and a function to open the schedule (such as a Uniform Resource Locator URL supporting navigation from the reporting function to the schedule sub-application). ② Creating a changeset: A changeset is created to represent the insertion operation for the schedule. This changeset contains the location of the insertion operation and the inserted content (i.e., the schedule). This allows the insertion operation and its location in the document to be recorded based on the changeset. ③ Applying the changeset: Applying the changeset to the reporting document means that a new schedule has been inserted at a specified location in the reporting document (such as inserting a summary of the reporting document as a card or link). This schedule, as part of the reporting document, can be clicked and opened by the object. ④ Share the changeset: Store the changeset on the server and share it with all users who are viewing the report document. This way, all users can see the newly inserted schedule and can click on and open the new schedule.

[0179] (5) Perform annotation operations in the report document.

[0180] The annotation operations can include, but are not limited to, underlining, commenting, and revision operations. The backend technology implementations of these operations are similar. The following section uses annotation as an example of a commenting operation to describe the process of making comments in a report document.

[0181] ① Comment Creation: When a target object selects text and adds a comment in a report document, first, an object representing the comment is created. This object contains the comment's content, the comment's author, and the position of the text associated with the comment (e.g., the character indices of the beginning and end characters of the commented document). Second, a unique comment ID is added to this object for subsequent follow-up and management. ② Changeset Creation: A changeset is created to represent the comment operation performed by the target object on the content in the report document. This changeset contains the comment operation type (e.g., adding a comment), the operation target (e.g., the target object's object identifier ID), and the operation content (e.g., the added comment content). This allows the comment operation and its associated text position to be recorded based on the changeset. ③ Changeset Application: Changesets can be applied to report documents, meaning that a new comment added at a specified location in the report document becomes part of the report document and can be seen and replied to by other users. ④ Changeset Sharing: Changesets can be stored on a server and shared with all users viewing the report document or sub-report documents. This allows all users to see the newly added comments and reply to them. ⑤ Multi-user interaction: To support multi-user interaction, a reply list needs to be added to the comment object. When a user replies to a comment, a new reply object is created and added to the comment object's reply list. A new changeset also needs to be created to represent this reply operation, then applied to the sub-report document and stored and shared with all users.

[0182] S1906: Submit the report document.

[0183] In the specific implementation, the completed sub-report document includes a submission component; after the target object confirms that it has completed the sub-report document, it can trigger the submission component to submit the sub-report document to the reporting object. It should be noted that the specific implementation process shown in step S1906 is the same as described above. Figure 3 The specific implementation process shown in step S303 in the illustrated embodiment is the same. Please refer to the relevant description of the specific implementation process shown in step S303 above, which will not be repeated here.

[0184] Furthermore, to facilitate the target audience's editing of the report document by referring to the document content in the corresponding historical sub-report documents, this embodiment also supports displaying the corresponding historical sub-report documents in the service interface that displays the report document. This way, if the target audience wants to refer to the document content in the historical sub-report documents for report editing, they can quickly initiate a detailed view of the historical sub-report documents from the service interface, which can improve report quality and efficiency to a certain extent. Specifically, in the service interface that displays the report document—specifically, the service interface that displays the document content included in the report document—a list of historical submission versions corresponding to the reporting object is also displayed. This list of historical submission versions includes document identifiers of one or more historical sub-report documents that the target audience has submitted for the report document at a historical time. Thus, when the target audience wants to view any historical sub-report document, they can perform a selection operation on the document identifier of any historical sub-report document in the historical submission version list. At this time, the terminal responds to the selection operation performed in the historical submission version list and displays the document content of the historical sub-report document corresponding to the selected document identifier.

[0185] A diagram illustrating how to display a list of submitted report versions within a service interface that displays report documents can be found here. Figure 23 ;like Figure 23 As shown, the report submission version list 2301 includes multiple historical sub-report documents displayed in chronological order of submission time. For example, the document identifier of the latest historical sub-report document 2 is displayed above the earlier historical sub-report document 1. Of course, the order of the multiple historical sub-report documents in the report submission version list can be customized by the target object to meet its viewing needs. Furthermore, if any document identifier in the historical submission version list 2301 is triggered, the document content of the historical sub-report document corresponding to that document identifier is displayed. It is worth noting that, in addition to including the historical sub-report documents corresponding to the target object's previously submitted report documents, the report submission version list can also display new historical sub-report documents created by the reported object through report editing (such as comments) of the submitted historical sub-report documents.

[0186] In summary, on the one hand, the embodiments of this application provide powerful report editing capabilities, greatly enriching the content formats that can be edited into report documents. This allows the completed sub-report documents to present complex information more intuitively, making it easier for the recipients to understand the report content, promoting communication and collaboration among members of the target company, and improving the quality and speed of feedback. On the other hand, the embodiments of this application support report editing via document import, greatly improving the efficiency of report editing and meeting the needs of the target recipients to refer to the content of historical sub-report documents for report editing, thus improving the experience of the target recipients in report editing.

[0187] The foregoing embodiments primarily introduce the rich report editing capabilities of the reporting tool (such as supporting the insertion of rich text and annotation in structured report documents), and the backend support for report editing capabilities (such as creating change commands to achieve report editing). Subsequent sections will introduce the overall reporting architecture, report document configuration and summarization, and other report-related content involved in the embodiments of this application; wherein:

[0188] I. Application Architecture.

[0189] The application architecture related to the reporting management method provided in this application embodiment can be found in [reference needed]. Figure 24a ;like Figure 24a This application architecture, from top to bottom, can include: a view layer, a routing layer, an access layer, a logic layer, and a storage layer. The view layer is the user interface that users can see and interact with, responding to user requests and displaying corresponding content. The routing layer is typically implemented in network devices (such as routers) and is responsible for guiding data transmission based on addressing schemes, usage patterns, and reachability. The access layer provides users with the ability to access the application system within their local network segment, primarily addressing the communication needs between adjacent users and providing sufficient bandwidth for this purpose. The logic layer is an intermediate layer for data abstraction, describing the overall logical structure of the database data. The main function of the storage layer is to provide physical storage for data and ensure its security and reliability, supporting encryption, compression, and backup operations to protect data security. The view layer, routing layer, access layer, logic layer, and storage layer work together in the network and application architecture to ensure correct data transmission, secure storage, and efficient display, thereby providing users with a smooth and secure interactive experience.

[0190] The structural diagram of the storage layer can be found in [reference needed]. Figure 24b ;like Figure 24bAs shown, the reporting management method provided in this application embodiment utilizes storage services provided by multiple storage servers. These storage servers may include, but are not limited to, document / template configuration servers, comment servers, and form servers. The document / template configuration server stores configured or created reporting documents (also called reporting templates); it provides a template list to the target object, which includes document identifiers (e.g., ...) of one or more reporting documents for which the target object has editing permissions. Figure 24b (Document / Template 1, Document / Template 2, etc.). The comment server is used to store comment information added to the report document. The form server is used to store the text content of each of the multiple sub-report documents corresponding to the report document; the form here can be understood as a form used to summarize the document content of each of the multiple sub-report documents corresponding to the report document, making it convenient for enterprise administrators or the reported subjects to view multiple sub-report documents.

[0191] II. Introduction to the reporting function.

[0192] (1) Reporting framework.

[0193] The reporting management method provided in this application mainly involves five business roles: enterprise administrator, document creator, reporting object, reported object, and temporary associate. The reporting document involved in this application is a document file containing a reporting content framework and template rules for the report to be filled in. The reporting content framework defines the reporting content to be filled in by the reporting object, such as project progress, sales volume, and work details. The template rules define the visibility scope of the reporting document (e.g., the reporting object and reported object), reporting frequency / cycle (e.g., weekly reporting), and reporting reminder notifications (e.g., providing a reminder before the end of the reporting cycle). Considering that the reporting document defines the reporting content that the reporting object needs to fill in for each report and the template rules of the reporting document, it functions similarly to a template; therefore, in this application embodiment, the reporting document can also be called a reporting template. In this application embodiment, the reporting template and the reporting document are not distinguished in description.

[0194] A diagram illustrating the flow of reporting documents and sub-reporting documents between the five business roles during reporting can be found here. Figure 25 ; the following is combined Figure 25 The permissions of each role in the reporting scenario are explained, including:

[0195] ① Enterprise Administrator: This refers to an enterprise member within the target enterprise who has management authority over the reporting function. The enterprise administrator can manage reporting templates through the management backend or the management portal on the terminal. When managing reporting templates, the administrator can perform backend authentication based on the object identifier (vid) of the operator (or document creator) currently operating on the reporting document, the target enterprise's unique identifier (corpid), the operator's identity document (skey), and the reporting template (template_id). This verifies whether the operator has the right to access the reporting template. After successful authentication, the administrator can create, save, or update reporting templates.

[0196] For example, the management permissions of an enterprise administrator can be found in [reference needed]. Figure 26a Management permissions include, but are not limited to, managing all reporting documents (or reporting templates) within the target enterprise. This management can include template creation and editing, specifically including, but not limited to: visibility scope, template rules, specifying superior rules (i.e., the superior reported object of the corresponding sub-reporting document), tag organization (such as tag classification of the reporting type to which the reporting document belongs), template field configuration (such as the configuration of fields in the reporting content framework of the reporting document), and template control rule configuration (such as the configuration of functional rules for each control in the reporting content framework of the reporting document). For example, when an enterprise administrator obtains a reporting template "collection form" created by the document creator, or a reporting template "collection form" created by the enterprise administrator themselves, the template rules they set can include: setting the reported object of the reporting document as the superior of the reported object, or the enterprise member corresponding to the tag. When saving the template rules in the background, the attribute of the reported object for the current reporting template will be recorded as superior or tag; only when the sub-reporting document corresponding to the reporting template is submitted will it be submitted to the specific enterprise member (i.e., the reported object) under the superior or tag. Similarly, template rules can also include setting the reporting object corresponding to the reporting template, so that only the reporting object set to the reporting template can retrieve the reporting model for reporting editing.

[0197] It can also manage the text content of each sub-report document corresponding to the report template, that is, manage the data submitted by each reporting object for the report document and obtain summary data. Specifically, it can perform data analysis, data statistics and other summary operations on the data in each sub-report document to obtain summary data, and manage the viewing of the report data. When an enterprise member opens the form link corresponding to the report document (the link used to open the form, which records the summary data for each sub-report document), it can determine whether to show the enterprise member the entry point to view the report data based on the management relationship of the report data. For example, based on the object identifier vid and the report template_id of the currently logged-in social application, it can query the sub-report documents corresponding to each report model that can be viewed by the reported object corresponding to the object identifier vid, as well as the report data obtained by summarizing each sub-report document (such as the submission ratio of sub-report documents, the distribution of personnel who have not submitted, and the entry point to view the historical report records of each reporting object, etc.).

[0198] It also allows management of permissions to create reporting templates, specifying whether each member of the target company has the authority to configure their own reporting templates. It also manages the usage status of created reporting templates, including enabled and disabled states. Only when a reporting template is enabled can the reporting recipient edit it, and the recipient is allowed to receive sub-report documents submitted by the reporting recipient based on that template. Furthermore, it allows for the display of reporting templates externally, directly showcasing them in the social application's workspace. This enables the target recipient to quickly open and edit the reporting template from the social application, improving the efficiency of reporting template editing to some extent.

[0199] ② Document Creator: This refers to a member of the target company who has the authority to create reporting templates. This member can be a super administrator, hierarchical administrator, or application administrator within the target company. When creating a reporting template, the document creator includes creating the reporting framework and template rules. Generally, the document creator also has permission to view the summary data of the sub-report documents corresponding to the reporting template they created.

[0200] When configuring report documents, document creators configure template rules. These rules can set main reporting tasks, such as periodic tasks and one-time tasks. Periodic tasks are those that need to be executed in every reporting cycle, while one-time tasks are those that only need to be executed once. Periodic tasks can include, but are not limited to, superior-level calculations, report reminders, and summary tasks. Superior-level calculations require submitting the sub-report documents corresponding to the report template to the superior (i.e., the reported object) in every reporting cycle; report reminders require providing the reporting object with the opportunity to edit the report template in every reporting cycle; and summary tasks require summarizing multiple submitted sub-report documents to obtain summary data in every reporting cycle. One-time tasks can include, but are not limited to, rule change notifications, notifications of changes to fixed reporting objects, and notifications of changes to creation permissions. Rule change notification refers to the notification that needs to be sent to the document creator (or the reporting object, the reported object) if the enterprise manager updates the template rules of the reporting template; fixed reporting object change notification refers to the notification that needs to be sent to the newly added reporting objects if there is a change to the reporting objects corresponding to the reporting template, so that the new reporting objects can fill in the report in a timely manner; creation permission change notification refers to the notification that needs to be sent to the enterprise members whose permissions have changed if the enterprise manager adjusts the creation permissions of each enterprise member in the target enterprise for the reporting template.

[0201] The document TimeLine (i.e., the deadline of the reporting period) is pushed by the document backend, and the TimeLine mapping relationship is also maintained by the document reporting backend. This mapping relationship can be simply understood as the mapping relationship between a reporting period and the data of each sub-report document submitted within that reporting period. For example, push notifications related to reporting can include, but are not limited to: Scenario 1, push notifications to the reported object; in this scenario, when the social application pushes a reporting reminder to the reported object, the parameters involved include "Template_id", "period timestamp", and "reported object vid". Then, the document backend uses this triple to confirm the corresponding "TimeLineID" and "DocID", that is, to confirm the time to send the reporting reminder to the reported object and the reporting template that needs to be reminded. Scenario 2: Pushing details of reports (such as text content and summary data in sub-report documents). In this scenario, the parameters involved include "Report JournalID" and "Reporter's vid". The document backend then uses this tuple to confirm the corresponding "TimeLineID" and "DocID", that is, to confirm the reporting time of the report details and the reporting template to which the report details belong.

[0202] For example, a flowchart illustrating the process of creating and sending reminders (such as the aforementioned reporting reminders, which may also include summary reminders) can be found in [reference needed]. Figure 26b ;like Figure 26b As shown, security verification is first performed based on the security ticket. After successful verification, a pre-test is performed, which mainly checks whether the reporting function is enabled and whether reporting reminders are required. If the reporting function is enabled and reporting reminders are required, the document list corresponding to the target object is obtained. This document list includes multiple reporting documents, and post-tests are performed on the reporting documents. These tests mainly check whether each reporting template in the document list is enabled, whether reminder rules are set, and whether the template rules of the reporting templates in the storage server are consistent with the template rules in the request. If all three are true, the next reporting cycle task is inserted, and it is checked whether the reporting template is a special template for the education bureau and school, and whether holiday and weekend checks are required (these checks can also be skipped). The visibility range of the reporting template is obtained, and the object identifiers of the reporting objects that have submitted sub-reporting documents in the current reporting cycle are viewed. Reporting reminders are then given to the reporting objects that are within the visibility range and have not yet submitted sub-reporting documents in the current reporting cycle.

[0203] For example, a flowchart illustrating the process of handling summary reminder tasks can be found here. Figure 26c ;like Figure 26c As shown, assuming the summary period is set from 0:00 to 0:00 the next day, and the summary reminder time is set to 17:00, then a summary reminder needs to be sent to the company manager when the time reaches 17:00, and the summary report will begin at 0:00 the next day. Similarly, if the summary period is set from 8:00 to 8:00 the next day, and the summary reminder time is set to 8:00, then both the summary report reminder and the summary report will be sent simultaneously when the time reaches 8:00 the next day.

[0204] For example, a flowchart illustrating the process of a document creator creating a report template can be found here. Figure 26d ;like Figure 26dAs shown, the process first detects all reporting templates in the social application and performs pre-parameter checks on each template (such as validating template controls and rules). Then, it retrieves the document content from each template and checks if it belongs to the Education Bureau or a school. If a template belongs to the Education Bureau or a school, it updates the Education Bureau's reporting template list and ends the process. If a template does not belong to the Education Bureau or a school, it performs post-checks (such as checking the number of templates and whether they have the same name) and verifies the permissions of the currently logged-in social application target (such as whether the target is a super administrator, a member of an enterprise with creation permissions, or simply the document creator of the reporting template). Finally, it writes back the changes made to the reporting templates, writing back the changed document content of the reporting template and then writing the changed document content of the reporting template back to the template list. Furthermore, it checks whether the reporting template is an Education Bureau template. If it is, the Education Bureau task is stored on the storage server, and the filling reminder task is also stored on the storage server. If it is not, the filling reminder task is stored on the storage server directly, the summary task is stored on the storage server, the changes to the reporting objects corresponding to the reporting template are stored on the storage server, and the parts of the template rule changes are stored on the storage server, and then the process ends.

[0205] ③ Reporting Target: This refers to company members who have the ability to edit the reporting template. The reporting target supports editing the reporting template to create sub-report documents, and allows for the submission of these sub-report documents, adding / deleting / modifying forms corresponding to the reporting template, and annotating the document content within the reporting template (such as comments).

[0206] For example, a flowchart illustrating the process of a reporting entity submitting a sub-report document can be found here. Figure 27a ;like Figure 27aAs shown, when the reporting target requests the template rules and document identifier (doc_id) of the web application to retrieve the reporting template, along with the corresponding reporting object (selected by the reporting target or fixed by default), the document service SVR (or document backend) forwards this request to the backend server of the social application. The backend server responds to the request, returning the document identifier (doc_id) and template rules of the reporting template to the document service, allowing the reporting target to view the reporting template. Then, the reporting target can use the document identifier (doc_id) to create a form identifier (doc_id) for the form corresponding to the reporting template and fill in the document content from the sub-reporting template. The reporting target also submits the form based on the form identifier (doc_id), the document identifier (doc_id) of the reporting template, and the list of reporting targets. The backend server of the social application uses the document identifier (doc_id) of the reporting template and the reporting period to generate a reporting time (timeline_id) for the document server. The submitted form is forwarded from the document service to the backend server corresponding to the social application. This backend server stores the form details, specifically periodic report content (journalidList) generated based on a mapping of reporting time (timeline_id). In other words, it stores the document content from each sub-report document corresponding to the reporting template received within the reporting period. Then, the backend server synchronizes the form to the reporting recipient and the document backend. Further, if the reporting template has asynchronous tasks, such as reporting reminders, a push notification is sent based on the reminder. This push notification consists of a reporting application message, the reporting template's reporting event timeline_id, and a message body. The message body contains the periodic report content (journalid List) and the document identifier doc_id of the reporting template, primarily used to filter older versions of the social application. Finally, the form returns the periodic report content (journalid List) to the reporting recipient.

[0207] For example, when the sub-report document submitted by the reporting object is a collection form, a flowchart illustrating the process of submitting the collection form and adding / deleting / modifying the corresponding forms and comments on the document content in the collection form can be found in [reference needed]. Figure 27b .like Figure 27bAs shown, the process involves obtaining object information of the reporting target, such as the object identifier and the document identifier of the reporting template. Then, it retrieves the security ticket for security checks and verifies the form corresponding to the reporting template, as well as preparing parameters (such as data in the form). Next, the form is forwarded to the document server (SVR), and the system saves the target object selected by the reporting target when submitting the sub-report document corresponding to the reporting template. After the sub-report document is submitted, a viewing reminder is sent to the target object, and statistics on submitted sub-report documents are displayed on the target object's side. Specifically, after forwarding the form to the document server (SVR), the document server can perform parameter validation and supplement data based on the validation results, such as supplementing the document name of the reporting template, the department, and relevant information. It also stores the form data locally and generates a sharing link for the form. Furthermore, it updates the form based on the submitted sub-report document and synchronously shares the corresponding sharing link.

[0208] ④ The recipient of the report: This refers to the enterprise members who receive the sub-report document corresponding to the report template. The recipient of the report template can be configured by the document creator or selected by the recipient themselves; there is no limitation on this.

[0209] ⑤ Temporary Associate: This temporary associate is neither the reporting recipient nor the object being reported to in the first reporting document. Instead, it is a member of the target company who can view the first sub-report document and its corresponding reporting information. For example, the temporary associate could be the general manager of the target company. The first sub-report document does not need to be filled out by the general manager or submitted to him, but the general manager has viewing and summarizing permissions for the first sub-report document, thus traversing the general manager's management of the target company. Of course, the temporary associate can also be other members of the target company besides the general manager. Specifically, it can be configured when configuring the document rules in the first reporting template, or it can be a default member of the target company.

[0210] Based on the above introduction to the five business roles, it is clear that the permissions for different business roles differ in reporting scenarios. For ease of understanding, a diagram illustrating the permission classification for each business role can be found here. Figure 27c The relevant descriptions of various permissions in this classification diagram have been given above and will not be repeated here.

[0211] (2) Configuration and summary of reporting templates / documents.

[0212] 1) Configuration of reporting templates / documents.

[0213] In this embodiment, the reporting document can be configured by a target object within the target enterprise. The reporting document configured by the target object can be referred to as the first reporting document. The target object can be an enterprise member within the target enterprise with configuration permissions for the first reporting document, such as an enterprise administrator or document creator. While both the enterprise administrator and the document creator can configure the first reporting document, their permissions are not entirely identical. For example, the enterprise administrator can manage all configured reporting documents within the target enterprise, such as adding, deleting, modifying, and querying reporting content or document rules within reporting documents, summarizing sub-report documents completed by each reporting document, and exporting and viewing form records. Similarly, the document creator can manage the reporting documents they created, such as adding, deleting, modifying, and querying reporting content or document rules within their own created reporting documents, and summarizing sub-report documents completed by their own created reporting documents, and exporting and viewing form records. Therefore, by assigning different reporting management permissions to different enterprise members within the target enterprise, the diverse reporting management needs of the target enterprise can be accommodated.

[0214] Specifically, target entities within the target enterprise with configuration permissions for reporting documents can perform report publishing operations in the social application. This allows them to configure the reporting content (i.e., the aforementioned reporting content framework) and set document rules for the first reporting document within the social application. When setting document rules, at least the reporting object identifier (such as an identifier uniquely identifying the reporting object within the target enterprise) of the reporting object to be filling out the first reporting document, and the reporting object identifier of the reporting recipient of the first sub-report document obtained from filling out the first reporting document, must be set. In this way, the social application can automatically publish the configured first sub-report document to the reporting objects corresponding to each reporting object identifier; and the reporting objects can then fill out the first reporting document, and after obtaining the first sub-report document, it will be automatically submitted to the reporting recipient corresponding to the reporting object identifier.

[0215] Therefore, this application embodiment supports unified configuration of the first reporting document by target objects within the target enterprise. By standardizing and normalizing the reporting content and document rules of the first reporting document, the standardization of the first sub-reporting documents filled out for the first reporting document can be ensured, which is beneficial for subsequent report summarization and management. Furthermore, compared to requiring reporting objects within the target enterprise to spend time configuring the first reporting document themselves, this saves the reporting objects the workload of configuring the first reporting document. The social application backend can automatically publish the first reporting document and collect the first sub-reporting documents based on the document rules set for the first reporting document, greatly improving reporting efficiency.

[0216] It's worth noting that in these related technologies, when company members have reporting needs, they must spend time creating and filling out reporting documents themselves, and actively select the recipients from the target company to submit the completed sub-report documents; alternatively, they can create collaboratively editable reporting documents in social applications, allowing both the reporting and receiving parties to report and view the same document; or, when reporting in social applications, only basic text editing is supported; and so on. It's easy to see that the reporting capabilities provided by these technologies are limited, resulting in limitations for company members in terms of report editing functions, report content display, project management integration, team collaboration and communication, and the overall reporting experience, leading to low reporting efficiency and increased difficulty in team collaboration.

[0217] However, the beneficial effects of configuring the reporting template in this application embodiment include at least the following: On the one hand, it supports the unified configuration of the first reporting document by the target object and its automatic batch distribution to the reporting objects for filling, and the first sub-reporting document filled by the reporting object can be automatically submitted to the reported object; compared with the reporting object having to configure the first reporting document itself, it saves the time of each reporting object to write and adjust the format, realizes the rapid creation of content-rich first reporting documents, and improves the reporting efficiency of the target enterprise. On the other hand, it supports the creation of a general first reporting document by the target object in the target enterprise (such as an enterprise member with the permission to create reporting documents). This first reporting document can be understood as a reporting template. When creating the reporting template, the reporting content and document rules of the reporting document are configured together; wherein, the document rules include the reporting object and the reported object of the first reporting document. The reporting object is an enterprise member with the permission to fill in the first reporting document, and the reported object is an enterprise member with the permission to receive the first sub-reporting document filled in for the first reporting document. In this way, the created first report document can be directly published to each reporting recipient from the social application backend for reporting. On the one hand, this eliminates the need for the target recipient to send the first report document to each reporting recipient sequentially, such as avoiding redirection to the conversation interface between the target and reporting recipients, and also saves reporting recipients a significant amount of time in creating the first report document, greatly improving the creation and distribution efficiency of the first report document. On the other hand, unified configuration of the first report document enables standardized document formatting. By standardizing the document format of the first report document, it is easier to manage the first report document and its corresponding first sub-report documents. Furthermore, after the reporting recipient completes the first report document and obtains the first sub-report document, they only need to perform a submit operation, which will automatically submit the first sub-report document to the recipient of the first report document, without the reporting recipient having to select the recipient manually. This reduces the number of steps required for submitting the first sub-report document, simplifies collaboration and communication between reporting recipients and recipients within the enterprise, improves the user's reporting experience, and enhances the reporting efficiency of the target enterprise.

[0218] 2) Compilation of reporting templates / documents.

[0219] The reporting recipient fills out the first reporting document, obtaining the corresponding first sub-report document. This first sub-report document is then submitted to the recipient of the first reporting document. If the recipient grants the social application aggregation permissions for the submitted first sub-report documents, the social application will perform document aggregation processing based on the received first sub-report documents to obtain the document reporting information corresponding to the first reporting document. This intelligent reporting aggregation method greatly facilitates the recipient's timely and real-time viewing of the document reporting information of the first reporting document, improving their aggregation experience. The recipient of the first reporting document can be a company administrator or a company member. Besides viewing the document reporting information of the first reporting document, the recipient can also view any first sub-report document submitted by any reporting recipient, and can perform form export and forwarding extensions of the document reporting information. Form export and forwarding extensions will be described in subsequent embodiments, but are not explained here.

[0220] For example, a schematic diagram of the summary process can be found here. Figure 28a ;like Figure 28a As shown, the process involves obtaining security credentials for security checks and performing pre-emptive checks on the social application (such as checking if the reporting function is enabled). Then, a template list is retrieved, and each reporting template in the list undergoes post-checks (such as checking if each reporting template in the document list is enabled, if reminder rules are set, and if the template rules in the storage server are consistent with the template rules in the request). Next, the start time of the aggregation period is calculated based on the request parameters, and it is determined whether the checks on the education bureau template and school template need to be skipped. Then, all submitted sub-report documents within the reporting period are retrieved, and the reporting objects for submitted sub-report documents in the current reporting period are queried. Next, it is determined whether there are any reporting objects that have not submitted sub-report documents; if so, a push notification is required, and a message is pushed to the reporting object. Finally, it is determined whether the aggregated data needs to be stored permanently; if so, the aggregated data is stored permanently.

[0221] Based on the above introduction to the backend technology of reporting management methods, the following section, in conjunction with the appendix... Figure 28b The main method flow of the reporting management method provided in the embodiments of this application is given. For example... Figure 28bAs shown, in the first part, if the reporting frontend sends a request to the document backend to retrieve a list of templates, the document backend responds by setting the reporting frontend to a logged-in state and forwarding the request to the reporting backend. This allows the reporting backend to retrieve the document identifiers of the reporting templates from the document backend and initialize the corresponding reporting documents, enabling the reporting templates to be displayed on the reporting frontend. In the second part, if the reporting object sends a request to the document backend to retrieve an old report (i.e., a reporting template initiated based on an application version without reporting functionality), the document backend responds by setting the reporting frontend to a logged-in state and forwarding the request to the reporting backend. This allows the reporting backend to insert reporting data into the old report and return the reporting reminder tasks for the reported object to the document backend. The document backend can then insert the reporting data into the old report and execute the reporting reminder tasks. Furthermore, the reporting backend will perform file indexing in the document backend to enable rapid detection of reporting templates or sub-report documents.

[0222] In the third part, after the document creator initiates template publication in the social application, the document backend creates a report document. If this report document is created based on a preset template (pre-set by the social application developer), the pre-report data from the preset template will be inserted into it. Then, the document backend returns the template identifier (or document identifier) ​​of the created report template to the frontend (i.e., the document creator). In the fourth part, enterprise managers or the reported recipients can view submitted sub-report documents, thus achieving the collection of sub-report documents. At this point, the reporting frontend sends a request to collect sub-report documents to the document backend. The document backend responds to this request by setting the reporting frontend to logged-in status and passing the request to the reporting backend, enabling the reporting backend to formulate template rules and periodically remind reported recipients to submit sub-report documents. The reporting backend also returns the reported reminder tasks for the reported recipients to the document backend, allowing the document backend to insert report data into old reports and execute report reminder tasks. Finally, the reporting backend also performs file indexing in the document backend to enable rapid detection of report templates or sub-report documents. In Part 5, if a member of the enterprise (such as the reporting party or the reported party) initiates annotation (such as commenting) on ​​an old report, the reporting front end will send the annotation request to the document back end. The document back end responds to the request by setting the reporting front end to the logged-in state and passing the request to the reporting back end, so that the reporting back end can add annotation information to the report document based on the annotation operation carried in the annotation request, and directly synchronize the inserted annotation information to the reporting party or the reported party.

[0223] As can be seen from Parts 2 and 5 above, the embodiments of this application can realize the synchronization of reporting templates for different application versions. That is, if the old version of the social application does not have a reporting function, while the new version of the social application does, then the new version of the social application can still insert rich text and annotate old reports initiated based on the old version of the social application, thereby applying powerful reporting editing capabilities to the old version of the reporting template and realizing the synchronization of reporting functions between different versions, which greatly facilitates the synchronization of reports by enterprise members.

[0224] The methods of the embodiments of this application have been described in detail above. To facilitate better implementation of the above-described solutions of the embodiments of this application, the apparatus of the embodiments of this application is provided below. In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program with a predetermined function, which works together with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

[0225] Figure 29 This application shows a schematic diagram of the structure of a reporting management device according to an exemplary embodiment; the reporting management device can be used to perform... Figure 3 and Figure 19 Some or all of the steps in the method embodiments shown. Please refer to [link / reference]. Figure 29 The device includes the following units:

[0226] Display unit 2901 is used to display a report document in a social application, the report document including one or more report items, the report items being in a structured data format;

[0227] The processing unit 2902 is used to perform editing operations on the report document according to the report items in the report document to obtain a sub-report document; the editing operations include at least one of the following: rich text insertion operation and annotation operation on the document content in the report document;

[0228] Processing unit 2902 is also used to submit reports of sub-report documents.

[0229] In one implementation, a reporting item corresponds to a reporting event type, and the reporting event type is used to indicate the type of the reporting event to be reported when the target object fills in the reporting item; the target object is a member of the target enterprise who serves as the reporting object in the reporting document; the processing unit 2902 is used to edit the reporting document according to the reporting items in the reporting document, and when obtaining a sub-reporting document, it is specifically used for:

[0230] Locate the target reporting item corresponding to the target reporting event in the reporting document;

[0231] Based on the reporting event type to which the target reporting event belongs, edit the target reporting item in the reporting document to obtain a sub-reporting document.

[0232] In one implementation, the editing operation is a rich text insertion operation. The processing unit 2902, when performing an editing operation on the target reporting item in the reporting document according to the reporting event type indicated by the target reporting event, specifically performs the following:

[0233] Perform an insert operation in the reporting area corresponding to the target reporting item, based on the reporting event type to which the target reporting event belongs;

[0234] The inserted rich text is displayed in the reporting area corresponding to the target reporting item; the data format of the rich text matches the reporting event type to which the target reporting event belongs;

[0235] The social application includes at least one business sub-application, and each business sub-application corresponds to an application function provided by the social application. The rich text comes from the corresponding business sub-application in the social application, and the rich text includes at least one of the following: text, image, document, file, calendar, meeting, and table.

[0236] In one implementation, the editing operation is a annotation operation on the document content; the document content includes reporting information, which consists of reporting items and rich text filled in by the reporting object for the reporting items;

[0237] Processing unit 2902, when editing target reporting items in a reporting document according to the reporting event type to which the target reporting event belongs, specifically performs the following:

[0238] According to the reporting event type to which the target reporting event belongs, mark the target reporting items in the reporting document;

[0239] The annotation operations for target reporting items include at least one of the following: underlining, commenting on, and revising the reporting information in the target reporting item.

[0240] In one implementation, the document content of the report document also includes template information in addition to the report information, wherein the report information consists of report items and rich text filled in by the reporting object for the report items; the processing unit 2902 is further used for:

[0241] Annotate the template information in the report document to obtain a sub-report document;

[0242] The annotation operations on template information include at least one of the following: drawing lines on the template information, commenting on the template information, and revising the template information.

[0243] In one implementation, the processing unit 2902 is further configured to:

[0244] The report document is treated as a whole and commented on to generate sub-report documents.

[0245] In one implementation, the reporting document includes a collaborative editing component; the processing unit 2902 is further configured to:

[0246] In response to a trigger operation on the collaborative editing component, the target company's corporate address book is displayed, which includes member identifiers of each member of the target company.

[0247] Select one or more member identifiers from the company address book;

[0248] In response to confirmation of one or more member identifiers, the one or more member identifiers are displayed in the reporting document; wherein, the enterprise members corresponding to the one or more member identifiers collaborate on editing the reporting document.

[0249] In one implementation, the reporting document includes an import component; the processing unit 2902 is further configured to:

[0250] In response to a triggered operation on the imported component, the report list window is displayed; the report list window is used to display one or more historical sub-report documents corresponding to the report document;

[0251] Select the target historical sub-report document from one or more historical sub-report documents based on the document selection operation performed in the report list window;

[0252] Use the document content from the target historical sub-report document to overwrite the corresponding document content in the report document.

[0253] In one implementation, the processing unit 2902, when using document content from the target historical sub-report document to overwrite the corresponding document content in the report document, specifically performs the following:

[0254] Display the document content of the target history sub-report document in a social application;

[0255] Select target content from the document content of the target historical sub-report document; the target content includes rich text filled in for one or more reporting items;

[0256] Use the target content to overlay the rich text in the reporting area corresponding to the relevant reporting item in the report document.

[0257] In one implementation, there are two target historical sub-report documents, including a first historical sub-report document and a second historical sub-report document; the processing unit 2902, when using the document content from the target historical sub-report documents to overwrite the corresponding document content in the report document, specifically performs the following:

[0258] Merge the rich text entered for each reporting item in the first historical sub-report document with the rich text entered for the corresponding reporting item in the second historical sub-report document;

[0259] The rich text in the corresponding reporting area of ​​each merged reporting item is used to overlay the rich text in the corresponding reporting area of ​​the reporting document.

[0260] In one implementation, the processing unit 2902 is further configured to:

[0261] Output content overwrite prompt message. The content overwrite prompt message is used to indicate whether to use the document content in the target reporting document and overwrite the corresponding document content in the reporting document;

[0262] Based on the confirmation of the content overwrite prompt, the step of using the document content in the target historical sub-report document to overwrite the corresponding document content in the report document is triggered.

[0263] In one implementation, the processing unit 2902 is further configured to:

[0264] The service interface that displays the report document shows a list of historical submission versions corresponding to the report document; the list of historical submission versions includes the document identifiers of one or more historical sub-report documents that the target object has submitted for the report document at a historical time.

[0265] In response to a selection operation performed in the list of historical commits, display the document content of the historical sub-report document corresponding to the selected document identifier.

[0266] In one implementation, the processing unit 2902 is further configured to:

[0267] Based on the editing operations in the report document, create change instructions. Change instructions are used to describe the operation attributes of the editing operations in the report document. The operation attributes include at least one of the following: operation location, operation type, operation content, and operation target.

[0268] Bind the change instructions to the reporting document, and render and display the document content generated by the editing operation based on the change instructions in the reporting document.

[0269] In one implementation, the processing unit 2902 is further configured to:

[0270] The change instructions are shared with the reporting object corresponding to the report document, so that the document content generated by the editing operation can be synchronously rendered and displayed on the reporting object side based on the change instructions.

[0271] According to one embodiment of this application, Figure 29 The reporting management device shown can be composed of various units, either individually or entirely, combined into one or more other units. Alternatively, some units can be further divided into functionally smaller units. This achieves the same operation without affecting the technical effects of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the reporting management device may also include other units. In practical applications, these functions can be implemented with the assistance of other units, and can be implemented collaboratively by multiple units. According to another embodiment of this application, a general-purpose computing device, such as a computer, including processing elements and storage elements such as a central processing unit (CPU), random access memory (RAM), and read-only memory (ROM), can be used to perform functions such as... Figure 3 and Figure 19 The computer program (including program code) for each step involved in the corresponding method shown, to construct such... Figure 29 The report management device shown herein, and the report management method for implementing the embodiments of this application, are described. A computer program may be recorded on, for example, a computer-readable recording medium, loaded onto the aforementioned computing device via the computer-readable recording medium, and run therein.

[0272] In this embodiment, the report document includes one or more report items with a fixed structure. These report items are matters that the target object needs to edit to complete the report. This structured report document approach saves report document creation time compared to requiring the reporting object to create the report document itself, and ensures the uniformity of document format across multiple reporting objects, greatly facilitating downstream reporting operations (such as report summarization and report viewing). Furthermore, when editing the report document, the reporting object can edit the report document according to the report items to obtain sub-reports. On the one hand, during the process of editing the report document, the report items can guide the reporting object's report editing. For example, if the reporting object needs to report today's work content, it only needs to edit the report item corresponding to today's report content, improving the reporting object's work efficiency. On the other hand, it provides the reporting object with rich report editing capabilities, such as supporting the insertion of rich text or the annotation of document content, making the report more intuitive and detailed, and helping to better showcase work results and plans. In summary, the embodiments of this application combine structured reporting documents with rich editing capabilities, which greatly enhances the reporting capabilities in social applications and improves the reporting efficiency within enterprises.

[0273] Figure 30 A schematic diagram of the structure of a terminal provided in an exemplary embodiment of this application is shown. Please refer to... Figure 30 The terminal includes a processor 3001, a communication interface 3002, and a computer-readable storage medium 3003. The processor 3001, communication interface 3002, and computer-readable storage medium 3003 can be connected via a bus or other means. The communication interface 3002 is used to receive and send data. The computer-readable storage medium 3003 can be stored in the terminal's memory and is used to store computer programs. The processor 3001 is used to execute the computer programs stored in the computer-readable storage medium 3003. The processor 3001 (or CPU (Central Processing Unit)) is the terminal's computing and control core, suitable for implementing one or more computer programs, specifically suitable for loading and executing one or more computer programs to achieve corresponding method flows or functions.

[0274] This application embodiment also provides a computer-readable storage medium (Memory), which is a memory device in a terminal for storing programs and data. It is understood that the computer-readable storage medium here can include both the built-in storage medium in the terminal and extended storage media supported by the terminal. The computer-readable storage medium provides storage space that stores the terminal's processing system. Furthermore, one or more computer programs suitable for loading and execution by the processor 3001 are stored in this storage space. It should be noted that the computer-readable storage medium here can be high-speed RAM or non-volatile memory, such as at least one disk storage device; optionally, it can also be at least one computer-readable storage medium located remotely from the aforementioned processor.

[0275] In one embodiment, a computer-readable storage medium stores one or more computer programs; the processor 3001 loads and executes the one or more computer programs stored in the computer-readable storage medium to implement the corresponding steps in the above-described reporting management method embodiments; specifically, the one or more computer programs in the computer-readable storage medium are loaded and executed by the processor 3001 to perform the steps of the embodiments of this application:

[0276] Displaying a report document in a social application, the report document includes one or more report items, which are in a structured data format;

[0277] Edit the report document according to the report items to obtain a sub-report document; the editing operation includes at least one of the following: rich text insertion operation and annotation operation of document content in the report document;

[0278] Submit the report document.

[0279] In one implementation, a reporting item corresponds to a reporting event type. The reporting event type indicates the type of reporting event to be reported when the target object fills in the reporting item. The target object is a member of the target enterprise that serves as the reporting object in the reporting document. When one or more instructions in the computer-readable storage medium are loaded and executed by the processor 3001 to edit the reporting document according to the reporting items in the reporting document to obtain a sub-reporting document, the following steps are specifically performed:

[0280] Locate the target reporting item corresponding to the target reporting event in the reporting document;

[0281] Based on the reporting event type to which the target reporting event belongs, edit the target reporting item in the reporting document to obtain a sub-reporting document.

[0282] In one implementation, the editing operation is a rich text insertion operation. One or more instructions in the computer-readable storage medium are loaded by the processor 3001 and executed according to the reporting event type indicated by the target reporting event. When editing a target reporting item in the reporting document, the following steps are specifically performed:

[0283] Perform an insert operation in the reporting area corresponding to the target reporting item, based on the reporting event type to which the target reporting event belongs;

[0284] The inserted rich text is displayed in the reporting area corresponding to the target reporting item; the data format of the rich text matches the reporting event type to which the target reporting event belongs;

[0285] The social application includes at least one business sub-application, and each business sub-application corresponds to an application function provided by the social application. The rich text comes from the corresponding business sub-application in the social application, and the rich text includes at least one of the following: text, image, document, file, calendar, meeting, and table.

[0286] In one implementation, the editing operation is a annotation operation on the document content; the document content includes reporting information, which consists of reporting items and rich text filled in by the reporting object for the reporting items;

[0287] When one or more instructions in a computer-readable storage medium are loaded and executed by processor 3001, and when editing a target reporting item in a reporting document according to the reporting event type to which the target reporting event belongs, the following steps are specifically performed:

[0288] According to the reporting event type to which the target reporting event belongs, mark the target reporting items in the reporting document;

[0289] The annotation operations for target reporting items include at least one of the following: underlining, commenting on, and revising the reporting information in the target reporting item.

[0290] In one implementation, the document content of the report document also includes template information in addition to the report information, which consists of report items and rich text filled in by the reporting object for the report items; one or more instructions in the computer-readable storage medium are loaded by the processor 3001 and the following steps are also executed:

[0291] Annotate the template information in the report document to obtain a sub-report document;

[0292] The annotation operations on template information include at least one of the following: drawing lines on the template information, commenting on the template information, and revising the template information.

[0293] In one implementation, one or more instructions in a computer-readable storage medium are loaded by processor 3001 and the following steps are also performed:

[0294] The report document is treated as a whole and commented on to generate sub-report documents.

[0295] In one implementation, the report document includes a collaborative editing component; one or more instructions in a computer-readable storage medium are loaded by processor 3001 and also execute the following steps:

[0296] In response to a trigger operation on the collaborative editing component, the target company's corporate address book is displayed, which includes member identifiers of each member of the target company.

[0297] Select one or more member identifiers from the company address book;

[0298] In response to confirmation of one or more member identifiers, the one or more member identifiers are displayed in the reporting document; wherein, the enterprise members corresponding to the one or more member identifiers collaborate on editing the reporting document.

[0299] In one implementation, the report document includes an import component; one or more instructions in a computer-readable storage medium are loaded by processor 3001 and also perform the following steps:

[0300] In response to a triggered operation on the imported component, the report list window is displayed; the report list window is used to display one or more historical sub-report documents corresponding to the report document;

[0301] Select the target historical sub-report document from one or more historical sub-report documents based on the document selection operation performed in the report list window;

[0302] Use the document content from the target historical sub-report document to overwrite the corresponding document content in the report document.

[0303] In one implementation, when one or more instructions in a computer-readable storage medium are loaded by processor 3001 and executed to overwrite the corresponding document content in the target history sub-report document, the following steps are specifically performed:

[0304] Display the document content of the target history sub-report document in a social application;

[0305] Select target content from the document content of the target historical sub-report document; the target content includes rich text filled in for one or more reporting items;

[0306] Use the target content to overlay the rich text in the reporting area corresponding to the relevant reporting item in the report document.

[0307] In one implementation, there are two target historical sub-report documents, including a first historical sub-report document and a second historical sub-report document; when one or more instructions in the computer-readable storage medium are loaded by the processor 3001 and executed to overwrite the corresponding document content in the report document using the document content in the target historical sub-report document, the following steps are specifically performed:

[0308] Merge the rich text entered for each reporting item in the first historical sub-report document with the rich text entered for the corresponding reporting item in the second historical sub-report document;

[0309] The rich text in the corresponding reporting area of ​​each merged reporting item is used to overlay the rich text in the corresponding reporting area of ​​the reporting document.

[0310] In one implementation, one or more instructions in a computer-readable storage medium are loaded by processor 3001 and the following steps are also performed:

[0311] Output content overwrite prompt message. The content overwrite prompt message is used to indicate whether to use the document content in the target reporting document and overwrite the corresponding document content in the reporting document;

[0312] Based on the confirmation of the content overwrite prompt, the step of using the document content in the target historical sub-report document to overwrite the corresponding document content in the report document is triggered.

[0313] In one implementation, one or more instructions in a computer-readable storage medium are loaded by processor 3001 and the following steps are also performed:

[0314] The service interface that displays the report document shows a list of historical submission versions corresponding to the report document; the list of historical submission versions includes the document identifiers of one or more historical sub-report documents that the target object has submitted for the report document at a historical time.

[0315] In response to a selection operation performed in the list of historical commits, display the document content of the historical sub-report document corresponding to the selected document identifier.

[0316] In one implementation, one or more instructions in a computer-readable storage medium are loaded by processor 3001 and the following steps are also performed:

[0317] Based on the editing operations in the report document, create change instructions. Change instructions are used to describe the operation attributes of the editing operations in the report document. The operation attributes include at least one of the following: operation location, operation type, operation content, and operation target.

[0318] Bind the change instructions to the reporting document, and render and display the document content generated by the editing operation based on the change instructions in the reporting document.

[0319] In one implementation, one or more instructions in a computer-readable storage medium are loaded by processor 3001 and the following steps are also performed:

[0320] The change instructions are shared with the reporting object corresponding to the report document, so that the document content generated by the editing operation can be synchronously rendered and displayed on the reporting object side based on the change instructions.

[0321] Based on the same inventive concept, the principle and beneficial effects of the terminal problem-solving method provided in the embodiments of this application are similar to the principle and beneficial effects of the reporting management method for problem-solving in the method embodiments of this application. For the sake of brevity, the principle and beneficial effects of the method implementation can be referred to.

[0322] This application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the above-described reporting management method.

[0323] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed in this application can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0324] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially as a computer program product. A computer program product includes one or more computer programs. When a computer program is loaded and executed on a computer device, the computer program performs the processes or functions described above in the embodiments of this application. The computer device can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in or transmitted through a computer-readable storage medium. The computer program can be transmitted from one website, computer device, server, or data center to another website, computer device, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium accessible to the computer device or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0325] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A reporting management method, characterized in that, include: Displaying a report document in a social application, the report document including one or more report items, the report items being in a structured data format; According to the reporting items in the reporting document, the reporting document is edited to obtain a sub-reporting document; the editing operation includes at least one of the following: rich text insertion operation and annotation operation of document content in the reporting document; Submit the sub-report document.

2. The method as described in claim 1, characterized in that, One reporting item corresponds to one reporting event type, and the reporting event type is used to indicate the type of reporting event to be reported when the target object fills in the reporting item; The target object is a member of the target enterprise who is the subject of the report document; the step of editing the report document according to the report items to obtain a sub-report document includes: Locate the target reporting item corresponding to the target reporting event that needs to be reported in the reporting document; According to the reporting event type to which the target reporting event belongs, the target reporting item is edited in the reporting document to obtain a sub-reporting document.

3. The method as described in claim 2, characterized in that, The editing operation is the insertion operation of the rich text. The editing operation of the target reporting item in the reporting document according to the reporting event type indicated by the target reporting event includes: According to the reporting event type to which the target reporting event belongs, perform an insertion operation in the reporting area corresponding to the target reporting item; The inserted rich text is displayed in the reporting area corresponding to the target reporting item; the data format of the rich text matches the reporting event type to which the target reporting event belongs; The social application includes at least one business sub-application, and each business sub-application corresponds to an application function provided by the social application. The rich text originates from the corresponding business sub-application in the social application, and the rich text includes at least one of the following: text, image, document, file, calendar, meeting, and table.

4. The method as described in claim 2, characterized in that, The editing operation is a annotation operation on the document content; the document content includes reporting information, which consists of reporting items and rich text filled in by the reporting object for the reporting items; The step of editing the target reporting item in the reporting document according to the reporting event type to which the target reporting event belongs includes: According to the reporting event type to which the target reporting event belongs, mark the target reporting item in the reporting document; The annotation operations on the target reporting item include at least one of the following: underlining, commenting, and revising the reporting information in the target reporting item.

5. The method as described in claim 1, characterized in that, The report document also includes template information in addition to the report information, wherein the report information consists of report items and rich text filled in by the reporting recipient for the report items; the method further includes: The template information is annotated in the report document to obtain a sub-report document; The annotation operations on the template information include at least one of the following: drawing lines on the template information, commenting on the template information, and revising the template information.

6. The method as described in claim 1, characterized in that, The method further includes: The report document is treated as a whole and commented on to obtain a sub-report document.

7. The method as described in any one of claims 1, 2, 5, or 6, characterized in that, The reporting document includes a collaborative editing component; the method further includes: In response to a trigger operation on the collaborative editing component, the target company's corporate address book is displayed, which includes member identifiers of each member of the target company. Select one or more member identifiers from the enterprise address book; In response to the confirmation operation of the one or more member identifiers, the one or more member identifiers are displayed in the report document; wherein, the enterprise members corresponding to the one or more member identifiers collaborate to edit the report document.

8. The method as described in claim 1, characterized in that, The reporting document includes an import component; the method also includes: In response to a trigger operation on the imported component, a report list window is displayed; the report list window is used to display one or more historical sub-report documents corresponding to the report document; Based on the document selection operation performed in the report list window, select the target historical sub-report document from the one or more historical sub-report documents; The document content in the target historical sub-report document is used to overlay and display the corresponding document content in the report document.

9. The method as described in claim 8, characterized in that, The step of using the document content from the target historical sub-report document to overlay and display the corresponding document content in the report document includes: The document content of the target historical sub-report document is displayed in the social application; Select target content from the document content of the target historical sub-report document; the target content includes rich text filled in for one or more reporting items; The target content is used to overlay the rich text in the reporting area corresponding to the relevant reporting item in the reporting document.

10. The method as described in claim 8, characterized in that, The number of target historical sub-report documents is two, including a first historical sub-report document and a second historical sub-report document; the step of using the document content in the target historical sub-report documents to overlay and display the corresponding document content in the report document includes: Merge the rich text entered for each report item in the first historical sub-report document and the rich text entered for the corresponding report item in the second historical sub-report document; The rich text in the corresponding reporting area of ​​each merged reporting item is used to overlay and display the rich text in the corresponding reporting area of ​​the reporting document.

11. The method according to any one of claims 8-10, characterized in that, Before using the document content from the target historical sub-report document to overwrite the corresponding document content in the report document, the method further includes: Output content overwrite prompt information, which is used to indicate whether to use the document content in the target reporting document to overwrite the corresponding document content in the reporting document; Based on the confirmation operation of the content overlay prompt information, the step of using the document content in the target historical sub-report document to overlay and display the corresponding document content in the report document is triggered.

12. The method as described in claim 1, characterized in that, The method further includes: The service interface that displays the report document shows a list of historical submission versions corresponding to the report document; the list of historical submission versions includes document identifiers of one or more historical sub-report documents that the target object has submitted for the report document at a historical time. In response to a selection operation performed in the historical submission list, the document content of the historical sub-report document corresponding to the selected document identifier is displayed.

13. The method as described in claim 1, characterized in that, After editing the report document according to the report items in the report document, the process further includes: Based on the editing operations in the report document, a change instruction is created. The change instruction describes the operation attributes of the editing operations in the report document. The operation attributes include at least one of the following: operation location, operation type, operation content, and operation target. The change instruction is bound to the report document, and the document content generated by the editing operation is rendered and displayed in the report document based on the change instruction.

14. The method as described in claim 13, characterized in that, The method further includes: The change instruction is shared with the reporting object corresponding to the report document, so that the document content generated by the editing operation is synchronously rendered and displayed on the reporting object side based on the change instruction.

15. A reporting management device, characterized in that, include: A display unit is used to display a report document in a social application, the report document including one or more report items, the report items being in a structured data format; The processing unit is configured to perform editing operations on the report document according to the report items in the report document to obtain a sub-report document; the editing operations include at least one of the following: rich text insertion operation and annotation operation on the document content in the report document; The processing unit is also used to submit the sub-report document.

16. A terminal, characterized in that, include: A processor, adapted to execute computer programs; A computer-readable storage medium storing a computer program, which, when executed by the processor, implements the reporting management method as described in any one of claims 1-14.

17. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer application program, which, when executed, implements the reporting management method as described in any one of claims 1-14.

18. A computer program product, characterized in that, The computer program product includes computer instructions that, when executed by a processor, implement the reporting management method as described in any one of claims 1-14.

Images