CN117742843B - Method and system for generating delivery service business form - Google Patents
Method and system for generating delivery service business form Download PDFInfo
- Publication number
- CN117742843B CN117742843B CN202410186996.3A CN202410186996A CN117742843B CN 117742843 B CN117742843 B CN 117742843B CN 202410186996 A CN202410186996 A CN 202410186996A CN 117742843 B CN117742843 B CN 117742843B
- Authority
- CN
- China
- Prior art keywords
- delivery
- service
- application
- pairing
- plug
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 42
- 230000006870 function Effects 0.000 claims description 34
- 238000012544 monitoring process Methods 0.000 claims description 6
- 238000012545 processing Methods 0.000 description 5
- 238000012986 modification Methods 0.000 description 4
- 230000004048 modification Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 230000007613 environmental effect Effects 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012795 verification Methods 0.000 description 2
- 238000004891 communication Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 238000012797 qualification Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a method and a system for generating a delivery service business form, wherein the method comprises the following steps: creating a business form template; generating an initial service form, calling an initial engine plug-in to monitor a delivery service application, executing an application task and generating a delivery application form; calling a pairing engine plug-in to execute a pairing task and generating a delivery service form; calling a delivery engine plug-in to execute a delivery task to complete delivery service, and updating the content of a delivery service form according to the execution result of the delivery service; and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in a database as a group of service forms. By tightly combining the form generation with the delivery service business flow, the business forms corresponding to the business steps are automatically generated based on different business form templates, the business form templates are set by using the plug-in mode, and the corresponding business forms are generated, so that the flexibility of the generation of the delivery service business form and the execution efficiency of the business flow are improved.
Description
Technical Field
The application belongs to the technical field of computer data processing, and particularly relates to a method and a system for generating a delivery service business form.
Background
The delivery service platform is a financial service platform for providing a core service of delivery service for the buyer and the seller. The core business comprises trade matching, contract transfer, spot futures delivery, financial service and the like, and also provides peripheral functions such as member management, quotation consultation, warehousing, logistics management and the like. The service platform is characterized in that one or a plurality of databases support service data, each core service corresponds to a group of database forms, taking a three-step service method as an example, at least involving core service steps such as a service application and pairing step, a notification step, a service step and the like, wherein a series of related service forms are designed only aiming at the requirements of each service step on the storage and reading of the service data, and the service form design method and the service steps of the service platform have the following defects in general: (1) Although the service form contains the required data, the service content of the data is unclear, the service form is difficult to maintain, and common maintenance problems such as data redundancy, data adding and deleting errors and the like are easy to occur when the data content of the form is changed under the conditions of service change and upgrading; (2) Form data and matched services are separated to a certain extent, the execution efficiency of the form driving service is low, and the internal service data flow and external service capacity of the platform are weakened; (3) The lack of a flexible and applicable form template is inefficient in generating the same form multiple times of business operations.
The information disclosed in this background section is only for enhancement of understanding of the general background of the application and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person of ordinary skill in the art.
Disclosure of Invention
Aiming at the problems existing in the prior art, the invention provides a method and a system for generating a delivery service business form.
Specifically, the application discloses a method for generating a delivery service business form, which specifically comprises the following steps:
S100, instantiating function engine plug-ins in a delivery service platform background server, and filling access addresses of the generated function engine plug-ins into service form templates corresponding to the function engine plug-ins;
S110, generating an initial service form based on initial data and a service form template, wherein the initial service form comprises an initial engine plug-in; calling an initial engine plug-in an initial service form based on a calling operation to monitor a delivery service application;
s120, when a business party is monitored to generate a delivery application, an initial engine plug-in performs an application task based on delivery application data and generates a delivery application form, wherein the delivery application form comprises a pairing engine plug-in; when the first preset condition is met, calling a pairing engine plug-in a delivery application form to execute a pairing task based on a calling operation;
S130, generating a delivery service form according to the execution result of the pairing task; the delivery service form comprises a delivery engine plug-in, and when the delivery engine plug-in meets a second preset condition, the delivery engine plug-in the delivery service form is called to execute a delivery task based on a calling operation; the delivery task is used for completing delivery service, updating the content of the delivery service form according to the execution result of the delivery service, and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in the database as a group of service forms.
In an embodiment, the calling operation is to acquire the plug-in entity of which the delivery service platform background server has completed the instantiation based on the plug-in access address recorded in the form item of each form and load the plug-in entity into the memory, and execute the plug-in function; and unloading the plug-in after the step of each calling operation is finished, releasing the plug-in entity resources at the same time between the calling party and the background server, and performing invalidation operation on the function engine plug-in instance access address in the service form template.
In an embodiment, in the step S120, the application task is configured to configure the delivery application data, and implement a delivery application operation, including obtaining a delivery application generated by a service party, and initial service form data, analyzing data related to the application, and generating a delivery application form based on the data related to the application and a corresponding service form template;
in the step S120, the pairing task is configured to implement pairing between multiple service parties based on service party service application data; the pairing steps comprise:
S122: acquiring the declared standard warehouse quantity to be delivered and the delivery request parameters in the delivery application form of the seller member, and searching the buyer member matched with the delivery request parameters;
S124: if the number of the proposed delivery intention buyers is smaller than the standard warehouse quantity, executing S126; if the number of the proposed delivery intention buyers holding the warehouse is larger than or equal to the standard warehouse quantity, executing S128;
S126: splitting the first sub-delivery application form corresponding to the paired standard warehouse quantity and the second sub-delivery application form corresponding to the residual standard warehouse quantity according to the buyer warehouse quantity, and generating a notification service form based on delivery data corresponding to the paired standard warehouse quantity in the first sub-delivery application form and a corresponding service form template; converting the second sub-delivery application form into a new initial service form, and executing step S110;
S128: setting the standard warehouse quantity in the delivery application form as the pairing standard warehouse holding quantity, and generating a notification service form based on the delivery data corresponding to the pairing standard warehouse quantity and the corresponding service form template.
In an embodiment, in the step S130, the delivering task includes: monitoring updating content of service operation results executed by both sides in a delivery service form, judging whether both sides fulfill delivery operation, and if the corresponding delivery operation of the buyer meets the requirement, delivering standard warehouse receipt certificates registered and held by the seller to the buyer; respectively recording the signature of the two parties of the service in the delivery end book; and updating the record data based on the delivery process to the delivery service form.
The application also provides a delivery service business form generation system, which comprises:
The form template creation module is used for instantiating the function engine plug-ins in the background server of the delivery service platform and filling the access addresses of the generated function engine plug-ins into the service form templates corresponding to each function engine plug-in;
The initial service form module is used for generating an initial service form based on initial data and a service form template, wherein the initial service form comprises an initial engine plug-in; calling an initial engine plug-in an initial service form based on a calling operation to monitor a delivery service application;
the application and pairing form module is used for generating a delivery application when a service party is monitored, the initial engine plug-in executes an application task based on delivery application data and generates a delivery application form, and the delivery application form comprises a pairing engine plug-in; when the first preset condition is met, calling a pairing engine plug-in a delivery application form to execute a pairing task based on a calling operation;
The delivery service form module is used for generating a delivery service form according to the execution result of the pairing task; the delivery service form comprises a delivery engine plug-in, and when the delivery engine plug-in meets a second preset condition, the delivery engine plug-in the delivery service form is called to execute a delivery task based on a calling operation; the delivery task is used for completing delivery service, updating the content of the delivery service form according to the execution result of the delivery service, and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in the database as a group of service forms.
In an embodiment, the calling operation is to acquire the plug-in entity of which the delivery service platform background server has completed the instantiation based on the plug-in access address recorded in the form item of each form and load the plug-in entity into the memory, and execute the plug-in function; and unloading the plug-in after the step of each calling operation is finished, releasing the plug-in entity resources at the same time between the calling party and the background server, and performing invalidation operation on the function engine plug-in instance access address in the service form template.
In an embodiment, in the applying and pairing form module, the applying task is configured to apply for delivery, so as to implement a delivery operation, including obtaining a delivery application generated by a service party, and initial service form data, analyzing data related to the application, and generating a delivery application form based on the data related to the application and a corresponding service form template;
In an embodiment, in the applying and pairing form module, the pairing task is configured to implement pairing between a plurality of service parties based on service party service application data, and includes the following modules:
The standard warehouse quantity determining module is used for acquiring the declared standard warehouse quantity to be delivered and the delivery request parameters in the delivery application form of the seller member and searching the buyer member matched with the delivery request parameters;
the buyer holding quantity judging module is used for judging: if the number of the proposed delivery intention buyers holding the warehouse is smaller than the standard warehouse number, calling a split pairing module; if the number of the proposed delivery intention buyers holding the warehouse is larger than or equal to the standard warehouse list, a direct pairing module is called;
The splitting and pairing module is used for splitting the first sub-delivery application form corresponding to the pairing standard warehouse quantity and the second sub-delivery application form corresponding to the residual standard warehouse quantity according to the buyer holding warehouse quantity, and generating a notification service form based on delivery data corresponding to the pairing standard warehouse quantity in the first sub-delivery application form and the corresponding service form template; converting the second sub-delivery application form into a new initial service form, and calling the initial service form module;
And the direct pairing module is used for setting the standard warehouse quantity in the delivery application form as the pairing standard warehouse holding quantity and generating a notification service form based on the delivery data corresponding to the pairing standard warehouse quantity and the corresponding service form template.
In an embodiment, in the delivery service form module, the delivery task is: monitoring updating content of service operation results executed by both sides in a delivery service form, judging whether both sides fulfill delivery operation, and if the corresponding delivery operation of the buyer meets the requirement, delivering standard warehouse receipt certificates registered and held by the seller to the buyer; respectively recording the signature of the two parties of the service in the delivery end book; and finally updating the record data based on the delivery process to the delivery service form.
The invention can at least achieve the following effects by adopting the method or the system: (1) The form data is derived from the business process, so that the form data is naturally and closely related to business content, the form generation and the business process of the delivery service are closely combined, business forms corresponding to business steps are automatically generated based on different business form templates, the business forms are automatically updated based on business propulsion, and the flexibility of the generation of the business forms of the delivery service and the execution efficiency of the business processes are improved; (2) Setting up a business form template innovatively, generating a corresponding business form based on the template, processing form data by using a plug-in mode, wherein different forms correspond to plug-ins for executing different task contents, driving delivery service business processes to advance based on the form data, and further combining each business process with the form data to improve the business execution efficiency.
Drawings
FIG. 1 is a flowchart of a method for generating a delivery service form according to an embodiment of the present invention;
Fig. 2 is a block diagram of a delivery service form generating system according to an embodiment of the present invention.
Detailed Description
The present application will be described in detail below with reference to the embodiments shown in the drawings. The embodiments are not intended to limit the application, but structural, methodological, or functional modifications of the application from those skilled in the art are included within the scope of the application.
The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the application described herein may be implemented, for example, in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "includes" and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.
Embodiment one: as shown in fig. 1, the present invention provides a method for generating a delivery service form, which specifically includes:
and S100, instantiating function engine plug-ins in a delivery service platform background server, and filling the access addresses of the generated function engine plug-ins into the service form templates corresponding to each function engine plug-in.
The business form templates are used to generate business forms, and different businesses correspond to different business form templates. In addition to determining the corresponding service form template, the premise of generating the service form is that each service data of the service corresponding to the service form needs to be acquired in advance, so each service form should be prepared with the corresponding service form template and the service data, for example, the initial service form is generated based on the initial data and the service form template.
Each type of form is provided with at least one functional engine plug-in, and the engine plug-in is used for executing corresponding tasks and driving the delivery service flow to execute. Before generating the form, the delivery service platform background server instantiates each functional plug-in, and fills the access address of the generated plug-in instance into the service form template corresponding to the form where each functional plug-in is located, so that when the service form is generated, a call interface of the corresponding plug-in capable of processing the form is obtained based on the service form template. The calling operation is to acquire the plug-in entity which is already instantiated by the background server of the delivery service platform based on the plug-in access address recorded in the form item of each form and load the plug-in entity into a memory to execute the plug-in function; and unloading the plug-in after the step of each calling operation is finished, releasing the plug-in entity resources at the same time between the calling party and the background server, and performing invalidation operations such as clearing, setting identification bits and the like on the function engine plug-in instance access address in the service form template. And executing and processing form data by using a plug-in mode, wherein different forms correspond to plug-ins executing different task contents, driving the delivery service business processes to advance based on the form data, further combining each business process with the form data, and improving the business execution efficiency.
S110, generating an initial service form based on initial data and a service form template, wherein the initial service form comprises an initial engine plug-in; calling an initial engine plug-in an initial service form based on a calling operation to monitor a delivery service application;
The business starts to collect initial data including various situations such as the participating users of each party having registered data, user related basic data, etc. on the delivery service platform, business related data, request data, service data, etc. The initial service form is specifically generated based on which materials, and needs to be specifically preset according to service contents, wherein the preset contents are embodied in each content item in the service form template.
The initial business form typically stores basic information of the delivery service including, but not limited to, participant basic information, current status information, platform data, and the like. Including but not limited to, participant company data, standard branding data, credit data, domain data, historical transaction data, rating data, and the like. The basic data stored in the initial business form at least contains necessary data for delivering services. The initial service form is provided with an initial engine plug-in, and the initial engine plug-in the initial service form is called based on the calling operation to monitor the delivery service application.
S120, when a business party is monitored to generate a delivery application, an initial engine plug-in performs an application task based on delivery application data and generates a delivery application form, wherein the delivery application form comprises a pairing engine plug-in; when the first preset condition is met, calling a pairing engine plug-in a delivery application form to execute a pairing task based on a calling operation;
in the embodiment of the present application, in the step S120, the application task is configured to apply for delivery, so as to implement a delivery application operation, including obtaining a delivery application generated by a service party, and initial service form data, analyzing data related to the application, and generating a delivery application form based on the data related to the application and a corresponding service form template;
After the buyer initiates a delivery application through a service interface, an initial engine plug-in monitors that a service party generates the delivery application, submits the application to a platform and executes related application tasks, performs security authentication on the delivery application and the platform environment, performs identity authentication and qualification authentication on a participant, determines the condition of a registered warehouse, determines the basic condition of goods, fixes a standard warehouse of the buyer, determines the goods variety, the transaction amount and other data of the requested delivery, configures delivery application data, completes the application tasks of delivery service, and generates a corresponding delivery application form. The data are obtained from the initial service form data, and the service request form is generated by combining the corresponding service form template by analyzing the service request generated by the service party. In addition, the application step can be modified reasonably according to different service conditions. And setting a first preset condition provides service preconditions and environmental protection for the delivery pairing. For example, the first preset condition may be that the terminal environment security authentication of the delivery service platform passes; the service application party completes the warehousing of goods, the quality verification and the submission of standard warehouse receipt to the platform; as well as other business premises and environmental guarantees. The present application is not limited herein, as those skilled in the art can reasonably modify the setting rules of the first preset condition based on the service requirement.
The delivery application involves a pairing of parties to a delivery, and the pairing step should be performed after the delivery application form is generated. In one embodiment, a pairing engine plug-in is set in the delivery application form, and the pairing engine plug-in the delivery application form is called to execute a pairing task based on a calling operation; the pairing task may be performed, for example, by:
S122: acquiring the declared standard warehouse quantity to be delivered and the delivery request parameters in the delivery application form of the seller member, and searching the buyer member matched with the delivery request parameters;
before searching for the buyer members, the buyer data set is used as a pairing search pool, the object of the buyer members is filtered based on the delivery requirement parameters in the seller member delivery application form, and the delivery intention of the buyer is determined among the buyer members matched with the delivery requirement parameters.
S124: if the number of the proposed delivery intention buyers is smaller than the standard warehouse quantity, executing S116; if the number of the proposed delivery intention buyers is greater than or equal to the standard warehouse-order number, executing S118;
different pairing modes adopted for matching results of different degrees are shown for splitting treatment of the forms, but the same forms are uniformly generated, so that the efficient treatment of subsequent steps is facilitated.
S126: splitting the first sub-delivery application form corresponding to the paired standard warehouse quantity and the second sub-delivery application form corresponding to the residual standard warehouse quantity according to the buyer warehouse quantity, and generating a notification service form based on delivery data corresponding to the paired standard warehouse quantity in the first sub-delivery application form and a corresponding service form template; converting the second sub-delivery application form into a new initial service form, and executing step S100;
s128: setting the standard warehouse quantity in the delivery application form as the pairing standard warehouse holding quantity, and generating a notification service form based on the delivery data corresponding to the pairing standard warehouse quantity and the corresponding service form template;
In the step of pairing, if the buyer is proposed to hold the number of bins equal to or greater than the standard warehouse count, the buyer data is modified and the buyer data is returned to the pairing search pool again based on the currently matched transaction amount.
S130, generating a delivery service form according to the execution result of the pairing task; the delivery service form comprises a delivery engine plug-in, and when the delivery engine plug-in meets a second preset condition, the delivery engine plug-in the delivery service form is called to execute a delivery task based on a calling operation; the delivery task is used for completing delivery service, updating the content of the delivery service form according to the execution result of the delivery service, and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in the database as a group of service forms.
The pairing task completes pairing of the two transaction parties, data materials related to pairing are obtained, a delivery service form is generated by combining the corresponding service form template, the delivery service form accesses a delivery engine plug-in instance, and the delivery service related operation is executed.
In an embodiment, in the step S130, the delivering task includes: monitoring updating content of service operation results executed by both sides in a delivery service form, judging whether both sides fulfill delivery operation, and if the corresponding delivery operation of the buyer meets the requirement, delivering standard warehouse receipt certificates registered and held by the seller to the buyer; after receiving the standard warehouse receipt, the buyer should pay for the payment, request to issue a delivery invoice, check and accept the delivery goods, pick up the delivery logistics and other delivery matters within a specified time; after acceptance, the signatures of both business parties in the delivery end book are recorded respectively, so that the delivery task is completed, and the record data based on the delivery process is updated to the delivery business form. The content recorded in the delivery service form may be modified reasonably based on actual service requirements.
In one embodiment, after completing a service flow of a delivery service, the delivery service platform correspondingly generates a series of delivery service forms, and the forms are stored as service credentials to the delivery service platform data, and the delivery service platform data binds and stores a set of service forms, so that an initial service form, a delivery application form and an updated delivery service form can be used as a set of service forms for binding; when the business flow is abnormal, a plurality of forms can be lacked, and abnormal handling record forms are added to record abnormal reasons and handling records; and when the business process is newly added, adding a business form corresponding to the new business process. Preferably, the delivery service platform performs data signature on a group of service forms which are fixedly stored as important certificates, and when the group of service forms need to be accessed or modified, signature verification of service parties needs to be obtained; further, each visit and modification has evidence. Based on the means, the credential data is prevented from being illegally accessed or modified, and is generally applied to scenes such as business tracing, transaction evidence, business withdrawal, transaction data analysis and the like.
Embodiment two: as shown in fig. 2, the present invention further provides a delivery service form generating system, including:
The form template creation module is used for instantiating the function engine plug-ins in the background server of the delivery service platform and filling the access addresses of the generated function engine plug-ins into the service form templates corresponding to each function engine plug-in;
The initial service form module is used for generating an initial service form based on initial data and a service form template, wherein the initial service form comprises an initial engine plug-in; calling an initial engine plug-in an initial service form based on a calling operation to monitor a delivery service application;
the application and pairing form module is used for generating a delivery application when a service party is monitored, the initial engine plug-in executes an application task based on delivery application data and generates a delivery application form, and the delivery application form comprises a pairing engine plug-in; when the first preset condition is met, calling a pairing engine plug-in a delivery application form to execute a pairing task based on a calling operation;
The delivery service form module is used for generating a delivery service form according to the execution result of the pairing task; the delivery service form comprises a delivery engine plug-in, and when the delivery engine plug-in meets a second preset condition, the delivery engine plug-in the delivery service form is called to execute a delivery task based on a calling operation; the delivery task is used for completing delivery service, updating the content of the delivery service form according to the execution result of the delivery service, and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in the database as a group of service forms.
In an embodiment, the calling operation is to acquire the plug-in entity of which the delivery service platform background server has completed the instantiation based on the plug-in access address recorded in the form item of each form and load the plug-in entity into the memory, and execute the plug-in function; and unloading the plug-in after the step of each calling operation is finished, releasing the plug-in entity resources at the same time between the calling party and the background server, and performing invalidation operation on the function engine plug-in instance access address in the service form template.
In an embodiment, in the applying and pairing form module, the applying task is configured to apply for delivery, so as to implement a delivery operation, including obtaining a delivery application generated by a service party, and initial service form data, analyzing data related to the application, and generating a delivery application form based on the data related to the application and a corresponding service form template;
In an embodiment, in the applying and pairing form module, the pairing task is configured to implement pairing between a plurality of service parties based on service party service application data, and includes the following modules:
The standard warehouse quantity determining module is used for acquiring the declared standard warehouse quantity to be delivered and the delivery request parameters in the delivery application form of the seller member and searching the buyer member matched with the delivery request parameters;
the buyer holding quantity judging module is used for judging: if the number of the proposed delivery intention buyers holding the warehouse is smaller than the standard warehouse number, calling a split pairing module; if the number of the proposed delivery intention buyers holding the warehouse is larger than or equal to the standard warehouse list, a direct pairing module is called;
The splitting and pairing module is used for splitting the first sub-delivery application form corresponding to the pairing standard warehouse quantity and the second sub-delivery application form corresponding to the residual standard warehouse quantity according to the buyer holding warehouse quantity, and generating a notification service form based on delivery data corresponding to the pairing standard warehouse quantity in the first sub-delivery application form and the corresponding service form template; converting the second sub-delivery application form into a new initial service form, and calling the initial service form module;
And the direct pairing module is used for setting the standard warehouse quantity in the delivery application form as the pairing standard warehouse holding quantity and generating a notification service form based on the delivery data corresponding to the pairing standard warehouse quantity and the corresponding service form template.
In an embodiment, in the delivery service form module, the delivery task is: monitoring updating content of service operation results executed by both sides in a delivery service form, judging whether both sides fulfill delivery operation, and if the corresponding delivery operation of the buyer meets the requirement, delivering standard warehouse receipt certificates registered and held by the seller to the buyer; respectively recording the signature of the two parties of the service in the delivery end book; and finally updating the record data based on the delivery process to the delivery service form.
The invention can at least achieve the following effects by adopting the method or the system: (1) The form data is derived from the business process, so that the form data is naturally and closely related to business content, the form generation and the business process of the delivery service are closely combined, business forms corresponding to business steps are automatically generated based on different business form templates, the business forms are automatically updated based on business propulsion, and the flexibility of the generation of the business forms of the delivery service and the execution efficiency of the business processes are improved; (2) Setting up a business form template innovatively, generating a corresponding business form based on the template, processing form data by using a plug-in mode, wherein different forms correspond to plug-ins for executing different task contents, driving delivery service business processes to advance based on the form data, and further combining each business process with the form data to improve the business execution efficiency.
According to one embodiment, a program product, such as a machine-readable medium, is provided. The machine-readable medium may have instructions (i.e., the elements described above implemented in software) that, when executed by a machine, cause the machine to perform the various operations and functions described above in connection with fig. 1 in various embodiments of the specification. In particular, a system or apparatus provided with a readable storage medium having stored thereon software program code implementing the functions of any of the above embodiments may be provided, and a computer or processor of the system or apparatus may be caused to read out and execute instructions stored in the readable storage medium.
In this case, the program code itself read from the readable medium may implement the functions of any of the above embodiments, and thus the machine-readable code and the readable storage medium storing the machine-readable code form part of the present specification.
Examples of readable storage media include floppy disks, hard disks, magneto-optical disks, optical disks (e.g., CD-ROMs, CD-R, CD-RWs, DVD-ROMs, DVD-RAMs, DVD-RWs), magnetic tapes, nonvolatile memory cards, and ROMs. Alternatively, the program code may be downloaded from a server computer or cloud by a communications network.
It will be appreciated by those skilled in the art that various changes and modifications can be made to the embodiments disclosed above without departing from the spirit of the invention. Accordingly, the scope of protection of this specification should be limited by the attached claims.
It should be noted that not all the steps and units in the above flowcharts and the system configuration diagrams are necessary, and some steps or units may be omitted according to actual needs. The order of execution of the steps is not fixed and may be determined as desired. The apparatus structures described in the above embodiments may be physical structures or logical structures, that is, some units may be implemented by the same physical client, or some units may be implemented by multiple physical clients, or may be implemented jointly by some components in multiple independent devices.
In the above embodiments, the hardware units or modules may be implemented mechanically or electrically. For example, a hardware unit, module or processor may include permanently dedicated circuitry or logic (e.g., a dedicated processor, FPGA or ASIC) to perform the corresponding operations. The hardware unit or processor may also include programmable logic or circuitry (e.g., a general purpose processor or other programmable processor) that may be temporarily configured by software to perform the corresponding operations. The particular implementation (mechanical, or dedicated permanent, or temporarily set) may be determined based on cost and time considerations.
The detailed description set forth above in connection with the appended drawings describes exemplary embodiments, but does not represent all embodiments that may be implemented or fall within the scope of the claims. The term "exemplary" used throughout this specification means "serving as an example, instance, or illustration," and does not mean "preferred" or "advantageous over other embodiments. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described embodiments.
The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (6)
1. A method for generating a delivery service business form, the method comprising:
S100, instantiating function engine plug-ins in a delivery service platform background server, and filling access addresses of the generated function engine plug-ins into service form templates corresponding to the function engine plug-ins;
S110, generating an initial service form based on initial data and a service form template, wherein the initial service form comprises an initial engine plug-in; calling an initial engine plug-in an initial service form based on a calling operation to monitor a delivery service application;
s120, when a business party is monitored to generate a delivery application, an initial engine plug-in performs an application task based on delivery application data and generates a delivery application form, wherein the delivery application form comprises a pairing engine plug-in; when the first preset condition is met, calling a pairing engine plug-in a delivery application form to execute a pairing task based on a calling operation;
S130, generating a delivery service form according to the execution result of the pairing task; the delivery service form comprises a delivery engine plug-in, and when the delivery engine plug-in meets a second preset condition, the delivery engine plug-in the delivery service form is called to execute a delivery task based on a calling operation; the delivery task is used for completing delivery service, updating the content of the delivery service form according to the execution result of the delivery service, and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in a database as a group of service forms;
The calling operation is to acquire the instantiated plug-in entity of the delivery service platform background server based on the plug-in access address recorded in the form item of each form, load the plug-in entity into a memory and execute the plug-in function; unloading the plug-in after the step of each calling operation is finished, releasing the plug-in entity resource at the same time between the calling party and the background server, and performing invalidation operation on the function engine plug-in instance access address in the service form template;
in the step S120, the pairing task is configured to implement pairing between multiple service parties based on service party service application data; the pairing steps comprise:
S122: acquiring the declared standard warehouse quantity to be delivered and the delivery request parameters in the delivery application form of the seller member, and searching the buyer member matched with the delivery request parameters;
S124: if the number of the proposed delivery intention buyers is smaller than the standard warehouse quantity, executing S126; if the number of the proposed delivery intention buyers holding the warehouse is larger than or equal to the standard warehouse quantity, executing S128;
S126: splitting the first sub-delivery application form corresponding to the paired standard warehouse quantity and the second sub-delivery application form corresponding to the residual standard warehouse quantity according to the buyer warehouse quantity, and generating a notification service form based on delivery data corresponding to the paired standard warehouse quantity in the first sub-delivery application form and a corresponding service form template; converting the second sub-delivery application form into a new initial service form, and executing step S110;
S128: setting the standard warehouse quantity in the delivery application form as the pairing standard warehouse holding quantity, and generating a notification service form based on the delivery data corresponding to the pairing standard warehouse quantity and the corresponding service form template.
2. The method for generating a delivery service form according to claim 1, wherein in the step S120, the application task is configured to configure delivery application data to implement a delivery application operation, and the delivery application operation includes obtaining a delivery application generated by a service party, initial service form data, analyzing data related to the delivery application therefrom, and generating a delivery application form based on the data related to the delivery application and a corresponding service form template.
3. The delivery service form generation method according to claim 1, wherein in the step S130, the delivery task includes: monitoring updating content of service operation results executed by both sides in a delivery service form, judging whether both sides fulfill delivery operation, and if the corresponding delivery operation of the buyer meets the requirement, delivering standard warehouse receipt certificates registered and held by the seller to the buyer; respectively recording the signature of the two parties of the service in the delivery end book; and updating the record data based on the delivery process to the delivery service form.
4. A delivery service business form generation system, comprising:
The form template creation module is used for instantiating the function engine plug-ins in the background server of the delivery service platform and filling the access addresses of the generated function engine plug-ins into the service form templates corresponding to each function engine plug-in;
The initial service form module is used for generating an initial service form based on initial data and a service form template, wherein the initial service form comprises an initial engine plug-in; calling an initial engine plug-in an initial service form based on a calling operation to monitor a delivery service application;
the application and pairing form module is used for generating a delivery application when a service party is monitored, the initial engine plug-in executes an application task based on delivery application data and generates a delivery application form, and the delivery application form comprises a pairing engine plug-in; when the first preset condition is met, calling a pairing engine plug-in a delivery application form to execute a pairing task based on a calling operation;
The delivery service form module is used for generating a delivery service form according to the execution result of the pairing task; the delivery service form comprises a delivery engine plug-in, and when the delivery engine plug-in meets a second preset condition, the delivery engine plug-in the delivery service form is called to execute a delivery task based on a calling operation; the delivery task is used for completing delivery service, updating the content of the delivery service form according to the execution result of the delivery service, and storing the binding relation of the initial service form, the delivery application form and the updated delivery service form in a database as a group of service forms;
The calling operation is to acquire the instantiated plug-in entity of the delivery service platform background server based on the plug-in access address recorded in the form item of each form, load the plug-in entity into a memory and execute the plug-in function; unloading the plug-in after the step of each calling operation is finished, releasing the plug-in entity resource at the same time between the calling party and the background server, and performing invalidation operation on the function engine plug-in instance access address in the service form template;
In the application and pairing form module, the pairing task is used for realizing the pairing of the service parties based on the service party pairing application data, and the pairing task comprises the following modules:
The standard warehouse quantity determining module is used for acquiring the declared standard warehouse quantity to be delivered and the delivery request parameters in the delivery application form of the seller member and searching the buyer member matched with the delivery request parameters;
the buyer holding quantity judging module is used for judging: if the number of the proposed delivery intention buyers holding the warehouse is smaller than the standard warehouse number, calling a split pairing module; if the number of the proposed delivery intention buyers holding the warehouse is larger than or equal to the standard warehouse list, a direct pairing module is called;
The splitting and pairing module is used for splitting the first sub-delivery application form corresponding to the pairing standard warehouse quantity and the second sub-delivery application form corresponding to the residual standard warehouse quantity according to the buyer holding warehouse quantity, and generating a notification service form based on delivery data corresponding to the pairing standard warehouse quantity in the first sub-delivery application form and the corresponding service form template; converting the second sub-delivery application form into a new initial service form, and calling the initial service form module;
And the direct pairing module is used for setting the standard warehouse quantity in the delivery application form as the pairing standard warehouse holding quantity and generating a notification service form based on the delivery data corresponding to the pairing standard warehouse quantity and the corresponding service form template.
5. The delivery service form generation system of claim 4, wherein in the application and pairing form module, the application task is configured to apply for delivery data, and implement a delivery application operation, where the delivery application operation includes obtaining a delivery application generated by a service party, and initial service form data, analyzing data related to the delivery application therefrom, and generating a delivery application form based on the data related to the delivery application and a corresponding service form template.
6. The delivery service form generation system of claim 4 wherein in the delivery service form module, the delivery tasks comprise: monitoring updating content of service operation results executed by both sides in a delivery service form, judging whether both sides fulfill delivery operation, and if the corresponding delivery operation of the buyer meets the requirement, delivering standard warehouse receipt certificates registered and held by the seller to the buyer; respectively recording the signature of the two parties of the service in the delivery end book; and updating the record data based on the delivery process to the delivery service form.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410186996.3A CN117742843B (en) | 2024-02-20 | 2024-02-20 | Method and system for generating delivery service business form |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410186996.3A CN117742843B (en) | 2024-02-20 | 2024-02-20 | Method and system for generating delivery service business form |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117742843A CN117742843A (en) | 2024-03-22 |
| CN117742843B true CN117742843B (en) | 2024-06-04 |
Family
ID=90261286
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410186996.3A Active CN117742843B (en) | 2024-02-20 | 2024-02-20 | Method and system for generating delivery service business form |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117742843B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN118037405B (en) * | 2024-04-12 | 2024-06-21 | 张家港保税数据科技有限公司 | Lightweight dynamic delivery service method and system |
| CN119558288B (en) * | 2025-01-26 | 2025-07-29 | 张家港保税数据科技有限公司 | Method and system for generating delivery service business form |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001078493A2 (en) * | 2000-04-17 | 2001-10-25 | Verisign, Inc. | Authenticated payment |
| CN109658289A (en) * | 2018-12-13 | 2019-04-19 | 大连飞创信息技术有限公司 | Off-site market comprehensive service platform |
| CN112116469A (en) * | 2020-06-28 | 2020-12-22 | 上海金融期货信息技术有限公司 | Memory-based multi-exchange full-service clearing system and method |
| CN112465620A (en) * | 2020-12-30 | 2021-03-09 | 广东金赋科技股份有限公司 | Terminal form filling service linkage method and device based on dynamic form and rule engine |
| CN114598656A (en) * | 2022-05-09 | 2022-06-07 | 张家港保税科技集团电子商务有限公司 | Load balancing method and system applied to delivery service platform |
| CN114862393A (en) * | 2022-05-18 | 2022-08-05 | 张家港保税科技集团电子商务有限公司 | Safe transaction pairing method and system under delivery service platform |
| CN116934065A (en) * | 2023-06-29 | 2023-10-24 | 重庆长安汽车股份有限公司 | Business management method and device based on flow engine |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20070288327A1 (en) * | 2006-06-13 | 2007-12-13 | Valentina Pulnikova | System and method of global electronic trade in the internet |
-
2024
- 2024-02-20 CN CN202410186996.3A patent/CN117742843B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2001078493A2 (en) * | 2000-04-17 | 2001-10-25 | Verisign, Inc. | Authenticated payment |
| CN109658289A (en) * | 2018-12-13 | 2019-04-19 | 大连飞创信息技术有限公司 | Off-site market comprehensive service platform |
| CN112116469A (en) * | 2020-06-28 | 2020-12-22 | 上海金融期货信息技术有限公司 | Memory-based multi-exchange full-service clearing system and method |
| CN112465620A (en) * | 2020-12-30 | 2021-03-09 | 广东金赋科技股份有限公司 | Terminal form filling service linkage method and device based on dynamic form and rule engine |
| CN114598656A (en) * | 2022-05-09 | 2022-06-07 | 张家港保税科技集团电子商务有限公司 | Load balancing method and system applied to delivery service platform |
| CN114862393A (en) * | 2022-05-18 | 2022-08-05 | 张家港保税科技集团电子商务有限公司 | Safe transaction pairing method and system under delivery service platform |
| CN116934065A (en) * | 2023-06-29 | 2023-10-24 | 重庆长安汽车股份有限公司 | Business management method and device based on flow engine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117742843A (en) | 2024-03-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN117742843B (en) | Method and system for generating delivery service business form | |
| CN112766907B (en) | Service data processing method, device and server | |
| US20180039770A1 (en) | Multi-Factor Profile and Security Fingerprint Analysis | |
| US20060041505A1 (en) | Fee-based message delivery system | |
| WO2019019750A1 (en) | Annuity management system and method, server, and storage medium | |
| CN110910230A (en) | Accounting method, accounting system and storage medium | |
| US20120278513A1 (en) | Priority scheduling for multi-channel context aware communication technology | |
| WO2019019447A1 (en) | Annuity data processing method and device, server and storage medium | |
| WO2018210097A1 (en) | Method and device for execution transaction mode by classification | |
| CN112685391A (en) | Service data migration method and device, computer equipment and storage medium | |
| CN113724077A (en) | Loan approval method, device and system | |
| WO2024060759A1 (en) | Supply chain financial asset auditing method and apparatus, and device and medium | |
| CN111709709A (en) | Information processing method, system and computer equipment based on factoring business | |
| CN111145031A (en) | A kind of insurance business customization method, device and system | |
| CN115564356A (en) | Real-time sharing method and device for relatives and friends logistics order information | |
| US20180060379A1 (en) | Automated correlation and deduplication of identities | |
| US11606425B2 (en) | Visibility of digital assets at channel level | |
| CA2970301C (en) | Improved network for onboarding and delivery of electronic payments to payees | |
| US20080244518A1 (en) | Telecom Business-Oriented Taxonomy for Reusable Services | |
| CN110348843A (en) | Resource integrated method, device, computer installation and storage medium | |
| EP3005255A1 (en) | Using commerce networks to facilitate business interactions among entities | |
| CN114971907A (en) | Service providing method and device based on block chain and 5G message | |
| EP2601627B1 (en) | Transaction processing system and method | |
| CN115330365A (en) | Data processing method and device based on block chain and computer equipment | |
| CN113824847A (en) | Method and device for determining charging abnormity, computing equipment and computer storage medium |
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 | ||
| GR01 | Patent grant |