CN112070585A - Order state unified management method and device, computer equipment and storage medium - Google Patents
Order state unified management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112070585A CN112070585A CN202010942260.6A CN202010942260A CN112070585A CN 112070585 A CN112070585 A CN 112070585A CN 202010942260 A CN202010942260 A CN 202010942260A CN 112070585 A CN112070585 A CN 112070585A
- Authority
- CN
- China
- Prior art keywords
- order
- state
- identifier
- rule table
- trigger
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 41
- 238000012790 confirmation Methods 0.000 claims abstract description 45
- 238000000034 method Methods 0.000 claims abstract description 17
- 238000004590 computer program Methods 0.000 claims description 23
- 230000004044 response Effects 0.000 claims description 5
- 230000008859 change Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000012544 monitoring process Methods 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000004075 alteration Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
- G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
- G06Q30/0635—Processing of requisition or of purchase orders
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/248—Presentation of query results
Abstract
The application relates to the technical field of order management, in particular to a unified management method and device for order states, computer equipment and a storage medium. The method comprises the following steps: responding to the order state confirmation request, and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier; inquiring the order table to determine the current order state corresponding to the order identifier; determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark; and updating the order state corresponding to the order identifier in the order table to be the target order state. The embodiment of the invention can conveniently and independently manage the order states of all orders in the system, and effectively solves the problems that the judging logics of the order states are too dispersed and are easy to miss or mutually cover when the order states are expanded in the prior art.
Description
Technical Field
The present application relates to the field of order management technologies, and in particular, to a unified order status management method, apparatus, computer device, and storage medium.
Background
When the order states (such as business states) of the orders are more and the scenes of the change of the order states are complex, a plurality of states exist in the life cycles of the orders, and if the cycle and the links of the orders are longer, the corresponding order states are more, the scenes of the change of the order states are correspondingly more complicated, and the difficulty in managing the order states is higher. Meanwhile, the change of the order state is also often used as a trigger event, so that when the order state is wrong, the affected order is not the system, and even the system related to the system is affected.
In addition, the judgment logic of the order state is dispersed in each scene, if the order state is to be changed or expanded, if the judgment logic of the order state in each scene is modified, the maintenance operation is complicated, and the problem that the judgment logic is omitted or mutually covered easily occurs during maintenance.
Disclosure of Invention
The invention provides a unified management method, a unified management device, computer equipment and a storage medium for order states, aiming at the defects of the prior art.
The present invention provides a unified order status management method according to a first aspect, and in one embodiment, the method includes:
responding to the order state confirmation request, and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier;
inquiring the order table to determine the current order state corresponding to the order identifier;
determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark;
and updating the order state corresponding to the order identifier in the order table to be the target order state.
In one embodiment, the step of determining the target order state corresponding to the order identifier according to the current order state, the service type identifier and the trigger event identifier includes:
taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table;
and determining the state information obtained by inquiring from the state trigger rule table as the state of the target order.
In one embodiment, the step of querying the state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions includes:
and taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table which is pre-loaded in a cache.
In one embodiment, before the step of querying the state trigger rule table pre-loaded in the cache by using the current order state, the service type identifier and the trigger event identifier as query conditions, the method includes:
acquiring a state trigger rule table from a database;
and pre-loading the state trigger rule table into a cache.
In one embodiment, the step of querying the state trigger rule table pre-loaded in the cache by using the current order state, the service type identifier and the trigger event identifier as query conditions includes:
detecting whether a state trigger rule table exists in a cache or not;
if the cache stores a state trigger rule table, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table which is pre-loaded in the cache;
if the state trigger rule table does not exist in the cache, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table stored in the database, the state trigger rule table is obtained from the database, and the state trigger rule table is preloaded into the cache.
In one embodiment, after the step of querying the state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions, the method comprises the following steps:
if the state information is not inquired from the state trigger rule table, recording an order mark through a log, recording the current order state corresponding to the order mark and distributing a first mark for the current order state, wherein the first mark is used for indicating that the current order state is not provided with a corresponding state trigger rule;
and sending a preset exception prompt to a sender of the order state confirmation request.
In an embodiment, the order status confirmation request is sent by a sender of the order status confirmation request after monitoring a trigger event corresponding to the trigger event identifier.
The present invention provides an order status unified management apparatus according to a second aspect, which in one embodiment comprises:
the request response module is used for responding to the order state confirmation request and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier;
the current state determining module is used for inquiring the order table to determine the current order state corresponding to the order mark;
the target state determining module is used for determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark;
and the order state updating module is used for updating the order state corresponding to the order identifier in the order table to be the target order state.
The present invention provides according to a third aspect a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of an embodiment of any of the methods described above when executing the computer program.
The present invention provides according to a fourth aspect a computer-readable storage medium having stored thereon a computer program which, when being executed by a processor, carries out the steps of the embodiments of the method of any one of the above.
In the embodiment of the invention, in response to the order state confirmation request, the order identifier corresponding to the order state confirmation request, the service type identifier corresponding to the order identifier and the trigger event identifier are obtained; inquiring the order table to determine the current order state corresponding to the order identifier; determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark; the order state corresponding to the order mark in the order table is updated to the target order state, so that the order states of all orders in the system can be independently managed conveniently, the problems that the judging logic of the order states is too dispersed and the judging logic is easy to miss or cover when the order states are expanded in the prior art are effectively solved, the life cycle of the order states of all orders is more visual, the probability of code false alteration is reduced, and the robustness of products is improved.
Drawings
FIG. 1 is a flow chart illustrating a unified order status management method according to an embodiment;
FIG. 2 is a diagram of an exemplary implementation of a unified order status management method;
FIG. 3 is a diagram of order status trigger rules in one embodiment;
FIG. 4 is a block diagram of an embodiment of an order status unified management apparatus;
FIG. 5 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The invention provides a unified order status management method, which in one embodiment comprises the following steps as shown in fig. 1:
s110: and responding to the order state confirmation request, and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier.
In this embodiment, the order status unified management method can be applied to the application environment shown in fig. 2, where "10" in fig. 2 is an order status management server (hereinafter, referred to as a management server), and "21", "22", and "23" are business side servers. The management server and the business side server can be realized by independent servers or a server cluster consisting of a plurality of servers.
In the embodiment, all the order states of the order and the corresponding trigger events capable of triggering the order state change are extracted from each service scene to be independently managed by the management server in a unified manner, when a service party in each service scenario monitors a trigger event, an order identifier (such as an order number and/or an order line number) of a related order, a service type identifier corresponding to the order identifier (for distinguishing different service scenarios), and a trigger event identifier corresponding to the monitored trigger event (for determining what the trigger event monitored by the service party is) are obtained, and generating an order state confirmation request and sending the order state confirmation request to a management server, wherein the management server responds to the request after receiving the request, and specifically, the management server responds to the order state confirmation request and acquires an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier.
S120: and querying the order table to determine the current order state corresponding to the order identifier.
In this embodiment, the order table is used to record the order status corresponding to each order. The current order state corresponding to the order identifier can be obtained through inquiring the order table.
S130: and determining the target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark.
In this embodiment, the target order state corresponding to the order identifier needs to be determined according to the current order state corresponding to the order identifier, the service type identifier, and the trigger event identifier.
In one embodiment, the step of determining the target order state corresponding to the order identifier according to the current order state, the service type identifier and the trigger event identifier includes:
taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table;
and determining the state information obtained by inquiring from the state trigger rule table as the state of the target order.
The state trigger rule table includes a plurality of order state trigger rules corresponding to a plurality of different service types, that is, each service type corresponds to a plurality of order state trigger rules, and the order state trigger rules need to be configured in advance. Specifically, the pre-preparing process of any order state triggering rule corresponding to any service type may be to list all order states of an order in a service scenario in advance and create an order state enumeration class, list all triggering events capable of triggering order state change and create an event enumeration class, and finally bind the order states and the triggering events to serve as the pre-prepared order state triggering rule.
According to the embodiment, the change of the order state is uniformly managed by prefabricating the order state trigger rule, the probability of error change of the order state is effectively reduced, the service risk brought by the newly added order state is reduced, and the flexibility of rule configuration is improved.
Further, how to determine the status of the target order based on the status trigger rule table is described below by way of an example.
As shown in fig. 3, the order states listed for a certain service type include "state 1", "state 2", "state 3", and "state 4", the trigger events listed include "event 1", "event 2", "event 3", and "event 4", and the preconfigured state trigger rule table includes 4 order state trigger rules. Assuming that the current order state is state 1 and the service type identifier is event 1, the current order state, i.e., state 1, and the service type identifier, i.e., event 1, are used as query conditions to query a state trigger rule table, and as can be seen from the state trigger rule table shown in fig. 3, the order state trigger rule applicable to state 1 and event 1 is a first trigger rule, and the target order state can be determined to be state 2 by the trigger rule. Similarly, if the current order state is state 2, the service type identifier is event 3, and the applicable trigger rule is the third trigger rule, it can be finally determined that the target order state is state 4.
Furthermore, after the management server queries the target order state, the management server may also return the target order state to a related service party, that is, a sender of the order state confirmation request, so that the management server is convenient to use in a service scenario.
S140: and updating the order state corresponding to the order identifier in the order table to be the target order state.
In this embodiment, after obtaining the target order state by querying from the state trigger rule table, the management server updates the order state corresponding to the order identifier in the order table to the target order state, for example, if the order state corresponding to the order identifier in the order table is state 1, and the determined target order state is state 4, the order state corresponding to the order identifier in the order table is updated to state 4.
In the embodiment of the invention, in response to the order state confirmation request, the order identifier corresponding to the order state confirmation request, the service type identifier corresponding to the order identifier and the trigger event identifier are obtained; inquiring the order table to determine the current order state corresponding to the order identifier; determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark; the order state corresponding to the order mark in the order table is updated to the target order state, so that the order states of all orders in the system can be independently managed conveniently, the problems that the judging logic of the order states is too dispersed and the judging logic is easy to miss or cover when the order states are expanded in the prior art are effectively solved, the life cycle of the order states of all orders is more visual, the probability of code false alteration is reduced, and the robustness of products is improved.
In one embodiment, the step of querying the state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions includes:
and taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table which is pre-loaded in a cache.
In this embodiment, in order to improve the query efficiency of the state trigger rule table and reduce the pressure of the database, the state trigger rule table is preloaded into the cache, and when the query is required, the state trigger rule table preloaded in the cache is queried by using the current order state, the service type identifier and the trigger event identifier as query conditions.
Further, in an embodiment, before the step of querying the state trigger rule table pre-loaded in the cache with the current order state, the service type identifier, and the trigger event identifier as query conditions, the method includes:
acquiring a state trigger rule table from a database;
and pre-loading the state trigger rule table into a cache.
In another embodiment, the step of querying the state trigger rule table pre-loaded in the cache by using the current order state, the service type identifier and the trigger event identifier as query conditions includes:
detecting whether a state trigger rule table exists in a cache or not;
if the cache stores a state trigger rule table, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table which is pre-loaded in the cache;
if the state trigger rule table does not exist in the cache, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table stored in the database, the state trigger rule table is obtained from the database, and the state trigger rule table is preloaded into the cache.
In this embodiment, when the state trigger rule table needs to be queried, the management server first detects whether the state trigger rule table exists in the cache, if the state trigger rule table exists in the cache, the state trigger rule table stored in the cache is queried to improve query efficiency, and if the state trigger rule table exists in the cache, the state trigger rule table stored in the database is queried, and the state trigger rule table in the database is backed up and loaded into the cache after querying, so that the state trigger rule table can be queried from the cache during subsequent querying to improve query efficiency.
In one embodiment, after the step of querying the state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions, the method comprises the following steps:
if the state information is not inquired from the state trigger rule table, recording an order mark through a log, recording the current order state corresponding to the order mark and distributing a first mark for the current order state, wherein the first mark is used for indicating that the current order state is not provided with a corresponding state trigger rule;
and sending a preset exception prompt to a sender of the order state confirmation request.
In this embodiment, if the management server does not query corresponding state information from the state trigger rule table according to the current order state, the service type identifier, and the trigger event identifier, and it may be that the state trigger rule table does not have an order state trigger rule corresponding to the current order state, at this time, it is necessary to record information related to the order state confirmation request through a log, and allocate a first identifier to the current order state to mark a current abnormal condition type, that is, the current order state is not configured with a corresponding state trigger rule. A preset exception prompt needs to be sent to the relevant service party, that is, the sender of the order state confirmation request, so that the relevant service party can handle the exception according to the current service of the relevant service party.
In one embodiment, as shown in fig. 4, there is provided an order status unified management apparatus, including the following modules:
a request response module 110, configured to respond to the order status confirmation request, and obtain an order identifier corresponding to the order status confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier;
a current state determining module 120, configured to query the order table to determine a current order state corresponding to the order identifier;
a target state determining module 130, configured to determine, according to the current order state, the service type identifier, and the trigger event identifier, a target order state corresponding to the order identifier;
and the order state updating module 140 is configured to update the order state corresponding to the order identifier in the order table to the target order state.
In one embodiment, the target state determination module includes:
the state query submodule is used for taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table;
and the target state determining submodule is used for determining the state information obtained by inquiring the state triggering rule table as the state of the target order.
In one embodiment, the status query sub-module is further configured to query, as a query condition, a status trigger rule table pre-loaded in the cache, with the current order status, the service type identifier, and the trigger event identifier.
In one embodiment, the target state determination module further comprises:
the rule table acquisition submodule is used for acquiring a state trigger rule table from a database;
and the rule table loading submodule is used for pre-loading the state trigger rule table into the cache.
In one embodiment, the status query submodule includes:
the detection unit is used for detecting whether a state trigger rule table exists in the cache or not;
the first processing unit is used for inquiring the state trigger rule table which is loaded in the cache in advance by taking the current order state, the service type identifier and the trigger event identifier as inquiry conditions when the state trigger rule table is stored in the cache;
and the second processing unit is used for inquiring the state trigger rule table stored in the database by taking the current order state, the service type identifier and the trigger event identifier as inquiry conditions when the state trigger rule table does not exist in the cache, acquiring the state trigger rule table from the database and pre-loading the state trigger rule table into the cache.
In one embodiment, the target state determination module further comprises:
the recording submodule is used for recording an order mark through a log when the state information is not inquired from the state trigger rule table, recording the current order state corresponding to the order mark and distributing a first mark for the current order state, wherein the first mark is used for indicating that the current order state is not provided with a corresponding state trigger rule;
and the abnormal prompt sending submodule is used for sending a preset abnormal prompt to a sender of the order state confirmation request.
In one embodiment, the order status confirmation request is sent by a sender of the order status confirmation request after monitoring a trigger event corresponding to the trigger event identifier.
For specific limitations of the order status unified management apparatus, reference may be made to the above limitations of the order status unified management method, which is not described herein again. All or part of the modules in the order status unified management device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, the internal structure of which may be as shown in FIG. 5. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as a state trigger rule table and the like. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a unified order status management method.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
responding to the order state confirmation request, and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier; inquiring the order table to determine the current order state corresponding to the order identifier; determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark; and updating the order state corresponding to the order identifier in the order table to be the target order state.
In one embodiment, when the processor executes the computer program to determine the target order state corresponding to the order identifier according to the current order state, the service type identifier and the trigger event identifier, the following steps are further implemented:
taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table; and determining the state information obtained by inquiring from the state trigger rule table as the state of the target order.
In one embodiment, the processor executes the computer program to realize the following steps when the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table:
and taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table which is pre-loaded in a cache.
In one embodiment, before the step of querying the state trigger rule table pre-loaded in the cache with the current order state, the service type identifier and the trigger event identifier as query conditions, the processor executes the computer program and further implements the following steps:
acquiring a state trigger rule table from a database; and pre-loading the state trigger rule table into a cache.
In one embodiment, when the processor executes the computer program to query the state trigger rule table pre-loaded in the cache with the current order state, the service type identifier and the trigger event identifier as query conditions, the following steps are further implemented:
detecting whether a state trigger rule table exists in a cache or not; if the cache stores a state trigger rule table, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table which is pre-loaded in the cache; if the state trigger rule table does not exist in the cache, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table stored in the database, the state trigger rule table is obtained from the database, and the state trigger rule table is preloaded into the cache.
In one embodiment, after the step of querying the state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions, the processor executes a computer program to further implement the following steps:
if the state information is not inquired from the state trigger rule table, recording an order mark through a log, recording the current order state corresponding to the order mark and distributing a first mark for the current order state, wherein the first mark is used for indicating that the current order state is not provided with a corresponding state trigger rule; and sending a preset exception prompt to a sender of the order state confirmation request.
In one embodiment, the order status confirmation request is sent by a sender of the order status confirmation request after monitoring a trigger event corresponding to the trigger event identifier.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
responding to the order state confirmation request, and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier; inquiring the order table to determine the current order state corresponding to the order identifier; determining a target order state corresponding to the order mark according to the current order state, the service type mark and the trigger event mark; and updating the order state corresponding to the order identifier in the order table to be the target order state.
In one embodiment, the computer program is executed by a processor, and when determining the target order state corresponding to the order identifier according to the current order state, the service type identifier and the trigger event identifier, further implements the following steps:
taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table; and determining the state information obtained by inquiring from the state trigger rule table as the state of the target order.
In one embodiment, the computer program is executed by a processor, and when querying a state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions, further implements the following steps:
and taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table which is pre-loaded in a cache.
In one embodiment, the computer program executed by the processor further implements the following steps before the step of querying the state trigger rule table pre-loaded in the cache with the current order state and service type identifier and the trigger event identifier as query conditions:
acquiring a state trigger rule table from a database; and pre-loading the state trigger rule table into a cache.
In one embodiment, when the computer program is executed by a processor and queries a state trigger rule table pre-loaded in a cache by using a current order state, a service type identifier and a trigger event identifier as query conditions, the following steps are further implemented:
detecting whether a state trigger rule table exists in a cache or not; if the cache stores a state trigger rule table, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table which is pre-loaded in the cache; if the state trigger rule table does not exist in the cache, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table stored in the database, the state trigger rule table is obtained from the database, and the state trigger rule table is preloaded into the cache.
In one embodiment, the computer program executed by the processor further implements the following steps after the step of querying the state trigger rule table by using the current order state and service type identifier and the trigger event identifier as query conditions:
if the state information is not inquired from the state trigger rule table, recording an order mark through a log, recording the current order state corresponding to the order mark and distributing a first mark for the current order state, wherein the first mark is used for indicating that the current order state is not provided with a corresponding state trigger rule; and sending a preset exception prompt to a sender of the order state confirmation request.
In one embodiment, the order status confirmation request is sent by a sender of the order status confirmation request after monitoring a trigger event corresponding to the trigger event identifier.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A unified order state management method is characterized by comprising the following steps:
responding to an order state confirmation request, and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier;
inquiring an order table to determine the current order state corresponding to the order identifier;
determining a target order state corresponding to the order identifier according to the current order state, the service type identifier and the trigger event identifier;
and updating the order state corresponding to the order identifier in the order table to be the target order state.
2. The order status unified management method according to claim 1,
the step of determining the target order state corresponding to the order identifier according to the current order state, the service type identifier and the trigger event identifier comprises the following steps:
taking the current order state, the service type identifier and the trigger event identifier as query conditions to query a state trigger rule table;
and determining the state information obtained by inquiring the state trigger rule table as the state of the target order.
3. The order status unified management method according to claim 2,
the step of querying a state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions includes:
and querying a state trigger rule table which is pre-loaded in a cache by taking the current order state, the service type identifier and the trigger event identifier as query conditions.
4. The order status unified management method according to claim 3,
before the step of querying the state trigger rule table pre-loaded in the cache by using the current order state, the service type identifier and the trigger event identifier as query conditions, the method comprises the following steps:
acquiring the state trigger rule table from a database;
and pre-loading the state trigger rule table into a cache.
5. The order status unified management method according to claim 3,
the step of querying a state trigger rule table pre-loaded in a cache by using the current order state, the service type identifier and the trigger event identifier as query conditions comprises the following steps:
detecting whether a state trigger rule table exists in a cache or not;
if the state trigger rule table is stored in the cache, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table which is pre-loaded in the cache;
if the state trigger rule table does not exist in the cache, the current order state, the service type identifier and the trigger event identifier are used as query conditions to query the state trigger rule table stored in a database, the state trigger rule table is obtained from the database, and the state trigger rule table is pre-loaded into the cache.
6. The order status unified management method according to claim 2,
after the step of querying a state trigger rule table by using the current order state, the service type identifier and the trigger event identifier as query conditions, the method comprises the following steps:
if no state information is inquired from the state trigger rule table, recording the order identification through a log, recording the current order state corresponding to the order identification and distributing a first identification for the current order state, wherein the first identification is used for indicating that the current order state is not provided with a corresponding state trigger rule;
and sending a preset exception prompt to a sender of the order state confirmation request.
7. The order status unified management method according to claim 1,
the order state confirmation request is sent by a sender of the order state confirmation request after the trigger event corresponding to the trigger event identification is monitored.
8. An order status unified management apparatus, comprising:
the request response module is used for responding to the order state confirmation request and acquiring an order identifier corresponding to the order state confirmation request, and a service type identifier and a trigger event identifier corresponding to the order identifier;
the current state determining module is used for inquiring an order table to determine the current order state corresponding to the order identifier;
a target state determining module, configured to determine, according to the current order state, the service type identifier, and the trigger event identifier, a target order state corresponding to the order identifier;
and the order state updating module is used for updating the order state corresponding to the order identifier in the order table to be the target order state.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010942260.6A CN112070585A (en) | 2020-09-09 | 2020-09-09 | Order state unified management method and device, computer equipment and storage medium |
| CA3130314A CA3130314A1 (en) | 2020-09-09 | 2021-09-09 | Order state unified management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010942260.6A CN112070585A (en) | 2020-09-09 | 2020-09-09 | Order state unified management method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112070585A true CN112070585A (en) | 2020-12-11 |
Family
ID=73664636
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010942260.6A Pending CN112070585A (en) | 2020-09-09 | 2020-09-09 | Order state unified management method and device, computer equipment and storage medium |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112070585A (en) |
| CA (1) | CA3130314A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817707A (en) * | 2020-12-30 | 2021-05-18 | 金蝶软件（中国）有限公司 | Task execution method and device, computer equipment and storage medium |
| CN114895978A (en) * | 2022-05-06 | 2022-08-12 | 上海金仕达软件科技有限公司 | Method, device, medium and equipment for processing state entrusted in report |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060070083A1 (en) * | 2004-09-30 | 2006-03-30 | Frank Brunswig | Publish-subscribe event notifications |
| CN111144982A (en) * | 2019-12-20 | 2020-05-12 | 网联清算有限公司 | Order state transition method and device, electronic equipment and storage medium |
-
2020
- 2020-09-09 CN CN202010942260.6A patent/CN112070585A/en active Pending
-
2021
- 2021-09-09 CA CA3130314A patent/CA3130314A1/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060070083A1 (en) * | 2004-09-30 | 2006-03-30 | Frank Brunswig | Publish-subscribe event notifications |
| CN111144982A (en) * | 2019-12-20 | 2020-05-12 | 网联清算有限公司 | Order state transition method and device, electronic equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112817707A (en) * | 2020-12-30 | 2021-05-18 | 金蝶软件（中国）有限公司 | Task execution method and device, computer equipment and storage medium |
| CN112817707B (en) * | 2020-12-30 | 2024-02-20 | 金蝶软件（中国）有限公司 | Task execution method, device, computer equipment and storage medium |
| CN114895978A (en) * | 2022-05-06 | 2022-08-12 | 上海金仕达软件科技有限公司 | Method, device, medium and equipment for processing state entrusted in report |
| CN114895978B (en) * | 2022-05-06 | 2023-10-13 | 上海金仕达软件科技股份有限公司 | Method, device, medium and equipment for processing entrusted state in newspaper disc |
Also Published As
| Publication number | Publication date |
|---|---|
| CA3130314A1 (en) | 2022-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110647438B (en) | Event monitoring method and device, computer equipment and storage medium | |
| CN110750267B (en) | Service information updating method, device, computer equipment and storage medium | |
| CN108897658B (en) | Method and device for monitoring master database, computer equipment and storage medium | |
| CN111611137A (en) | Alarm monitoring method and device, computer equipment and storage medium | |
| CN110633160A (en) | Interface calling method and device, computer equipment and storage medium | |
| CN108446172B (en) | Data calling method and device, computer equipment and storage medium | |
| CN110334126B (en) | Timing task processing method and device based on Spring MVC and computer equipment | |
| CN109460252B (en) | Configuration file processing method and device based on git and computer equipment | |
| CN108924258B (en) | Background information pushing method and device, computer equipment and storage medium | |
| CN112613993B (en) | Transaction data processing method and device, computer equipment and storage medium | |
| CN112070585A (en) | Order state unified management method and device, computer equipment and storage medium | |
| CN108763046B (en) | Thread running monitoring method, device, computer equipment and storage medium | |
| CN110727698A (en) | Database access method and device, computer equipment and storage medium | |
| US10616055B2 (en) | Hash based device configuration management | |
| CN112865992A (en) | Method and device for switching master nodes in distributed master-slave system and computer equipment | |
| CN110674149B (en) | Service data processing method and device, computer equipment and storage medium | |
| CN113946427A (en) | Task processing method, processor and storage medium for multi-operating system | |
| CN108924772B (en) | Short message sending method and device, computer equipment and storage medium | |
| CN111198921A (en) | Database switching method and device, computer equipment and storage medium | |
| CN114500315A (en) | Equipment state monitoring method and device, computer equipment and storage medium | |
| CN112132652B (en) | Order information acquisition method and device, computer equipment and storage medium | |
| CN111159233B (en) | Distributed caching method, system, computer equipment and storage medium | |
| CN113010306A (en) | Service data processing method and device, computer equipment and storage medium | |
| CN111382976A (en) | Early warning data processing method and device, computer equipment and storage medium | |
| CN109831521B (en) | Cache instance management method and device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20201211 |