CN117933200A - Document editing method and device, computer equipment and storage medium - Google Patents

Document editing method and device, computer equipment and storage medium Download PDF

Info

Publication number
CN117933200A
CN117933200A CN202410104343.6A CN202410104343A CN117933200A CN 117933200 A CN117933200 A CN 117933200A CN 202410104343 A CN202410104343 A CN 202410104343A CN 117933200 A CN117933200 A CN 117933200A
Authority
CN
China
Prior art keywords
bill
field
editing
target
original
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202410104343.6A
Other languages
Chinese (zh)
Inventor
张冠华
张应树
陈兵
江专生
游俊斌
陈晓云
姚卓宗
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kingdee Deeking Cloud Computing Co ltd
Original Assignee
Kingdee Deeking Cloud Computing Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Kingdee Deeking Cloud Computing Co ltd filed Critical Kingdee Deeking Cloud Computing Co ltd
Priority to CN202410104343.6A priority Critical patent/CN117933200A/en
Publication of CN117933200A publication Critical patent/CN117933200A/en
Pending legal-status Critical Current

Links

Landscapes

  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to a document editing method, a document editing device, computer equipment, a storage medium and a computer program product. The method comprises the following steps: based on the acquisition request, acquiring an original bill and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill; editing processing is carried out on the fields corresponding to the editing request in the target bill based on the editing request; and storing the edited field in a data table corresponding to the target bill. The method can dynamically, independently, adaptively and with low energy consumption edit the fields of the bill.

Description

Document editing method and device, computer equipment and storage medium
Technical Field
The present application relates to the field of data processing technology, and in particular, to a document editing method, apparatus, computer device, storage medium, and computer program product.
Background
Along with the development of internet technology, the operations of editing fields and field values are required to be performed according to actual business requirements and aiming at bill data in a database table.
In the current editing method of the fields and the field values, on one hand, the whole editing is directly carried out on the original database table, and the original database table is invasive, so that the corresponding field editing can not be independently and adaptively carried out according to the actual service requirements; on the other hand, the fields to be edited need to be repeatedly acquired in the original database table, thereby increasing the consumption of computer resources.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a document editing method, apparatus, computer device, computer-readable storage medium, and computer program product that can independently, adaptively, and with low power consumption edit fields in a document.
In a first aspect, the present application provides a document editing method, including:
Acquiring an original bill based on an acquisition request and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on fields corresponding to the editing request in the target document based on the editing request;
And storing the edited field in a data table corresponding to the target document.
In one embodiment, the editing processing, based on the editing request, in the target document for a field corresponding to the editing request includes: determining fields corresponding to the editing request in a bill header part and a bill body part of the bill, and editing the field values of the determined fields; the storing the edited field in a data table corresponding to the target document includes: and displaying the edited fields and the field values respectively corresponding to the bill header part and the bill body part, and storing the fields and the field values in a data table corresponding to the target bill.
In one embodiment, if the original document is identified to carry the edited field, before directly obtaining the target document corresponding to the original document, the method further includes: storing each bill subjected to cloning processing at the historical moment in a mutually independent cache space respectively; and if the bill corresponding to the acquisition request exists in the bills stored in the cache space, taking the bill corresponding to the acquisition request as a target bill.
In one embodiment, if not, performing clone processing on the original document to obtain a target document corresponding to the original document, including: converting the original bill into object type data; determining a mapping relation between the object type data and the relation type data based on the matched object type data and relation type data; and cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
In one embodiment, after the editing request is processed in the target document for the field corresponding to the editing request, the method further includes: updating the metadata version identifier corresponding to the target document based on the edited field and the field value; if the current metadata version identifier corresponding to the target bill is matched with the history metadata version identifier corresponding to the original bill, associating metadata corresponding to the history metadata version identifier with each field in the target bill; and if the current metadata version identifier corresponding to the target bill is not matched with the historical metadata version identifier corresponding to the original bill, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target bill.
In one embodiment, after the editing request is processed in the target document for the field corresponding to the editing request, the method further includes: acquiring a cache deleting instruction corresponding to the editing process based on the editing process; based on the cache deleting instruction, deleting a field and a field value which are stored in a cache space and correspond to the cache deleting instruction; and acquiring the stored fields and field values from a data table corresponding to the target bill, and storing the fields and the field values in a corresponding cache space again.
In a second aspect, the present application also provides a document editing apparatus, including:
The acquisition module is used for acquiring an original bill based on the acquisition request and identifying the original bill, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
the editing module is used for editing the fields corresponding to the editing request in the target document based on the editing request;
And the storage module is used for storing the edited field in a data table corresponding to the target bill.
In a third aspect, the present application also provides a computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
Acquiring an original bill based on an acquisition request and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on fields corresponding to the editing request in the target document based on the editing request;
And storing the edited field in a data table corresponding to the target document.
In a fourth aspect, the present application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of:
Acquiring an original bill based on an acquisition request and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on fields corresponding to the editing request in the target document based on the editing request;
And storing the edited field in a data table corresponding to the target document.
In a fifth aspect, the application also provides a computer program product comprising a computer program which, when executed by a processor, performs the steps of:
Acquiring an original bill based on an acquisition request and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on fields corresponding to the editing request in the target document based on the editing request;
And storing the edited field in a data table corresponding to the target document.
The bill editing method, the bill editing device, the computer equipment, the storage medium and the computer program product comprise the steps of firstly, if the obtained original bill carries the edited field, directly and efficiently obtaining a target bill which corresponds to the original bill and is independent of the original bill, and if not, obtaining the target bill through cloning; the obtained fields of the target bill are subjected to editing processing in a targeted manner based on the editing request, and the fields after editing processing are stored in an independent data table corresponding to the target bill; based on the method, the fields of the bill can be edited dynamically, independently, adaptively and with low power consumption on the premise of not affecting the content and the structure of the original data.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the related art, the drawings that are required to be used in the embodiments or the related technical descriptions will be briefly described, and it is apparent that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to the drawings without inventive effort for those skilled in the art.
FIG. 1 is an application environment diagram of a document editing method in one embodiment;
FIG. 2 is a flow diagram of a document editing method in one embodiment;
FIG. 3 is a schematic diagram of a user interface applied to a document editing method in one embodiment;
FIG. 4 is a schematic diagram of a user interface for use with a document editing method in yet another embodiment;
FIG. 5 is a schematic diagram of a user interface for use with a document editing method in yet another embodiment;
FIG. 6 is a schematic diagram of a user interface for use with a document editing method in yet another embodiment;
FIG. 7 is a schematic diagram of a user interface for use with a document editing method in yet another embodiment;
FIG. 8 is a diagram of storing metadata in one embodiment;
FIG. 9 is a block diagram showing a structure of a document editing apparatus in one embodiment;
FIG. 10 is an internal block diagram of a computer device in one embodiment;
fig. 11 is an internal structural view of a computer device in yet another embodiment.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The bill editing method provided by the embodiment of the application can be applied to an application environment shown in figure 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104 or may be located on a cloud or other network server.
In one embodiment, the terminal 102 obtains the original document from the server 104 based on the obtaining request and identifies the original document, if the original document is identified to carry the edited field, the terminal directly obtains the target document corresponding to the original document, if not, the terminal 102 clones the original document to obtain the target document corresponding to the original document; the terminal 102 performs editing processing on a field corresponding to the editing request in the target document based on the editing request; the terminal 102 transmits the edited field to the server 104 so that the server 104 stores the edited field and the field value in a data table corresponding to the target document.
In yet another embodiment, the server 104 obtains the original document and identifies the original document based on the obtaining request from the terminal 102, if the original document is identified to carry the edited field, the server 104 directly obtains the target document corresponding to the original document, and if not, the server 104 clones the original document to obtain the target document corresponding to the original document; the server 104 performs editing processing for a field corresponding to the editing request in the target document based on the editing request from the terminal 102; the server 104 stores the edited field in a data table corresponding to the target document.
The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices, and portable wearable devices, where the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart vehicle devices, and the like. The portable wearable device may be a smart watch, smart bracelet, headset, or the like. The server 104 may be implemented as a stand-alone server or as a server cluster of multiple servers.
In an exemplary embodiment, as shown in fig. 2, a document editing method is provided, and an example of application of the method to the terminal in fig. 1 is described, including the following steps S202 to S206. Wherein:
Step S202, acquiring an original bill and identifying the original bill based on the acquisition request, and directly acquiring a target bill corresponding to the original bill if the original bill is identified to carry the edited field; if not, carrying out cloning processing on the original bill to obtain a target bill corresponding to the original bill. Wherein the acquisition request is a request for acquisition of the specified information; the acquisition request may represent input received by the terminal from a user interface.
The cloning process is to create a corresponding copy according to the original information, wherein the copy has the same data as the original information.
Wherein, the receipt is a file containing text information, which can be used for recording and delivering transactions, exchanging information or as a proof of business activity; the documents may include invoices, receipts, purchase orders, delivery notes, and reimbursement notes.
Wherein the field represents a data structure for storing a single data element; fields in the document are used to represent various portions or attributes of the document to provide detailed transaction information. Further, the field includes a field body and a field value corresponding to the field body, that is, the field body in the field represents a data type of the data, and the field value in the field represents a specific data value corresponding to the field body; for example, when the field body is expressed as "date", the field value may be expressed as "1 month 1 day".
Still further, a field may be represented as a data structure including a field body and a field value, or may be represented as only a field body; the field according to the present embodiment may be represented as a data structure including a field body and a field value.
The original receipt carries the edited field, which means that the field of the receipt matched with the original receipt is edited at the historical moment, and after the field editing is completed, the receipt matched with the original receipt synchronizes the edited field content into the original receipt, so that the original receipt carries the corresponding edited field. The method includes the steps that an original bill corresponding to an acquisition request is acquired based on the acquisition request, fields in the acquired original bill are identified, if the original bill carries the fields after editing, the original bill indicates that a target bill matched with the original bill exists, and the target bill can be directly acquired; if not, cloning the original bill to obtain a target bill; wherein the target document contains the same data as the original document.
Step S204, based on the editing request, editing processing is performed on the fields corresponding to the editing request in the target document.
Wherein the editing request is a request for editing for the specified information; the edit request may represent input received by the terminal from the user interface.
Illustratively, based on the editing request, in the target document, editing processing is performed for the field body and the field value corresponding to the editing request, and the editing processing may include processing for adding, deleting, and changing the field body or the field value.
Step S206, the edited field is stored in a data table corresponding to the target document.
Wherein, the data table is a structure for organizing and storing data in a table form.
Illustratively, a data table corresponding to the target bill is obtained, and the edited field body and the field value are stored in the data table; optionally, the field body is stored in a header portion of the data table, the field values are stored in a body portion of the data table, and each field value is stored in a column in which the corresponding field body is located.
Optionally, splitting processing can be performed on the data table corresponding to the original bill to obtain a target data table corresponding to the target bill; the target data table can comprise a field body and a field value corresponding to an original bill in an initial state, the field body and the field value which are matched with the editing processing in the target data table are correspondingly changed or reserved based on the field body and the field value after the editing processing corresponding to the target bill, and the unmatched field body and the unmatched field value are deleted, so that the ductility and the applicability of the target data table are improved.
In the bill editing method, firstly, if the obtained original bill carries the edited field, directly and efficiently obtaining a target bill which corresponds to the original bill and is independent of the original bill, and if not, obtaining the target bill through cloning; the obtained fields of the target bill are subjected to editing processing in a targeted manner based on the editing request, and the fields after editing processing are stored in an independent data table corresponding to the target bill; based on the method, the fields of the bill can be edited dynamically, independently, adaptively and with low power consumption on the premise of not affecting the content and the structure of the original data.
In an exemplary embodiment, based on the editing request, editing processing is performed in the target document for a field corresponding to the editing request, including step S302; the edited field is stored in a data table corresponding to the target document, including step S304. Wherein:
In step S302, a field corresponding to the editing request is determined in the document header portion and the document body portion of the document, and editing processing is performed with respect to the field value of the determined field.
In this embodiment and any one of the following embodiments, the field is represented as a field body in a data structure including a field body and a field value, and the field value is represented as a field value in a data structure including a field body and a field value.
The bill header part is the top part in the bill, namely, represents an area for describing basic information of the bill, such as the basic information of a title, a date, a bill number and the like; the document body part is a main body part in the document, namely, represents a region described for detailed information of the document, such as detailed information of item quantity, item unit price, item specification, item total price and the like.
Illustratively, based on the editing request, a field corresponding to the editing request is determined in a document header portion and/or a document body portion of the document, and editing processing corresponding to the editing request is performed for a field value of the determined field.
And step S304, displaying the edited fields and the field values corresponding to the bill head part and the bill body part respectively, and storing the fields and the field values in a data table corresponding to the target bill.
Illustratively, displaying the edited fields and the field values in a user interface and storing the fields and the field values in a data table corresponding to the target bill; optionally, the edited field and the field value may be displayed separately up and down according to the document head part and the document body part, or stored in a data table separately up and down.
In this embodiment, corresponding editing processing, display processing and storage processing are performed on fields and field values of a bill header portion and a bill body portion of a bill, so that complete and comprehensive processing on the bill is realized.
In an exemplary embodiment, if the original document is identified to carry the edited field, the method further includes steps S402 to S404 before directly acquiring the target document corresponding to the original document. Wherein:
Step S402, storing each bill obtained through cloning processing at the historical moment in a mutually independent cache space.
In step S404, if the document corresponding to the acquisition request exists in the documents stored in the buffer space, the document corresponding to the acquisition request is used as the target document.
The buffer space is a memory area in the computer equipment for storing temporary data to increase the data access speed.
Illustratively, documents obtained by cloning different original documents at corresponding historical moments are respectively stored in mutually independent cache spaces; based on the acquisition request, if a bill corresponding to the acquisition request is matched with the bill stored in the cache space, the matched bill is taken as a target bill; if the bill corresponding to the acquisition request is not matched with the bill stored in the cache space, acquiring the original bill based on the acquisition request and performing cloning processing to obtain the corresponding target bill.
Optionally, taking the Ehcche cache as an intermediate cache, wherein the Ehcche cache is a Java cache framework; corresponding Ehcache caches are determined according to different account covers, so that each account cover is ensured to have independent cache space, and therefore the account cover level isolation effect is achieved. Broadcast updating of Ehcache cache can be realized through a message queue, namely, a subscriber of the message is arranged on each node and used for monitoring the message in the message queue, and when the subscriber receives the updated message, the node executes corresponding cache updating operation.
In this embodiment, documents corresponding to the acquisition request may be directly matched in the cached documents, so as to reduce clone processing for the documents, and further save computer resources.
In an exemplary embodiment, if not, cloning is performed on the original document to obtain a target document corresponding to the original document, including steps S502 to S506. Wherein:
step S502, converting the original bill into object type data.
Wherein object-type data is a data structure organized and represented in the form of objects.
Illustratively, an object model is obtained, the object model being an object-based data representation; based on the object model, converting the original document into an object in the object model, namely converting the original document into object type data, wherein the object in the object model refers to an instance of a class, namely the object type data represents the object obtained by class instantiation in object-oriented programming.
Step S504, based on the matched object type data and relation type data, determining the mapping relation between the object type data and the relation type data.
Wherein the relational data is a data structure organized and represented in tabular form.
Illustratively, a relational model database is obtained, wherein the relational model database is a table-based data representation mode, and different fields and field values are prestored in the relational model database; and determining the mapping relation between the attributes of the object and the fields in the relational model database based on the matched attributes of the object and the fields in the relational model database, so as to obtain the mapping relation between the object type data and the relational type data, wherein the attributes of the object are characteristic, state or descriptive information of the object.
And step S506, cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
And cloning the object type data of the determined mapping relationship to obtain a corresponding target bill, wherein the target bill synchronously reflects the mapping relationship between the object type data and the relational data.
Alternatively, mapping the objects in the Object model into a relational model database structure based on SQL (Structured Query Language ) may be implemented based on ORM (Object-Relational Mapping) technology, so as to establish a mapping relationship between the Object-type data and the relational data, so that the Object-type data and the relational data are mutually converted based on the mapping relationship.
In this embodiment, the original document is converted into the object in the object model, and then the mapping relationship between the attribute of the object and the fields in the relational model database is determined, so as to realize efficient conversion between the object data and the relational data.
In an exemplary embodiment, based on the editing request, after editing processing is performed on the field corresponding to the editing request in the target document based on the editing request, the method further includes steps S602 to S606. Wherein:
Step S602, based on the edited field and the field value, updating the metadata version identification corresponding to the target document.
Wherein, the metadata is data for explaining, explaining and managing the data by the pointer; metadata may represent data describing attributes for fields and field values, such as, for example, location, style, name, identification, font size, page location, etc. of fields. The metadata version identification is an identifier for identifying and managing version information of metadata.
Illustratively, updating the metadata version identifier corresponding to the target document based on the edited field and the field value; optionally, if the fields or field values before and after the editing process have no difference, it may be understood that the metadata version identifier is updated to the current metadata version identifier corresponding to the target document.
Optionally, updating the metadata version identification correspondingly for each edit of a field or field value; or after editing all the fields and field values corresponding to the editing request, correspondingly updating the metadata version identification.
In step S604, if the current metadata version identifier corresponding to the target document matches the historical metadata version identifier corresponding to the original document, the metadata corresponding to the historical metadata version identifier is associated with each field in the target document.
Step S606, if the current metadata version identifier corresponding to the target document is not matched with the history metadata version identifier corresponding to the original document, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target document.
For example, if the current metadata version identifier corresponding to the target document is matched with the historical metadata version identifier corresponding to the original document, the field or the field value of the target document is not different from that of the original document, and the metadata corresponding to the historical metadata version identifier can be directly associated with each field in the target document; if the current metadata version identifier corresponding to the target document is not matched with the historical metadata version identifier corresponding to the original document, the method indicates that the field or the field value of the target document is changed compared with that of the original document, metadata corresponding to the current metadata version identifier is obtained and is associated with each field in the target document.
Optionally, the metadata version identifier and the metadata may be cached by a Redis, where the Redis is an open-source memory database and cache system; the corresponding metadata version identifier and metadata can be directly selected from the cache space corresponding to the Redis without re-reading.
In this embodiment, a matching relationship between a current metadata version identifier corresponding to a target document and a historical metadata version identifier corresponding to an original document is determined, so that a metadata sharing relationship is established, and metadata corresponding to the historical metadata version identifier is directly associated with each field in the target document, so as to avoid re-reading the metadata, and further save computer resources.
Furthermore, the data and the metadata are independently processed and stored, so that the coupling degree between the data and the metadata is reduced, and on one hand, under the scene of delivering without metadata, a user or a system can directly use the data without knowing the structure of the metadata in detail; on the other hand, metadata can be managed independently for metadata to better control and maintain the metadata of the data.
In an exemplary embodiment, after performing the editing process for the field corresponding to the editing request in the target document based on the editing request, the method further includes steps S702 to S706. Wherein:
step S702, based on the editing process, acquires a deletion cache instruction corresponding to the editing process.
In step S704, based on the delete cache instruction, the field and the field value corresponding to the delete cache instruction stored in the cache space are deleted.
The deletion cache instruction is used for designating cache data to be deleted.
Illustratively, based on the edited field and the field value, acquiring a delete cache instruction corresponding to the edited field and the field value; based on the cache deleting instruction, deleting the field and the field value corresponding to the cache deleting instruction stored in the cache space, namely synchronizing the editing operation for the target document into the document corresponding to the target document in the cache space, so as to delete the field and the field value corresponding to the editing operation in the cache space.
Step S706, the stored fields and field values are obtained from the data table corresponding to the target document, and are restored in the corresponding cache space.
The method includes the steps of deleting a field and a field value corresponding to an editing operation in a cache space, acquiring a stored field and a field value corresponding to the editing operation in a data table corresponding to a target document, and storing the field and the field value in the corresponding cache space again, namely, acquiring a new field and a new field value in the data table corresponding to the target document and storing the new field and the field value in the cache space again after deleting the original field and the original field value in the cache space.
Optionally, broadcast updating of the cache data may be implemented through a message queue, that is, a subscriber of the message is set on each node, for listening to the message in the message queue, and when the subscriber receives the update message, the node performs a corresponding cache updating operation.
For example, when editing is performed on one field or field value of the target document, a node corresponding to the current computer equipment generates a deletion cache instruction corresponding to the edited field or field value, and the deletion cache instruction is broadcast and sent to all nodes of the same group, wherein the nodes of the same group represent nodes which cooperatively complete the same work task; after receiving the delete cache command, all nodes of the same packet delete the field or field value corresponding to the delete cache command stored in the cache space. When the bill corresponding to the target bill is read in the cache space again, the node corresponding to the current computer equipment accesses the data table corresponding to the target bill, and the stored field and the field value are acquired in the data table to be stored in the corresponding cache space again, so that the cache on all the nodes of the same group is effectively updated, further, different nodes working cooperatively share the same updating information, and the cache consistency is maintained.
In an exemplary embodiment, the method further includes steps S802 to S806. Wherein:
Step S802, displaying different documents to which the edited field values belong row by row respectively, wherein the field values corresponding to the different documents are displayed row by row according to the corresponding fields.
The user interface is provided with a data table, wherein the data table comprises a first row of fields, different rows outside the first row are respectively edited field values corresponding to different documents, and the field value corresponding to any document is displayed column by column according to the corresponding field located in the first row.
Step S804, based on the sorting request, the different documents are arranged according to the sequence corresponding to the sorting request.
Illustratively, based on the sorting request input by the user interface, the different documents are arranged according to the sequence corresponding to the sorting request, namely, the sorting is performed for the row where the documents are located; optionally, sorting of different documents may be implemented according to rules such as numerical order, time order, etc. of field values.
Step S806, based on the filtering request, the documents meeting the filtering conditions corresponding to the filtering request are reserved.
Based on the filtering request input by the user interface, reserving the documents meeting the filtering conditions corresponding to the filtering request, and filtering the documents not meeting the filtering conditions; optionally, filtering for different documents can be implemented according to rules such as numerical ranges, time ranges of field values and the like.
In this embodiment, the fields and the field values after editing processing corresponding to different documents are visually displayed, and based on the visual display, different documents are efficiently and accurately sorted or filtered.
In one exemplary embodiment, as shown in FIG. 3, the editing of fields and field values may be performed for the header (i.e., header) and body (i.e., body) of the document; wherein the editable fields include text, numerical values, formulas, dates, auxiliary materials, basic materials, and attributes of the taken-out basic materials; the text field is used for representing text information, the numerical value field is used for representing numerical value information, the formula field is used for calculating numerical value information corresponding to the numerical value field according to a formula, and the date field is used for representing date information; the basic data field is used for storing key reference data, such as key information of customer basic information, product basic information and the like; the auxiliary information field is used for storing additional information related to the key data, such as special requirements, preferences of customers and the like, and is used for describing and remarking auxiliary information related to the key information; the attribute field of the basic data is brought out for associating the basic data to acquire the corresponding attribute information, for example, the "commodity category" field corresponding to the basic data field is automatically acquired according to the associated "commodity" basic data field.
As shown in fig. 3, in the user interface, documents corresponding to different scenes may be selected for editing, for example, a sales management scene, a purchase management scene, an inventory management scene, a production management scene, a commission management scene, a payable on demand scene, and a cashier management scene; in the sales management scene, different types of documents such as sales quotation, sales order, sales delivery, sales return and the like are included.
The editable field names corresponding to the table heads are arranged on the upper side of the user interface for explanation, the editable field names corresponding to the table bodies are arranged on the lower side of the user interface for explanation, and in addition, information such as field types, field values, whether modification is allowed after checking the bill, whether the bill must be input, and the applicable bill is also explained; and controls of 'newly added header field' and 'newly added body field' are arranged for inputting an editing request for editing the fields and field values of the header and the body.
As shown in fig. 4, when editing the formula field of the document, the field name is designated as a formula, and the field type is designated as a numerical value, the formula field can be defined for the decimal number and the field value in a customized manner, for example, the decimal number is defined as 2, and the field value is defined as the increase of 100 of the available credit in the document head; it can also define whether the modification is allowed or not after the bill is checked and whether the input is necessary or not; and the applicable bill can be defined, and if the edited field is applicable to various bills, the system can automatically transfer the content of the field appointed in the upstream bill to the corresponding field in the downstream bill when the downstream bill is created.
As shown in fig. 5, when editing the basic data field of the document, the value source of the corresponding field value may represent the source of the commodity, department, warehouse space, settlement mode, payment type, supplier, etc.
As shown in fig. 6, after the editing process for the fields and the field values of the document is completed, the fields and the field values (i.e., the basic information) corresponding to the document header are displayed on the upper side, wherein the fields and the field values that are original in the document header are displayed, for example, "document number": "XSDD-20230906-00005", "document date": "2023-09-06", "customer": information such as "customer 001"; the edited field and the field value in the bill header are displayed, for example, a formula: "100.00", "auxiliary data": "telemarketing", "basic data": information such as "order bulk".
As shown in fig. 6, the fields and the field values corresponding to the bill body are displayed in a table form at the lower side, wherein the original fields and the field values in the bill body are displayed, for example, "price tax summation": "1000.00"; the edited field and the field value in the bill body are displayed, for example, "numerical value": "345.00", "date": "2023-10-01".
As shown in fig. 7, after the editing processing of the fields and the field values of the document is completed, the fields and the field values corresponding to the document are displayed in a table form, wherein the first action is a field, and the second action is a field value of the field corresponding to the document; wherein, the original fields and field values in the bill are displayed, for example, "basic data": "general commodity 001", "bring out basic data attribute": "commodity category 001", "price tax totalization": "1000.00"; the edited field and the field value in the bill are displayed, for example, a formula: "100.00", "auxiliary data": "telemarketing", "basic data": "order bulk guest".
As shown in fig. 7, a control for performing filtering processing is further disposed on the upper side of the user interface, that is, according to the designated filtering conditions, documents meeting the filtering conditions are reserved, and documents not meeting the filtering conditions are hidden or deleted; the upper side of the user interface is also provided with a control for deleting, starting and closing the bill, and a check box corresponding to the bill is arranged at the same time, so that the bill can be intuitively and rapidly selected and corresponding operation can be carried out.
As shown in fig. 8, in metadata corresponding to a metadata version identifier, metadata is stored in an area to which the associated field belongs in the document, that is, metadata of a field corresponding to a document header is stored in a main table, and metadata of a field corresponding to a document body is stored in an entry table; for example, if the "document number" is a field corresponding to the document header, the metadata of the "field name" corresponding to the document header is stored in the main table; the commodity is a field corresponding to the bill body, and the metadata of the corresponding field name is stored in an entry table.
It should be understood that, although the steps in the flowcharts related to the embodiments described above are sequentially shown as indicated by arrows, these steps are not necessarily sequentially performed in the order indicated by the arrows. The steps are not strictly limited to the order of execution unless explicitly recited herein, and the steps may be executed in other orders. Moreover, at least some of the steps in the flowcharts described in the above embodiments may include a plurality of steps or a plurality of stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of the steps or stages is not necessarily performed sequentially, but may be performed alternately or alternately with at least some of the other steps or stages.
Based on the same inventive concept, the embodiment of the application also provides a bill editing device for realizing the bill editing method. The implementation of the solution provided by the device is similar to the implementation described in the above method, so the specific limitation in the embodiments of the document editing device or devices provided below may refer to the limitation of the document editing method hereinabove, and will not be repeated here.
In an exemplary embodiment, as shown in fig. 9, there is provided a document editing apparatus including: an acquisition module 902, an editing module 904, and a storage module 906, wherein:
the acquiring module 902 is configured to acquire an original document and identify the original document based on the acquiring request, and if the original document is identified to carry the edited field, directly acquire a target document corresponding to the original document; if not, carrying out cloning processing on the original bill to obtain a target bill corresponding to the original bill.
And the editing module 904 is used for editing the field corresponding to the editing request in the target document based on the editing request.
And the storage module 906 is used for storing the fields after editing processing in a data table corresponding to the target document.
In one exemplary embodiment, the editing module 904 is further configured to:
Determining a field corresponding to the editing request in a bill header part and a bill body part of the bill, and editing the field value of the determined field; the storage module 906 is further configured to: and displaying the edited fields and the field values corresponding to the bill header part and the bill body part respectively, and storing the fields and the field values in a data table corresponding to the target bill.
In one exemplary embodiment, the obtaining module 902 is further configured to: storing each bill subjected to cloning processing at the historical moment in a mutually independent cache space respectively; and if the bill corresponding to the acquisition request exists in the bills stored in the cache space, taking the bill corresponding to the acquisition request as a target bill.
In one exemplary embodiment, the obtaining module 902 is further configured to: converting the original bill into object type data; determining a mapping relationship between the object type data and the relationship data based on the matched object type data and relationship data; and cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
In one exemplary embodiment, the editing module 904 is further configured to: updating the metadata version identifier corresponding to the target bill based on the edited field and the field value; if the current metadata version identifier corresponding to the target bill is matched with the historical metadata version identifier corresponding to the original bill, associating metadata corresponding to the historical metadata version identifier with each field in the target bill; and if the current metadata version identifier corresponding to the target bill is not matched with the historical metadata version identifier corresponding to the original bill, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target bill.
In one exemplary embodiment, the editing module 904 is further configured to: acquiring a cache deleting instruction corresponding to the editing process based on the editing process; based on the cache deleting instruction, deleting the field and the field value corresponding to the cache deleting instruction stored in the cache space; and acquiring the stored fields and field values from the data table corresponding to the target bill, and storing the fields and the field values in the corresponding cache space again.
The modules in the document editing apparatus may be implemented in whole or in part by software, hardware, or a combination thereof. The above modules may be embedded in hardware or may be independent of a processor in the computer device, or may be stored in software in a memory in the computer device, so that the processor may call and execute operations corresponding to the above modules.
In one exemplary embodiment, a computer device is provided, which may be a server, and the internal structure thereof may be as shown in fig. 10. The computer device includes a processor, a memory, an Input/Output interface (I/O) and a communication interface. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface is connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer device is for storing data associated with document editing. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for communicating with an external terminal through a network connection. The computer program when executed by a processor implements a document editing method.
In an exemplary embodiment, a computer device, which may be a terminal, is provided, and an internal structure thereof may be as shown in fig. 11. The computer device includes a processor, a memory, an input/output interface, a communication interface, a display unit, and an input means. The processor, the memory and the input/output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input/output interface. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The input/output interface of the computer device is used to exchange information between the processor and the external device. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless mode can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program when executed by a processor implements a document editing method. The display unit of the computer device is used for forming a visual picture, and can be a display screen, a projection device or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, can also be a key, a track ball or a touch pad arranged on the shell of the computer equipment, and can also be an external keyboard, a touch pad or a mouse and the like.
It will be appreciated by those skilled in the art that the structures shown in fig. 10 and 11 are merely block diagrams of portions of structures associated with aspects of the application and are not intended to limit the computer device to which aspects of the application may be applied, and that a particular computer device may include more or fewer components than those shown, or may combine certain components, or may have a different arrangement of components.
In one exemplary embodiment, a computer device is provided comprising a memory and a processor, the memory having stored therein a computer program, the processor when executing the computer program performing the steps of:
Based on the acquisition request, acquiring an original bill and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on the fields corresponding to the editing request in the target bill based on the editing request;
and storing the edited field in a data table corresponding to the target bill.
In one embodiment, the processor when executing the computer program further performs the steps of: determining a field corresponding to the editing request in a bill header part and a bill body part of the bill, and editing the field value of the determined field; and displaying the edited fields and the field values corresponding to the bill header part and the bill body part respectively, and storing the fields and the field values in a data table corresponding to the target bill.
In one embodiment, the processor when executing the computer program further performs the steps of: storing each bill subjected to cloning processing at the historical moment in a mutually independent cache space respectively; and if the bill corresponding to the acquisition request exists in the bills stored in the cache space, taking the bill corresponding to the acquisition request as a target bill.
In one embodiment, the processor when executing the computer program further performs the steps of: converting the original bill into object type data; determining a mapping relationship between the object type data and the relationship data based on the matched object type data and relationship data; and cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
In one embodiment, the processor when executing the computer program further performs the steps of: updating the metadata version identifier corresponding to the target bill based on the edited field and the field value; if the current metadata version identifier corresponding to the target bill is matched with the historical metadata version identifier corresponding to the original bill, associating metadata corresponding to the historical metadata version identifier with each field in the target bill; and if the current metadata version identifier corresponding to the target bill is not matched with the historical metadata version identifier corresponding to the original bill, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target bill.
In one embodiment, the processor when executing the computer program further performs the steps of: acquiring a cache deleting instruction corresponding to the editing process based on the editing process; based on the cache deleting instruction, deleting the field and the field value corresponding to the cache deleting instruction stored in the cache space; and acquiring the stored fields and field values from the data table corresponding to the target bill, and storing the fields and the field values in the corresponding cache space again.
In one embodiment, a computer readable storage medium is provided having a computer program stored thereon, which when executed by a processor, performs the steps of:
Based on the acquisition request, acquiring an original bill and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on the fields corresponding to the editing request in the target bill based on the editing request;
and storing the edited field in a data table corresponding to the target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: determining a field corresponding to the editing request in a bill header part and a bill body part of the bill, and editing the field value of the determined field; and displaying the edited fields and the field values corresponding to the bill header part and the bill body part respectively, and storing the fields and the field values in a data table corresponding to the target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of:
Storing each bill subjected to cloning processing at the historical moment in a mutually independent cache space respectively; and if the bill corresponding to the acquisition request exists in the bills stored in the cache space, taking the bill corresponding to the acquisition request as a target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: converting the original bill into object type data; determining a mapping relationship between the object type data and the relationship data based on the matched object type data and relationship data; and cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: updating the metadata version identifier corresponding to the target bill based on the edited field and the field value; if the current metadata version identifier corresponding to the target bill is matched with the historical metadata version identifier corresponding to the original bill, associating metadata corresponding to the historical metadata version identifier with each field in the target bill; and if the current metadata version identifier corresponding to the target bill is not matched with the historical metadata version identifier corresponding to the original bill, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a cache deleting instruction corresponding to the editing process based on the editing process; based on the cache deleting instruction, deleting the field and the field value corresponding to the cache deleting instruction stored in the cache space; and acquiring the stored fields and field values from the data table corresponding to the target bill, and storing the fields and the field values in the corresponding cache space again.
In one embodiment, a computer program product is provided comprising a computer program which, when executed by a processor, performs the steps of:
Based on the acquisition request, acquiring an original bill and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on the fields corresponding to the editing request in the target bill based on the editing request;
and storing the edited field in a data table corresponding to the target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: determining a field corresponding to the editing request in a bill header part and a bill body part of the bill, and editing the field value of the determined field; and displaying the edited fields and the field values corresponding to the bill header part and the bill body part respectively, and storing the fields and the field values in a data table corresponding to the target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: storing each bill subjected to cloning processing at the historical moment in a mutually independent cache space respectively; and if the bill corresponding to the acquisition request exists in the bills stored in the cache space, taking the bill corresponding to the acquisition request as a target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: converting the original bill into object type data; determining a mapping relationship between the object type data and the relationship data based on the matched object type data and relationship data; and cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: updating the metadata version identifier corresponding to the target bill based on the edited field and the field value; if the current metadata version identifier corresponding to the target bill is matched with the historical metadata version identifier corresponding to the original bill, associating metadata corresponding to the historical metadata version identifier with each field in the target bill; and if the current metadata version identifier corresponding to the target bill is not matched with the historical metadata version identifier corresponding to the original bill, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target bill.
In one embodiment, the computer program when executed by the processor further performs the steps of: acquiring a cache deleting instruction corresponding to the editing process based on the editing process; based on the cache deleting instruction, deleting the field and the field value corresponding to the cache deleting instruction stored in the cache space; and acquiring the stored fields and field values from the data table corresponding to the target bill, and storing the fields and the field values in the corresponding cache space again.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, database, or other medium used in embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high density embedded nonvolatile Memory, resistive random access Memory (ReRAM), magneto-resistive random access Memory (Magnetoresistive Random Access Memory, MRAM), ferroelectric Memory (Ferroelectric Random Access Memory, FRAM), phase change Memory (PHASE CHANGE Memory, PCM), graphene Memory, and the like. Volatile memory can include random access memory (Random Access Memory, RAM) or external cache memory, and the like. By way of illustration, and not limitation, RAM can be in various forms such as static random access memory (Static Random Access Memory, SRAM) or dynamic random access memory (Dynamic Random Access Memory, DRAM), etc. The databases referred to in the embodiments provided herein may include at least one of a relational database and a non-relational database. The non-relational database may include, but is not limited to, a blockchain-based distributed database, and the like. The processor referred to in the embodiments provided in the present application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, or the like, but is not limited thereto.
The technical features of the above embodiments may be arbitrarily combined, and all possible combinations of the technical features in the above embodiments are not described for brevity of description, however, as long as there is no contradiction between the combinations of the technical features, they should be considered as the scope of the description.
The foregoing examples illustrate only a few embodiments of the application and are described in detail herein without thereby limiting the scope of the application. It should be noted that it will be apparent to those skilled in the art that several variations and modifications can be made without departing from the spirit of the application, which are all within the scope of the application. Accordingly, the scope of the application should be assessed as that of the appended claims.

Claims (10)

1. A document editing method, the method comprising:
Acquiring an original bill based on an acquisition request and identifying, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
Editing processing is carried out on fields corresponding to the editing request in the target document based on the editing request;
And storing the edited field in a data table corresponding to the target document.
2. The method according to claim 1, wherein the editing process for a field corresponding to the editing request in the target document based on the editing request includes:
determining fields corresponding to the editing request in a bill header part and a bill body part of the bill, and editing the field values of the determined fields;
the storing the edited field in a data table corresponding to the target document includes:
and displaying the edited fields and the field values respectively corresponding to the bill header part and the bill body part, and storing the fields and the field values in a data table corresponding to the target bill.
3. The method of claim 1, wherein if the original document is identified as carrying the edited field, the method further comprises, before directly acquiring the target document corresponding to the original document:
storing each bill subjected to cloning processing at the historical moment in a mutually independent cache space respectively;
And if the bill corresponding to the acquisition request exists in the bills stored in the cache space, taking the bill corresponding to the acquisition request as a target bill.
4. The method of claim 1, wherein if not, performing clone processing on the original document to obtain a target document corresponding to the original document, including:
converting the original bill into object type data;
Determining a mapping relation between the object type data and the relation type data based on the matched object type data and relation type data;
And cloning the object type data of the determined mapping relation to obtain the corresponding target bill.
5. The method according to claim 1, wherein the method further comprises, after performing editing processing for a field corresponding to the editing request in the target document based on the editing request:
Updating the metadata version identifier corresponding to the target document based on the edited field and the field value;
if the current metadata version identifier corresponding to the target bill is matched with the history metadata version identifier corresponding to the original bill, associating metadata corresponding to the history metadata version identifier with each field in the target bill;
And if the current metadata version identifier corresponding to the target bill is not matched with the historical metadata version identifier corresponding to the original bill, acquiring metadata corresponding to the current metadata version identifier and associating the metadata with each field in the target bill.
6. The method according to claim 1, wherein the method further comprises, after performing editing processing for a field corresponding to the editing request in the target document based on the editing request:
acquiring a cache deleting instruction corresponding to the editing process based on the editing process;
based on the cache deleting instruction, deleting a field and a field value which are stored in a cache space and correspond to the cache deleting instruction;
And acquiring the stored fields and field values from a data table corresponding to the target bill, and storing the fields and the field values in a corresponding cache space again.
7. A document editing apparatus, the apparatus comprising:
The acquisition module is used for acquiring an original bill based on the acquisition request and identifying the original bill, and if the original bill is identified to carry the edited field, directly acquiring a target bill corresponding to the original bill; if not, carrying out clone processing on the original bill to obtain a target bill corresponding to the original bill;
the editing module is used for editing the fields corresponding to the editing request in the target document based on the editing request;
And the storage module is used for storing the edited field in a data table corresponding to the target bill.
8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 6 when the computer program is executed.
9. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
10. A computer program product comprising a computer program, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 6.
CN202410104343.6A 2024-01-24 2024-01-24 Document editing method and device, computer equipment and storage medium Pending CN117933200A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202410104343.6A CN117933200A (en) 2024-01-24 2024-01-24 Document editing method and device, computer equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202410104343.6A CN117933200A (en) 2024-01-24 2024-01-24 Document editing method and device, computer equipment and storage medium

Publications (1)

Publication Number Publication Date
CN117933200A true CN117933200A (en) 2024-04-26

Family

ID=90751890

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202410104343.6A Pending CN117933200A (en) 2024-01-24 2024-01-24 Document editing method and device, computer equipment and storage medium

Country Status (1)

Country Link
CN (1) CN117933200A (en)

Similar Documents

Publication Publication Date Title
CN106952072A (en) A kind of method and system of data processing
CN115544183A (en) Data visualization method and device, computer equipment and storage medium
CN109767098A (en) Processing method, device, computer equipment and the storage medium of product attribute
CN114444478A (en) Voucher visualization method and device, electronic equipment and storage medium
CN112328575A (en) Data asset blood margin generation method and device and electronic equipment
CN115409014A (en) Document template generation method and device, computer equipment and storage medium
CN117933200A (en) Document editing method and device, computer equipment and storage medium
CN114676359A (en) Form display method and device, computer equipment and storage medium
CN114547157A (en) Knowledge graph analysis system and method
US20040143517A1 (en) System and method for managing material distribution and returned materials
CN115408396B (en) Method, device, computer equipment and storage medium for storing business data
CN117435198A (en) Page generation method and device
CN117372152A (en) Resource return plan information generation method and device and computer equipment
CN117951223A (en) Data synchronization method, device, computer equipment and storage medium
CN116303657A (en) Group image generation method, group image generation device, computer device, and storage medium
CN114816405A (en) Business view interface display method and device, computer equipment and storage medium
CN117669528A (en) Document generation method, device, computer equipment and storage medium
CN115203486A (en) Deduction scheme generation method and device and computer equipment
CN115907337A (en) Material storage method, system, device, storage medium and program product
CN117435581A (en) Index identification method, apparatus, device, storage medium, and program product
CN116383138A (en) Document changing method, device, computer equipment and storage medium
CN117114727A (en) Method, device, computer equipment and storage medium for generating product model
CN117033452A (en) Database processing method, device, computer equipment and storage medium
CN116069865A (en) Inventory sharing method, apparatus, computer device and storage medium
CN117592757A (en) Report data processing method, device, computer equipment and storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination