Commodity Data Update Method, Device, Server, and Storage Medium

Abstract

The present application discloses a method, apparatus, server, and storage medium for updating commodity data, belonging to the field of Internet technologies. The method includes: receiving a commodity data update request, which is used to update the commodity information corresponding to a target commodity, and the commodity data update request includes process attribute information, where different command processes correspond to different process attribute information; determining a target command process corresponding to the commodity data update request according to the process attribute information; and executing the target command process to update the commodity information corresponding to the target commodity. It can achieve isolation of different commodity data update operations, avoid data confusion when multiple users update commodity data simultaneously, and optimize the commodity data update process.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of Internet technologies, and particularly to a method, an apparatus, a server, and a storage medium for updating commodity data. Background Art

[0002] A local life platform is a platform that provides commodity information such as catering, life services, and leisure and entertainment. Users can learn more convenient and comprehensive commodity information through the local life platform, such as commodity prices, detailed commodity information, commodity preferential activities, etc.

[0003] In related technologies, in order to maintain the commodity business in the local life platform, the business of a certain store often needs to be jointly maintained by multiple types of users. For example, merchant administrators, responsible salespersons of the store, operation editors, etc. Taking the commodity price as an example, there may be multiple users who need to modify the commodity content at the same time. For example, user A modifies the price of commodity A in a certain future period, but user A does not choose to publish the price. Subsequently, user B modifies the price of commodity A on the same day and chooses to publish it immediately; since user A and user B share the same data editing area, the modification of the price of commodity A by user B will overwrite the modification of the price of commodity A by user A, resulting in the modification of the price of commodity A by user A being invalid or published earlier, and thus there may be a situation of commodity information loss or conflict. Summary of the Invention

[0004] Embodiments of the present application provide a method, an apparatus, a server, and a storage medium for updating commodity data. The technical solutions are as follows:

[0005] On the one hand, embodiments of the present application provide a method for updating commodity data, and the method includes:

[0006] Receiving a commodity data update request, where the commodity data update request is used to update the commodity information corresponding to a target commodity, and the commodity data update request includes process attribute information, where different command processes correspond to different process attribute information;

[0007] Determining a target command process corresponding to the commodity data update request according to the process attribute information;

[0008] Executing the target command process to update the commodity information corresponding to the target commodity.

[0009] On the other hand, embodiments of the present application provide a commodity data update apparatus, and the apparatus includes:

[0010] A receiving module, configured to receive a commodity data update request, where the commodity data update request is used to update the commodity information corresponding to a target commodity, and the commodity data update request includes process attribute information, where different command processes correspond to different process attribute information;

[0011] A first determination module, configured to determine a target command process corresponding to the commodity data update request according to the process attribute information.

[0012] An update module, configured to execute the target command process and update the commodity information corresponding to the target commodity.

[0013] On the other hand, an embodiment of the present application provides a server, which includes a processor and a memory. A computer program is stored in the memory, and the computer program is loaded and executed by the processor to implement the commodity data update method as described in the above aspect.

[0014] On the other hand, an embodiment of the present application provides a non-transitory computer-readable storage medium, on which a computer program is stored, and the computer program is loaded and executed by a processor to implement the commodity data update method as described in the above aspect.

[0015] On the other hand, an embodiment of the present application provides a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the server reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the server executes the commodity data update method provided in various optional implementation manners of the above aspect.

[0016] The technical solution provided by the embodiment of the present application can bring the following beneficial effects:

[0017] The concept of a command process is proposed. Different command processes can be determined for different commodity data update requests based on different process attribute information included in the commodity data update request, so that when updating commodity data, it can be updated based on its corresponding command process. For example, if there are commodity update data requests from two users, different command processes can be established for them respectively, and the two command processes are executed respectively to update the commodity information, which can isolate different commodity data update operations, thereby avoiding data confusion when multiple users update commodity data simultaneously, and optimizing the commodity data update process. Description of the Drawings

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0019] Figure 1Shows a schematic diagram of the implementation environment provided by various embodiments of the present application;

[0020] Figure 2 Shows a flowchart of a commodity data update method provided by an embodiment of the present application;

[0021] Figure 3 Shows a flowchart of a commodity data update method provided by another embodiment of the present application;

[0022] Figure 4 Shows a flowchart of a commodity data update method provided by another embodiment of the present application;

[0023] Figure 5 Shows a flowchart of a commodity data update method provided by another embodiment of the present application;

[0024] Figure 6 Shows a schematic diagram of the execution process of a command flow shown in an exemplary embodiment of the present application;

[0025] Figure 7 Shows a flowchart of a commodity data update method provided by another embodiment of the present application;

[0026] Figure 8 Shows the structural diagram of a command flow provided by an exemplary embodiment of the present application;

[0027] Figure 9 Shows the structural block diagram of a commodity data update device provided by an embodiment of the present application;

[0028] Figure 10 Shows the structural block diagram of a server provided by an embodiment of the present application. Detailed implementation manners

[0029] To make the objectives, technical solutions and advantages of the present application clearer, the following will further describe the implementation manners of the present application in detail with reference to the accompanying drawings.

[0030] In the related art, generally, multiple users are required to jointly maintain various product information in a product operation platform. For example, the merchant providing the product, the responsible salesperson in the product operation platform, etc. These users all have the permission to modify the product information. When multiple users jointly update a certain product information, problems such as product data update conflicts and cross-coverage may occur, thus affecting the execution of some important update tasks for product information. For example, in an application scenario, for product A on the operation platform, both user A and user B have the permission to modify the product information of product A. When the user hopes to modify the product price of product A in the next week, after user A modifies it, the current modified data is saved first, but the modified data is not submitted for publication. On the other hand, user B needs to urgently modify the current price of product A and chooses to publish immediately after the modification. In the traditional data update method, since multiple people share the same data editing area when editing together, when user B chooses to modify and publish, the modified data of user A that was not originally selected for publication will also be published to the product operation platform at the same time, resulting in conflicting information in the product information of product A, thus threatening the interests of the merchant or the operation platform.

[0031] Different from the product data update method in the related art, the embodiment of the present application provides a new product data update method. Figure 1 The figure shows a schematic diagram of the implementation environment provided by each embodiment of the present application. The implementation environment includes a first terminal 101, a server 102, and a second terminal 103.

[0032] The first terminal 101 is a device with the function of viewing and maintaining product data. It can be a device installed with a product operation application program, such as a smart phone, a tablet computer, a PC (Personal Computer), etc. Among them, the product operation application program can be a meal ordering application, a ticket purchasing application, a hotel reservation application, etc. In the embodiment of the present application, the first terminal 101 is the device held by the target role. The target role refers to the role that has the permission to update or modify the product data in the product operation platform, such as the product-providing merchant, the product-responsible salesperson, etc.; optionally, after the target role initiates a product data update request for the product information of the target product on the first terminal 101, the first terminal 101 sends the product data update request to the server 102, so that the server 102 can determine the corresponding command process based on the product data update request; optionally, the target role can submit the product update data that needs to be updated in the product operation interface provided by the first terminal 101, so that the server 102 can update the product information based on the product update data.

[0033] The first terminal 101 is connected to the server 102 through a wired or wireless network.

[0034] Server 102 is the background server or business server corresponding to the commodity operation application program. It is a device with functions such as creating a command process, executing a command process, and updating commodity information. It can be a single server, a server cluster composed of several servers, or a cloud server. In the embodiments of the present application, server 102 can receive a commodity data update request sent by the first terminal 101, determine the corresponding command process for this commodity data update request, and update the commodity information by executing the corresponding command process. Optionally, server 102 can receive commodity update data sent from the first terminal 101, execute the command process, and publish the commodity update data online, that is, update the commodity information on other terminals.

[0035] Server 102 and the second terminal 103 are connected through a wired or wireless network.

[0036] The second terminal 103 is a device installed with a commodity operation client. The second terminal 103 is a terminal providing commodity query and commodity trading functions. It can be a smart phone, a tablet computer, a PC, etc. In the embodiments of the present application, the second terminal 103 can receive commodity update data sent from the server 102 and update the commodity information correspondingly in the commodity operation client, so that users can timely understand the latest information of the commodity.

[0037] In this embodiment, the concept of a command process is proposed. Server 102 can determine different command processes for different commodity data update requests based on different process attribute information included in the commodity data update request, so that when updating commodity data, it can be updated based on its corresponding command process. For example, if there are commodity update data requests from two users, different command processes can be established for them respectively, and the two command processes are executed respectively to achieve the update of commodity information, thereby realizing the isolation of different commodity data update operations and avoiding the situation of data confusion when multiple users update commodity data simultaneously, optimizing the commodity data update process.

[0038] Please refer to Figure 2 , which shows a flowchart of a commodity data update method provided by an embodiment of the present application. In the embodiments of the present application, this method is described by taking the method applied to the Figure 1 shown server as an example. The method includes:

[0039] Step 201, receive a commodity data update request. The commodity data update request is used to update the commodity information corresponding to the target commodity. The commodity data update request includes process attribute information, where different command processes correspond to different process attribute information.

[0040] Among them, the commodity information of the commodity can be the commodity price, commodity detailed information (commodity picture and text description), commodity status (commodity on the shelf or commodity off the shelf), commodity inventory, etc.

[0041] In one possible implementation, when a user needs to adjust the product information of an online product, the user can select the target product to be modified in the product information modification interface, and select the product information to be modified, such as the product price. After submission, a product data update request for the product price corresponding to the target product is initiated to the server, and the corresponding server will receive the product data update request sent by the terminal.

[0042] Compared to the related art, when different users modify product data online, they modify the same product data area, which may cause the subsequent modified data to overwrite the previous modification. In the embodiment of the present application, in order to distinguish different product data update requests, different command processes are determined for the product data update requests based on the process attribute information corresponding to the product data update requests.

[0043] For the scenario where a user initiates a request to update product data, if different users initiate the request to update product data, the corresponding request initiators of the product data update request are different; if the product data corresponding to different products are modified, the corresponding product identifiers are different; if different product contents of the same product are modified, such as price or graphic description, the corresponding update modules of the product update may not be the same. Therefore, in a possible implementation manner, the request information corresponding to different product data update requests is determined as process attribute information to distinguish different command processes.

[0044] Optionally, roles or users that can initiate product data update requests must have permission to modify product data.

[0045] Step 202: determine the target command process corresponding to the commodity data update request according to the process attribute information.

[0046] The command flow is the operation steps required from receiving a product data update request to publishing the product update data online.

[0047] In order to distinguish different product data update requests and avoid confusion between the product data updated based on the product data update request and the product data corresponding to other update requests, in a possible implementation, different command processes are determined for different product data update requests based on different process attribute information, thereby isolating different product data update requests and avoiding data confusion when updating product information under different product update requests.

[0048] In an exemplary example, if user A initiates a change to the price of product A, the product update data request may include the identifier of user A, the identifier of the product, and the price of the product. Then, the identifier of user A, the identifier of the product, and the price of the product can be determined as process attribute information, and the target command process can be determined based on this process attribute information.

[0049] Step 203: Execute the target command process to update the product information corresponding to the target product.

[0050] After the server determines the corresponding target command process for the received product data update request, it can execute the target command process, that is, from receiving the product update data to publishing the product update data, to update the product information corresponding to the target product based on the product update data. The specific implementation logic can be that when the command process indicates that the product update data meets the publishing conditions, the product update data is sent to other terminals. After receiving the product update data, other terminals will update the product information by themselves.

[0051] In summary, in the embodiments of the present application, the concept of a command process is proposed. By proposing the concept of a command process, different command processes can be determined for different product data update requests based on the different process attribute information included in the product data update request, so that when updating product data, it can be updated based on its corresponding command process. For example, if there are product update data requests from two users, different command processes can be established for them respectively, and the two command processes can be executed respectively to update the product information, thereby realizing the isolation of different product data update operations and avoiding the situation of data confusion when multiple users update product data at the same time, optimizing the product data update process.

[0052] In a possible application scenario, if user A initiates a modification to the product description information of product A, but during this modification process, user A only saves the modified content and does not submit or publish it. After a period of time, user A wants to continue to modify the product description information of product A based on the previous modified content. At this time, if the server creates a new command process based on the product data update request, obviously, user A needs to re-enter the previous modified content, and it will cause the command process corresponding to the previous product data update request to be invalid, resulting in a waste of server processing resources. Therefore, in a possible implementation manner, the server can determine whether there is an already created command process (an unfinished command process) based on the process attribute information represented by the product update data. If there is, the already created command process is determined as the target command process corresponding to the current product data update request. If not, a new command process is created for the product data update request. The following embodiments will respectively describe the product data update methods in two cases.

[0053] In an exemplary example, such asFigure 3 As shown in Figure 1 , it shows a flowchart of a commodity data update method provided by another embodiment of the present application. In the embodiments of the present application, this method is described by taking the server shown in Figure 1 as an example. The method includes: Figure 1 Step 301: Receive a commodity data update request, which is used to update the commodity information corresponding to the target commodity. The commodity data update request contains process attribute information, where different command processes correspond to different process attribute information.

[0054] Among them, the process attribute information includes a request initiation method identifier, a commodity identifier corresponding to the target commodity, and the type of commodity information to be updated. For the request initiator identifier, that is, a commodity data update request initiated by a certain role (user), it can be represented by a user or role account (Identity Document, ID); for the commodity identifier corresponding to the target commodity, since different commodities generally have different IDs, therefore, the commodity ID can be used to represent it; for the type of commodity information to be updated, since commodity information includes many aspects, such as price, graphic description, inventory, status, etc., therefore, different modules are divided for commodity information according to the type of commodity information, such as a price module, an inventory module, a status module, a graphic description module, etc., and each module is used as the type of commodity information to be updated.

[0055] Optionally, the process attribute information may include at least one of the three mentioned above, or may further include a merchant ID, corresponding to the problem that the commodity may need to be updated in multiple merchants.

[0056] In a possible implementation manner, when the user initiates a commodity data update request for the target commodity, the commodity data update request will carry the corresponding request initiator identifier (user ID), the commodity identifier corresponding to the target commodity (commodity ID), and the type of commodity information to be updated (modified module name or module name identifier). Then, the corresponding server receives the commodity data update request, and thus obtains the process attribute information corresponding to the commodity data update request.

[0057]

[0058] Step 302: In response to the created command process corresponding to the process attribute information being included in the command process set, determine the created command process as the target command process. The command process set includes at least one created command process.

[0059] Among them, the created command process means that the command process is not completed and the commodity update data associated with the command process has not been published.

[0060]

[0060] Since different command processes have different process attribute information, it is necessary to determine whether the received product update data has a created command process. To do this, it is necessary to search the command process set based on this process attribute information. If the process attribute information corresponding to the created command process found is the same as this process attribute information, there is no need to create a new command process for this product update data. Instead, only the created command process needs to be determined as the target command process corresponding to the current product update data.

[0061] In a possible implementation manner, the method for searching for a target command process in the command process set according to the process attribute information may include the following steps:

[0062] First, obtain the request initiator identifier corresponding to the product data update request, the product identifier corresponding to the target product, and the type of product information to be updated.

[0063] In the embodiments of the present application, the request initiator identifier, the product identifier corresponding to the target product, and the type of product information to be updated are determined as the process attribute information. That is, if these three types of information are all the same, it means that they are the target command processes corresponding to the same product data update request.

[0064] Optionally, the process attribute information may have less information than the above three types of information. For example, any two of the above three types of information; it may also include more information than the above three types of information. For example, a merchant ID is added to the process attribute information. The embodiments of the present application do not limit this.

[0065] In a possible implementation manner, the product data update request carries the above process attribute information. When the server receives the product data update request, it obtains the process attribute information included in the product data update request, so as to search the created command processes according to this process attribute information and confirm whether there is a created command process that matches this process attribute information.

[0066] In an exemplary example, the role ID + product ID + content module may be used as the key value to search for the corresponding created command process in the command process set.

[0067] Optionally, when creating a command process, the command process and its corresponding process attribute information may be associated and stored, so as to search for the target command process in the command process set based on the process attribute information later.

[0068] Second, in response to the request initiator identifier, the product identifier, and the type of product information being the same as the process attribute information corresponding to the created command process, determine the created command process as the target command process.

[0069] In a possible implementation, when in the process attribute information corresponding to the created command process, the request initiator identifier, the product identifier, and the product information type are all consistent with the process attribute information represented by the current product data update request, it is determined that the user wants to continue to improve the product update data based on the previously unfinished created command process. The created command process can be determined as the target command process and fed back to the user.

[0070] Step 303: Obtain the draft data associated with the created command process, where the draft data is the historical product update data of the target product and the historical product update data has not been published.

[0071] To avoid confusion of product update data corresponding to different command processes, after the server creates a command process according to the product data update request, if it receives the input and save operations of the user on the product update data, it will associate the received product update data with its corresponding command process as draft data, so that the user can continue to modify the product update data based on the draft data in the future, or update the online product based on the draft data.

[0072] In a possible implementation, after determining the created command process (unfinished command process) according to the process attribute information, obtain the draft data (historical product update data) associated with it and return the draft data to the user, so that the user can continue to modify the product data based on the draft data.

[0073] Optionally, if the draft data is a product graphic description, its rendering screen is also fed back to the user, so that the user can continue to modify the information related to the product graphic description based on the rendering screen.

[0074] Step 304: In response to receiving the input operation of the product update data, modify the draft data according to the product update data.

[0075] In a possible implementation, the user continues to modify the product information based on the historical product update data and clicks to save the product update data. Then the server receives the input operation of the product update data and modifies the draft data associated with the created command process according to the product update data corresponding to the input operation, that is, determines the target command process corresponding to the current product data update request and the product data to be updated corresponding to the current product data update request.

[0076] Step 305: Execute the target command process to update the product information corresponding to the target product.

[0077] In a possible implementation manner, according to the execution steps of the target command process, and when the target command process indicates to publish product update data, update the product information corresponding to the target product online based on the draft data associated with the target command process.

[0078] In this embodiment, by searching in the command process set through the process attribute information, and after finding a created command process that is consistent with the process attribute information, it indicates that the user needs to continue with product data update based on the previously unfinished command process. Therefore, the created command process is determined as the target command process corresponding to the current product data update request, and the draft data corresponding to the created command process is fed back to the user, so that the user can continue to modify the product information based on the historical product update data, avoiding the user having to re-enter the historical product update data, improving the efficiency of the user in performing product data update, and at the same time avoiding waste of server processing resources caused by creating a new command process.

[0079] The above embodiment describes the situation where there is a created command process that is consistent with the process attribute information corresponding to the current product data update request. This embodiment focuses on describing how the server determines the target command process based on the product data update request if there is no created command process that is consistent with the process attribute information.

[0080] In an exemplary example, as Figure 4 shown, it shows a flowchart of a product data update method provided by another embodiment of the present application. The embodiment of the present application takes this method as being applied to Figure 1 the server shown as an example for illustration. The method includes:

[0081] Step 401, receive a product data update request, where the product data update request is used to update the product information corresponding to the target product, and the product data update request contains process attribute information. Among them, different command processes correspond to different process attribute information.

[0082] The implementation manner of this step can refer to the above embodiment, and this embodiment will not elaborate on it.

[0083] Step 402, in response to the fact that the command process set does not include a created command process corresponding to the process attribute information, create a target command process corresponding to the process attribute information.

[0084] Among them, the command process attribute information includes the request initiator identifier corresponding to the product data update request, the product identifier corresponding to the target product, and the type of product information to be updated.

[0085] Among them, the manner of searching for a created command process in the command process set according to the command process attribute information can refer to the above embodiment, and this embodiment will not elaborate on it here.

[0086] In a possible implementation, when it is determined that there is no created command process in the command process set that is consistent with the process attribute information, it indicates that the current commodity data update request is different from the unfinished command processes existing in the server, and a new command process, that is, the target command process, needs to be created for the commodity data update request, and the process attribute information is associated with the target command process for subsequent search convenience.

[0087] Step 403: In response to receiving an input operation of commodity update data, create draft data according to the commodity update data.

[0088] Since the command process corresponding to the current commodity data update request is a newly created one, this command process does not have historical commodity update data, that is, draft data. Therefore, in a possible implementation, when the user inputs the commodity update data to be updated in the terminal and saves the commodity update data, correspondingly, the server receives the input operation of the commodity update data, and creates new draft data for the target command process according to the commodity update data.

[0089] Step 404: Associate the draft data with the target command process.

[0090] To facilitate subsequent modification by the user based on the draft data or update of the online commodity information by the server based on the draft data, in a possible implementation, the draft data is associated with the target command process.

[0091] Step 405: Execute the target command process to update the commodity information corresponding to the target commodity.

[0092] In a possible implementation, according to the execution steps of the target command process, and after the target command process indicates the release of the commodity update data, update the commodity information corresponding to the target commodity online according to the draft data associated with the target command process.

[0093] In this embodiment, when no created command process is found in the command process set according to the process attribute information, it indicates that the current commodity data update request is a new update request. Therefore, the server needs to create a new command process and draft data for the current commodity data update request to update the commodity information according to the command process and the draft data.

[0094] The above embodiments focus on describing the process of determining the target command process corresponding to the commodity data update request, and this embodiment focuses on describing the process of executing the target command process to update the commodity information.

[0095] As Figure 5 shown, it shows a flowchart of a commodity data update method provided by another embodiment of the present application. In the embodiments of the present application, this method is applied toFigure 1 Taking the server shown as an example for illustration, the method includes:

[0096] Step 501, receiving a commodity data update request, which is used to update the commodity information corresponding to the target commodity. The commodity data update request contains process attribute information, where different command processes correspond to different process attribute information.

[0097] Step 502, determining the target command process corresponding to the commodity data update request according to the process attribute information.

[0098] The implementation manners of Step 501 and Step 502 can refer to the above embodiments, and will not be elaborated herein.

[0099] Step 503, in response to the submission operation of the draft data, updating the process status corresponding to the target command process from the editing status to the review status. The draft data is the commodity update data of the target commodity.

[0100] Among them, in the editing status, the user can modify the draft data.

[0101] When the server creates the corresponding target command process for this commodity data update request, starting from the creation of the target command process, the target command process is set to be in the editing status until the user submits the draft data, and then the process status will change.

[0102] Among them, when the user is editing the draft data, or the user only saves the draft data without submitting it, the server sets the target command process to be in the editing status.

[0103] When the user finishes editing the commodity update data, that is, the draft data, if it is confirmed to be correct, the user can click the submission control, and then the server receives the submission operation of the draft data and can change the process status of the target command process from the editing status to the review status.

[0104] Step 504, in response to the target command process being in the review status, auditing the draft data according to the audit rules to obtain an audit result.

[0105] In order to ensure that the submitted commodity update data meets the market requirements and rules and avoid randomly changing the commodity information from threatening the interests of other users, in a possible implementation manner, audit rules are set. The audit rules are used to audit the submitted commodity update data (draft data), and only the draft data that passes the audit can be used for online publication.

[0106] Among them, the determination method of the audit rules may include the following steps:

[0107] First, obtaining the commodity attribute information corresponding to the target commodity.

[0108] Among them, the review rules are determined based on the draft data (commodity update data) submitted by the user. Therefore, when the server receives the submission operation of the draft data, the above process of determining the review rules is carried out immediately.

[0109] Among them, the commodity attribute information may refer to the category to which the target commodity belongs. For example, the target commodity belongs to the book category, the home category, or the plant category. It may also refer to the industry to which the target commodity belongs, such as the medical beauty category, the flower category, the skin care category, etc., or other more detailed information. The embodiments of the present application do not limit this.

[0110] In a possible implementation manner, after the server receives the submission operation of the draft data, it immediately obtains the commodity attribute information corresponding to the target commodity, so as to determine the corresponding review rules according to the commodity attribute information subsequently.

[0111] Second, determine the review rules according to the commodity attribute information, where different commodity attribute information corresponds to different review rules.

[0112] Among them, the review rules refer to some indicators that can be recognized by the server for passing or rejecting the review. For example, the commodity commission setting needs to be less than 0.5; the commodity description information shall not contain words such as "best".

[0113] In a possible implementation manner, after the server obtains the commodity attribute information corresponding to the target commodity, it can determine the corresponding review rules according to the commodity attribute information and save the review rules in the command context corresponding to the target command process, so as to review the draft data based on the review rules.

[0114] Optionally, the review rules can also be set by the administrator in charge of commodity operation.

[0115] Third, store the review rules in the command context corresponding to the target command process.

[0116] In a possible implementation manner, the review rules are stored in the command context corresponding to the target command process. When the process state corresponding to the target command process changes from the editing state to the review state, the draft data is reviewed according to the review rules in the command context to obtain the review result.

[0117] Step 505, in response to the review result indicating that the draft data passes the review, update the target command process from the review state to the release state.

[0118] In a possible implementation manner, after the review result indicates that the draft data passes the review, it means that the draft data meets the commodity information specification and can be used for online release. Then, the process state corresponding to the target command process is updated from the review state to the release state.

[0119] Optionally, if the review result indicates that the draft data has not been reviewed, it means that the product information currently modified by the user does not conform to the product information specification and needs to be modified and submitted again. Therefore, in order to remind the user to modify the draft data, the process status corresponding to the target command process is updated from the review status to the edit status, so that the user can modify the draft data again in the edit status.

[0120] Step 506, in response to the target command process being in the release state, update the product information corresponding to the target product according to the draft data.

[0121] In a possible implementation manner, when the target command process is in the release state, it means that the draft data can be used to be released online, and then the server can update the product information corresponding to the target product according to the draft data.

[0122] Step 507, in response to the completion of the product information update, clear the draft data and the target command process. The draft data is the product update data of the target product.

[0123] In a possible implementation manner, when the server determines that the product information update online is completed, it means that the target command process has been completed, and then the target command process and the draft data can be cleared to avoid occupying the server processing resources by the completed command process and the draft data.

[0124] Optionally, if the server determines that the draft data has not been successfully released, that is, in the case of release failure, it means that there may be some reasons. For example, the product update data is set incorrectly, or other reasons cause the product information not to be released online on time. In order to facilitate the user to modify the product update data and release it online again, the server can update the process status corresponding to the target command process from the release state to the edit state in the case of release failure, so that the user can re-edit the product update data based on the release failure situation.

[0125] In an exemplary example, such as Figure 6As shown, it shows a schematic diagram of the execution process of the command flow shown in an exemplary embodiment of the present application. When the command flow is created, it is in the production process (i.e., the editing state); when a submission operation for the draft data is received and the submission is successful, the server determines that the draft data has been submitted, and then the server submits the draft data for review, and the command flow turns to the review process (review state); when the review result indicates that the draft data passes the review, the process state is updated to the review passed or to be released (i.e., the release state). After the server determines that the release policy is real-time release, it updates the product information according to the draft data, and the process state is in the release process. When the release is successful, the process state is release successful; if the release fails, the process state is release failed, and the process state is updated to the production process; optionally, as long as the process state is before the release process, the user can initiate a withdrawal of the draft data. For example, when the command flow is in the review process and the user needs to modify the draft data, a withdrawal can be initiated, and the process state is updated from the review process to the production process; when the process state is in the to-be-released state, the user can also initiate a withdrawal, and the process state is updated from the to-be-released state to the production process; optionally, when the draft data fails to pass the review (rejected review), the process state is updated from the review process to the review rejected, and then updated to the production process, so that the user can re-edit the draft data.

[0126] In this embodiment, the conversion of each process state after the target command flow is created is described, that is, the conversion between the three states of the editing state, the review state, and the release state. And when the process state turns to the release state, the product update data can be used to update the product information. In addition, after the product information is updated, the target command flow and the draft data corresponding to the current product data update request are cleared to avoid occupying the server processing resources.

[0127] In a possible application scenario, since the number of product information that the user needs to modify is large, if the product data update operation is performed on the same day, it is obvious that the product information update cannot be achieved in time. The user's request is that the product update data can be edited in advance, the release time can be set, and the product update data can be released to the online at the release time on time. The embodiment of the present application provides a release policy option for this application scenario, so that the user can set the release time according to their own needs.

[0128] On Figure 5 this basis, as Figure 7 shown, step 506 may include step 506A and step 506B.

[0129] Step 506A, in response to the target command flow being in the release state, obtain a preset release policy from the command context corresponding to the target command flow.

[0130] In a possible implementation, when the user submits draft data, a publishing strategy for the product update data can be set. Taking the publishing time as an example, if the user needs to update the product information immediately, the user can select real-time publishing, that is, after the target command process is in the publishing state, the product information is immediately updated according to the draft data; if the user wants to update the product information at a certain future time, the user can select a delayed publishing strategy and preset a publishing time, so that after the target command process reaches the preset publishing time, the product information is updated according to the draft data.

[0131] Optionally, if the user does not set a preset publishing strategy, the server defaults to the real-time publishing strategy.

[0132] Among them, when the server receives a publishing strategy setting operation, the preset publishing strategy is stored in the command context corresponding to the target command process, so that when the target command process is in the publishing state, the product information can be updated based on the preset publishing strategy.

[0133] Step 506B, update the product information corresponding to the target product according to the preset publishing strategy and the draft data.

[0134] Taking the preset publishing strategy as the publishing time as an example, the preset publishing strategy can include two types: real-time publishing and delayed publishing. Real-time publishing means that after the process status is updated to the publishing state, the product information is immediately updated according to the draft data; delayed publishing means that after the process status is updated to the publishing state, the product information is not immediately updated, but after reaching the publishing time indicated by the delayed publishing, the product information is updated according to the draft data.

[0135] Among them, the process of updating the product information according to the preset publishing strategy and the draft data can include the following steps:

[0136] First, in response to the preset publishing strategy being real-time publishing, update the product information according to the draft data.

[0137] In a possible implementation, after the user selects the real-time publishing strategy, the server pre-stores the real-time publishing strategy in the process context corresponding to the target command process. When the target command process is in the publishing state and it is determined that the product update data needs to be published in real time, the product information is immediately updated according to the draft data.

[0138] Second, in response to the preset publishing strategy being delayed publishing, add the target command process to the publishing queue, and the publishing queue contains at least one command process in the publishing state.

[0139] When the server obtains that the preset publishing policy is delayed publishing and the delay publishing time, it means that the user does not want to immediately publish the product update data at the current moment. To meet the user's need for delayed publishing, the target command process can be added to the publishing queue first, so that the product update data can be published later when the publishing time is reached.

[0140] Optionally, the target command process can be added to the publishing queue in the order of the publishing times indicated by the delayed publishing.

[0141] Third, in response to reaching the publishing time corresponding to the delayed publishing, update the product information according to the draft data.

[0142] In a possible implementation manner, after the target command process is added to the publishing queue, the server can monitor the publishing times of each command process in the publishing queue in real time. If the current time reaches the publishing time, the product information is immediately updated according to the draft data.

[0143] Among them, the server can scan the publishing queue at preset time intervals to determine whether there is a command process that reaches the publishing time corresponding to the delayed publishing. The preset time interval can be 1h.

[0144] In this embodiment, by pre-storing the publishing policy in the command context corresponding to the target command process, the product information can be updated based on the user's needs. If the user needs to publish in real time, after the target command process is in the publishing state, the product information is immediately updated according to the product update data; if the user needs to publish later, the target command process updates the product information based on the publishing time corresponding to the delayed publishing, which improves the efficiency of the user to update the product data and avoids the delay problem when a large number of product information needs to be updated.

[0145] In an exemplary example, for the determination and execution process of the target command process shown in the above embodiment, the structure of the command process can be obtained, such as Figure 8As shown, it shows the structural diagram of the command flow provided by an exemplary embodiment of the present application. According to the commodity data update request, the command flow 800 is determined. The process attribute information included in the command flow 800 may include: command ID, commodity ID, module, role identifier, and process status. Among them, the commodity ID is the ID corresponding to the target commodity to be updated by the commodity data update request; the role identifier is the identifier of the request initiator corresponding to the commodity data update request; the module is the type of commodity information to be updated corresponding to the commodity data update request; the command ID is the identifier corresponding to the command flow 800; the process status is the status of the command flow 800, for example, the editing status, the review status, and the release status. Optionally, the command flow 800 is associated with draft data, where the draft data is the commodity update data; optionally, the command flow 800 further includes a command context, and the command context at least includes a review rule and a release policy, where the review rule is used to review the draft data associated with the command flow 800, and the release policy is used to indicate the time for updating the commodity information according to the draft data.

[0146] The following is an embodiment of the device of the present application, which can be used to execute the method embodiment of the present application. For the details not disclosed in the device embodiment of the present application, please refer to the method embodiment of the present application.

[0147] Please refer to Figure 9 , which shows the structural block diagram of the commodity data update device provided by an embodiment of the present application. The device has the functions of implementing the above method example, and the functions can be implemented by hardware or by hardware executing corresponding software. As Figure 9 shown, the device may include:

[0148] A receiving module 901, configured to receive a commodity data update request, where the commodity data update request is used to update the commodity information corresponding to the target commodity, and the commodity data update request includes process attribute information, where different command flows correspond to different process attribute information;

[0149] A first determining module 902, configured to determine the target command flow corresponding to the commodity data update request according to the process attribute information;

[0150] An updating module 903, configured to execute the target command flow and update the commodity information corresponding to the target commodity.

[0151] Optionally, the first determining module 902 includes:

[0152] A determining unit, configured to, in response to the command flow set including the created command flow corresponding to the process attribute information, determine the created command flow as the target command flow, where the command flow set includes at least one created command flow;

[0153] A creation unit, configured to create the target command process corresponding to the process attribute information in response to the fact that the created command process corresponding to the process attribute information is not included in the set of command processes.

[0154] Optionally, the determination unit is further configured to:

[0155] Obtain the identity of the request initiator corresponding to the commodity data update request, the commodity identity corresponding to the target commodity, and the type of commodity information to be updated;

[0156] In response to the identity of the request initiator, the commodity identity, and the type of commodity information being consistent with the process attribute information corresponding to the created command process, determine the created command process as the target command process.

[0157] Optionally, the apparatus further includes:

[0158] A first acquisition module, configured to acquire draft data associated with the created command process, where the draft data is historical commodity update data of the target commodity and the historical commodity update data has not been published;

[0159] A modification module, configured to modify the draft data according to the commodity update data in response to an input operation of commodity update data being received.

[0160] Optionally, the apparatus further includes:

[0161] A creation module, configured to create draft data according to the commodity update data in response to an input operation of commodity update data being received;

[0162] An association module, configured to associate the draft data with the target command process.

[0163] Optionally, the update module 903 includes:

[0164] A first update unit, configured to update the process state corresponding to the target command process from an editing state to an auditing state in response to a submission operation of the draft data, where the draft data is the commodity update data of the target commodity;

[0165] An auditing unit, configured to audit the draft data according to an auditing rule to obtain an auditing result in response to the target command process being in the auditing state;

[0166] A second update unit, configured to update the target command process from the auditing state to a publishing state in response to the auditing result indicating that the draft data passes the audit;

[0167] A third update unit, configured to update the product information corresponding to the target product according to the draft data in response to the target command process being in the release state.

[0168] Optionally, the third update unit is further configured to:

[0169] In response to the target command process being in the release state, obtain a preset release policy from the command context corresponding to the target command process;

[0170] Update the product information corresponding to the target product according to the preset release policy and the draft data.

[0171] Optionally, the third update unit is further configured to:

[0172] In response to the preset release policy being real-time release, update the product information according to the draft data;

[0173] In response to the preset release policy being delayed release, add the target command process to a release queue, where the release queue includes at least one command process in the release state;

[0174] In response to the release time corresponding to the delayed release being reached, update the product information according to the draft data.

[0175] Optionally, the device further includes:

[0176] A second acquisition module, configured to acquire product attribute information corresponding to the target product;

[0177] A second determination module, configured to determine the review rule according to the product attribute information, where different product attribute information corresponds to different review rules;

[0178] A storage module, configured to store the review rule in the command context corresponding to the target command process.

[0179] Optionally, the device further includes:

[0180] A clearing module, configured to clear the draft data and the target command process in response to the completion of the update of the product information, where the draft data is the product update data of the target product.

[0181] In summary, the embodiments of the present application propose the concept of a command process. Different command processes can be determined for different commodity data update requests based on the different process attribute information included in the commodity data update requests, so that the commodity data can be updated based on the corresponding command process when updating the commodity data. For example, if there are commodity update data requests from two users, different command processes can be established for them respectively, and the two command processes can be executed respectively to update the commodity information, thereby realizing the isolation of different commodity data update operations and avoiding data confusion when multiple users update the commodity data simultaneously, and optimizing the commodity data update process.

[0182] It should be noted that when the device provided in the above embodiment realizes its functions, only the above-mentioned division of each functional module is used for illustration. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. In addition, the device provided in the above embodiment and the method embodiment belong to the same concept, and the specific implementation process is detailed in the method embodiment, which will not be repeated here.

[0183] Please refer to Figure 10 , which shows a structural block diagram of a server provided in an embodiment of the present application. The server can be used to implement the commodity data update method provided in the above embodiment. Specifically:

[0184] The server 1000 includes a central processing unit (CPU) 1001, a system memory 1004 including a random access memory (RAM) 1002 and a read-only memory (ROM) 1003, and a system bus 1005 connecting the system memory 1004 and the central processing unit 1001. The server 1000 further includes a basic input / output system (I / O system) 1006 for facilitating the transmission of information between various components within the server, and a mass storage device 1007 for storing an operating system 1013, application programs 1014, and other program modules 1015.

[0185] The basic input / output system 1006 includes a display 1008 for displaying information and input devices 1009 such as a mouse and a keyboard for user input of information. Both the display 1008 and the input devices 1009 are connected to the central processing unit 1001 through an input / output controller 1010 connected to the system bus 1005. The basic input / output system 1006 may further include an input / output controller 1010 for receiving and processing inputs from a plurality of other devices such as a keyboard, a mouse, or an electronic stylus. Similarly, the input / output controller 1010 also provides outputs to a display screen, a printer, or other types of output devices.

[0186] The mass storage device 1007 is connected to the central processing unit 1001 through a mass storage controller (not shown) connected to the system bus 1005. The mass storage device 1007 and its associated computer-readable storage medium provide non-volatile storage for the server 1000. That is, the mass storage device 1007 may include a computer-readable storage medium (not shown) such as a hard disk or a compact disc read-only memory (CD-ROM) drive.

[0187] Without loss of generality, the computer-readable storage medium may include computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable storage instructions, data structures, program modules, or other data. Computer storage media includes RAM, ROM, erasable programmable read-only registers (EPROM), electrically-erasable programmable read-only memory (EEPROM), flash memory or other solid-state storage technologies, CD-ROM, digital versatile disc (DVD) or other optical storage, magnetic tape cartridges, tapes, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the above several types. The above-mentioned system memory 1004 and mass storage device 1007 may be collectively referred to as memory.

[0188] The memory stores one or more programs, the one or more programs are configured to be executed by one or more central processing units 1001, the one or more programs contain instructions for implementing the above method embodiments, and the central processing unit 1001 executes the one or more programs to implement the methods provided by the above respective method embodiments.

[0189] According to various embodiments of the present application, the server 1000 may also run by connecting to a remote server on the network through a network such as the Internet. That is, the server 1000 may be connected to the network 1012 through the network interface unit 1011 connected to the system bus 1005. Or rather, the network interface unit 1011 may also be used to connect to other types of networks or remote server systems (not shown).

[0190] The memory further includes one or more programs. The one or more programs are stored in the memory, and the one or more programs include steps for performing the methods provided in the embodiments of the present application that are executed by the server.

[0191] Embodiments of the present application further provide a computer-readable storage medium. The computer-readable storage medium stores at least one instruction, and the at least one instruction is loaded and executed by the processor to implement the commodity data update method described in each of the above embodiments.

[0192] According to one aspect of the present application, there is provided a computer program product or a computer program. The computer program product or the computer program includes computer instructions, and the computer instructions are stored in a computer-readable storage medium. The processor of the server reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the server executes the commodity data update method provided in various alternative implementations of the above aspect.

[0193] It should be understood that the term "plurality" mentioned herein refers to two or more. "And / or" describes the association relationship of associated objects and indicates that there can be three relationships. For example, A and / or B may represent: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. In addition, the step numbers described herein only exemplarily show a possible execution sequence between steps. In some other embodiments, the above steps may not be executed in the order of the numbers. For example, two steps with different numbers may be executed simultaneously, or two steps with different numbers may be executed in the reverse order of the illustration. Embodiments of the present application do not limit this.

[0194] The above are only alternative embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for updating commodity data, characterized in that, the method includes: Receiving a commodity data update request, which is used to update the commodity information corresponding to the target commodity. The commodity data update request contains process attribute information, where different command processes correspond to different process attribute information, and the command process is the operation steps required from receiving the commodity data update request to publishing the commodity update data online; Determining the target command process corresponding to the commodity data update request according to the process attribute information; Executing the target command process to update the commodity information corresponding to the target commodity; When the command process indicates that the commodity update data meets the release conditions, sending the commodity update data to a second terminal. After receiving the commodity update data, the second terminal updates the commodity information by itself; The determining the target command process corresponding to the commodity data update request according to the process attribute information includes: In response to the created command process corresponding to the process attribute information being included in the command process set, determining the created command process as the target command process, where the command process set includes at least one created command process; In response to the created command process corresponding to the process attribute information not being included in the command process set, creating the target command process corresponding to the process attribute information; The determining the created command process as the target command process in response to the created command process corresponding to the process attribute information being included in the command process set includes: Obtaining the request initiator identifier corresponding to the commodity data update request, the commodity identifier corresponding to the target commodity, and the type of commodity information to be updated; In response to the request initiator identifier, the commodity identifier, and the type of commodity information being consistent with the process attribute information corresponding to the created command process, determining the created command process as the target command process.

2. The method according to claim 1, characterized in that, after determining the created command process as the target command process, the method further includes: Obtaining draft data associated with the created command process, where the draft data is the historical commodity update data of the target commodity and the historical commodity update data has not been published; In response to receiving an input operation of commodity update data, modifying the draft data according to the commodity update data.

3. The method according to claim 1, characterized in that, after creating the target command process corresponding to the process attribute information, the method further includes: In response to receiving an input operation of commodity update data, creating draft data according to the commodity update data; Associating the draft data with the target command process.

4. The method according to any one of claims 1 to 3, characterized in that, the executing the target command process to update the commodity information corresponding to the target commodity includes: In response to a submission operation on draft data, update the process status corresponding to the target command process from the editing status to the review status, where the draft data is the product update data of the target product; In response to the target command process being in the review status, review the draft data according to the review rules to obtain a review result; In response to the review result indicating that the draft data has passed the review, update the target command process from the review status to the release status; In response to the target command process being in the release status, update the product information corresponding to the target product according to the draft data.

5. The method according to claim 4, wherein, the updating the product information corresponding to the target product according to the draft data in response to the target command process being in the release status includes: In response to the target command process being in the release status, obtain a preset release policy from the command context corresponding to the target command process; Update the product information corresponding to the target product according to the preset release policy and the draft data.

6. The method according to claim 5, wherein, the updating the product information corresponding to the target product according to the preset release policy and the draft data includes: In response to the preset release policy being real-time release, update the product information according to the draft data; In response to the preset release policy being delayed release, add the target command process to a release queue, where the release queue includes at least one command process in the release status; In response to the release time corresponding to the delayed release being reached, update the product information according to the draft data.

7. The method according to claim 4, wherein, after the updating the process status corresponding to the target command process from the editing status to the review status in response to a submission operation on draft data, the method further includes: Obtain the product attribute information corresponding to the target product; Determine the review rules according to the product attribute information, where different product attribute information corresponds to different review rules; Store the review rules in the command context corresponding to the target command process.

8. The method according to any one of claims 1 to 3, wherein, after the updating the product information corresponding to the target product, the method further includes: In response to the completion of the update of the product information, clear the draft data and the target command process, where the draft data is the product update data of the target product.

9. A product data update device, wherein, the device includes: A receiving module, configured to receive a product data update request for updating the product information corresponding to a target product, where the product data update request includes process attribute information, and different command processes correspond to different process attribute information, and the command process is the operation steps required to publish the product update data to the online after receiving the product data update request; A first determination module, configured to determine a target command process corresponding to the commodity data update request according to the process attribute information; An update module, configured to execute the target command process, update the commodity information corresponding to the target commodity, and when the command process indicates that the commodity update data meets the release condition, send the commodity update data to a second terminal, and after receiving the commodity update data, the second terminal updates the commodity information by itself; The determining the target command process corresponding to the commodity data update request according to the process attribute information includes: In response to the created command process corresponding to the process attribute information being included in the command process set, determining the created command process as the target command process, where the command process set includes at least one created command process; In response to the created command process corresponding to the process attribute information not being included in the command process set, creating the target command process corresponding to the process attribute information; The responding to the created command process corresponding to the process attribute information being included in the command process set and determining the created command process as the target command process includes: Obtaining an initiator identifier corresponding to the commodity data update request, a commodity identifier corresponding to the target commodity, and a type of commodity information to be updated; In response to the initiator identifier, the commodity identifier, and the type of commodity information being consistent with the process attribute information corresponding to the created command process, determining the created command process as the target command process.

10. A server Characterized in that The server includes a processor and a memory, and a computer program is stored in the memory, and the computer program is loaded and executed by the processor to implement the commodity data update method according to any one of claims 1 to 8.

11. A non-transitory computer-readable storage medium, on which a computer program is stored, Characterized in that The computer program, when executed by a processor, implements the commodity data update method according to any one of claims 1 to 8.

Images