Report text generation method and device, equipment, storage medium and program product

Abstract

The invention relates to a report text generation method and device, equipment, a storage medium and a program product. The method comprises the following steps: constructing a reusable filling task library, newly creating a report, and selecting and associating tasks needing to be filled from the filling task library; defining a report text framework by adopting a tree data structure, transmitting the attribute of each node in the form of a JSON character string, and analyzing and storing the attribute in a database; adjusting a node sequence through a visual dragging engine, driving a task node to issue a bound filling task to a handling user, setting different approval processes and multi-stage approval routes, and marking the task node as a completed state after approval is passed; if the approval is not passed, returning to the handled user for modification; and when all the task nodes are completed, triggering a text generation instruction, and according to a newest node sequence, integrating contents of the title node and the completed task nodes to generate a report text document meeting a format requirement. By adopting the method, the differentiated structure requirements of different types of periodic reports can be met.

Description

Technical Field

[0001] This application relates to the field of intelligent reporting technology, and in particular to a method, apparatus, computer device, computer-readable storage medium, and computer program product for generating report text. Background Technology

[0002] With the development of intelligent reporting technology, current corporate groups primarily rely on simple form-filling systems to generate the main body of periodic disclosure reports. Some companies use basic form-filling systems that only provide fixed form-filling functions. After staff fill in the specified data in the system, it can only export table data in a single format. The text structure of the report body (such as heading levels and content order) still needs to be manually adjusted in external document tools. However, existing systems cannot customize the text structure of the report body; the heading levels and content order are fixed, which cannot adapt to the differentiated structural needs of different types of periodic reports within the group, resulting in poor structural flexibility. Summary of the Invention

[0003] Therefore, it is necessary to provide a method, apparatus, computer equipment, computer-readable storage medium, and computer program product for generating report text that can adapt to the differentiated structural requirements of different types of periodic reports, addressing the aforementioned technical problems.

[0004] Firstly, this application provides a method for generating report text, including:

[0005] Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0006] Create a new report by selecting and associating tasks from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; node types include title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks; adjust the node order using a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0007] Based on a custom workflow, the driving task node distributes the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the department in charge, the rich text of the completed data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0008] When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0009] In one embodiment, the method further includes:

[0010] The system collects real-time data on task node status, reporting progress, and approval timeliness. Based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

[0011] In one embodiment, the method further includes:

[0012] During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

[0013] In one embodiment, the newly created report includes:

[0014] The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

[0015] In one embodiment, the method further includes:

[0016] During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all tasks that have been filled in. The document style of the report document inherits the preset format, which includes font and paragraph spacing.

[0017] In one embodiment, the custom workflow includes process control logic for creation, distribution, filling, approval, cancellation, reset, and forced completion.

[0018] Secondly, this application also provides a report text generation apparatus, comprising:

[0019] The building module is used to build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0020] The new module is used to create new reports. It selects and associates the tasks to be filled in from the task library. It uses a tree data structure to define the text framework of the report body. The attributes of each node are transmitted as JSON strings, parsed and stored in the database. The attributes of a node include node ID, node type, parent node ID, node level, node order, node content and node status. The node type includes title nodes that do not require filling in the process and are set to completed by default, and task nodes that are bound to the task to be filled in. The node order can be adjusted through a visual drag-and-drop engine. The adjusted node order is saved in real time and the structure logic of the generated report is updated.

[0021] The approval module is used to drive task nodes to distribute bound data entry tasks to the responsible users based on a custom workflow; it sets different approval processes and multi-level approval routes based on the data entry department, and sends the completed rich text to the approving users; after approval, the task node is marked as completed; if the approval fails, it is returned to the responsible user for modification.

[0022] The generation module is used to trigger the text generation instruction when all task nodes are in a completed state. It integrates the content of the title node and the completed task nodes according to the latest node order to generate a report text document that meets the format requirements.

[0023] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0024] Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0025] Create a new report by selecting and associating tasks from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; node types include title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks; adjust the node order using a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0026] Based on a custom workflow, the driving task node distributes the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the department in charge, the rich text of the completed data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0027] When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0028] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0029] Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0030] Create a new report by selecting and associating tasks from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; node types include title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks; adjust the node order using a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0031] Based on a custom workflow, the driving task node distributes the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the department in charge, the rich text of the completed data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0032] When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0033] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0034] Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0035] Create a new report by selecting and associating tasks from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; node types include title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks; adjust the node order using a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0036] Based on a custom workflow, the driving task node distributes the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the department in charge, the rich text of the completed data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0037] When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0038] The aforementioned report text generation method, apparatus, computer equipment, computer-readable storage medium, and computer program product construct a reusable data entry task library. This library supports manual single-item creation and batch uploading of data entry tasks, and can maintain the corresponding data entry department, handling user, and activation status. It achieves standardized management and efficient reuse of data entry tasks, avoiding redundant operations caused by repeated creation. When creating a new report, the required data entry tasks are selected and associated from the data entry task library. A tree-structured data structure is used to define the text framework of the report text. The attributes of each node are transmitted as JSON strings, parsed, and stored in the database. Node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status. Node types are divided into title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks. A visual drag-and-drop engine adjusts the node order, saving the adjusted node order in real time and synchronously updating the report generation structure logic, thus satisfying the requirements of report completion. This system not only meets the personalized customization needs of the data structure but also ensures real-time updates and accurate storage of the structural logic. Based on a custom workflow, task nodes are driven to distribute the bound data entry tasks to the corresponding users. Different approval processes and multi-level approval routes are set according to the data entry department. The rich text of the data completed by the user is sent to the approving user. If the approval is successful, the task node is marked as completed; if the approval fails, the rich text is returned to the user for modification. This achieves automated flow between data entry and approval. The real-time linkage between approval results and task node status ensures the compliance and accuracy of the data entry and simplifies the process of returning data for modification, improving overall business processing efficiency. When all task nodes are in the completed state, the system automatically triggers the text generation command. It integrates the content corresponding to the title nodes and the completed task nodes according to the latest node order to generate a report text document that meets the format requirements. This ensures the logicality, completeness, and format standardization of the report content, effectively improving the overall quality and efficiency of report generation and adapting to report production needs in multiple scenarios. Attached Figure Description

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

[0040] Figure 1 This is a diagram illustrating the application environment of a report text generation method in one embodiment;

[0041] Figure 2This is a flowchart illustrating a method for generating report text in one embodiment;

[0042] Figure 3 This is a flowchart illustrating the report text generation method in another embodiment;

[0043] Figure 4 This is a schematic diagram of the report filling process for a report text generation method in one embodiment;

[0044] Figure 5 This is a structural block diagram of a report text generation device in one embodiment;

[0045] Figure 6 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0046] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0047] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0048] The report text generation method provided in this application embodiment can be applied to, for example, Figure 1The application environment shown can involve only terminal 102, only server 104, or both terminal 102 and server 104. Terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or located in the cloud or on other network servers. Specifically, terminal 102 or server 104 completes a method for generating report text. This method includes: constructing a reusable data entry task library, which supports manual single-item creation and batch uploading of data entry tasks, and can maintain the data entry department, handling user, and activation status corresponding to the task; achieving standardized management and efficient reuse of data entry tasks, avoiding redundant operations caused by repeated creation; when creating a new report, selecting and associating the required data entry tasks from the data entry task library, defining the text framework of the report text using a tree data structure, transmitting the attributes of each node in the form of a JSON string, parsing and storing it in the database; the node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; among which, the node type is divided into title nodes that do not require data entry and are set to the completed status by default, and task nodes bound to data entry tasks. At the same time, the node order is adjusted through a visual drag-and-drop engine, the adjusted node order is saved in real time, and the structural logic of the generated report is updated synchronously, satisfying the report structure requirements. While meeting personalized customization needs, the system also ensures real-time updates and accurate storage of structural logic. Based on a custom workflow, task nodes are driven to distribute bound data entry tasks to corresponding users. Different approval processes and multi-level approval routes are set according to the data entry department. The rich text of the completed data entry by the user is sent to the approving user. If the approval is successful, the task node is marked as completed; if the approval fails, the rich text is returned to the user for modification. This achieves automated workflow between data entry and approval. The real-time linkage between approval results and task node status ensures the compliance and accuracy of the data entry, simplifies the process of returning data for modification, and improves overall business processing efficiency. When all task nodes are in the completed state, the system automatically triggers the text generation command. It integrates the content corresponding to the title nodes and completed task nodes according to the latest node order to generate a report text document that meets the format requirements. This ensures the logicality, completeness, and format standardization of the report content, effectively improving the overall quality and efficiency of report generation and adapting to report production needs in multiple scenarios.

[0049] Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection equipment. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. Server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0050] In one exemplary embodiment, such as Figure 2 As shown, a method for generating report body text is provided, which can be applied to... Figure 1 Taking server 104 as an example, the explanation includes the following steps 202 to 208. Wherein:

[0051] Step 202: Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0052] Among them, reusable means that the data entry tasks stored in the library can be repeatedly selected and used in the creation process of different reports.

[0053] Specifically, a reusable data entry task library is constructed, which has dual task entry capabilities. It supports users to manually create data entry tasks one by one, as well as to upload organized task data in batches. At the same time, it provides a complete task attribute maintenance function, which can flexibly manage the data entry department, the handling user and the activation status of each task, so as to realize the standardized storage and efficient reuse of data entry tasks and provide a basic data source for subsequent report creation.

[0054] Step 204: Create a new report. Select and associate the tasks to be filled in from the task library. Define the text framework of the report body using a tree data structure. Transmit the attributes of each node as a JSON string, parse and store it in the database. The node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status. Node types include title nodes that do not require filling in the process and are set to completed by default, and task nodes that are bound to the task being filled in. Adjust the node order through a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0055] The tree data structure refers to a hierarchical data organization form, starting from the root node and extending downwards to several child nodes. A clear parent-child hierarchical relationship exists between nodes, clearly defining the text framework of the report body and intuitively presenting the report's module division and hierarchical logic. JSON strings refer to strings organized using JavaScript Object Notation (JSON), characterized by their lightweight nature, ease of parsing, and cross-platform compatibility. They are used to serialize and store node attribute information, facilitating efficient database read / write and rapid system parsing. Node IDs are unique identifiers for each node, ensuring accurate retrieval, modification, and association within the database; they are the core identifier for node management. Parent node IDs identify the parent node to which the current node belongs, used to construct the parent-child hierarchical relationship between nodes in the tree data structure, supporting the hierarchical logic of the report framework. Node hierarchy parameters represent the node's position within the tree data structure, intuitively reflecting the chapter hierarchy of the report body, such as first-level headings, second-level headings, and task modules.

[0056] Specifically, when creating a new report, the system first filters and associates the required data entry tasks from a reusable task library, laying the data foundation for filling in the report content. Then, a tree-structured data framework is used to build the text framework of the report body. Node attributes, including node ID, node type, parent node ID, node level, node order, node content, and node status, are transmitted as JSON strings, parsed, and stored in the database, achieving structured management of node information. Node types are divided into two categories: title nodes do not require data entry and are set to "completed" by default, primarily used to build the report hierarchy; task nodes are bound to data entry tasks and carry the core data entry content. The system also supports adjusting the node order via a visual drag-and-drop engine. The system saves the adjusted node order in real time and updates the generated report structure logic synchronously, ensuring the report framework conforms to actual needs.

[0057] Step 206: Based on the custom workflow, the task node is driven to send the bound data entry task to the user in charge; based on the different approval processes and multi-level approval routes set by the data entry department, the rich text after data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0058] The custom workflow refers to a task processing framework that allows for flexible configuration of process steps, execution rules, and workflow logic according to business needs. It is the core mechanism driving the automated advancement of the entire process from task issuance to completion, and supports adaptation to different scenarios for data entry and approval. Multi-level approval routing includes approval workflow paths with multiple review levels. Data entry must be submitted for review sequentially according to preset levels, adapting to multi-role collaborative review scenarios.

[0059] Based on the preset logic of the custom workflow, the system drives the task nodes bound to the data entry tasks, accurately distributing the corresponding data entry tasks to the designated users. Simultaneously, according to the differentiated needs of the departments submitting the data, the system configures exclusive approval processes and multi-level approval routes. After the user completes the data entry, the system pushes the generated rich text content to the corresponding approving user. After the approving user completes the review, if the result is approved, the system automatically marks the task node as completed; if the approval is not approved, the system returns the data entry task to the original user, who can then revise and improve it before resubmitting for approval.

[0060] Step 208: With all task nodes in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0061] Among them, the trigger text generation instruction refers to the instruction signal automatically initiated by the system to start the report text creation process when the condition of "all task nodes are completed" is met. It is the core triggering mechanism that connects the task completion status with the text generation operation.

[0062] In the aforementioned report text generation method, a reusable task library is constructed. This library supports manual single-item creation and batch uploading of tasks, and allows maintenance of the corresponding task's department, handling user, and activation status. This achieves standardized management and efficient reuse of tasks, avoiding redundant operations caused by repeated creation. When creating a new report, the required tasks are selected and associated from the task library. A tree-structured data structure defines the text framework of the report body. The attributes of each node are transmitted as JSON strings, parsed, and stored in the database. Node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status. Node types are divided into title nodes (which do not require a data entry process and are set to "completed" by default) and task nodes bound to specific tasks. A visual drag-and-drop engine adjusts the node order, saving the adjusted order in real time and synchronously updating the report's generated structure logic. This satisfies the need for personalized report structure customization while ensuring... The system features real-time updates and precise storage of structural logic. Based on a custom workflow, task nodes are driven to distribute bound data entry tasks to corresponding users. Different approval processes and multi-level approval routes are set according to the department submitting the data. The rich text file completed by the user is sent to the approving user. If approved, the task node is marked as completed; if not, the rich text file is returned to the user for modification. This automates the data entry and approval process. Real-time linkage between approval results and task node status ensures the compliance and accuracy of the data entry while simplifying the modification process, improving overall business processing efficiency. When all task nodes are in the completed state, a text generation command is automatically triggered. The system integrates the content corresponding to the title nodes and completed task nodes according to the latest node order, generating a report document that meets the required format. This ensures the logical consistency, completeness, and format standardization of the report content, effectively improving the overall quality and efficiency of report generation and adapting to report production needs in various scenarios.

[0063] In one embodiment, the method further includes:

[0064] The system collects real-time data on task node status, reporting progress, and approval timeliness. Based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

[0065] The status of a task node refers to its current stage in the entire process of data entry and approval, such as not started, data entry in progress, pending approval, approved, or returned. Approval timeliness data refers to the total time elapsed from the submission of the data to the completion of the approval process (approval or return).

[0066] Specifically, S401. Data Acquisition and Analysis: The system collects task node status (such as the number of "completed"), data entry progress, and approval timeliness in real time. It generates statistical reports by department, task, and other dimensions, and supports exporting to Excel format.

[0067] S402. Visual chart display: Use bar charts, pie charts and other visual charts to intuitively display key indicators such as completion rate and task distribution.

[0068] The above embodiments enable dynamic tracking and precise control of key data throughout the entire report generation process, allowing relevant personnel to intuitively grasp the progress of each department and task, promptly identify issues such as delayed reporting and approval bottlenecks, and quickly intervene to coordinate, effectively ensuring the overall progress of report generation. At the same time, it provides data support for subsequent optimization of reporting task allocation, adjustment of approval processes, and improvement of work efficiency, further enhancing the practicality and optimizability of the technical solution and helping to form an efficient and controllable report generation management system.

[0069] In one embodiment, the method further includes:

[0070] During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

[0071] Among them, the pre-configured templates refer to standardized form filling templates that are configured and stored in advance, which include fixed format frameworks, field settings and sample content, for users to adopt and use to standardize the form filling content format.

[0072] Specifically, the system can maintain associated table templates, edit and save rich text on the front end, and import the system's preset templates when filling in data. At the same time, it can manually import indicator data from the upstream system as a reference. The system will automatically identify the corresponding content fields that need to be filled in and complete the automatic filling of the content.

[0073] In the above embodiments, the repetitive workload of manual data entry by users is greatly reduced, information errors caused by manual input are reduced, and the accuracy and efficiency of the data entry are improved. At the same time, the uniformity of the data entry format is ensured by the pre-set templates, and the real-time synchronization and consistency verification of data are achieved by directly introducing indicator data from the upstream system, avoiding redundancy and deviation caused by secondary data entry.

[0074] In one embodiment, the newly created report includes:

[0075] The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

[0076] Among them, the structure configuration refers to the core framework settings of the report, including the division of title node hierarchy and the association rules between task nodes.

[0077] Specifically, in S201, administrators create new periodic reports in the system, select the relevant reporting tasks from the task library, and manually add new tasks or delete irrelevant tasks to ensure that the reports contain only the necessary information.

[0078] S202. The node management page defines the text framework of the report body through a tree structure, and uses a tree data structure to store the report structure. Node attributes, including node ID, node type, parent node ID, node level, node order, node content, and node status, are transmitted in the form of JSON strings, parsed, and stored in the database.

[0079] S203. Develop a visual drag-and-drop engine that dynamically adjusts the node order through front-end DOM manipulation and event listeners, with the system saving the adjusted structure in real time. The system automatically updates the structure logic of the generated report to ensure that the output content matches the structure.

[0080] S204. When creating a report, a new report can be quickly generated based on historical reports, without having to manually add titles and task nodes again, thus improving report creation efficiency.

[0081] The above embodiments greatly simplify the process of creating new reports, avoid redundant work of repeatedly building report frameworks and configuring node relationships, and significantly improve the efficiency of creating new reports.

[0082] In one embodiment, the method further includes:

[0083] During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all tasks that have been filled in. The document style of the report document inherits the preset format, which includes font and paragraph spacing.

[0084] Real-time preview refers to the ability for users to view the current presentation of the report text document in real time during the report generation process, without waiting for the final document to be generated, facilitating timely identification and adjustment of problems. Rendering refers to the system's process of transforming the report's node content and preset formats into a visual document, converting abstract configuration data into a document form that users can intuitively view.

[0085] Specifically, S501 supports real-time preview of generated documents. The front-end page can render reports according to two cases: "all completed tasks" and "all reported tasks", ensuring that the title node and task node content are correctly embedded (like the position of a chart in a Word document).

[0086] S502. Supports document generation and style inheritance system to ensure that the format of the generated document (such as font and paragraph spacing) is consistent with the content filled in.

[0087] In the above embodiments, users can intuitively compare the report presentation effects under different task completion statuses, clearly grasp the completeness and progress of the report content, and facilitate early detection of the impact of incomplete tasks on the overall report and timely follow-up processing.

[0088] In one embodiment, the custom workflow includes process control logic for creation, distribution, filling, approval, cancellation, reset, and forced completion.

[0089] Among them, "forced completion" refers to the control operation that skips normal process nodes and manually marks the task as completed in special cases.

[0090] Specifically, the custom workflow encompasses seven major process control logics: creation, distribution, data entry, approval, cancellation, reset, and forced completion, forming a complete task lifecycle management chain. From the initial creation of the task and its precise distribution to the responsible user, to the user completing the data entry and entering the approval stage, it also includes flexible control functions for canceling invalid tasks, resetting the process to its initial state, and forcibly completing special tasks, thus constructing a complete workflow system covering both routine processes and special scenarios.

[0091] The above embodiments provide systematic and standardized process support for the full lifecycle management of data entry tasks, ensuring that every step from task initiation to completion has clear logical guidance, avoiding efficiency losses caused by process confusion or operational omissions; at the same time, through flexible process control functions such as invalidation, reset, and forced completion, it can cope with special scenarios such as task changes, error correction, and emergency handling that occur during the data entry process, ensuring both the rigor of process execution and the flexibility of business processing, effectively adapting to the report generation needs under different scenarios.

[0092] In one embodiment, reference Figure 3 The image shows a method for generating report text in a specific embodiment. The method includes:

[0093] S1: Create a data entry task library, maintain the tasks that need to be entered, and allow administrators to create report tasks as needed and set the corresponding template text and tables.

[0094] S101. The system supports manual single-task creation via the task interface, as well as batch uploading. It allows maintenance of the task's reporting department, task handler, and activation status. When organizational restructuring causes changes to the reporting department name, the latest reporting department can be synchronized with a single click.

[0095] S102. The task library allows you to view the reference status of tasks, showing in detail the person in charge of the task history, the department that filled it out, and the associated reports.

[0096] S103. The system can maintain associated table templates, edit and save rich text on the front end, import system-preset templates when filling in data, and manually import indicator data from upstream systems as a reference.

[0097] S2: Create reports and associate them with tasks. By associating tasks and managing structured nodes, reports can be intelligently orchestrated and automatically generated.

[0098] S201. Administrators create new periodic reports in the system, select the relevant reporting tasks from the task library, and can manually add new tasks or delete irrelevant tasks to ensure that the reports contain only the necessary information.

[0099] S202. The node management page defines the text framework of the report body through a tree structure, and uses a tree data structure to store the report structure. Node attributes, including node ID, node type, parent node ID, node level, node order, node content, and node status, are transmitted in the form of JSON strings, parsed, and stored in the database.

[0100] S203. Develop a visual drag-and-drop engine that dynamically adjusts the node order through front-end DOM manipulation and event listeners, with the system saving the adjusted structure in real time. The system automatically updates the structure logic of the generated report to ensure that the output content matches the structure.

[0101] S204. When creating a report, a new report can be quickly generated based on historical reports, without having to manually add titles and task nodes again, thus improving report creation efficiency.

[0102] S3: Report preparation and review, such as Figure 4 As shown, the workflow enables the distribution, submission, and approval of tasks. Different approval processes are implemented based on the department submitting the data.

[0103] S301. Customize the workflow to construct the core process control logic, including creation, distribution, data entry, approval, cancellation, reset, and forced completion. Based on the custom workflow, the task nodes will distribute the bound data entry tasks to the responsible users.

[0104] S302. The system sets different approval processes based on the reporting department (e.g., tasks of the management department only require single review within the department, while tasks of other departments require dual review by the reporting department and the management department).

[0105] S303. Implements multi-level approval routing, supports automatic allocation of approvers based on roles, and supports personnel to serve as approvers in multiple departments.

[0106] S304. The data entry process supports the import of task templates and historical report tasks, which makes it easier for data entry personnel to fill in data based on historical tasks and improves data entry efficiency.

[0107] S305. The content to be filled in is a rich text input box built into the front end. The system will save the rich text content to the database and generate the corresponding format of the input document content according to the input format.

[0108] S4: Report Submission Statistics. The system supports statistics on submission tasks, monitoring the submission status of periodic reports by department, task, and other dimensions. The submission status is displayed intuitively through visual charts.

[0109] S401. Data Acquisition and Analysis: The system collects task node status (such as the number of "completed"), data entry progress, and approval timeliness in real time. It generates statistical reports by department, task, and other dimensions, and supports exporting to Excel format.

[0110] S402. Visual chart display: Use bar charts, pie charts and other visual charts to intuitively display key indicators such as completion rate and task distribution.

[0111] S5: Report document generation and archiving. The system provides a report document preview function and supports document generation. It integrates the title node with the content of the completed task nodes to automatically generate a report text document that meets the format requirements (such as Word format), and can archive completed reports.

[0112] S501 supports real-time preview of generated documents. The front-end page can render reports according to two scenarios: "all completed tasks" and "all reported tasks," ensuring that the title node and task node content are correctly embedded (like the position of a chart in a Word document).

[0113] S502. Supports document generation and style inheritance system to ensure that the format of the generated document (such as font and paragraph spacing) is consistent with the content filled in.

[0114] S503. Report archiving: After management personnel have verified that the reports are "completed," they can archive them and store them locally in object storage. Record the archivist and the archiving time.

[0115] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0116] Based on the same inventive concept, this application also provides a report text generation apparatus for implementing the report text generation method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more report text generation apparatus embodiments provided below can be found in the limitations of the report text generation method described above, and will not be repeated here.

[0117] In one exemplary embodiment, such as Figure 5 As shown, a report text generation device is provided, including: a construction module 502, a new creation module 504, an approval module 506, and a generation module 508, wherein:

[0118] Module 502 is used to build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0119] A new module, 504, is created to generate new reports. It selects and associates tasks to be filled in from the task library. A tree-structured data structure is used to define the text framework of the report body. The attributes of each node are transmitted as JSON strings, parsed, and stored in the database. The attributes of a node include node ID, node type, parent node ID, node level, node order, node content, and node status. Node types include title nodes that do not require filling in any process and are set to completed by default, and task nodes that are bound to the task being filled in. The node order can be adjusted through a visual drag-and-drop engine, and the adjusted node order is saved in real time and the structure logic of the generated report is updated.

[0120] The approval module 506 is used to drive task nodes to distribute bound data entry tasks to the handling users based on a custom workflow; it sets different approval processes and multi-level approval routes based on the data entry department, and sends the completed rich text to the approving users; after approval, the task node is marked as completed; if the approval fails, it is returned to the handling user for modification.

[0121] The generation module 508 is used to trigger the main text generation instruction when all task nodes are in a completed state. It integrates the content of the title node and the completed task nodes according to the latest node order to generate a report main text document that meets the format requirements.

[0122] In one embodiment, the generation module 508 is used to:

[0123] The system collects real-time data on task node status, reporting progress, and approval timeliness. Based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

[0124] In one embodiment, the construction module 502 is used for:

[0125] During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

[0126] In one embodiment, a new module 504 is created for:

[0127] The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

[0128] In one embodiment, the generation module 508 is further configured to:

[0129] During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all tasks that have been filled in. The document style of the report document inherits the preset format, which includes font and paragraph spacing.

[0130] In one embodiment, the custom workflow includes process control logic for creation, distribution, filling, approval, cancellation, reset, and forced completion.

[0131] Each module in the aforementioned report text generation device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0132] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 6 As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements a method for generating report text. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0133] Those skilled in the art will understand that Figure 6 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0134] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0135] The building module is used to build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0136] The new module is used to create new reports. It selects and associates the tasks to be filled in from the task library. It uses a tree data structure to define the text framework of the report body. The attributes of each node are transmitted as JSON strings, parsed and stored in the database. The attributes of a node include node ID, node type, parent node ID, node level, node order, node content and node status. The node type includes title nodes that do not require filling in the process and are set to completed by default, and task nodes that are bound to the task to be filled in. The node order can be adjusted through a visual drag-and-drop engine. The adjusted node order is saved in real time and the structure logic of the generated report is updated.

[0137] The approval module is used to drive task nodes to distribute bound data entry tasks to the responsible users based on a custom workflow; it sets different approval processes and multi-level approval routes based on the data entry department, and sends the completed rich text to the approving users; after approval, the task node is marked as completed; if the approval fails, it is returned to the responsible user for modification.

[0138] The generation module is used to trigger the text generation instruction when all task nodes are in a completed state. It integrates the content of the title node and the completed task nodes according to the latest node order to generate a report text document that meets the format requirements.

[0139] In one embodiment, the method further includes:

[0140] The system collects real-time data on task node status, reporting progress, and approval timeliness. Based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

[0141] In one embodiment, the method further includes:

[0142] During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

[0143] In one embodiment, the newly created report includes:

[0144] The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

[0145] In one embodiment, the method further includes:

[0146] During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all tasks that have been filled in. The document style of the report document inherits the preset format, which includes font and paragraph spacing.

[0147] In one embodiment, the custom workflow includes process control logic for creation, distribution, filling, approval, cancellation, reset, and forced completion.

[0148] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0149] Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0150] Create a new report by selecting and associating tasks from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; node types include title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks; adjust the node order using a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0151] Based on a custom workflow, the driving task node distributes the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the department in charge, the rich text of the completed data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0152] When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0153] In one embodiment, the method further includes:

[0154] The system collects real-time data on task node status, reporting progress, and approval timeliness. Based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

[0155] In one embodiment, the method further includes:

[0156] During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

[0157] In one embodiment, the newly created report includes:

[0158] The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

[0159] In one embodiment, the method further includes:

[0160] During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all tasks that have been filled in. The document style of the report document inherits the preset format, which includes font and paragraph spacing.

[0161] In one embodiment, the custom workflow includes process control logic for creation, distribution, filling, approval, cancellation, reset, and forced completion.

[0162] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

[0163] Build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks.

[0164] Create a new report by selecting and associating tasks from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; node attributes include node ID, node type, parent node ID, node level, node order, node content, and node status; node types include title nodes (which do not require data entry and are set to completed by default) and task nodes bound to data entry tasks; adjust the node order using a visual drag-and-drop engine, save the adjusted node order in real time, and update the structure logic of the generated report.

[0165] Based on a custom workflow, the driving task node distributes the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the department in charge, the rich text of the completed data entry is sent to the approving user; after approval, the task node is marked as completed; if the approval fails, it is returned to the user in charge for modification.

[0166] When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

[0167] In one embodiment, the method further includes:

[0168] The system collects real-time data on task node status, reporting progress, and approval timeliness. Based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

[0169] In one embodiment, the method further includes:

[0170] During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

[0171] In one embodiment, the newly created report includes:

[0172] The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

[0173] In one embodiment, the method further includes:

[0174] During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all tasks that have been filled in. The document style of the report document inherits the preset format, which includes font and paragraph spacing.

[0175] In one embodiment, the custom workflow includes process control logic for creation, distribution, filling, approval, cancellation, reset, and forced completion.

[0176] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0177] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0178] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0179] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for generating report body text, characterized in that, The method includes: Construct a reusable data entry task library, which supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user, and activation status of tasks; Create a new report by selecting and associating the tasks to be filled in from the task library; define the text framework of the report body using a tree data structure, transmit the attributes of each node as JSON strings, parse and store them in the database; the attributes of each node include node ID, node type, parent node ID, node level, node order, node content, and node status; the node type includes title nodes that do not require a filling process and are set to completed by default, and task nodes that are bound to the filling tasks; adjust the node order through a visual drag-and-drop engine, save the adjusted node order in real time, and update the structural logic of the generated report; Based on a custom workflow, the task node is driven to send the bound data entry task to the user in charge; based on different approval processes and multi-level approval routes set by the data entry department, the rich text after data entry is sent to the approving user; after approval, the task node is marked as completed; if approval fails, it is returned to the user in charge for modification. When all task nodes are in a completed state, trigger the text generation command, integrate the content of the title node and the completed task nodes according to the latest node order, and generate a report text document that meets the format requirements.

2. The method according to claim 1, characterized in that, The method further includes: The system collects real-time data on task node status, reporting progress, and approval timeliness; based on the collected data, it generates statistical reports and displays the reporting status through visual charts, categorized by reporting department and task.

3. The method according to claim 1, characterized in that, The method further includes: During the process of handling the data entry task by the user, in response to the import operation of the preset template and the indicator data of the upstream system, the corresponding content to be filled in is automatically filled in.

4. The method according to claim 1, characterized in that, The newly created report includes: The system retrieves the structure configuration of historical reports, inherits the existing title node hierarchy and the relationships between task nodes to obtain the initial report, and generates a new report in response to adjustments made to the initial report.

5. The method according to claim 1, characterized in that, The method further includes: During the real-time preview of the report document, the report document is rendered in two scenarios: one for all completed tasks and the other for all submitted tasks. The document style of the report document inherits a preset format, which includes font and paragraph spacing.

6. The method according to claim 1, characterized in that, The custom workflow includes process control logic for creation, distribution, data entry, approval, cancellation, reset, and forced completion.

7. A report text generation device, characterized in that, The device includes: The module is used to build a reusable data entry task library. The data entry task library supports manual single-item creation and batch uploading of tasks, and supports maintaining the data entry department, handling user and activation status of tasks. A new module is used to create new reports. It selects and associates the tasks to be filled in from the task library. A tree-structured data structure is used to define the text framework of the report body. The attributes of each node are transmitted as JSON strings, parsed, and stored in the database. The attributes of each node include node ID, node type, parent node ID, node level, node order, node content, and node status. The node type includes title nodes that do not require a filling process and are set to completed by default, and task nodes that are bound to the filling task. The node order can be adjusted through a visual drag-and-drop engine. The adjusted node order is saved in real time and the structural logic of the generated report is updated. The approval module is used to drive the task node to send the bound data entry task to the handling user based on a custom workflow; to send the completed rich text to the approving user based on different approval processes and multi-level approval routes set by the data entry department; to mark the task node as completed after approval; and to return the data entry to the handling user for modification if the approval fails. The generation module is used to trigger the text generation instruction when all task nodes are in a completed state. It integrates the content of the title node and the completed task nodes according to the latest node order to generate a report text document that meets the format requirements.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images