A method, device and storage medium for quickly generating bills of lading with different types

Abstract

The application relates to a method and device for quickly generating waybills with different types and a storage medium, and is applied to the technical field of logistics express, and comprises the following steps: filling in form contents on a browser page, sending the form contents to a backend system by the browser, calling a waybill creation interface according to the form contents by the backend system, creating a waybill according to compulsory items of the form contents, calling a corresponding logistics track uploading interface according to the form contents after the waybill is created, creating a waybill logistics track according to compulsory items of the form contents, performing value assignment on writable items of the form contents, calling corresponding interfaces of the waybill containing the waybill logistics track according to the value assignment result to give the waybill attributes, and completing creation of the waybill. In the application, when various types of waybills are created, business personnel only need to fill in various types of information on a browser page, the backend system automatically generates the waybills according to the various types of information, and no additional manual operation is needed, so that the time of test or development personnel is liberated.

Description

Technical Field

[0001] This invention relates to the field of logistics and express delivery technology, specifically to a method, apparatus, and storage medium for rapidly generating waybills of different types. Background Technology

[0002] Currently, business personnel do not use testing tools to generate data. Testers or developers need to manually create waybills, logistics tracks, problem item types, and value-added item types. Completing these operations requires API calls in multiple systems, and creating a single waybill takes several minutes. When business personnel conduct business function acceptance testing in the test environment, they need a large number of waybills of different types. At this time, developers or testers have to spend some time helping to generate data, which is inefficient for both parties. This will affect the development and testing progress of subsequent iterations and the progress of business acceptance testing. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a method, apparatus and storage medium for rapidly generating waybills with different types, so as to solve the problem that in the prior art, the creation of waybills requires testers or developers to manually create waybills, logistics tracks, problem item types and value-added item types. The creation of a large number of different types of waybills requires a lot of time from developers or testers, resulting in a waste of human resources.

[0004] According to a first aspect of the present invention, a method for rapidly generating waybills with different types is provided, the method comprising:

[0005] Fill out a form on the browser front-end page. The form content includes required fields and optional fields.

[0006] The browser sends the form content to the backend system, which then calls the waybill creation interface to create a waybill based on the required fields in the form.

[0007] Generate a corresponding number of waybills based on the number of waybills for different logistics trajectories in the fillable fields of the form content. Classify waybills according to different logistics trajectories, and place waybills of each category in a separate array. Call the corresponding logistics trajectory upload interface for waybills in each array, and create waybill logistics trajectories based on the required fields of the form content.

[0008] The form content is assigned values ​​to the fillable fields, and based on the assignment results, the corresponding interface is called to assign waybill attributes to the waybill containing the waybill logistics trajectory, thus completing the creation of the waybill.

[0009] Preferably,

[0010] The required fields include: sender and recipient's mobile phone number and address;

[0011] The addresses include the receiving address, sending address, delivery address, and signature address;

[0012] The data entered by the user in the address field must contain at least one address depending on the nature of the waybill;

[0013] The fillable fields include: the number of waybills for different logistics routes and the waybill attributes;

[0014] The waybill attributes include: whether a problem shipment is required, the type of problem shipment, whether value-added services are required, and the type of value-added services.

[0015] When a user leaves a field blank in a form, the backend system automatically assigns a value to the blank field.

[0016] Preferably,

[0017] The backend system automatically assigns values ​​to unfilled fillable fields, including:

[0018] For the number of waybills in different logistics trajectories, the backend system automatically assigns the number of waybills in each logistics trajectories to 1;

[0019] The backend system automatically assigns a value of 0 to indicate whether a problem component is needed.

[0020] The backend system automatically assigns a value of 0 to whether value-added services are needed.

[0021] Preferably,

[0022] The process of assigning values ​​to the fillable fields in the form and then, based on the assignment results, calling the corresponding interface to assign waybill attributes to waybills containing waybill logistics trajectories includes:

[0023] If the user fills in "requires problem shipment" in the form, the backend system assigns a value of 1 to whether a problem shipment is needed, obtains the problem shipment type filled in by the user, assigns a corresponding problem shipment type code based on the problem shipment type, and calls the problem shipment system interface to create a problem shipment based on the code, adding the problem shipment attribute to the waybill;

[0024] If the user fills in the form indicating that they need value-added services, the backend system assigns a value of 1 to whether value-added services are needed, obtains the value-added service type filled in by the user, assigns a corresponding value-added service type code based on the value-added service type, and calls the value-added service system's create value-added service interface based on the code to add value-added service attributes to the waybill.

[0025] Preferably,

[0026] The types of logistics trajectories include: receipt, dispatch, arrival, delivery, and signature.

[0027] For the logistics tracking of the delivery order, the user fills in the delivery address in the address field of the form;

[0028] For the logistics tracking of the outgoing waybill, the user fills in the recipient address and sender address in the address field of the form;

[0029] For the logistics tracking of a delivery waybill, the user fills in the recipient address, sender address, and destination address in the address field of the form;

[0030] For the logistics tracking of the delivery order, the user fills in the recipient address, sender address, arrival address and delivery address in the address field of the form;

[0031] For the logistics tracking of the signed waybill, the user fills in the recipient address, sender address, arrival address, delivery address, and signature address in the address field of the form.

[0032] Preferably,

[0033] The process involves categorizing waybills based on their logistics trajectories, with each category stored in a separate array. For each waybill in the array, the corresponding logistics trajectory upload interface is called to create the waybill logistics trajectory based on the required fields in the form.

[0034] Based on different logistics routes, waybills are divided into: receipt waybill, dispatch waybill, arrival waybill, delivery waybill, and signed waybill.

[0035] Place waybills of the same type in the same array. For waybills of the same type, call the corresponding logistics track upload interface to traverse all waybills in the array and create a waybill logistics track based on the address entered by the user.

[0036] Preferably, it further includes:

[0037] After the waybill is created, the data for this waybill creation is stored in the browser's storage, and the time point and waybill number of this waybill creation are displayed on the browser's front-end page.

[0038] The number of waybill data stored in the browser page's Storage is no more than X, and the waybill data is arranged in reverse chronological order of the waybill creation time in Storage;

[0039] When the number of waybill data stored in the browser's storage exceeds X records, the earliest waybill data will be removed according to the waybill creation time. The removed waybill data will be sent to the backend system, and the backend system will store the removed waybill data in the personal storage space of the waybill creator.

[0040] According to a second aspect of the present invention, an apparatus for rapidly generating waybills of different types is provided, the apparatus comprising:

[0041] Form filling module: Used to fill out forms on the browser front-end page. The form content includes required fields and optional fields.

[0042] Waybill creation module: This module is used when the browser sends the form content to the backend system, and the backend system calls the waybill creation interface to create a waybill based on the required fields in the form content.

[0043] Logistics Track Creation Module: This module generates a corresponding number of waybills based on the number of waybills for different logistics tracks in the fillable fields of the form. It categorizes waybills according to different logistics tracks, and places waybills of each category in a separate array. For waybills in each array, it calls the corresponding logistics track upload interface to create waybill logistics tracks based on the required fields of the form.

[0044] Waybill Attribute Assignment Module: This module assigns values ​​to the fillable fields in the form and, based on the assignment results, calls the corresponding interface to assign waybill attributes to waybills containing waybill logistics tracks, thus completing the creation of the waybill.

[0045] According to a third aspect of the present invention, a storage medium is provided, the storage medium storing a computer program, which, when executed by a host controller, implements the steps of the above-described method.

[0046] The technical solutions provided by the embodiments of the present invention may include the following beneficial effects:

[0047] This application involves inserting a plugin into a browser page, where users fill in a form within the plugin. The browser then sends the form to the backend system. The backend system uses this form to create a waybill based on the required fields. Once the waybill is created, it uses the corresponding logistics tracking upload interface to create the logistics tracking information based on the required fields. The system then assigns values ​​to the optional fields and uses the appropriate interfaces to assign waybill attributes to the waybill containing the logistics tracking information, thus completing the waybill creation process. In this application, when creating various waybills, business personnel only need to fill in various information on the browser page, and the backend system automatically generates the waybill based on this information, eliminating the need for additional manual operations and freeing up time for testing and development personnel.

[0048] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the invention. Attached Figure Description

[0049] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0050] Figure 1 This is a flowchart illustrating a method for rapidly generating waybills with different types, according to an exemplary embodiment.

[0051] Figure 2 This is a schematic diagram of a system for rapidly generating waybills with different types, according to an exemplary embodiment.

[0052] In the attached diagram: 1-Form filling module, 2-Waybill creation module, 3-Logistics track creation module, 4-Waybill attribute assignment module. Detailed Implementation

[0053] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.

[0054] Example 1

[0055] Figure 1 This is a flowchart illustrating a method for rapidly generating waybills with different types, according to an exemplary embodiment. Figure 1 As shown, the method includes:

[0056] S1. Fill out a form on the browser front-end page. The form content includes required fields and optional fields.

[0057] S2, the browser sends the form content to the backend system, and the backend system calls the create waybill interface to create a waybill based on the required fields in the form content;

[0058] S3 generates a corresponding number of waybills based on the number of waybills for different logistics trajectories in the fillable fields of the form content. The waybills are classified according to different logistics trajectories, and each type of waybill is placed in a separate array. The corresponding logistics trajectory upload interface is called for the waybills in each array, and the waybill logistics trajectory is created based on the required fields of the form content.

[0059] S4: Assign values ​​to the fillable fields in the form, and based on the assignment results, call the corresponding interface to assign waybill attributes to the waybill containing the waybill logistics trajectory, thus completing the creation of the waybill;

[0060] It is understandable that business personnel currently do not use testing tools to generate data. Testers or developers need to manually create waybills, logistics tracks, problem item types, and value-added item types. This requires the following steps: Open the backend waybill creation system, enter the sender's and recipient's mobile phone numbers, sender and recipient addresses, etc., to create a waybill; Open the backend logistics track creation system, enter the waybill number, select the required logistics track, and create the waybill logistics track; Open the backend problem item creation system, enter the tracking number, select the problem item type, and create a problem item waybill; Open the backend value-added information creation system, enter the tracking number, select the value-added service type, and create the waybill value-added service type; Record the waybill information obtained from the above steps into an Excel file or Notepad for business personnel to use. Since some business scenarios require waybills to be reused after use, the above steps need to be repeated to create new waybills. To avoid testers or developers wasting time during the waybill creation process, this application provides the following technical solution:

[0061] The user opens the Chrome browser, imports the local plugin package in the plugins panel, and then left-clicks to open the plugin. A front-end page appears, containing a form that the user must fill out. The form includes required and optional fields. The browser sends the form content to the back-end system, which calls the waybill creation interface to create waybills based on the required fields. It then generates a corresponding number of waybills based on the number of waybills with different logistics trajectories in the optional fields. The waybills are categorized according to their logistics trajectories, with each category placed in a separate array. For each waybill in the array, the corresponding logistics trajectory upload interface is called to create the waybill logistics trajectory based on the required fields. Finally, values ​​are assigned to the optional fields, and the appropriate interfaces are called for waybills containing logistics trajectories based on the assigned values. This application assigns attributes to waybills to complete waybill creation. It works by inserting a plugin into a browser page, where users fill in a form within the plugin. The browser sends the form to the backend system, which then calls the waybill creation interface based on the required fields. After creation, the system calls the corresponding logistics track upload interface to create the waybill's logistics track based on the required fields. The system then assigns values ​​to the optional fields and, based on these values, calls the appropriate interface to assign waybill attributes to the waybill containing the logistics track, thus completing waybill creation. In this application, when creating various waybills, business personnel only need to fill in information on the browser page, and the backend system automatically generates waybills based on this information, eliminating the need for additional manual operation and freeing up testing and development time.

[0062] Preferably,

[0063] The required fields include: sender and recipient's mobile phone number and address;

[0064] The addresses include the receiving address, sending address, delivery address, and signature address;

[0065] The data entered by the user in the address field must contain at least one address depending on the nature of the waybill;

[0066] The fillable fields include: the number of waybills for different logistics routes and the waybill attributes;

[0067] The waybill attributes include: whether a problem shipment is required, the type of problem shipment, whether value-added services are required, and the type of value-added services.

[0068] When a user leaves the field blank in the form, the backend system automatically assigns a value to the blank field.

[0069] Understandably, the required fields in the form are information that users must fill in, namely the sender's and recipient's mobile phone numbers. These include the recipient's, sender's, recipient's, delivery person's, and signatory's mobile phone numbers. The specific mobile phone numbers included depend on the delivery progress. For example, if the package is in the "arrived" status, then the required fields will include the sender's address, recipient's address, and delivery address; as well as the recipient's, sender's, and recipient's mobile phone numbers. It's worth emphasizing that the "receive-send-arrived-delivered-signature" process refers to logistics and transportation. The process follows a fixed sequence, meaning that if a logistics package is in the "arrived" state, it must have already gone through the receiving and dispatching processes. The fillable fields include: the number of waybills for different logistics trajectories (e.g., 1 waybill for receiving, 2 waybills for dispatching, and 3 waybills for arriving) and waybill attributes. The waybill attributes include: whether a problem package is needed, the type of problem package, whether value-added services are needed, and the type of value-added services. When the user does not fill in the fillable fields in the form, the backend system automatically assigns values ​​to the unfilled fields.

[0070] Preferably,

[0071] The backend system automatically assigns values ​​to unfilled fillable fields, including:

[0072] For the number of waybills in different logistics trajectories, the backend system automatically assigns the number of waybills in each logistics trajectories to 1;

[0073] The backend system automatically assigns a value of 0 to indicate whether a problem component is needed.

[0074] The backend system automatically assigns a value of 0 to whether value-added services are needed.

[0075] Understandably, when a user leaves the form blank for the number of waybills for different routes, the backend system automatically defaults to 1 for each route. Similarly, if the user leaves the form blank for whether a problem shipment is needed, the system automatically assigns a value of 0, where 0 indicates no problem and 1 indicates a problem. The default value of 1 for the waybill quantity above indicates a quantity of 1, which needs to be distinguished. If the user leaves the form blank for whether value-added services are needed, the backend system automatically assigns a value of 0.

[0076] Preferably,

[0077] The process of assigning values ​​to the fillable fields in the form and then, based on the assignment results, calling the corresponding interface to assign waybill attributes to waybills containing waybill logistics trajectories includes:

[0078] If the user fills in "requires problem shipment" in the form, the backend system assigns a value of 1 to whether a problem shipment is needed, obtains the problem shipment type filled in by the user, assigns a corresponding problem shipment type code based on the problem shipment type, and calls the problem shipment system interface to create a problem shipment based on the code, adding the problem shipment attribute to the waybill;

[0079] If the user fills in the form that they need value-added services, the backend system will assign a value of 1 to whether value-added services are needed, obtain the value-added service type filled in by the user, assign a corresponding value-added service type code according to the value-added service type, and call the value-added service system's value-added service creation interface according to the code to add value-added service attributes to the waybill.

[0080] Understandably, the backend retrieves the "Is a problem shipment needed?" field (0 = not needed, 1 = needed, default 0 if not filled in). If a problem shipment is not needed, this step is skipped. If the form indicates a problem shipment is needed, the backend retrieves the problem shipment type entered by the user (e.g., A2 = address unknown, A5 = customer refused delivery, etc.), assembles the message, calls the "Create Problem Shipment" interface of the problem shipment system, and adds the problem shipment attribute to the waybill. Similarly, the backend retrieves the "Is a value-added service needed?" field (0 = not needed, 1 = needed, default 0 if not filled in). If value-added services are not needed, this step is skipped. If the form indicates a value-added service is needed, the backend retrieves the value-added service type entered by the user (e.g., 107 = cash on delivery, 109 = collect on delivery, etc.), assembles the message, calls the "Create Value-Added Service" interface of the value-added service system, and adds the value-added service attribute to the waybill.

[0081] Preferably,

[0082] The types of logistics trajectories include: receipt, dispatch, arrival, delivery, and signature.

[0083] For the logistics tracking of the delivery order, the user fills in the delivery address in the address field of the form;

[0084] For the logistics tracking of the outgoing waybill, the user fills in the recipient address and sender address in the address field of the form;

[0085] For the logistics tracking of a delivery waybill, the user fills in the recipient address, sender address, and destination address in the address field of the form;

[0086] For the logistics tracking of the delivery order, the user fills in the recipient address, sender address, arrival address and delivery address in the address field of the form;

[0087] For the logistics tracking of the signed waybill, the user fills in the recipient address, sender address, arrival address, delivery address and signature address in the address field of the form;

[0088] Understandably, logistics tracking types include receipt, dispatch, arrival, delivery, and signature. The type of logistics tracking determines the type of waybill, which is determined by the address entered by the user. That is, if the user only enters the receipt address, the logistics tracking is a receipt tracking, and the waybill is a receipt waybill. If the user enters both the receipt and dispatch addresses, the logistics tracking is a receipt tracking, and the waybill is a receipt waybill. If the user enters all three addresses, the logistics tracking is an arrival tracking, and the waybill is an arrival waybill.

[0089] Preferably,

[0090] The process involves categorizing waybills based on their logistics trajectories, with each category stored in a separate array. For each waybill in the array, the corresponding logistics trajectory upload interface is called to create the waybill logistics trajectory based on the required fields in the form.

[0091] Based on different logistics routes, waybills are divided into: receipt waybill, dispatch waybill, arrival waybill, delivery waybill, and signed waybill.

[0092] Place waybills of the same type in the same array. For waybills of the same type, call the corresponding logistics track upload interface to traverse all waybills in the array and create a waybill logistics track based on the address entered by the user.

[0093] Understandably, the backend obtains the required number of orders for each different logistics trajectory (e.g., 1 order for receiving trajectory, 2 orders for receiving and sending / receiving trajectory, 1 order for receiving, sending, and arriving trajectory; the default number of orders for each trajectory is 1 if not specified). It then categorizes the created waybills without logistics trajectories (by the type of logistics trajectory, such as sending trajectory, arriving trajectory, etc.) into different arrays. Finally, it calls different logistics trajectory upload interfaces (receiving, sending, arriving, dispatching, signing, etc.) to iterate through these arrays and create logistics trajectories that meet the user's needs.

[0094] Preferably, it further includes:

[0095] After the waybill is created, the data for this waybill creation is stored in the browser's storage, and the time point and waybill number of this waybill creation are displayed on the browser's front-end page.

[0096] The number of waybill data stored in the browser page's Storage is no more than X, and the waybill data is arranged in reverse chronological order of the waybill creation time in Storage;

[0097] When the number of waybill data stored in the browser's storage exceeds X records, the earliest waybill data will be removed according to the waybill creation time. The removed waybill data will be sent to the backend system, and the backend system will store the removed waybill data in the personal storage space of the waybill creator.

[0098] Understandably, after the above steps are completed, the data for this order creation will be stored in Chrome's storage. Storage refers to the browser's storage space, and the time and order number of this order creation will be displayed on the page in the plugin panel. Storage can store a maximum of 10 records, arranged in reverse chronological order of creation time. After more than 10 records are stored, the earliest created order record in the queue will be removed. After removal, the order creation time and the created order number will be sent to the creator's work notification list via a message center call. The historical orders can be found in the work notification later. The plugin panel also provides users with a function to manually clear the data. Clicking clear will clear all historical data.

[0099] Example 2

[0100] Figure 2 This is a schematic diagram of a system for rapidly generating waybills with different types, according to an exemplary embodiment, comprising:

[0101] Form filling module 1: Used to fill in forms on the browser front-end page. The form content includes required fields and optional fields.

[0102] Waybill creation module 2: This module is used when the browser sends the form content to the backend system, and the backend system calls the waybill creation interface to create a waybill based on the required fields in the form content.

[0103] Logistics Track Creation Module 3: This module generates a corresponding number of waybills based on the number of waybills for different logistics tracks in the fillable fields of the form. It categorizes waybills according to different logistics tracks, and places waybills of each category in a separate array. It calls the corresponding logistics track upload interface for waybills in each array and creates waybill logistics tracks based on the required fields of the form.

[0104] Waybill Attribute Assignment Module 4: This module assigns values ​​to the fillable fields in the form and, based on the assignment results, calls the corresponding interface to assign waybill attributes to waybills containing waybill logistics tracing data, thus completing the creation of the waybill.

[0105] Understandably, this application uses a form filling module 1 for filling out a form on the browser front-end page, where the form content includes required and optional fields; a waybill creation module 2 for the browser to send the form content to the back-end system, where the back-end system calls the waybill creation interface to create a waybill based on the required fields of the form content; a logistics trajectory creation module 3 for generating a corresponding number of waybills based on the number of waybills with different logistics trajectories in the optional fields of the form content, classifying waybills according to different logistics trajectories, placing each category of waybills in a separate array, and calling the corresponding logistics trajectory upload interface for each waybill in the array to create a waybill logistics trajectory based on the required fields of the form content; and a waybill attribute assignment module 4 for assigning values ​​to the optional fields of the form content, and calling the corresponding method for waybills containing waybill logistics trajectories based on the assignment results. This application uses an interface to assign waybill attributes, completing the creation of the waybill. It works by inserting a plugin into a browser page, where users fill in the form content within the plugin. The browser sends the form content to the backend system, which then calls the waybill creation interface based on the form content. The backend system creates the waybill based on the required fields. After the waybill is created, it calls the corresponding logistics track upload interface based on the form content, creating the waybill's logistics track based on the required fields. Then, it assigns values ​​to the optional fields in the form and, based on the assignment results, calls the corresponding interface to assign waybill attributes to the waybill containing the logistics track, completing the waybill creation. In this application, when creating various waybills, business personnel only need to fill in various information on the browser page, and the backend system automatically generates the waybill based on this information, eliminating the need for additional manual operation and freeing up testing or development time.

[0106] Example 3:

[0107] This embodiment provides a storage medium storing a computer program, which, when executed by a host controller, implements the various steps in the above method.

[0108] It is understood that the storage medium mentioned above can be a read-only memory, a hard disk, or an optical disk, etc.

[0109] It is understood that the same or similar parts in the above embodiments can be referred to each other, and the contents not described in detail in some embodiments can be referred to the same or similar contents in other embodiments.

[0110] It should be noted that in the description of this invention, the terms "first," "second," etc., are used for descriptive purposes only and should not be construed as indicating or implying relative importance. Furthermore, in the description of this invention, unless otherwise stated, "a plurality of" means at least two.

[0111] Any process or method description in the flowchart or otherwise herein can be understood as representing a module, segment, or portion of code comprising one or more executable instructions for implementing a particular logical function or process, and the scope of the preferred embodiments of the invention includes additional implementations in which functions may be performed not in the order shown or discussed, including substantially simultaneously or in reverse order depending on the functions involved, as will be understood by those skilled in the art to which embodiments of the invention pertain.

[0112] It should be understood that various parts of the present invention can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc.

[0113] Those skilled in the art will understand that all or part of the steps of the methods in the above embodiments can be implemented by a program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, the program includes one or a combination of the steps of the method embodiments.

[0114] Furthermore, the functional units in the various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0115] The storage media mentioned above can be read-only memory, disk, or optical disk, etc.

[0116] In the description of this specification, references to terms such as "one embodiment," "some embodiments," "example," "specific example," or "some examples," etc., indicate that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the invention. In this specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in one or more embodiments or examples.

[0117] Although embodiments of the present invention have been shown and described above, it is understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for rapidly generating waybills with different types, characterized in that, The method includes: Fill out the form on the browser's front-end page. The form includes required fields and optional fields. The browser sends the form content to the backend system, which then calls the waybill creation interface to create a waybill based on the required fields in the form. Generate a corresponding number of waybills based on the number of waybills for different logistics trajectories in the fillable fields of the form content. Classify waybills according to different logistics trajectories, and place waybills of each category in a separate array. Call the corresponding logistics trajectory upload interface for waybills in each array, and create waybill logistics trajectories based on the required fields of the form content. The process involves categorizing waybills based on their logistics trajectories, with each category stored in a separate array. For each waybill in the array, the corresponding logistics trajectory upload interface is called to create the waybill logistics trajectory based on the required fields in the form. Based on different logistics routes, waybills are divided into: receipt waybill, dispatch waybill, arrival waybill, delivery waybill, and signed waybill. Place waybills of the same type in the same array. For waybills of the same type, call the corresponding logistics track upload interface to traverse all waybills in the array and create a waybill logistics track based on the address entered by the user. Assign values ​​to the fillable fields in the form, and based on the assignment results, call the corresponding interface to assign waybill attributes to the waybill containing the waybill logistics trajectory, thus completing the creation of the waybill; The process of assigning values ​​to the fillable fields in the form and then, based on the assignment results, calling the corresponding interface to assign waybill attributes to waybills containing waybill logistics trajectories includes: If the user fills in "requires problem shipment" in the form, the backend system assigns a value of 1 to whether a problem shipment is needed, obtains the problem shipment type filled in by the user, assigns a corresponding problem shipment type code based on the problem shipment type, and calls the problem shipment system interface to create a problem shipment based on the code, adding the problem shipment attribute to the waybill; If the user fills in the form indicating that they need value-added services, the backend system assigns a value of 1 to whether value-added services are needed, obtains the value-added service type filled in by the user, assigns a corresponding value-added service type code based on the value-added service type, and calls the value-added service system's create value-added service interface based on the code to add value-added service attributes to the waybill.

2. The method according to claim 1, characterized in that, The required fields include: sender and recipient's mobile phone number and address; The addresses include the receiving address, sending address, delivery address, and signature address; The data entered by the user in the address field must contain at least one address depending on the nature of the waybill; The fillable fields include: the number of waybills for different logistics routes and the waybill attributes; The waybill attributes include: whether a problem shipment is required, the type of problem shipment, whether value-added services are required, and the type of value-added services. When a user leaves a field blank in a form, the backend system automatically assigns a value to the blank field.

3. The method according to claim 2, characterized in that, The backend system automatically assigns values ​​to unfilled fillable fields, including: For the number of waybills in different logistics trajectories, the backend system automatically assigns the number of waybills in each logistics trajectories to 1; The backend system automatically assigns a value of 0 to indicate whether a problem component is needed. The backend system automatically assigns a value of 0 to whether value-added services are needed.

4. The method according to claim 1, characterized in that, The types of logistics trajectories include: receipt, dispatch, arrival, delivery, and signature. For the logistics tracking of the delivery order, the user fills in the delivery address in the address field of the form; For the logistics tracking of the outgoing waybill, the user fills in the recipient address and sender address in the address field of the form; For the logistics tracking of a shipment, the user fills in the recipient address, sender address, and destination address in the address field of the form; For the logistics tracking of the delivery order, the user fills in the recipient address, sender address, arrival address and delivery address in the address field of the form; For the logistics tracking of the signed waybill, the user fills in the recipient address, sender address, arrival address, delivery address, and signature address in the address field of the form.

5. The method according to claim 1, characterized in that, Also includes: After the waybill is created, the data for this waybill creation is stored in the browser's storage, and the time point and waybill number of this waybill creation are displayed on the browser's front-end page. The number of waybill data stored in the Storage of the browser page is no more than X, and the waybill data is arranged in reverse chronological order of the time the waybill was created in Storage; When the number of waybill data stored in the browser's storage exceeds X records, the earliest waybill data will be removed according to the waybill creation time. The removed waybill data will be sent to the backend system, and the backend system will store the removed waybill data in the personal storage space of the waybill creator.

6. An apparatus for rapidly generating waybills of different types, characterized in that, The device includes: Form filling module: Used to fill out forms on the browser front-end page. The form content includes required fields and optional fields; Waybill creation module: This module is used when the browser sends the form content to the backend system, and the backend system calls the waybill creation interface to create a waybill based on the required fields in the form content. Logistics Track Creation Module: This module generates a corresponding number of waybills based on the number of waybills for different logistics tracks in the fillable fields of the form. It categorizes waybills according to different logistics tracks, and places waybills of each category in a separate array. For waybills in each array, it calls the corresponding logistics track upload interface to create waybill logistics tracks based on the required fields of the form. The process involves categorizing waybills based on their logistics trajectories, with each category stored in a separate array. For each waybill in the array, the corresponding logistics trajectory upload interface is called to create the waybill logistics trajectory based on the required fields in the form. Based on different logistics routes, waybills are divided into: receipt waybill, dispatch waybill, arrival waybill, delivery waybill, and signed waybill. Place waybills of the same type in the same array. For waybills of the same type, call the corresponding logistics track upload interface to traverse all waybills in the array and create a waybill logistics track based on the address entered by the user. Waybill Attribute Assignment Module: This module assigns values ​​to the fillable fields in the form and, based on the assignment results, calls the corresponding interface to assign waybill attributes to waybills containing waybill logistics tracks, thus completing the creation of the waybill. The process of assigning values ​​to the fillable fields in the form and then, based on the assignment results, calling the corresponding interface to assign waybill attributes to waybills containing waybill logistics trajectories includes: If the user fills in "requires problem shipment" in the form, the backend system assigns a value of 1 to whether a problem shipment is needed, obtains the problem shipment type filled in by the user, assigns a corresponding problem shipment type code based on the problem shipment type, and calls the problem shipment system interface to create a problem shipment based on the code, adding the problem shipment attribute to the waybill; If the user fills in the form indicating that they need value-added services, the backend system assigns a value of 1 to whether value-added services are needed, obtains the value-added service type filled in by the user, assigns a corresponding value-added service type code based on the value-added service type, and calls the value-added service system's create value-added service interface based on the code to add value-added service attributes to the waybill.

7. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by the main controller, implements the steps of the method for rapidly generating waybills of different types as described in any one of claims 1-5.

Images