CN113449496A - Method and device for automatically generating maintenance document - Google Patents
Method and device for automatically generating maintenance document Download PDFInfo
- Publication number
- CN113449496A CN113449496A CN202110711244.0A CN202110711244A CN113449496A CN 113449496 A CN113449496 A CN 113449496A CN 202110711244 A CN202110711244 A CN 202110711244A CN 113449496 A CN113449496 A CN 113449496A
- Authority
- CN
- China
- Prior art keywords
- maintenance
- page
- bill
- document
- brand
- 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.)
- Granted
Links
- 238000012423 maintenance Methods 0.000 title claims abstract description 159
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000009193 crawling Effects 0.000 claims abstract description 52
- 230000008439 repair process Effects 0.000 claims description 69
- 238000012545 processing Methods 0.000 claims description 40
- 230000002159 abnormal effect Effects 0.000 claims description 20
- 238000012795 verification Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010586 diagram Methods 0.000 description 14
- 238000004891 communication Methods 0.000 description 7
- 230000005856 abnormality Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000003287 optical effect Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000013475 authorization Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 239000000835 fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000003252 repetitive effect Effects 0.000 description 2
- 239000004065 semiconductor Substances 0.000 description 2
- 206010033799 Paralysis Diseases 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000009191 jumping Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000011218 segmentation Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/174—Form filling; Merging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/951—Indexing; Web crawling techniques
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Data Mining & Analysis (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a device for automatically generating a maintenance document, and relates to the field of computers. One embodiment of the method comprises: analyzing a brand identifier in the order opening request, and acquiring a first maintenance bill and an address identifier corresponding to the brand identifier from a configuration library; acquiring a billing page in a target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawling field values of all page fields in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page. According to the embodiment, the maintenance manufacturer system can automatically complete bill opening of different manufacturer systems of different brands, complex steps of manually exporting data and manually inputting are omitted, and automatic bill opening of multiple bill quantities in a short time is achieved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a device for automatically generating a maintenance document.
Background
With the diversified development of digital electronic products, the maintenance demand of various digital electronic devices is increasing day by day, and data recording and maintenance order storage are required during maintenance, so that a basis is provided for subsequent inquiry and dispute handling during maintenance.
The maintenance center usually signs a contract with tens of 3C maintenance manufacturers and obtains maintenance authorization, and different maintenance manufacturers require that the maintained commodities need to be ordered in the manufacturer system. In the prior art, the order is opened in a manufacturer system usually in a manual mode, which wastes manpower and has high cost and low efficiency.
Disclosure of Invention
In view of this, embodiments of the present invention provide a method and an apparatus for automatically generating a maintenance document, which can replace manual entry by an automatic billing method, reduce the cost of manual entry, improve the billing efficiency, and save the labor cost.
To achieve the above object, according to an aspect of the embodiments of the present invention, a method and an apparatus for automatically generating a repair document are provided.
The automatic order opening method of the embodiment of the invention comprises the following steps: analyzing a brand identifier in the order opening request, and acquiring a first maintenance bill and an address identifier corresponding to the brand identifier from a configuration library; acquiring a billing page in a target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawling field values of all page fields in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page.
Optionally, before acquiring the first repair document and the address identifier corresponding to the brand identifier from the configuration library, the method further includes: analyzing the brand identification to be configured and the address identification to be configured in the configuration request; and sending the address identifier to be configured to a target system corresponding to the brand identifier to be configured, receiving verification information returned by the target system after the target system verifies the address identifier, and confirming that the verification information is information indicating that the address identifier to be configured is legal.
Optionally, the method further comprises: before field values of all page fields in the billing page are crawled from the first maintenance document, corresponding relations between the page fields in the billing page and corresponding document fields in the first maintenance document are preserved in advance; crawling field values of all page fields in the billing page from the first maintenance document, wherein the crawling comprises the following steps: and traversing the page fields in the opening page, and for any page field: judging whether a target bill field corresponding to any page field exists in the first maintenance bill according to the corresponding relation; if yes, crawling a field value of the target document field; if not, sending prompt information indicating that crawling fails to be performed so as to prompt a user to manually enter a corresponding relation between a page field in the billing page and a bill field corresponding to the first maintenance bill.
Optionally, before crawling the field value of the target document field, further comprising: confirming that any one single word segmentation has the crawling authority; if any single-letter field does not have the crawling right, sending out prompt information indicating no crawling right to prompt a user to manually input the field value of any single-letter field.
Optionally, after acquiring the first repair document and the address identifier corresponding to the brand identifier from the configuration library, the method further includes: configuring a task processing mode; (ii) a The task processing mode comprises the following steps: any one of automatic timing execution, execution by time period, and manual trigger execution; before acquiring the opening page in the target system according to the brand identifier and the address identifier, the method further comprises the following steps: and determining the task processing mode.
Optionally, before acquiring the first repair document and the address identifier corresponding to the brand identifier from the configuration library, the method further includes: configuring an exception handling strategy corresponding to the address identifier; the exception handling policy comprises: alarm modes corresponding to the abnormal types; the method further comprises the following steps: after a second maintenance form corresponding to the first maintenance form is generated, a second maintenance form generation result returned by the target system is obtained; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation is successful, sending prompt information indicating that the generation of the maintenance bill is successful; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation fails, analyzing the abnormal type from the second-dimension bill repair generation result, determining an alarm mode according to a corresponding abnormal processing strategy, and performing abnormal processing alarm according to the determined alarm mode; the exception type comprises one or more of server exception, network exception and state code identification exception; the exception handling alarm form comprises one or more of short message, mail and telephone.
Optionally, the order request includes: opening the order time period; obtaining a first maintenance document corresponding to the brand identifier from a configuration library, including: acquiring all first maintenance documents corresponding to the brand identification in the order opening time period from a configuration library; the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page, and the method comprises the following steps: and the target system respectively generates a second repair bill corresponding to each first repair bill according to the filled bill opening page.
To achieve the above object, according to another aspect of the embodiments of the present invention, there is provided a system for automatically generating a repair document.
The system for automatically generating the maintenance document comprises the following components: the task generation module is used for analyzing the brand identification in the order opening request and acquiring a first maintenance bill and an address identification corresponding to the brand identification from a configuration library; the automatic processing module is used for acquiring a billing page in a target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawling field values of all page fields in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page.
Optionally, the system further comprises: the configuration module is used for analyzing the brand identifier to be configured and the address identifier to be configured in the configuration request before acquiring the first maintenance document and the address identifier corresponding to the brand identifier from the configuration library; and sending the address identifier to be configured to a target system corresponding to the brand identifier to be configured, receiving verification information returned by the target system after the target system verifies the address identifier to be configured, and confirming that the verification information is information indicating that the address identifier to be configured is legal.
Optionally, the configuration module is further configured to pre-store a correspondence between a page field in the billing page and a corresponding document field in the first maintenance document before crawling a field value of each page field in the billing page from the first maintenance document;
crawling field values of all page fields in the billing page from the first maintenance document, wherein the crawling comprises the following steps: and traversing page fields in the single-word opening page, and for any single-word opening segment: judging whether a target document field corresponding to any single letter opening field exists in the first maintenance document according to the corresponding relation; if yes, crawling a field value of the target document field; if not, sending prompt information indicating that crawling fails to be performed so as to prompt a user to manually enter a corresponding relation between a page field in the billing page and a bill field corresponding to the first maintenance bill.
Optionally, the automatic processing module is further configured to confirm that any one of the single word paragraphs has a crawling right before crawling a field value of the target document field; if any single-letter field does not have the crawling right, sending out prompt information indicating no crawling right to prompt a user to manually input the field value of any single-letter field.
Optionally, the automatic processing module is further configured to configure a task processing mode after acquiring the first maintenance document and the address identifier corresponding to the brand identifier from a configuration library; the task processing mode comprises the following steps: any one of automatic timing execution, execution by time period, and manual trigger execution; before acquiring the opening page in the target system according to the brand identifier and the address identifier, the method further comprises the following steps: and determining the task processing mode.
Optionally, the configuration module is further configured to configure an exception handling policy corresponding to the address identifier before acquiring the first maintenance document and the address identifier corresponding to the brand identifier from a configuration library; the exception handling policy comprises: alarm modes corresponding to the abnormal types;
the automatic processing module is further used for acquiring a second repair sheet generation result returned by the target system after a second repair sheet corresponding to the first repair sheet is generated; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation is successful, sending prompt information indicating that the generation of the maintenance bill is successful; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation fails, analyzing the abnormal type from the second-dimension bill repair generation result, determining an alarm mode according to a corresponding abnormal processing strategy, and performing abnormal processing alarm according to the determined alarm mode; the exception type comprises one or more of server exception, network exception and state code identification exception; the exception handling alarm form comprises one or more of short message, mail and telephone.
Optionally, the order request includes: opening the order time period; obtaining a first maintenance document corresponding to the brand identifier from a configuration library, including: acquiring all first maintenance documents corresponding to the brand identification in the order opening time period from a configuration library; the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page, and the method comprises the following steps: and the target system respectively generates a second repair bill corresponding to each first repair bill according to the filled bill opening page.
To achieve the above object, according to still another aspect of the embodiments of the present invention, there is provided an electronic device for automatically generating a repair document.
The electronic equipment for automatically generating the maintenance document comprises: one or more processors; storage means for storing one or more programs; when the one or more programs are executed by the one or more processors, the one or more processors implement the method for automatically generating a repair document according to the embodiment of the invention.
To achieve the above object, according to still another aspect of embodiments of the present invention, there is provided a computer-readable medium.
The computer readable medium of the embodiment of the invention stores a computer program, and the program realizes the method for automatically generating the maintenance document of the embodiment of the invention when being executed by a processor.
One embodiment of the above invention has the following advantages or benefits: in the embodiment of the invention, the corresponding second maintenance document is generated by crawling the corresponding field value from the first maintenance document to the billing page according to the brand identifier and the address identifier, so that the step of manually billing a brand manufacturer system by a bill recorder is avoided, manpower is greatly saved, and the billing efficiency is improved. Compared with the existing manual entry method, the embodiment of the invention saves the manual entry link, reduces the repetitive work of a person who opens a region, improves the working efficiency and reduces the manual entry cost.
Further effects of the above-mentioned non-conventional alternatives will be described below in connection with the embodiments.
Drawings
The drawings are included to provide a better understanding of the invention and are not to be construed as unduly limiting the invention. Wherein:
FIG. 1 is a schematic diagram of the main flow of a method of automatically generating a repair document according to an embodiment of the invention;
FIG. 2 is a schematic diagram of the main flow of verifying address identifiers in a configuration repository according to an embodiment of the present invention;
FIG. 3 is a schematic diagram of a main flow of crawling field values of various page fields in a form page from a first repair form according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of the main flow of an exception handling policy of another embodiment of the present invention;
FIG. 5 is a schematic diagram of the major modules of a system for automatically generating repair documents in accordance with an embodiment of the present invention;
FIG. 6 is an exemplary system architecture diagram in which embodiments of the present invention may be employed;
fig. 7 is a schematic block diagram of a computer system suitable for use in implementing a terminal device or server of an embodiment of the invention.
Detailed Description
Exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which various details of embodiments of the invention are included to assist understanding, and which are to be considered as merely exemplary. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted in the following description for clarity and conciseness.
Fig. 1 is a schematic diagram of a main flow of a method for automatically generating a repair document according to an embodiment of the present invention. As shown in fig. 1, the method mainly includes:
step S101: analyzing the brand identification in the order opening request; step S102: acquiring a first maintenance document and an address identifier corresponding to the brand identifier from a configuration library; step S103: acquiring a billing page in a target system according to a brand identifier and an address identifier corresponding to the automatic billing task; step S104: crawling field values of all page fields in a list page from the first maintenance document; step S105: and filling the crawled field value into a billing page so that the target system generates a second maintenance document corresponding to the automatic billing task according to the filled billing page.
Wherein the brand mark is the brand of a product to be opened; the address mark is a webpage address of a to-be-opened manufacturer system and is configured in association with the brand mark; the target system is a to-be-issued order manufacturer system; each brand mark only corresponds to one address mark; the first maintenance bill is a bill recorded by the maintenance center in the maintenance process, and the second maintenance bill is a bill corresponding to the first maintenance bill after the maintenance manufacturer automatically opens the bill. For example, the maintenance center a has authorization to maintain 10 brands of mobile phones, such as brand a, brand B, and brand C, and now wants to open a maintenance order of brand B from the maintenance center a, the brand to be opened is brand B, the target system is a brand B manufacturer system, the address identifier is a web address of the brand B manufacturer system, the first maintenance document is a document to be filled when the maintenance center a maintains brand B mobile phone 001, and the second maintenance document is a document to be maintained of 001 mobile phone that brand B manufacturer needs to obtain from the maintenance center a, and is registered in the brand B manufacturer system.
Before obtaining the first repair document and the address identifier corresponding to the brand identifier from the configuration repository, in an alternative embodiment, as shown in fig. 2, the method includes: step S201: analyzing the brand identification to be configured and the address identification to be configured in the configuration request; step S202: sending the address identifier to be configured to a target system corresponding to the brand identifier to be configured; step S203: receiving verification information returned by the target system after the target system verifies the address identifier to be configured; step S204: the confirmation authentication information is information indicating that the address identification to be configured is valid.
In an optional embodiment, the target system returns the verification information with the format of robots.
Before confirming that the verification information is the information indicating that the address identifier to be configured is legal, whether the address identifier to be configured is legal or not needs to be verified, in an optional embodiment, if the path of the address identifier to be configured can be successfully accessed, that is, the path of the address identifier is considered to be legal, information indicating that the address identifier to be configured is legal is sent at this moment; if the path of the address identifier to be configured cannot be accessed due to manual operation errors and the like, the path of the address identifier to be configured is considered to be illegal, and information indicating that the address identifier to be configured is illegal is sent.
After the verification information is confirmed to be the information indicating that the address identifier to be configured is legal, the confirmed address identifier is stored in a corresponding brand identifier directory in a configuration library. For example, brand a has brand divisions respectively in city a, city B, and city C, and different vendor systems are used in each region due to various factors such as policy environment, and at this time, three address identifiers, i.e., vendor systems of the three brand divisions in city a, city B, and city C, need to be stored in the brand a directory.
Before crawling field values of various page fields in a form page from a first repair form, in an alternative embodiment, as shown in fig. 3, the method includes:
step S301: pre-storing a corresponding relation between a page field in the bill opening page and a corresponding bill field in the first maintenance bill;
step S302: and traversing page fields in the single page, and for any page field: judging whether a target document field corresponding to any page field exists in the first maintenance document according to the corresponding relation;
if yes, go to step S303: crawling the field value of the target document field; if not, jumping to step S304: and sending prompt information indicating that the crawling fails so as to prompt a user to manually enter a corresponding relation between a page field in the bill opening page and a bill field corresponding to the first maintenance bill.
For the setting of the corresponding relationship between the page field in the billing page and the data field in the first maintenance document, in an alternative embodiment, the page field in the pre-saved billing page may correspond to the corresponding document field in a plurality of first maintenance documents, for example, to purchase all the maintenance documents of brand B from three maintenance vendors A, B, C, but since the respective maintenance vendors use their respective maintenance systems, the document fields used are not uniform, the page field is set to "maintenance time" in brand B vendor, the maintenance time is represented by "registration time" in maintenance vendor a, the maintenance time is represented by "maintenance time" in maintenance vendor B, and the maintenance time is represented by "order receiving time" in maintenance vendor C. In order to ensure that the billing failure caused by the non-uniform system of each maintenance manufacturer can be avoided in the automatic billing process, before the field values of each page field in the billing page are crawled from the first maintenance bill corresponding to the automatic billing task, the registration time, the maintenance time and the order receiving time are set to be in corresponding relation with the maintenance time, so that when the page field is set to be the maintenance time, the bill field representing the maintenance time can be smoothly obtained from the maintenance manufacturer A, B, C.
When the corresponding relation between the page field in the order opening page and the data field in the first maintenance document cannot be entered manually, namely the field value of the target document field cannot be crawled from the first maintenance document, prompt information indicating that the data is insufficient and the automatic order opening cannot be performed is sent, and a user is prompted to select to skip the field value and perform automatic order opening or finish the automatic order opening. Because the first maintenance documents needing automatic invoicing are all history documents, data can not be supplemented, when the first maintenance documents do not contain target document fields corresponding to the page fields in the invoicing page, manual subsequent filling can not be carried out, and filling of other page fields can only be continuously completed by skipping filling of the field values.
In an optional embodiment, before crawling the field value of the target document field, the method further comprises: confirming that any page field has crawling authority; if any page field does not have the crawling right, sending out prompt information representing no crawling right to prompt a user to manually input the field value of any page field.
For example, in order to prevent malicious automatic billing, automatic billing needs to be performed under the supervision of a person, at this time, a billing page of a brand B manufacturer contains a page field of a "supervisor", and the page field does not have a crawling right, i.e., cannot be filled in by crawling, and needs to be manually filled in by an operator supervising a current automatic billing program, so as to ensure the accuracy of billing, and avoid the malicious billing caused under the unsupervised condition.
In an optional embodiment, after acquiring the first repair document and the address identifier corresponding to the brand identifier from the configuration library, the method further includes: configuring a task processing mode; the task processing mode comprises the following steps: any one of automatic timing execution, execution by time period, and manual trigger execution; before acquiring the opening page in the target system according to the brand identifier and the address identifier, the method further comprises the following steps: a task processing mode is determined.
The automatic timing execution means that after the execution time is set, an execution cycle can be set, and when the execution time reaches each execution cycle, the execution is performed once; for example, if the execution is set to 10 pm per sunday, the automatic order issuance is executed only once at 10 pm per sunday. The execution according to the time period means that the automatic order opening is executed once after a certain time period; for example, if the execution is set every 12 hours, the automatic billing is executed every 12 hours later. The manual trigger execution means that the automatic order opening is executed only when manual operation is carried out.
In an optional embodiment, before obtaining the first repair document and the address identifier corresponding to the brand identifier from the configuration library, the method further includes: configuring an exception handling strategy corresponding to the address identifier; the exception handling policy comprises: alarm modes corresponding to the abnormal types; the exception type comprises one or more of server exception, network exception and state code identification exception; the exception handling alarm form comprises one or more of short message, mail and telephone.
And according to different severity grades of the abnormal types, corresponding to different abnormal processing alarm forms. For example, the network exception is a common exception type in life, and the order can be normally opened after the network is recovered to be normal, so that the order opening failure caused by the network exception is not important for a user to check and receive in time corresponding to an exception handling alarm form of a mail; however, if the order opening fails due to the server abnormality, it means that the server may be paralyzed and cannot work normally, and the severity level is much higher than the network abnormality, so the corresponding abnormality processing alarm form can be sending an email and making a call at the same time, and a user needs to know the server abnormality in time and check the cause of the abnormality, and repair the abnormality in time, so as to avoid causing serious economic loss.
After generating the second repair sheet corresponding to the first repair sheet, in an alternative embodiment, as shown in fig. 4, the method includes:
step S401: acquiring a second dimension bill repair generation result returned by the target system; if the second repair form generation result is information indicating that the second repair form is successfully generated, executing step S402: sending prompt information indicating that the generation of the maintenance document is successful; and if the second repair form generation result is information indicating that the second repair form generation is failed, skipping to execute the steps S403 to S405, wherein: step S403: analyzing the abnormal type from the second maintenance document generation result; step S404: determining an alarm mode according to an exception handling strategy; step S405: and performing exception handling alarm according to the determined alarm mode.
In an alternative embodiment, the order request includes: opening the order time period; obtaining a first maintenance document corresponding to the brand identifier from a configuration library, including: acquiring all first maintenance documents corresponding to the brand identification in the order opening time period from a configuration library; the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page, and the second maintenance bill comprises the following steps: and the target system respectively generates a second maintenance bill corresponding to each first maintenance bill according to the filled billing page. For example, to make a maintenance order of brand B brand in about three months at maintenance manufacturer a and complete automatic ordering in brand B system, the order-issuing time period is set from 11 days at 2 months in 2021 to 11 days at 5 months in 2021 in order to obtain 100 first maintenance orders of all brand B brands that maintenance manufacturer a made during 11 days at 2 months in 2021 to 11 days at 5 months in 2021, and at the same time, 100 second maintenance orders are correspondingly generated in brand B system.
The method for automatically generating the maintenance document is simple and convenient, avoids the step of manual order opening of a brand manufacturer system by a document recorder, greatly saves manpower, improves the document opening efficiency, reduces the repetitive work of an area opening person, improves the work efficiency and reduces the manual document recording cost.
FIG. 5 is a schematic diagram of the main modules of a system 500 for automatically generating repair documents, according to an embodiment of the present invention. As shown in fig. 5, includes:
the task generating module 501 is configured to analyze a brand identifier in the order opening request, and obtain a first repair document and an address identifier corresponding to the brand identifier from a configuration library;
the automatic processing module 502 is configured to obtain a billing page in the target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawl field values of each page field in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance document corresponding to the first maintenance document according to the filled billing page.
In an optional embodiment, the system further comprises: the configuration module is used for analyzing the brand identifier to be configured and the address identifier to be configured in the configuration request before acquiring the first maintenance document and the address identifier corresponding to the brand identifier from the configuration library; and sending the address identifier to be configured to a target system corresponding to the brand identifier to be configured, receiving verification information returned by the target system after the target system verifies the address identifier to be configured, and confirming that the verification information is information indicating that the address identifier to be configured is legal.
In an optional embodiment, the configuration module is further configured to pre-store a correspondence between a page field in the invoice page and a corresponding document field in the first maintenance document before crawling field values of each page field in the invoice page from the first maintenance document;
crawling field values of all page fields in the billing page from the first maintenance document, wherein the crawling comprises the following steps: and traversing page fields in the single-word opening page, and for any single-word opening segment: judging whether a target document field corresponding to any single letter opening field exists in the first maintenance document according to the corresponding relation; if yes, crawling field values of target document fields; if not, sending prompt information indicating that the crawling fails to be performed so as to prompt a user to manually enter a corresponding relation between a page field in the bill opening page and a bill field corresponding to the first maintenance bill.
In an alternative embodiment, the automatic processing module 502 is further configured to confirm that any one-word segment has the crawling authority before crawling the field value of the target document field; if any single-letter field does not have the crawling right, prompting information indicating no crawling right is sent out to prompt a user to manually input the field value of any single-letter field.
In an alternative embodiment, the automatic processing module 502 is further configured to configure the task processing mode after acquiring the first repair document and the address identifier corresponding to the brand identifier from the configuration library; the task processing mode comprises the following steps: any one of automatic timing execution, execution by time period, and manual trigger execution; before acquiring the opening page in the target system according to the brand identifier and the address identifier, the method further comprises the following steps: a task processing mode is determined.
In an optional embodiment, the configuration module is further configured to configure an exception handling policy corresponding to the address identifier before acquiring the first maintenance document and the address identifier corresponding to the brand identifier from the configuration library; the exception handling strategy comprises the following steps: alarm modes corresponding to the abnormal types;
the automatic processing module is also used for acquiring a second repair sheet generation result returned by the target system after generating a second repair sheet corresponding to the first repair sheet; if the second-dimension repair bill generation result is information indicating that the second-dimension repair bill is successfully generated, sending prompt information indicating that the repair bill is successfully generated; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation fails, analyzing an abnormal type from the second-dimension bill repair generation result, determining an alarm mode according to an abnormal processing strategy, and performing abnormal processing alarm according to the determined alarm mode; the exception type comprises one or more of server exception, network exception and state code identification exception; the exception handling alarm form comprises one or more of short message, mail and telephone.
In an alternative embodiment, the order request includes: opening the order time period; obtaining a first maintenance document corresponding to the brand identifier from a configuration library, including: acquiring all first maintenance documents corresponding to the brand identification in the order opening time period from a configuration library; the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page, and the second maintenance bill comprises the following steps: and the target system respectively generates a second maintenance bill corresponding to each first maintenance bill according to the filled billing page.
According to the system for automatically generating the maintenance document, the corresponding field value is crawled from the first maintenance document to the billing page according to the brand identifier and the address identifier to generate the corresponding second maintenance document, so that the step that a bill recording worker manually sends the system billing of a brand manufacturer is avoided, labor is greatly saved, and the billing efficiency is improved.
The system for automatically generating the maintenance document can execute the method provided by the embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the method provided by the embodiment of the present invention.
Fig. 6 illustrates an exemplary system architecture 600 of a method of automatically generating a repair document or a system of automatically generating a repair document to which embodiments of the invention may be applied.
As shown in fig. 6, the system architecture 600 may include terminal devices 601, 602, 603, a network 604, and a server 605. The network 604 serves to provide a medium for communication links between the terminal devices 601, 602, 603 and the server 605. Network 604 may include various types of connections, such as wire, wireless communication links, or fiber optic cables, to name a few.
A user may use the terminal devices 601, 602, 603 to interact with the server 605 via the network 604 to receive or send messages or the like. Various communication client applications, such as shopping applications, web browser applications, search applications, instant messaging tools, mailbox clients, social platform software, and the like, may be installed on the terminal devices 601, 602, and 603.
The terminal devices 601, 602, 603 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like.
The server 605 may be a server that provides various services, such as a background management server that supports shopping websites browsed by users using the terminal devices 601, 602, and 603. The background management server may analyze and perform other processing on the received data such as the product information query request, and feed back a processing result (e.g., target push information and product information) to the terminal device.
It should be noted that the method for automatically generating a repair document according to the embodiment of the present invention is generally executed by the server 605, and accordingly, the system for automatically generating a repair document is generally disposed in the server 605.
It should be understood that the number of terminal devices, networks, and servers in fig. 6 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation.
Referring now to FIG. 7, shown is a block diagram of a computer system 700 suitable for use with a terminal device implementing an embodiment of the present invention. The terminal device shown in fig. 7 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present invention.
As shown in fig. 7, the computer system 700 includes a Central Processing Unit (CPU)701, which can perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM)702 or a program loaded from a storage section 708 into a Random Access Memory (RAM) 703. In the RAM 703, various programs and data necessary for the operation of the system 700 are also stored. The CPU 701, the ROM 702, and the RAM 703 are connected to each other via a bus 704. An input/output (I/O) interface 705 is also connected to bus 704.
The following components are connected to the I/O interface 705: an input portion 706 including a keyboard, a mouse, and the like; an output section 705 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 708 including a hard disk and the like; and a communication section 709 including a network interface card such as a LAN card, a modem, or the like. The communication section 709 performs communication processing via a network such as the internet. A drive 710 is also connected to the I/O interface 705 as needed. A removable medium 711 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 710 as necessary, so that a computer program read out therefrom is mounted into the storage section 708 as necessary.
In particular, according to the embodiments of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method illustrated in the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 709, and/or installed from the removable medium 711. The computer program performs the above-described functions defined in the system of the present invention when executed by the Central Processing Unit (CPU) 701.
It should be noted that the computer readable medium shown in the present invention can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present invention, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present invention, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The modules described in the embodiments of the present invention may be implemented by software or hardware. The described modules may also be provided in a processor, which may be described as: a processor includes a sending module, an obtaining module, a determining module, and a first processing module. The names of these modules do not form a limitation on the modules themselves in some cases, and for example, the sending module may also be described as a "module sending a picture acquisition request to a connected server".
As another aspect, the present invention also provides a computer-readable medium that may be contained in the apparatus described in the above embodiments; or may be separate and not incorporated into the device. The computer readable medium carries one or more programs which, when executed by a device, cause the device to comprise:
analyzing the brand identification in the order opening request, and acquiring a first maintenance document and an address identification corresponding to the brand identification from a configuration library;
acquiring a billing page in a target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawling field values of all page fields in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance document corresponding to the first maintenance document according to the filled billing page.
According to the technical scheme of the embodiment of the invention, the maintenance manufacturer system can automatically complete bill opening of different brands and different manufacturer systems of the 3C maintenance bill, so that manual data export is reduced, the complicated step that staff go to the brand manufacturer system for manual input is omitted, automatic bill opening of multiple bill quantities in a short time can be realized, the working efficiency is improved, the cost of manual bill recording is reduced, and the whole maintenance system is further optimized.
The above-described embodiments should not be construed as limiting the scope of the invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions can occur, depending on design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method of automatically generating a repair document, the method comprising:
analyzing a brand identifier in the order opening request, and acquiring a first maintenance bill and an address identifier corresponding to the brand identifier from a configuration library;
acquiring a billing page in a target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawling field values of all page fields in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page.
2. The method of claim 1, further comprising, prior to obtaining the first repair document and the address identifier corresponding to the brand identifier from a configuration repository:
analyzing the brand identification to be configured and the address identification to be configured in the configuration request; and sending the address identifier to be configured to a target system corresponding to the brand identifier to be configured, receiving verification information returned by the target system after the target system verifies the address identifier to be configured, and confirming that the verification information is information indicating that the address identifier to be configured is legal.
3. The method of claim 1, further comprising:
before field values of all page fields in the billing page are crawled from the first maintenance document, corresponding relations between the page fields in the billing page and corresponding document fields in the first maintenance document are preserved in advance;
crawling field values of all page fields in the billing page from the first maintenance document, wherein the crawling comprises the following steps: and traversing the page fields in the opening page, and for any page field: judging whether a target bill field corresponding to any page field exists in the first maintenance bill according to the corresponding relation; if yes, crawling a field value of the target document field; if not, sending prompt information indicating that crawling fails to be performed so as to prompt a user to manually enter a corresponding relation between a page field in the billing page and a bill field corresponding to the first maintenance bill.
4. The method of claim 3, further comprising, prior to crawling field values of the target document field: confirming that any page field has crawling authority; if any page field does not have the crawling right, sending out prompt information representing no crawling right to prompt a user to manually input the field value of any page field.
5. The method of claim 1, after obtaining the first repair document and the address identifier corresponding to the brand identifier from a configuration repository, further comprising: configuring a task processing mode; the task processing mode comprises the following steps: any one of automatic timing execution, execution by time period, and manual trigger execution;
before acquiring the opening page in the target system according to the brand identifier and the address identifier, the method further comprises the following steps: and determining the task processing mode.
6. The method of claim 1, further comprising, prior to obtaining the first repair document and the address identifier corresponding to the brand identifier from a configuration repository: configuring an exception handling strategy corresponding to the address identifier; the exception handling policy comprises: alarm modes corresponding to the abnormal types;
the method further comprises the following steps: after a second maintenance form corresponding to the first maintenance form is generated, a second maintenance form generation result returned by the target system is obtained; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation is successful, sending prompt information indicating that the generation of the maintenance bill is successful; if the second-dimension bill repair generation result is information indicating that the second-dimension bill repair generation fails, analyzing the abnormal type from the second-dimension bill repair generation result, determining an alarm mode according to a corresponding abnormal processing strategy, and performing abnormal processing alarm according to the determined alarm mode;
the exception type comprises one or more of server exception, network exception and state code identification exception; the exception handling alarm form comprises one or more of short message, mail and telephone.
7. The method of claim 1, wherein the billing request comprises: opening the order time period;
obtaining a first maintenance document corresponding to the brand identifier from a configuration library, including: acquiring all first maintenance documents corresponding to the brand identification in the order opening time period from a configuration library;
the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page, and the method comprises the following steps: and the target system respectively generates a second repair bill corresponding to each first repair bill according to the filled bill opening page.
8. A system for automatically generating a repair document, comprising:
the task generation module is used for analyzing the brand identification in the order opening request and acquiring a first maintenance bill and an address identification corresponding to the brand identification from a configuration library;
the automatic processing module is used for acquiring a billing page in a target system corresponding to the brand identifier according to the brand identifier and the address identifier, and crawling field values of all page fields in the billing page from the first maintenance document; and filling the crawled field value into the billing page so that the target system generates a second maintenance bill corresponding to the first maintenance bill according to the filled billing page.
9. An electronic device for automatically generating a repair document, comprising: one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-7.
10. A computer-readable medium, on which a computer program is stored, which, when being executed by a processor, carries out the method according to any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110711244.0A CN113449496B (en) | 2021-06-25 | 2021-06-25 | Method and device for automatically generating maintenance bill |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110711244.0A CN113449496B (en) | 2021-06-25 | 2021-06-25 | Method and device for automatically generating maintenance bill |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113449496A true CN113449496A (en) | 2021-09-28 |
| CN113449496B CN113449496B (en) | 2024-05-17 |
Family
ID=77812715
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110711244.0A Active CN113449496B (en) | 2021-06-25 | 2021-06-25 | Method and device for automatically generating maintenance bill |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113449496B (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040181749A1 (en) * | 2003-01-29 | 2004-09-16 | Microsoft Corporation | Method and apparatus for populating electronic forms from scanned documents |
| CN1664810A (en) * | 2004-03-03 | 2005-09-07 | 微软公司 | Assisted form filling |
| EP1879117A1 (en) * | 2006-07-14 | 2008-01-16 | Accenture Global Services GmbH | System, method and computer program product for monitoring the filling in of remote forms |
| CN101777143A (en) * | 2009-12-22 | 2010-07-14 | 金蝶软件（中国）有限公司 | Method, device and system for business bill conversion |
| CN104318425A (en) * | 2014-10-08 | 2015-01-28 | 广州市海珠区电子政务技术信息中心 | Service information logging method and system |
| CN106681971A (en) * | 2015-11-11 | 2017-05-17 | 阿里巴巴集团控股有限公司 | Form data processing method and device |
| US20170262421A1 (en) * | 2016-03-14 | 2017-09-14 | Tommy Yue | Form Autofilling System |
| CN107885986A (en) * | 2016-09-30 | 2018-04-06 | 联芯科技有限公司 | A kind of form filling method, form data store method and device |
| CN110362802A (en) * | 2019-07-18 | 2019-10-22 | 中国工商银行股份有限公司 | For by the method, apparatus of document information input system, calculate equipment, medium |
| CN110704519A (en) * | 2019-08-29 | 2020-01-17 | 中国平安财产保险股份有限公司 | Business document conversion method and device, storage medium and computer equipment |
| CN112580301A (en) * | 2019-09-27 | 2021-03-30 | 北京国双科技有限公司 | Form verification method, device, equipment and storage medium |
| CN112765944A (en) * | 2020-12-30 | 2021-05-07 | 维沃移动通信有限公司 | Form filling method, device, equipment and medium |
-
2021
- 2021-06-25 CN CN202110711244.0A patent/CN113449496B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040181749A1 (en) * | 2003-01-29 | 2004-09-16 | Microsoft Corporation | Method and apparatus for populating electronic forms from scanned documents |
| CN1664810A (en) * | 2004-03-03 | 2005-09-07 | 微软公司 | Assisted form filling |
| CN1673995A (en) * | 2004-03-24 | 2005-09-28 | 微软公司 | Method and apparatus for populating electronic forms from scanned documents |
| EP1879117A1 (en) * | 2006-07-14 | 2008-01-16 | Accenture Global Services GmbH | System, method and computer program product for monitoring the filling in of remote forms |
| CN101777143A (en) * | 2009-12-22 | 2010-07-14 | 金蝶软件（中国）有限公司 | Method, device and system for business bill conversion |
| CN104318425A (en) * | 2014-10-08 | 2015-01-28 | 广州市海珠区电子政务技术信息中心 | Service information logging method and system |
| CN106681971A (en) * | 2015-11-11 | 2017-05-17 | 阿里巴巴集团控股有限公司 | Form data processing method and device |
| US20170262421A1 (en) * | 2016-03-14 | 2017-09-14 | Tommy Yue | Form Autofilling System |
| CN107885986A (en) * | 2016-09-30 | 2018-04-06 | 联芯科技有限公司 | A kind of form filling method, form data store method and device |
| CN110362802A (en) * | 2019-07-18 | 2019-10-22 | 中国工商银行股份有限公司 | For by the method, apparatus of document information input system, calculate equipment, medium |
| CN110704519A (en) * | 2019-08-29 | 2020-01-17 | 中国平安财产保险股份有限公司 | Business document conversion method and device, storage medium and computer equipment |
| CN112580301A (en) * | 2019-09-27 | 2021-03-30 | 北京国双科技有限公司 | Form verification method, device, equipment and storage medium |
| CN112765944A (en) * | 2020-12-30 | 2021-05-07 | 维沃移动通信有限公司 | Form filling method, device, equipment and medium |
Non-Patent Citations (1)
| Title |
|---|
| 马建华;李赛红;徐兰兰;: "深层网中基于入口查询的表单填充策略", 计算机工程, no. 07, 5 April 2010 (2010-04-05) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113449496B (en) | 2024-05-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107908680A (en) | Management method, electronic device and the computer-readable recording medium of wechat public platform | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| US8484724B2 (en) | User permissions in computing systems | |
| CN111258832B (en) | Interface parameter verification method, device, equipment and medium | |
| CN114219645A (en) | Accounting date switching method, device, equipment, readable storage medium and product | |
| CN114564294A (en) | Intelligent service arranging method and device, computer equipment and storage medium | |
| CN111163428B (en) | Method and server for generating short message bill | |
| CN113010238A (en) | Permission determination method, device and system for micro application call interface | |
| US20150140957A1 (en) | Prepaid phone card charging | |
| CN111126935B (en) | Method and device for processing security data, electronic equipment and storage medium | |
| CN112559024A (en) | Method and device for generating transaction code change list | |
| CN113449496A (en) | Method and device for automatically generating maintenance document | |
| CN116049099A (en) | Data processing method, device, electronic equipment and computer readable medium | |
| CN109063468A (en) | A kind of installation kit integrity verification and the method for reparation | |
| CN114968822A (en) | Interface testing method and device, computer equipment and storage medium | |
| CN111526184B (en) | Business auditing method and device | |
| CN114648012A (en) | Bill processing method and device, electronic equipment and computer readable medium | |
| CN113468446A (en) | Method, system and equipment for supporting identification of third-party two-dimensional code data | |
| CN112215592B (en) | Data processing method and system | |
| CN112783903A (en) | Method and device for generating update log | |
| CN112241332A (en) | Interface compensation method and device | |
| CN112819554B (en) | Service processing method and device based on page operation and computer equipment | |
| CN112215531B (en) | Method and device for solving logistics distribution problem | |
| CN112783665B (en) | Interface compensation method and device | |
| CN117827630A (en) | Method and device for generating test script |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |