CN113609831A

CN113609831A - Method and device for generating product delivery flow template

Info

Publication number: CN113609831A
Application number: CN202110897160.0A
Authority: CN
Inventors: 周子雄
Original assignee: Beijing Jindi Technology Co Ltd
Current assignee: Beijing Jindi Technology Co Ltd
Priority date: 2021-08-05
Filing date: 2021-08-05
Publication date: 2021-11-05

Abstract

Embodiments of the present disclosure provide a method and an apparatus for generating a product delivery flow template, a computer-readable storage medium, an electronic device, and a computer program. The method comprises the following steps: acquiring a basic configuration template of a target product; adding custom nodes experienced in the delivery flow of the target product on the basic configuration template based on the custom node adding operation initiated by the target product provider; and generating a target product delivery flow template containing the self-defined nodes based on the basic configuration template. The technical scheme of the present disclosure can effectively realize that the product provider customizes the delivery rule according to the characteristics of different products aiming at various customized delivery scenes. The stability of the product delivery process is met, the customizability of the process is guaranteed, and the product delivery efficiency and the transparency of the process are improved.

Description

Method and device for generating product delivery flow template

Technical Field

The present disclosure relates to the field of computer technologies, and in particular, to a method and an apparatus for generating a product delivery flow template, an electronic device, a computer-readable storage medium, and a computer program.

Background

The current online shopping products mainly check the delivery progress of commodities through each platform, and the mode of the delivery progress is mainly embodied as two modes: the system comprises a fixed mode, namely a physical commodity delivery mode, wherein key links such as payment, delivery, receiving, goods returning and changing, completion and the like are arranged on main link nodes, and various commodities are delivered in the same mode. And secondly, in the process mode, all delivery link users do not need to participate, the delivery steps are checked only as a process node, for example, the logistics express delivery progress can be displayed by each stage node, but the process is only limited to the logistics company processing process, and the users do not need to participate. However, the current mode has limitations, and various virtual goods and customized services are increasingly appearing in the actual production life, and in the commodity delivery link, a user and a merchant need to negotiate to establish rules together, or the user needs to participate in the rules (for example, delivery of various raw materials, or necessary agreement signing in the process). Firstly, the problem that the delivery process occurs is solved offline, the problems of low efficiency and opaque progress exist, and a large amount of manual intervention and work such as information recording and tracking are needed. Secondly, the customized development delivery process has a problem of high cost, and some scenes with a large demand and stable specialized processes try to use the scheme.

Disclosure of Invention

The present disclosure is directed to a method and an apparatus for generating a product delivery flow template, an electronic device, a computer-readable storage medium, and a computer program, so as to solve at least some of the technical problems described in the foregoing background.

Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.

According to a first aspect of the present disclosure, there is provided a method for generating a product delivery flow template, including: acquiring a basic configuration template of a target product; adding custom nodes experienced in the delivery flow of the target product on the basic configuration template based on the custom node adding operation initiated by the target product provider; and generating a target product delivery flow template containing the self-defined nodes based on the basic configuration template.

In an exemplary embodiment of the present disclosure, the method further comprises: receiving configuration information input by a target product provider and/or a target product user on an interface of a user-defined node; in response to determining that the configuration information input is complete, the custom node containing the configuration information is stored.

In an exemplary embodiment of the disclosure, after generating the target product delivery flow template containing the custom node, the method further comprises: generating a version number of the target product delivery flow template; in response to the target product user submitting the target product order based on the target product delivery flow template, the target product order is bound to the version number.

In an exemplary embodiment of the present disclosure, the method further comprises: updating the version number of the target product delivery flow template in response to the target product provider modifying the nodes included in the target product delivery flow template; and binding the new target product order with the updated version number in response to the new target product order submitted by the target product user based on the target product delivery flow template with the updated version number.

In an exemplary embodiment of the present disclosure, the configuration information includes at least one of: node operation authority configuration information, node type configuration information, node handling time configuration information, node name configuration information and node jump name configuration information.

In an exemplary embodiment of the present disclosure, storing a custom node containing configuration information includes: and storing the self-defined nodes containing the configuration information into a preset non-relational database.

In an exemplary embodiment of the disclosure, generating a target product delivery flow template containing custom nodes based on a base configuration template comprises: generating a state machine representing the execution sequence among the nodes based on the user-defined nodes and the basic nodes included in the basic configuration template; checking the state machine, and determining the execution sequence of the nodes included in the target product delivery flow template; and generating a target product delivery flow template based on the nodes after the execution sequence is determined.

According to a second aspect of the present disclosure, there is provided a generation apparatus of a product delivery flow template, including:

the acquisition module is used for acquiring a basic configuration template of a target product; the adding module is used for adding the custom nodes experienced in the delivery flow of the target product on the basis of the custom node adding operation initiated by the target product provider; and the generating module is used for generating a target product delivery flow template containing the self-defined nodes based on the basic configuration template.

In an exemplary embodiment of the present disclosure, the apparatus further includes: the receiving module is used for receiving configuration information input by a target product provider and/or a target product user at a custom node; and the first storage module is used for responding to the confirmation of the input of the configuration information and storing the self-defining node containing the configuration information.

In an exemplary embodiment of the present disclosure, the apparatus further includes: the second storage module is used for generating the version number of the target product delivery flow template; and the first binding module is used for binding the target product order with the version number in response to the target product user submitting the target product order based on the target product delivery flow template.

In an exemplary embodiment of the present disclosure, the apparatus further includes: an update module for updating a version number of the target product delivery flow template in response to the target product provider modifying a node included in the target product delivery flow template; and the second binding module is used for binding the new target product order with the updated version number in response to the target product user submitting the new target product order based on the target product delivery flow template with the updated version number.

In an exemplary embodiment of the disclosure, the first storage module is further configured to: and storing the self-defined nodes containing the configuration information into a preset non-relational database.

In an exemplary embodiment of the present disclosure, the generating module includes: the first generation unit is used for generating a state machine representing the execution sequence among the nodes based on the self-defined nodes and the basic nodes included in the basic configuration template; the determining unit is used for verifying the state machine and determining the execution sequence of the nodes included in the target product delivery flow template; and the second generation unit is used for generating the target product delivery flow template based on the nodes after the execution sequence is determined.

According to a third aspect of the present disclosure, there is provided an electronic device comprising: a processor; and a memory for storing executable instructions for the processor; wherein the processor is configured to execute the method for generating the product delivery flow template via execution of the executable instructions.

According to a fourth aspect of the present disclosure, there is provided a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the method for generating a product delivery flow template as described above.

According to a fifth aspect of the present disclosure, there is provided a computer program comprising computer readable code which, when run on a device, a processor in the device executes instructions for implementing the steps in the method for generating a product delivery flow template as described above.

As can be seen from the foregoing technical solutions, the method and apparatus for generating a product delivery flow template, the computer-readable storage medium, the electronic device, and the computer program in the exemplary embodiments of the present disclosure have at least the following advantages and positive effects:

in the method and the device for generating the product delivery flow template, the electronic device, the computer-readable storage medium and the computer program in the embodiments of the disclosure, the target product provider adds the custom node experienced in the delivery flow of the target product on the basis of the basic configuration template, and finally generates the target product delivery flow template including the custom node, thereby realizing that the product provider customizes the delivery rule according to the characteristics of different products for various customized delivery scenes. The method meets the stability of the product delivery process, ensures the customizability of the process, and improves the product delivery efficiency and the transparency of the process.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure. It is to be understood that the drawings in the following description are merely exemplary of the disclosure, and that other drawings may be derived from those drawings by one of ordinary skill in the art without the exercise of inventive faculty.

FIG. 1 is a system diagram to which the present disclosure is applicable;

FIG. 2 is a flow chart diagram of a method for generating a product delivery flow template provided by an exemplary embodiment of the present disclosure;

FIG. 3 is an exemplary diagram of a base configuration template provided by an exemplary embodiment of the present disclosure;

FIG. 4 is a flowchart illustrating a method for generating a product delivery flow template according to another exemplary embodiment of the present disclosure;

FIG. 5 is an exemplary diagram of an interface for adding custom nodes provided by an exemplary embodiment of the present disclosure;

FIG. 6 is a flowchart illustrating a method for generating a product delivery flow template according to another exemplary embodiment of the present disclosure;

FIG. 7 is a flowchart illustrating a method for generating a product delivery flow template according to another exemplary embodiment of the present disclosure;

FIG. 8 is a schematic structural diagram of an apparatus for generating a product delivery flow template according to an exemplary embodiment of the present disclosure;

FIG. 9 is a schematic structural diagram of an apparatus for generating a product delivery flow template according to another exemplary embodiment of the present disclosure;

fig. 10 is a block diagram of an electronic device provided in an exemplary embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, apparatus, steps, etc. In other instances, well-known structures, methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

Furthermore, the terms "first", "second", etc. are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present disclosure, "a plurality" means at least two, e.g., two, three, etc., unless explicitly specifically limited otherwise. The symbol "/" generally indicates that the former and latter associated objects are in an "or" relationship.

In the present disclosure, unless otherwise expressly specified or limited, the terms "connected" and the like are to be construed broadly, e.g., as meaning electrically connected or in communication with each other; may be directly connected or indirectly connected through an intermediate. The specific meaning of the above terms in the present disclosure can be understood by those of ordinary skill in the art as appropriate.

Exemplary System

Fig. 1 shows a schematic diagram of a system architecture 100 of a method or apparatus for generating a product delivery flow template to which an embodiment of the present disclosure may be applied.

As shown in fig. 1, the system architecture 100 may include one or more of

terminal devices

101, 102, 103, a network 104, and a server 105. The network 104 serves as a medium for providing communication links between the

terminal devices

101, 102, 103 and the server 105. Network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, among others.

It should be understood that the number of terminal devices, networks, and servers in fig. 1 is merely illustrative. There may be any number of terminal devices, networks, and servers, as desired for implementation. For example, server 105 may be a server cluster comprised of multiple servers, or the like.

The user may use the

terminal devices

101, 102, 103 to interact with the server 105 via the network 104 to receive or send messages or the like. The

terminal devices

101, 102, 103 may have installed thereon various communication client applications, such as a shopping application, a web browser application, an instant messaging tool, and the like.

The

terminal devices

101, 102, 103 may be a variety of electronic devices including, but not limited to, smart phones, tablets, portable and desktop computers, digital cinema projectors, and the like.

The server 105 may be a server that provides various services. For example, the user sends a request for setting a product delivery flow template to the server 105 using the terminal device 103 (which may also be the terminal device 101 or 102). The background text server can send the basic configuration template of the template product to the terminal device according to the request, and the user adds the user-defined node on the basis of the basic configuration template to generate the template product delivery flow template.

Exemplary method

Referring to fig. 2, a flowchart of a method for generating a product delivery flow template according to an exemplary embodiment of the present disclosure is provided, where the present embodiment is applicable to an electronic device (such as the

terminal device

101, 102, 103 or the server 105 shown in fig. 1), and the method includes the following steps:

s210, acquiring a basic configuration template of the target product.

And S220, adding the custom nodes experienced in the delivery process of the target product on the basic configuration template based on the custom node adding operation initiated by the target product provider.

And S230, generating a target product delivery flow template containing the self-defined nodes based on the basic configuration template.

According to the method for generating the product delivery flow template provided by the embodiment of the disclosure, the target product provider adds the custom node experienced in the delivery flow of the target product on the basis of the basic configuration template, and finally generates the target product delivery flow template containing the custom node, so that the product provider can customize delivery rules according to the characteristics of different products aiming at various customized delivery scenes. The method meets the stability of the product delivery process, ensures the customizability of the process, and improves the product delivery efficiency and the transparency of the process.

In S210, the electronic device may obtain and display the basic configuration template of the target product from a local or remote location. The target product may be any type of product, and the delivery process of the target product is not a fixed process, and a target product provider (e.g., a merchant) is required to define the delivery process according to the characteristics of the target product. By way of example, the target product may be a virtual account number, a virtual rechargeable card, a copyright application service, and the like. The delivery process of these products often requires co-participation by both the merchant and the user. For example, the user registers or applies for, uploads the relevant file, and then is checked by the merchant.

The basic configuration template may be a preset product release template containing a number of fixed delivery flow nodes. For example, the basic configuration template comprises a material delivery node, a service start node and a service completion node.

In S220, the electronic device may add the custom node experienced in the delivery flow of the target product on the basic configuration template based on the add custom node operation initiated by the target product provider.

Wherein the custom node can be added by the target product provider operating the electronic device. For example, the target product provider adds custom nodes on the base configuration template by clicking on the add node button. The added custom node can comprise pre-configured information and also can comprise personalized configuration information input by the target product provider.

As shown in fig. 3, an exemplary diagram of a base configuration template is shown. In fig. 3, the step 1 of submitting a demand node, the step 2 of confirming the demand node, and the step 3 of delivering the demand node are the basic nodes of the basic configuration template itself. The add node button is used to add custom nodes in the base configuration template.

In S230, the electronic device may generate a target product delivery flow template including custom nodes based on the base configuration template.

Specifically, after the target product provider adds the custom node, the electronic device may compile the input related information, and solidify each flow node into the program of the target product delivery flow template, so as to generate the target product delivery flow template for the target product and complete the release of the target product. The subsequent target product provider and target product user can operate the delivery flow of the target product according to the delivery rule defined by the target product delivery flow template.

In some alternative implementations, as shown in fig. 4, S230 may include the following sub-steps:

s2301, based on the self-defined nodes and the basic nodes included in the basic configuration template, a state machine for representing the execution sequence among the nodes is generated.

The state machine is a directed graph and consists of a group of nodes and a group of corresponding transfer functions. The state machine operates by responding to a series of events. Each event is within the control range of a transfer function belonging to the current node, where the range of the function is a subset of the nodes. The function returns to the next (and possibly the same) node to be executed. At least one of the nodes must be in a final state and the state machine stops when the final state is reached.

The electronic equipment can carry out operation according to the information input by the target product provider, the state machine is generated by using the related data contained in each node, and the transfer of each process node is solidified into the program through the state machine, so that the related process nodes can only be carried out according to the process followed by the program, if illegal operation is carried out, the shielding is carried out uniformly, the process nodes cannot be damaged, and the robustness and the stability of the program are ensured.

And S2302, checking the state machine and determining the execution sequence of the nodes included in the target product delivery flow template.

After the state machine is generated, the electronic equipment can automatically traverse all possible node combinations, so that only a unique and effective result is obtained under the condition that all compliance entry parameters are combined, an unexpected result value cannot be generated, and the robustness of the whole system is further improved through program self-checking.

As an example, the state machine specifies 3 states a, b, c. State flows that are not within these 3 states are discarded directly. For example: a- > b- > c is a prescribed path, the state machine only allows a- > b or b- > c to be executed, and any other state flow (e.g., a- > c, b- > a, c- > b, etc.) is discarded.

S2303, based on the nodes after the execution sequence is determined, a target product delivery flow template is generated.

After the execution sequence of each node is determined, a target product delivery flow template is generated, and when an operator carries out a product delivery flow based on the target product delivery flow template, the product delivery flow can be carried out only according to the specified node circulation sequence.

According to the implementation mode, the state machine for representing the execution sequence among the nodes is generated, the target product delivery flow template can be executed according to the specified node circulation sequence, errors generated during node circulation are avoided, and the stability of the delivery flow is improved.

In some optional implementations, after S220, the method may further include the steps of:

first, receiving configuration information input by a target product provider and/or a target product user on an interface of a custom node.

The configuration information may be information input by a user for configuring a function of the custom node. Wherein the user may be a target product provider and/or a target product user.

Then, in response to determining that the configuration information input is complete, the custom node containing the configuration information is stored.

Generally, the template product provider may indicate that the configuration information input of the electronic device is completed by clicking a button for indicating that the configuration information input is completed, inputting a command, and the like, and the electronic device determines that the configuration information input is completed after detecting the operation. Various information contained in the custom node can be stored in a preset storage area, such as a local storage area, a remote database and the like.

The implementation mode generates the self-defined node containing the configuration information by receiving the configuration information input by the target product provider and/or the target product user, and realizes that the target product user configures various functions to the self-defined node in a personalized manner, thereby further improving the pertinence of the product delivery process and being beneficial to further improving the product delivery efficiency.

In some optional implementations, the configuration information includes at least one of:

node operation authority configuration information, node type configuration information, node handling time configuration information, node name configuration information and node jump name configuration information.

The node operation authority configuration information is used for representing an operator (such as a merchant or a customer) authorized by the user-defined node.

The node type configuration information is used to characterize the type of information that needs to be input to operate the node, including, but not limited to: file uploading, picture uploading, related information entry, time information entry, text entry and the like. Generally, files or information corresponding to the types can be input through preset components, for example, a pull-down menu can be set on an interface displaying a custom node, the menu includes various types of names, each type of name corresponds to one component, and a node operator can select the type name in the menu to select the corresponding component for information entry.

The node processing time configuration information is used for configuring the relevant time of the product delivery flow corresponding to the user-defined node. Such as the expiration date of the product delivery flow corresponding to the custom node.

The node name configuration information is used for configuring the name of the user-defined node. The node hop name configuration information is used to configure the name of the component, e.g., the name of the next button, used to hop to the next node.

As shown in fig. 5, an exemplary diagram of an interface for adding a custom node is shown, wherein the node name option inputs the content of the node name configuration information. The content input by the node description option is the description content of the target product provider on the current node. The content input by the transaction duration option is the node transaction time configuration information, which is used for configuring the effective duration of the current node. The content input by the node operator option is the node operation authority configuration information, and a merchant or a customer can be selected. The content submitted for input of the content option is the node type configuration information, as shown in 501, which includes options such as text, date interval, picture, file, and the like, and the title of the node type may also be input in the title bar. The next button name option input indicates the next node to execute after the current node is completed.

The various configuration information provided by the optional implementation mode can effectively and accurately limit the content contained in the user-defined node, thereby realizing the personalized configuration of the user-defined node, being beneficial to enabling the delivery flow of the user-defined target product to be more matched with the actual flow and enabling the delivery flow of the target product to be more perfect.

In some alternative implementations, the custom node containing the configuration information is stored in a preset non-relational database. The non-relational database has the characteristics of flexible format, high speed, high expansibility, low cost and the like. As an example, the non-relational database can adopt MongoDB, the MongoDB storage format is flexible, hot data is automatically cached after indexes are built, and the query efficiency is high. The response time is about 10ms, which is higher than the MySQL relational database. In the embodiment, the non-relational database is adopted to store the user-defined nodes, so that the time cost for modifying the nodes by a target product provider each time is low, the time consumption of a program is basically not considered, and a good foundation is established for the actual application of related codes in each scene.

With further reference to fig. 6, a flow diagram of a method of generating a product delivery flow template according to another embodiment of the present disclosure is schematically illustrated. On the basis of the embodiment shown in fig. 2, after S230, the following steps may be further included:

and S240, generating the version number of the target product delivery flow template.

And S250, binding the target product order with the version number in response to the target product user submitting the target product order based on the target product delivery flow template.

In the embodiment corresponding to fig. 6, the corresponding version number is generated while the target product delivery flow template is generated, and the version number is stored in correspondence with the target product delivery flow template, so that when a target product user places an order, the target product order is bound with the version number, and when the target product order is queried and the like, the target product delivery flow template used by the target product order can be extracted according to the version number, so that the product delivery flow template of the corresponding version can be traced according to the product order, the risk that the template used when the order is submitted is inconsistent with the template used when the order is queried is reduced, the stability of the product delivery flow template is improved, and the expandability of the product delivery flow template is improved.

In S240, the electronic device may save the target product delivery flow template and generate a version number for the target product delivery flow template.

Alternatively, the target product delivery flow template may be saved in the form of a snapshot. The snapshot mainly has the function of online data backup and recovery. When the application failure or file damage occurs to the storage device, the data can be quickly recovered, and the data can be recovered to the state of an available time point, so that the stability of the product delivery process is improved.

In S250, the electronic device may bind the target product order with the version number in response to the target product user submitting the target product order based on the target product delivery flow template.

Specifically, when the target product provider issues the target product using the target product delivery flow template corresponding to a certain version number, if the target product user submits the target product order through the target product delivery flow template of the version, the target product order is bound to the version number. If the target product provider subsequently modifies the target product delivery flow template, the target product order still corresponds to the target product flow template bound thereto.

In the subsequent process, in response to receiving a query request for the target product order (which may be a query request issued by a target product provider or a target product user), the electronic device may extract the saved target product delivery process template of the corresponding version and display the target product order based on the version number of the binding.

In some optional implementations, as shown in fig. 7, on the basis of the embodiment corresponding to fig. 6, the method may further include the following steps:

and S260, responding to the target product provider modifying the nodes included in the target product delivery flow template, and updating the version number of the target product delivery flow template.

Typically, the target product delivery flow template may be re-saved while the version number is updated such that the updated version number corresponds to the re-saved target product delivery flow template.

Optionally, the modified target product delivery process template may be saved in a snapshot form and associated with the updated version number.

S270, responding to the target product user submitting a new target product order based on the target product delivery process template with the updated version number, and binding the new target product order with the updated version number.

In the embodiment corresponding to fig. 7, the version number is updated when the node included in the target product delivery flow template is modified, and the modified target product delivery flow template is correspondingly stored, so that when the target product user places an order, the new target product order is bound with the updated version number, and therefore, when the subsequent operations such as querying the new target product order are performed, the product delivery flow template of the corresponding version can be traced. The method and the device realize that the target product delivery flow template is correspondingly stored with the new version number as long as the target product delivery flow template is modified, further reduce the risk that the template used when the order is submitted is inconsistent with the template used when the order is inquired, and improve the stability of the product delivery flow template.

Exemplary devices

Fig. 8 schematically shows a structural diagram of a device for generating a product delivery flow template according to an embodiment of the present disclosure. The generation apparatus of the product delivery flow template provided in the embodiment of the present disclosure may be disposed on the terminal device, or may also be disposed on the server, or may be partially disposed on the terminal device and partially disposed on the server, for example, may be disposed on the server 105 in fig. 1 (according to actual replacement), but the present disclosure is not limited thereto.

The apparatus for generating a product delivery flow template provided by the embodiment of the present disclosure may include: an obtaining module 810, configured to obtain a basic configuration template of a target product; an adding module 820, configured to add a custom node experienced in the delivery flow of the target product on the basic configuration template based on an add custom node operation initiated by the target product provider, and a custom node generating module 830, configured to generate a target product delivery flow template including the custom node based on the basic configuration template.

In this embodiment, the obtaining module 810 can obtain and display the basic configuration template of the target product locally or remotely. The target product may be any type of product, and the delivery process of the target product is not a fixed process, and a target product provider (e.g., a merchant) is required to define the delivery process according to the characteristics of the target product. By way of example, the target product may be a virtual account number, a virtual rechargeable card, a copyright application service, and the like. The delivery process of these products often requires co-participation by both the merchant and the user. For example, the user registers or applies for, uploads the relevant file, and then is checked by the merchant.

In this embodiment, the adding module 820 may add the custom node experienced in the delivery flow of the target product on the basic configuration template based on an add custom node operation initiated by the target product provider.

Wherein the custom node can be added by the target product provider operating the electronic device. For example, the target product provider adds custom nodes on the base configuration template by clicking on the add node button.

In this embodiment, the generating module 830 may generate a target product delivery flow template including the custom node based on the base configuration template.

Specifically, after the target product provider adds the custom node, the generating module 830 may compile the input related information, and solidify each flow node into the program of the target product delivery flow template, so as to generate the target product delivery flow template for the target product and complete the release of the target product. The subsequent target product provider and target product user can operate the delivery flow of the target product according to the delivery rule defined by the target product delivery flow template.

Referring to fig. 9, fig. 9 is a schematic structural diagram of a data compression apparatus according to another exemplary embodiment of the present disclosure.

In some optional implementations, the apparatus further comprises: a receiving module 840, configured to receive configuration information input by a target product provider and/or a target product user on an interface of a custom node; a first storage module 850 for storing the custom node containing the configuration information in response to determining that the configuration information input is complete;

in some optional implementations, the apparatus further comprises: a second storage module 860 for generating a version number of the target product delivery flow template; a first binding module 870 for binding the target product order with the version number in response to the target product user submitting the target product order based on the target product delivery flow template.

In some optional implementations, the second storage module 860 is further configured to: and saving the target product delivery flow template in a snapshot form.

In some optional implementations, the apparatus further comprises: an update module 880 for updating the version number of the target product delivery flow template in response to the target product provider modifying the nodes comprised in the target product delivery flow template; a second binding module 890 for binding the new target product order with the updated version number in response to the target product user submitting the new target product order based on the target product delivery flow template with the updated version number.

In some optional implementations, the configuration information includes at least one of: node operation authority configuration information, node type configuration information, node handling time configuration information, node name configuration information and node jump name configuration information.

In some optional implementations, the first storage module 850 is further configured to: and storing the self-defined nodes containing the configuration information into a preset non-relational database.

In some optional implementations, the generating module 830 includes: a first generating unit 8301, configured to generate a state machine representing an execution order between each node based on the custom node and the base node included in the base configuration template; a determining unit 8302, configured to check the state machine and determine an execution order of the nodes included in the target product delivery flow template; a second generating unit 8303 is configured to generate the target product delivery flow template based on the nodes after the execution order is determined.

According to the generation device of the product delivery flow template provided by the embodiment of the disclosure, the target product provider adds the custom node experienced in the delivery flow of the target product on the basis of the basic configuration template, and finally generates the target product delivery flow template containing the custom node, so that the product provider can customize delivery rules according to the characteristics of different products aiming at various customized delivery scenes. The method meets the stability of the product delivery process, ensures the customizability of the process, and improves the product delivery efficiency and the transparency of the process.

The specific implementation of each module, unit and sub-unit in the device for generating a product delivery flow template provided by the embodiment of the present disclosure may refer to the content in the method for generating a product delivery flow template, and is not described herein again.

It should be noted that although several modules, units and sub-units of the apparatus for action execution are mentioned in the above detailed description, such division is not mandatory. Indeed, the features and functionality of two or more modules, units and sub-units described above may be embodied in one module, unit and sub-unit, in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module, unit and sub-unit described above may be further divided into embodiments by a plurality of modules, units and sub-units.

Exemplary electronic device

As shown in FIG. 10, the example electronic device 100 includes a processor 1001 for executing software routines although a single processor is shown for clarity, the electronic device 100 may include a multi-processor system. The processor 1001 is connected to a communication infrastructure 1002 for communicating with other components of the electronic device 100. The communication infrastructure 1002 may include, for example, a communication bus, a crossbar, or a network.

Electronic device 100 also includes Memory, such as Random Access Memory (RAM), which may include a main Memory 1003 and a secondary Memory 1010. The secondary memory 1010 may include, for example, a hard disk drive 1011 and/or a removable storage drive 1012, and the removable storage drive 1012 may comprise a floppy disk drive, a magnetic tape drive, an optical disk drive, etc. The removable storage drive 1012 reads from and/or writes to a removable storage unit 1013 in a conventional manner. Removable storage unit 1013 may comprise a floppy disk, magnetic tape, optical disk, etc. which is read by and written to by removable storage drive 1012. As will be appreciated by one skilled in the relevant art, the removable storage unit 1013 includes a computer-readable storage medium having stored thereon computer-executable program code instructions and/or data.

In an alternative embodiment, secondary memory 1010 may additionally or alternatively include other similar means for allowing computer programs or other instructions to be loaded into electronic device 100. Such means may include, for example, a removable storage unit 1021 and an interface 1020. Examples of the removable storage unit 1021 and interface 1020 include: a program cartridge and cartridge interface (such as that found in video game console devices), a removable memory chip (such as an EPROM, or PROM) and associated socket, and other removable storage units 1021 and interfaces 1020 that allow software and data to be transferred from the removable storage unit 1021 to the electronic device 100.

Electronic device 100 also includes at least one communication interface 1040. Communications interface 1040 allows software and data to be transferred between electronic device 100 and external devices via communications path 1041. In various embodiments of the present disclosure, communication interface 1040 allows data to be transferred between electronic device 100 and a data communication network, such as a public data or private data communication network. The communication interface 1040 may be used to exchange data between different electronic devices 100, which electronic devices 100 form part of an interconnected computer network. Examples of communication interface 1040 may include a modem, a network interface (such as an ethernet card), a communication port, an antenna with associated circuitry, and so forth. Communication interface 1040 may be wired or may be wireless. Software and data transferred via communications interface 1040 are in the form of signals which may be electronic, magnetic, optical or other signals capable of being received by communications interface 1040. These signals are provided to a communications interface via communications path 1041.

As shown in fig. 10, the electronic device 100 also includes a display interface 1031 and an audio interface 1032, the display interface 1031 performing operations for rendering images to an associated display 1030, and the audio interface 1032 for performing operations for playing audio content through an associated speaker 1033.

In this document, the term "computer program product" may refer, in part, to: removable storage unit 1013, removable storage unit 1021, a hard disk installed in hard disk drive 1011, or a carrier wave carrying software over communications path 1041 (wireless link or cable) to communications interface 1040. Computer-readable storage media refers to any non-transitory tangible storage medium that provides recorded instructions and/or data to electronic device 100 for execution and/or processing. Examples of such storage media include floppy disks, magnetic tape, CD-ROMs, DVDs, Blu-ray (TM) disks, hard disk drives, ROMs, or integrated circuits, USB memory, magneto-optical disks, or a computer-readable card, such as a PCMCIA card, etc., whether internal or external to electronic device 100. Transitory or non-tangible computer-readable transmission media may also participate in providing software, applications, instructions, and/or data to the electronic device 100, examples of such transmission media include radio or infrared transmission channels, network connections to another computer or another networked device, and the internet or intranet that includes e-mail transmissions and information recorded on websites and the like.

Computer programs (also called computer program code) are stored in the main memory 1003 and/or the secondary memory 1010. Computer programs may also be received via communications interface 1040. Such computer programs, when executed, enable electronic device 100 to perform one or more features of embodiments discussed herein. In various embodiments, the computer programs, when executed, enable the processor 1001 to perform the features of the embodiments described above. Accordingly, such computer programs represent controllers of the electronic device 100.

The software may be stored in a computer program product and loaded into electronic device 100 using removable storage drive 1012, hard drive 1011, or interface 1020. Alternatively, the computer program product may be downloaded to electronic device 100 via communications path 1041. The software, when executed by the processor 1001, causes the electronic device 100 to perform the functions of the embodiments described herein.

It should be understood that the embodiment of fig. 10 is given by way of example only. Thus, in some embodiments, one or more features of electronic device 100 may be omitted. Also, in some embodiments, one or more features of electronic device 100 may be combined together. Additionally, in some embodiments, one or more features of electronic device 100 may be separated into one or more components.

It will be appreciated that the elements shown in fig. 10 serve to provide a means for performing the various functions and operations of the server described in the above embodiments.

In one embodiment, a server may be generally described as a physical device including at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the physical device to perform necessary operations.

Exemplary computer readable storage Medium

Embodiments of the present application also provide a computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the functions of the method shown in fig. 2-7.

Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by an electronic device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.

From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.

Exemplary computer program

The disclosed embodiments also provide a computer program product for storing computer readable instructions, which when executed cause a computer to execute the method for generating a product delivery flow template in any possible implementation manner.

The computer program product may be embodied in hardware, software or a combination thereof. In one alternative, the computer program product is embodied in a computer storage medium, and in another alternative, the computer program product is embodied in a Software product, such as a Software Development Kit (SDK), or the like.

The foregoing describes the general principles of the present disclosure in conjunction with specific embodiments, however, it is noted that the advantages, effects, etc. mentioned in the present disclosure are merely examples and are not limiting, and they should not be considered essential to the various embodiments of the present disclosure. Furthermore, the foregoing disclosure of specific details is for the purpose of illustration and description and is not intended to be limiting, since the disclosure is not intended to be limited to the specific details so described.

In the present specification, the embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts in the embodiments are referred to each other. For the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.

Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions.

The methods and apparatus of the present disclosure may be implemented in a number of ways. For example, the methods and apparatus of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A method for generating a product delivery process template, comprising:

acquiring a basic configuration template of a target product;

adding custom nodes experienced in the delivery flow of the target product on the basic configuration template based on custom node adding operation initiated by a target product provider;

and generating a target product delivery flow template containing the self-defined nodes based on the basic configuration template.

2. The method of claim 1, wherein after adding the custom node experienced in the delivery flow of the target product, the method further comprises:

receiving configuration information input by the target product provider and/or the target product user on the interface of the custom node;

in response to determining that the configuration information input is complete, storing the custom node containing the configuration information.

3. The method of claim 1, wherein after said generating a target product delivery flow template containing said custom node, said method further comprises:

generating the version number of the target product delivery flow template;

and binding the target product order with the version number in response to the target product order submitted by a target product user based on the target product delivery flow template.

4. The method of claim 3, further comprising:

updating a version number of the target product delivery flow template in response to the target product provider modifying a node included in the target product delivery flow template;

and binding the new target product order with the updated version number in response to the target product user submitting the new target product order based on the target product delivery flow template with the updated version number.

5. The method of claim 1, wherein the configuration information comprises at least one of:

6. The method of claim 2, wherein storing the custom node containing the configuration information comprises:

and storing the user-defined nodes containing the configuration information into a preset non-relational database.

7. The method of claim 1, wherein generating a target product delivery flow template containing the custom node based on the base configuration template comprises:

generating a state machine representing the execution sequence among the nodes based on the self-defined nodes and the basic nodes included by the basic configuration template;

checking the state machine, and determining the execution sequence of the nodes included in the target product delivery flow template;

and generating the target product delivery flow template based on the nodes after the execution sequence is determined.

8. An apparatus for generating a product delivery process template, comprising:

the acquisition module is used for acquiring a basic configuration template of a target product;

the adding module is used for adding the custom node experienced in the delivery flow of the target product on the basis of the operation of adding the custom node initiated by the target product provider;

and the generating module is used for generating a target product delivery flow template containing the self-defined nodes based on the basic configuration template.

9. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of generating a product delivery flow template of any of claims 1-7 via execution of the executable instructions.

10. A computer-readable storage medium, on which a computer program is stored, the computer program, when being executed by a processor, implementing the method for generating a product delivery flow template according to any one of claims 1 to 7.

11. A computer program comprising computer readable code for, when run on a device, a processor in the device executing instructions for carrying out the steps of the method according to any one of claims 1 to 7.