Enterprise information management system printing data processing method and device, product and medium

By converting editable table documents on the server side of the enterprise information management system to generate cross-platform format table documents, the problem of uncontrollable printing results is solved, and format consistency and efficient printing operations are achieved.

CN122152248APending Publication Date: 2026-06-05SHANGHAI HEIHU NETWORK TECHNOLOGY CO LTD +1

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
SHANGHAI HEIHU NETWORK TECHNOLOGY CO LTD
Filing Date
2026-03-19
Publication Date
2026-06-05

AI Technical Summary

Technical Problem

Existing enterprise information management systems suffer from uncontrollable printing results and poor format consistency due to the influence of users' personal habits and local software environment during the printing process.

Method used

On the server side, editable table documents are converted to generate cross-platform format table documents, including triggering formula calculations, obtaining format parameters, applying page break splitting and paper adaptation rules to ensure consistent printing format.

Benefits of technology

It achieves uniformity and accuracy in printing format, improves operational efficiency, avoids data errors, and optimizes server-side computing performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122152248A_ABST
    Figure CN122152248A_ABST
Patent Text Reader

Abstract

A kind of enterprise information management system print data processing method and device, product, medium, print data processing method includes: receiving print data, generating editable table document;In response to formula contained in editable table document, trigger formula to complete calculation;Get the format parameter of editable table document, and determine conversion rule according to format parameter;Based on conversion rule, editable table document is converted into cross-platform format table document, and cross-platform format table document is pushed to the user end of enterprise information management system.The above scheme can be converted into cross-platform format table document on the server side to the editable table document, realize print format uniformity.Formula calculation is triggered actively before conversion, which avoids printing out wrong data after conversion.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of enterprise information management technology, and in particular to a method, apparatus, product, and medium for processing printed data in an enterprise information management system. Background Technology

[0002] In enterprise information management, especially in manufacturing production management, printing is a high-frequency and critical operation. Enterprise information management systems (hereinafter referred to as "the system") typically need to support multiple types of printing tasks, including production work orders, process flow drawings, quality inspection reports, etc. Existing systems generally adopt printing solutions based on editable spreadsheet documents, commonly using Excel. When printing is required, the user first selects the corresponding print data in the system, which then fills it into a preset Excel template, generating an Excel document. Subsequently, the user downloads the Excel document to their local computer and manually opens it using locally installed office software. Finally, the user sets print settings such as paper orientation, scaling, and margins in Excel and then executes the print operation.

[0003] The difference between server-generated editable table documents and user-processed editable table documents leads to uncontrollable printing results and poor format consistency due to differences in user habits and uncertainties in local software environments. Summary of the Invention

[0004] To address the aforementioned issues, this invention provides a method for processing print data in an enterprise information management system, which can convert editable table documents into cross-platform format table documents on the server side, thereby achieving uniform printing format.

[0005] In a first aspect, the present invention provides a method for processing print data in an enterprise information management system, applied to the server side of the enterprise information management system, the method comprising: Receive print data and generate an editable table document; In response to the presence of a formula within the editable table document, the formula is triggered to complete the calculation. Obtain the format parameters of the editable table document, and determine the conversion rules based on the format parameters; Based on the conversion rules, the editable table document is converted into a cross-platform format table document, and the cross-platform format table document is pushed to the user terminal of the enterprise information management system.

[0006] Optionally, the format parameters of the editable table document include the number of rows and columns filled by the printed data. Before converting the editable table document into a cross-platform format table document, the method further includes generating a set of printable cells based on the number of rows and columns filled by the printed data.

[0007] Optionally, the format parameters of the editable table document may also include the number of horizontal page breaks, the height of each row, and the width of each column. The conversion rules include: page break splitting rules and / or paper adaptation rules. The page break splitting rules are used to split the set of printed cells according to the number of horizontal page breaks, and the paper adaptation rules are used to determine whether it is necessary to enlarge the set of printed cells.

[0008] Optionally, converting the editable table document into a cross-platform table document based on the page break splitting rules includes: Determine whether the number of horizontal page breaks is greater than or equal to 1; If the result is yes, then get the line number of each horizontal page break; Create N-1 split tables and end page tables, and arrange the N-1 split tables and end page tables sequentially on different print pages, where N is the number of horizontal page breaks; The set of printed cells before the first horizontal page break is retained as the first page table. The set of printed cells after the Nth horizontal page break is copied to the last page table. The set of printed cells between the nth and (n+1)th horizontal page breaks is copied to the nth split table. The cross-platform format table document includes the first page table, N-1 split tables, and the last page table, where n is a positive integer from 1 to N-1.

[0009] Optionally, converting the editable table document into a cross-platform table document based on paper adaptation rules includes: Calculate the total row height and total column width based on the height of each row and the width of each column. The total row height is equal to the number of rows in the printed cell set. The height of each row, and the total column width, equal to the number of columns in the printed cell set. Column width; Obtain the height and width of the paper, calculate the height threshold and width threshold, where the height threshold = height. Height coefficient, width threshold = width Width coefficient, wherein both the height coefficient and the width coefficient are greater than 0 and less than 1; Compare the height threshold with the total row height, and the width threshold with the total column width, respectively, to determine whether the total row height is less than the height threshold and the total column width is less than the width threshold. If the judgment result is yes, then the enlarged set of printed cells is triggered, and the cross-platform format table document contains the enlarged set of printed cells.

[0010] Optionally, both the height coefficient and the width coefficient are greater than 0.35 and less than 0.45.

[0011] Optionally, based on the conversion rules, converting the editable table document into a cross-platform format table document includes: Based on the page break splitting rules, determine whether the set of printed cells needs to be split; If the judgment result is yes, the set of printed cells is split into multiple split sets of printed cells; Based on the paper adaptive rule, determine whether to perform magnification for each set of split print cells and determine the magnification ratio for each set of split print cells. If at least one split set of print cells needs to be enlarged, then an execution is triggered to enlarge each set of print cells that needs to be enlarged by the same proportion, wherein the same proportion is the smallest of the enlargement proportions of each set of print cells that needs to be enlarged.

[0012] Optionally, the print data includes print settings information, which is used to configure the display parameters of the cross-platform format table document.

[0013] Optionally, the print settings information includes one or more of the following: print orientation, centering, margins, height orientation auto-adjustment, and width orientation compression.

[0014] Optionally, triggering the formula to complete the calculation includes the following steps: Determine the calculation options for the formula, including: disabling calculation chain parameters; Perform the calculation according to the calculation options and return the result.

[0015] Secondly, the present invention provides a print data processing device for an enterprise information management system, comprising: The data receiving unit is used to receive print data and generate an editable table document; The formula calculation unit is used to respond to formulas contained in an editable table document, triggering the formula to complete the calculation. The rule determination unit is used to obtain the format parameters of the editable table document and determine the conversion rules based on the format parameters; The document conversion unit is used to convert editable tabular documents into cross-platform format tabular documents based on conversion rules, and then push the cross-platform format tabular documents to the user end of the enterprise information management system.

[0016] Thirdly, the present invention also provides a computer-readable storage medium, which is a non-volatile or non-transient storage medium, on which a computer program is stored, wherein the computer program is executed by a computer to perform the printing data processing method of any of the above-described enterprise information management systems.

[0017] Fourthly, the present invention also provides a computer program product, including a computer program / instruction, wherein when the computer program / instruction is run by a computer, the printing data processing method of any of the above-described enterprise information management systems is executed.

[0018] Compared with the prior art, the embodiments of the present invention have the following beneficial effects: This invention, through server-side conversion of editable tabular documents into cross-platform tabular formats, solves the problem of inconsistent printing formats caused by reliance on the user's local environment. By proactively triggering formula calculations before conversion, it ensures that the data in the printed document is the latest calculated result, avoiding the printing of incorrect data after conversion.

[0019] Furthermore, after obtaining multiple split tables based on page break splitting rules, the scaling ratio calculation for each split table is performed independently according to the paper adaptation rule. When at least one set of split print cells needs to be enlarged, the smallest scaling ratio among all scaling ratios is used as the uniform ratio, and the same scaling ratio is applied to each set of print cells that needs to be enlarged. This ensures visual consistency across multiple pages of the document and avoids the print cell set exceeding the usable area of ​​the target paper after enlargement by selecting the smallest ratio.

[0020] Furthermore, by identifying computation options that include disabling computation chain parameters and performing calculations accordingly, the computational overhead caused by traversing the dependency chains of formulas is reduced. This solves the problem of cumulative performance loss in high-concurrency, resource-constrained server-side scenarios, improving system throughput without altering the computational logic, and ensuring timely and accurate calculation results. Attached Figure Description

[0021] Figure 1 This is a flowchart of the printing data processing method of the enterprise information management system in an embodiment of the present invention; Figure 2 This is a schematic diagram of the printing data processing device of the enterprise information management system in an embodiment of the present invention. Detailed Implementation

[0022] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be clearly and completely described below with reference to the accompanying drawings and specific embodiments. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0023] As mentioned in the background section, due to differences in user habits and uncertain local software environments during the use of existing systems, uncontrollable printing results and poor formatting consistency occur when users print editable table documents locally. To address this technical problem, this invention provides a printing data processing method for an enterprise information management system, applied to the server side of the enterprise information management system.

[0024] In this embodiment of the invention, by actively triggering formula calculations in the generated editable table document before conversion, data errors during document conversion on the server side can be avoided. Specifically, the document is identified by detection or other methods to determine whether it contains formulas. If formulas are found, the calculation is triggered to ensure that the data in the document is in its final state, thus preventing errors in printed content due to outdated formulas.

[0025] The server retrieves the format parameters of the editable table document and determines the conversion rules based on these parameters. Based on these rules, the editable table document is converted into a cross-platform table document, such as a PDF document, and then pushed to the user's device. Users can print directly without downloading the source file or installing corresponding office software, ensuring consistent printing results across all devices.

[0026] To make the above-mentioned objectives, features and beneficial effects of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0027] The printing data processing method for an enterprise information management system provided in this embodiment of the invention can be applied to an enterprise information management system. This enterprise information management system can be a cloud-based manufacturing collaboration platform. The backend of the system can run on a cloud or local server for processing and storing data. The user end of the system can be implemented based on a webpage or an app, used to retrieve the printing data needed by the user and view the effect of document conversion.

[0028] like Figure 1 As shown, Figure 1This is a flowchart of a print data processing method for an enterprise information management system according to a first embodiment of the present invention. Specifically, in this embodiment, step S101 involves receiving print data and generating an editable table document. The print data may be business records selected by the user on the client side of the enterprise information management system. After receiving the print data, the server fills in the business data according to a preset template, such as an Excel template, to generate an editable table document containing the actual data, such as an Excel format document. The editable table document may be temporarily stored in the server's memory or in a non-persistent storage medium for temporary data.

[0029] Step S102: In response to the presence of formulas within the editable table document, the formula calculation is triggered. After generating or loading the editable table document, the server first determines whether the document contains formulas through detection or other methods. If formulas are present, the calculation is proactively triggered, and this calculation can be performed by the calculation engine. This ensures that all dynamic data dependent on formulas, such as totals, averages, data that changes based on conditions, or data related to other cells, are correctly updated to the displayed result data. Formula calculations can be completed in the server's memory without requiring any software calls from the user.

[0030] Step S103: Obtain the format parameters of the editable table document and determine the conversion rules based on the format parameters. Specifically, the format parameters can be obtained by parsing the editable table document or by directly querying the target format parameters. Format parameters may include, but are not limited to: the number of rows and columns filled with actual data in the document, i.e., the range of cells filled with content, as well as the height of each row, the width of each column, the number and position of user- or system-preset horizontal page breaks, etc. Based on the obtained format parameters, specific conversion rules are determined. If the conversion rules are uniform on the server side, the cross-platform format document generated by the uniform conversion rules will have a fixed layout. This fundamentally solves the problem of inconsistent printing formats caused by reliance on the user's local software version and personalized operations in traditional solutions.

[0031] Step S104: Based on the conversion rules, the editable table document is converted into a cross-platform format table document, and the cross-platform format table document is pushed to the user terminal of the enterprise information management system. According to the determined conversion rules, the editable table document is processed and converted into a cross-platform format table document, such as a PDF document. The server returns the access path of the generated PDF file or the file itself as a response to the user terminal. After receiving the response, the user terminal can directly open and view the PDF file in a browser or mobile application. Printing can be done directly by calling the browser's built-in printing plugin. Users do not need to perform operations such as downloading, opening local software, selecting templates, and manually adjusting formatting, thus improving operational efficiency.

[0032] Furthermore, before converting the editable table document into a cross-platform format table document, the process includes generating a set of printable cells based on the number of rows and columns filled by the print data. In the printing scenario of an enterprise information management system, editable table documents are usually generated based on a preset template. The template itself may contain a large number of blank rows and columns. Traditional printing methods will print the areas actually filled with data and blank areas indiscriminately. Alternatively, users may decide which blank areas should not be included in the print, but different users have different preferences for the blank areas to be removed and retained, resulting in inconsistent formatting. This embodiment of the invention accurately identifies the range of cells actually occupied by user data by obtaining the number of rows and columns filled by the print data. The set of printable cells generated based on this range provides a clear object for subsequent format processing and conversion operations. The processing range is narrowed from the entire worksheet to the area containing only valid data, avoiding problems such as excessively large print areas, inaccurate scaling calculations, or pagination errors caused by blank areas.

[0033] Furthermore, the conversion rules include: page break splitting rules and paper adaptation rules, or either page break splitting rules or paper adaptation rules can be applied individually. Page break splitting rules are used to split the set of printed cells based on the number of horizontal page breaks, while paper adaptation rules are used to determine whether to enlarge the set of printed cells. When the system executes a user's printing request, the editable table document may contain multiple logical pages identified by horizontal page breaks. There may also be cases where the content is small and directly printed would be concentrated in the corners of the page. By effectively splitting the set of printed cells and rationally distributing them across each page, the readability of the printed document can be improved. For small-sized cells concentrated in the corners of the page, enlargement is used to fully utilize paper space and improve the visual effect of the print.

[0034] In this embodiment of the invention, for an editable table document containing horizontal page breaks, the original set of printable cells is divided by the horizontal page breaks by precisely identifying the position of each horizontal page break. In the editable table document, the horizontal page breaks express the printing pagination logic. The horizontal page break splitting rules are then used to transform the pagination effect of the final cross-platform format document, thereby ensuring that each logical page is presented independently on a different printable page.

[0035] In some implementations, the first step is to check if the number of horizontal page breaks is greater than or equal to 1. If so, page splitting is performed. When the number of horizontal page breaks is N, the original set of printable cells is actually divided into N+1 regions by the page breaks, which the user wants to print on N+1 print pages. The area before the first page break is the first page table, and the area after the Nth page break is the last page table. Split tables are located between every two adjacent page breaks. Specifically, by retaining the first page table, N-1 split tables and last page tables are created, corresponding to the N+1 split regions. The N regions of the printable cell set, excluding the first page table, are copied to the corresponding N-1 split tables and last page tables. The final cross-platform format document contains the first page table, split tables, and last page table, with each table occupying an independent print page. Here, N is a positive integer.

[0036] In some implementations, after determining if a horizontal page break is present, it can be further checked whether the number of horizontal page breaks is equal to 1. If the result is yes, the page is directly split into a first page table and a last page table. If the result is no, N-1 split tables and a last page table are created, and the set of printable cells between the nth and (n+1)th page breaks is copied into the nth split table, where n is a positive integer from 1 to N-1. Simultaneously, the set of printable cells after the Nth page break is copied into the last page table.

[0037] Through the above implementation method, the editable table document containing horizontal page breaks is split, accurately restoring the user's expected printing pagination logic, and each table can be further processed separately.

[0038] Furthermore, the first page table, split tables, and last page table inherit the metadata of the editable table document, which includes format parameters, print settings, page footer settings, and custom attributes. After copying the print cell set to the split tables and last page table respectively, the process also includes triggering a metadata update.

[0039] By inheriting the metadata of the original editable table document, it ensures that all split printable cell sets, including the first page table, split tables, and last page table, maintain consistency in print orientation, margins, etc., avoiding print quality discrepancies due to lost settings. It triggers metadata updates to ensure that page break rules can support more complex conversions of editable table documents, and that each page of the generated cross-platform format table document correctly displays page number information, while also ensuring that the information in the header and footer matches the information in the original editable table document. For manufacturing industries, this information typically includes business type, production batch number, log time, etc., and often involves product quality inspection traceability and process iteration traceability. Inheriting and updating metadata facilitates accurate traceability when using printed documents later.

[0040] In this embodiment of the invention, there is often a mismatch between the size of the printed cell set and the target printing paper size. When the size of the printed cell set is significantly smaller than the paper size, if printed directly, the printed content will appear too small on the paper, leaving a large amount of blank space around it, affecting the reading experience and the document's aesthetics. This embodiment of the invention uses paper adaptive rules to quantitatively compare the content size with the paper size, triggering a magnification operation when specific conditions are met, so that the content can make fuller use of the paper space.

[0041] Specifically, the total row height and total column width are calculated based on the height of each row and the width of each column. The total row height equals the number of rows in the printed cell set. Row height, total column width = number of columns in the printed cell set Column width. The server can convert the above size-related parameters into a uniform physical unit of measurement, such as inches or millimeters, for accurate comparison with paper sizes. A standard resolution can be used as the conversion benchmark. Obtain the height and width of the target paper, for example, A4 paper is 11.69 inches × 8.27 inches or 297 mm × 210 mm.

[0042] Calculate the threshold based on the preset height and width coefficients: Height threshold = Paper height Height coefficient, width threshold = paper width Width coefficient. Both the height coefficient and width coefficient are values ​​greater than 0 and less than 1. The magnitude of the coefficient determines the strictness of triggering magnification. For example, for a document split into multiple tables of varying sizes, a smaller coefficient results in a more lenient trigger condition, meaning more tables will be deemed to require magnification; a larger coefficient results in a stricter trigger condition, meaning only very small tables will be magnified. The specific coefficients can be pre-configured in the server's memory or obtained in real-time from the user's latest configuration data.

[0043] The system compares the height threshold with the total row height and the width threshold with the total column width to determine if both of the following conditions are met simultaneously: the total row height is less than the height threshold, and the total column width is less than the width threshold. If both conditions are met, the content size of the current printable cell set is determined to be significantly smaller than the paper size, requiring a magnification operation. If neither condition is met, the content size is determined to be large enough, requiring no magnification and remaining unchanged. If the determination result is yes, the server triggers the magnification of the printable cell set. The magnification operation may include: calculating an appropriate magnification ratio based on the paper's height and width to ensure the magnified content fits the available area of ​​the paper; and adjusting the print margin settings to ensure the magnified content is centered on the paper. The final generated cross-platform format table document contains the magnified printable cell set, occupying a print area in the document that matches the paper size. This embodiment establishes quantifiable magnification trigger conditions by setting calculation thresholds for height and width coefficients and comparing them with the size of the printable cell set, avoiding the arbitrariness of subjective judgment.

[0044] Furthermore, in the paper adaptive rule, the values ​​of the height and width coefficients determine the threshold range for triggering magnification, thus affecting the actual effect of the entire rule. By limiting the height and width coefficients to a range greater than 0.35 and less than 0.45, a balance point is achieved. This ensures that small-sized printed cell sets have the opportunity to be magnified, while avoiding unnecessary magnification of medium-sized content. In the specific implementation, users can fine-tune the coefficients within the range of 0.35 to 0.45 according to actual printing needs. For example, if more content is desired to be magnified, the coefficient can be adjusted to 0.35; if only very small content is desired to be magnified, the coefficient can be adjusted to 0.45.

[0045] Preferably, the server-side configuration of paper adaptation rules presets the height and width coefficients to 0.4, which is 40% of the paper threshold. In one specific implementation, the system provides a default configuration of 0.4 for both the height and width coefficients, while allowing modification of the specific values ​​of the height and width coefficients through a configuration interface or parameter input, but the value range is limited to between 0.35 and 0.45 to ensure the stability and effectiveness of the adaptation rules.

[0046] Furthermore, in the paper adaptation rules, the content type of the editable table document is analyzed. The height and width coefficients are determined based on the content type, which includes text-intensive, table-intensive, and mixed text and image types. If none of these types apply, it falls under the default type, and its height and width coefficients are set to the default configuration. Different content types have varying sensitivities to scaling: text-intensive content requires higher readability after scaling and thus more lenient scaling conditions; table-intensive content requires higher boundary alignment after scaling and thus more stringent scaling conditions; and mixed text and image content requires a balance between both. This solution dynamically adjusts the coefficients based on the content type, providing differentiated scaling strategies for different content types and further enhancing the precision of the printing effect.

[0047] Furthermore, this content type is determined by the proportion of various data formats (e.g., text, tables, images) contained in the document. Specifically, the content types analyzed for editable table documents include, but are not limited to: if more than 80% of the cells in the printed cell set contain text content and the average number of characters per cell is greater than 10, it is classified as text-intensive. If more than 50% of the cells in the printed cell set contain numerical data and exhibit a clear row and column alignment structure, it is classified as table-intensive. If the printed cell set contains images and the number of cells with images exceeds 5% of the total number of cells in the cell set, it is classified as a mixed text and image type. The height and width coefficients are dynamically adjusted based on whether the content is text-intensive, table-intensive, or a mixed text and image type, so that the zoom judgment can adapt to the display needs of different content types.

[0048] In some implementations, both page break splitting rules and paper adaptation rules are applied simultaneously. The editable table document is first split into multiple independent sets of printable cells, each corresponding to an independent print page. Since the specific number of rows, columns, row height, and column width may differ for each split set of printable cells, their judgments based on the paper adaptation rules will vary. Even if the judgment for each split set of printable cells is that enlargement is required, the required enlargement ratio may differ each time it is performed.

[0049] Specifically, in some implementations, based on the page break splitting rules, the original set of printable cells is split according to the number of horizontal page breaks N, resulting in multiple split sets of printable cells. The split sets of printable cells can be the first page table, N-1 split tables, and the last page table, for a total of N+1 tables.

[0050] If each set of split print cells is scaled independently, the resulting cross-platform document will have inconsistent scaling across different pages, leading to a lack of visual consistency and negatively impacting the reading experience and professionalism. This embodiment addresses this by introducing a uniform scaling factor, using the smallest possible scaling factor. This ensures that all split print cell sets, when scaled up, do not exceed the usable area of ​​the target paper, achieving a consistent display style across the entire document.

[0051] In some implementations, print data includes print settings information, which is used to configure the display parameters of cross-platform formatted table documents. In the printing scenarios of enterprise information management systems, users often want to have a certain degree of personalized control over the final print output, such as different preferences between different departments, or different business types requiring different paper orientations and content positions on the page.

[0052] By including print settings information in the received print data, users can submit their printing preferences to the server along with the print request. This print settings information is parsed by the server and used to guide subsequent document conversion, ensuring that the final cross-platform formatted table document displays parameters that meet the user's needs. This transforms print settings that previously required manual adjustment in the user's local software into display parameters that can be automatically applied on the server, preserving the user's personalization options while avoiding dependence on local software.

[0053] Furthermore, print settings may include, but are not limited to: print orientation (landscape or portrait), centering, margin size, height auto-adjustment, and width compression. After receiving the print data, the server can extract and parse the print settings to convert them into display parameters. In the subsequent process of converting the editable table document into a cross-platform table document based on conversion rules, the document's layout is adjusted according to these display parameters.

[0054] Specifically, in some implementations, if the print settings include a print orientation parameter and the value is landscape, then when generating a cross-platform format table document, the orientation of each page will be set to landscape; if the value is portrait or not specified, a portrait layout will be used. If the print settings include a centering parameter and the value is yes, then when setting the page layout, horizontal and / or vertical centering options will be enabled to ensure that the content is displayed in the center of the page. If the print settings specify page margin values, such as 0.5 inches on each side, then the blank areas around the page will be set according to this value when generating the page; if not specified, the system default page margins will be used. If the print settings include a height-adaptive parameter and the value is yes, then when setting the page layout, the vertical page number limit will be removed, allowing the number of pages to automatically expand according to the content height, ensuring that all rows can be printed completely. If the print settings include a width-compression parameter and the value is yes, then when setting the page layout, all columns will be compressed to the width of one page to avoid content being truncated horizontally due to too many columns. The above display parameters can be applied individually or in any combination. For example, when configuring print settings, users can choose to print only in portrait orientation, or choose to print in landscape orientation, center the display, and enable width compression to adapt to tables with many columns but few rows.

[0055] Furthermore, triggering the formula to complete the calculation includes determining the calculation options for the formula, including disabling calculation chain parameters. In the process of processing print data in an enterprise information management system, editable spreadsheet documents may contain numerous formulas with complex dependencies, forming calculation chains.

[0056] When formula calculations are triggered, if the local Excel software only processes a single file opened by the current user at a time, there is no multi-task concurrency pressure. For a single file, even traversing the complete formula dependency chain is not noticeable to the user. However, after shifting the formula calculation process from the user's local machine to the server for unified processing, the server needs to handle a large number of print requests from hundreds or thousands of users simultaneously. Each request corresponds to an editable spreadsheet document that may contain multiple formulas. If each document uses the calculation chain traversal method, the server needs to repeatedly build and traverse the formula dependency graph, leading to a sharp increase in CPU computing resources. The overhead of calculation chain traversal in a single-file scenario is dramatically amplified in a concurrent scenario.

[0057] In some embodiments, a parameter to disable the calculation chain is introduced in the calculation options, altering the execution logic of formula calculations. The system no longer traverses the complete formula calculation chain but instead employs a more direct calculation method, thereby reducing unnecessary computational overhead and improving the formula calculation speed when batch processing large-scale editable tabular documents on the server side. For batch printing scenarios, the introduction of the parameter to disable the calculation chain results in a relatively insignificant increase in computation time when processing multiple documents consecutively, leading to a better user experience.

[0058] Furthermore, after performing the calculation according to the calculation options and before returning the calculation result, the process includes: detecting whether a formula calculation error occurred during the calculation process; if the result is yes, then reverting and re-executing the calculation using default calculation options, which include enabling the calculation chain parameter. While disabling the calculation chain parameter can improve formula calculation efficiency and meet the accuracy requirements of most scenarios, in certain special cases, such as when using specific calculation functions, disabling the calculation chain may lead to abnormal calculation order, thereby causing calculation errors. This solution introduces error detection, providing a way to ensure the correctness of the calculation result in abnormal situations while maintaining efficient calculation. The detection-revert-recalculation mechanism achieves a balance between performance improvement and reliability assurance.

[0059] Furthermore, detecting whether a formula calculation error has occurred during the calculation process includes: monitoring the execution status of the formula and recording the error type and location; determining a local correction strategy based on the error type and location; performing calculations on the smallest region associated with the calculation error based on the local correction strategy and detecting it again; if the returned result still contains errors, then a judgment result of "yes" is returned. The detection-return-recalculation mechanism directly discards all calculation results after detecting an error and recalculates the entire system using the default option of enabling the calculation chain. While this can solve the correctness problem, it is costly, resulting in wasted computing resources and increased processing latency.

[0060] By introducing a refined error handling mechanism, instead of immediately rolling back after an error is detected, the system categorizes and diagnoses errors based on their recorded type and location, and then matches targeted local correction strategies. For example, for circular reference errors, the system locally enables the computation chain for the calculation options forming the loop; for missing dependency errors, it supplements the missing dependency calculation options; and for function parameter errors, it attempts to correct the parameters and then locally recalculates. This precise repair approach preserves most of the correctly calculated results, recalculating only the smallest affected area, thereby further improving the efficiency and resource utilization of server-side formula calculations while ensuring the correctness of the results.

[0061] Furthermore, after determining the corresponding local correction strategy based on the error type and location, the process further includes: recording the processing history of the local correction strategy, wherein the processing history includes the error type, error location, local correction strategy used, correction time, and correction result; performing statistical analysis based on the accumulated processing history, and dynamically adjusting the error type classification and diagnosis rules and the priority order of the local correction strategy according to the analysis results. During server-side operation, the processing of formula calculation errors will accumulate a large amount of historical data. Historical data can not only be used for troubleshooting but also for optimizing the error handling itself.

[0062] Specifically, dynamically adjusting the classification and diagnostic rules for error types can include one or more of the following: changing the judgment threshold for error types, adding new error types, or optimizing local correction strategies. Specifically, changing the judgment threshold for error types can be achieved by adjusting the critical values ​​of the feature parameters used to distinguish different error types, thereby optimizing the error type judgment scheme. Adding new error types can include splitting an existing error type into multiple subtypes based on the clustering analysis results of error features, or defining new error types. Optimizing local correction strategies can be achieved by adjusting the parameters of the strategies based on the success rate and processing time of each strategy in historical processing records. As business changes and system upgrades occur, the characteristics of error types and locations may change. This solution can automatically detect and adjust these changes to keep error handling always in an optimal state.

[0063] Therefore, by adopting the solution of the first embodiment, the editable table document is converted into a cross-platform table document on the server side, which solves the problem of inconsistent printing formats caused by dependence on the user's local environment. By actively triggering formula calculations before conversion, it is ensured that the data in the printed document is the latest calculated result, avoiding the printing of incorrect data after conversion.

[0064] Figure 2 This is a schematic diagram of the structure of a print data processing device for an enterprise information management system according to a second embodiment of the present invention. Those skilled in the art will understand that the print data processing device for the enterprise information management system in this embodiment can be used to implement the method and technical solutions described in the above embodiments.

[0065] Specifically, refer to Figure 2 The printing data processing device 2 of the enterprise information management system in this embodiment may include: The data receiving unit 21 is used to receive print data and generate an editable table document; the formula calculation unit 22 is used to trigger the formula to complete the calculation in response to the formula contained in the editable table document; the rule determination unit 23 is used to obtain the format parameters of the editable table document and determine the conversion rules according to the format parameters; the document conversion unit 24 is used to convert the editable table document into a cross-platform format table document based on the conversion rules and push the cross-platform format table document to the user terminal of the enterprise information management system.

[0066] In specific implementation, the modules / units included in the various devices and products described in the above embodiments can be software modules / units, hardware modules / units, or a combination of both.

[0067] For example, for various devices and products applied to or integrated into a chip, each module / unit can be implemented using hardware methods such as circuits, or at least some modules / units can be implemented using software programs that run on a processor integrated within the chip, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits; for various devices and products applied to or integrated into a chip module, each module / unit can be implemented using hardware methods such as circuits, and different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or different components of the chip module, or at least some modules / units can be implemented using hardware methods such as circuits. The components can be implemented using software programs that run on the processor integrated within the chip module. The remaining (if any) modules / units can be implemented using hardware methods such as circuits. For various devices and products applied to or integrated into the terminal, each of its components / units can be implemented using hardware methods such as circuits. Different modules / units can be located in the same component (e.g., chip, circuit module, etc.) or in different components within the terminal. Alternatively, at least some modules / units can be implemented using software programs that run on the processor integrated within the terminal, while the remaining (if any) modules / units can be implemented using hardware methods such as circuits.

[0068] Furthermore, embodiments of the present invention also disclose a computer-readable storage medium, which is a non-volatile or non-transient storage medium, on which a computer program is stored, and the computer program is executed by a computer. Figure 1 The method and technical solution in the illustrated embodiment. Preferably, the storage medium may include ROM, RAM, disk, or optical disk, etc.

[0069] Furthermore, embodiments of the present invention also disclose a computer program product, including a computer program / instruction, wherein when the computer program / instruction is executed by a computer, the printing data processing method of any of the above-mentioned enterprise information management systems is executed.

[0070] While the present invention has been disclosed above, it is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of the invention; therefore, the scope of protection of the present invention should be determined by the scope defined in the claims.

Claims

1. A method for processing print data in an enterprise information management system, characterized in that, The method, applied to the server side of the enterprise information management system, includes: Receive print data and generate an editable table document; In response to the presence of a formula within the editable table document, the formula is triggered to complete the calculation. Obtain the format parameters of the editable table document, and determine the conversion rules based on the format parameters; Based on the conversion rules, the editable table document is converted into a cross-platform format table document, and the cross-platform format table document is pushed to the user terminal of the enterprise information management system.

2. The printing data processing method of the enterprise information management system as described in claim 1, characterized in that, The format parameters of the editable table document include the number of rows and columns filled by the printed data. Before converting the editable table document into a cross-platform format table document, the method further includes: generating a set of printable cells based on the number of rows and columns filled by the printed data.

3. The printing data processing method of the enterprise information management system as described in claim 2, characterized in that, The format parameters of the editable table document also include the number of horizontal page breaks, the height of each row, and the width of each column. The conversion rules include: page break splitting rules and / or paper adaptation rules. The page break splitting rules are used to split the set of printed cells according to the number of horizontal page breaks, and the paper adaptation rules are used to determine whether it is necessary to enlarge the set of printed cells.

4. The printing data processing method of the enterprise information management system as described in claim 3, characterized in that, Converting the editable table document into a cross-platform table document based on the page break splitting rules includes: Determine whether the number of horizontal page breaks is greater than or equal to 1; If the result is yes, then get the line number of each horizontal page break; Create N-1 split tables and end page tables, and arrange the N-1 split tables and end page tables sequentially on different print pages, where N is the number of horizontal page breaks; The set of printed cells before the first horizontal page break is retained as the first page table. The set of printed cells after the Nth horizontal page break is copied to the last page table. The set of printed cells between the nth and (n+1)th horizontal page breaks is copied to the nth split table. The cross-platform format table document includes the first page table, N-1 split tables, and the last page table, where n is a positive integer from 1 to N-1.

5. The printing data processing method of the enterprise information management system as described in claim 3, characterized in that, Converting the editable table document into a cross-platform table document based on paper adaptation rules includes: Calculate the total row height and total column width based on the height of each row and the width of each column. The total row height is equal to the number of rows in the printed cell set. The height of each row, and the total column width, equal to the number of columns in the printed cell set. Column width; Obtain the height and width of the paper, calculate the height threshold and width threshold, where the height threshold = height. Height coefficient, width threshold = width Width coefficient, wherein both the height coefficient and the width coefficient are greater than 0 and less than 1; Compare the height threshold with the total row height, and the width threshold with the total column width, respectively, to determine whether the total row height is less than the height threshold and the total column width is less than the width threshold. If the judgment result is yes, then the enlarged set of printed cells is triggered, and the cross-platform format table document contains the enlarged set of printed cells.

6. The printing data processing method of the enterprise information management system as described in claim 5, characterized in that, The height coefficient and width coefficient are both greater than 0.35 and less than 0.

45.

7. The printing data processing method of the enterprise information management system as described in claim 3, characterized in that, Based on the conversion rules, converting the editable table document into a cross-platform table document includes: Based on the page break splitting rules, determine whether the set of printed cells needs to be split; If the judgment result is yes, the set of printed cells is split into multiple split sets of printed cells; Based on the paper adaptive rule, determine whether to perform magnification for each set of split print cells and determine the magnification ratio for each set of split print cells. If at least one split set of print cells needs to be enlarged, then an execution is triggered to enlarge each set of print cells that needs to be enlarged by the same proportion, wherein the same proportion is the smallest of the enlargement proportions of each set of print cells that needs to be enlarged.

8. The printing data processing method of the enterprise information management system as described in claim 1, characterized in that, The print data includes print settings information, which is used to configure the display parameters of the cross-platform format table document.

9. The printing data processing method of the enterprise information management system as described in claim 8, characterized in that, The print settings information includes one or more of the following: print orientation, centering, margins, height orientation auto-adjustment, and width orientation compression.

10. The printing data processing method of the enterprise information management system as described in claim 1, characterized in that, The process of triggering the formula to complete the calculation includes the following steps: Determine the calculation options for the formula, including: disabling calculation chain parameters; Perform the calculation according to the calculation options and return the result.

11. A printing data processing device for an enterprise information management system, characterized in that, include: The data receiving unit is used to receive print data and generate an editable table document; The formula calculation unit is used to respond to formulas contained in an editable table document, triggering the formula to complete the calculation. The rule determination unit is used to obtain the format parameters of the editable table document and determine the conversion rules based on the format parameters; The document conversion unit is used to convert editable tabular documents into cross-platform format tabular documents based on conversion rules, and then push the cross-platform format tabular documents to the user end of the enterprise information management system.

12. A computer-readable storage medium, said computer-readable storage medium being a non-volatile storage medium or a non-transient storage medium, having stored thereon a computer program, characterized in that, The computer program is executed by a computer, and the printing data processing method of the enterprise information management system according to any one of claims 1 to 10 is executed.

13. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the computer, the printing data processing method of the enterprise information management system according to any one of claims 1 to 10 is executed.