CN112581069A - System, method, apparatus and storage medium for processing task - Google Patents

System, method, apparatus and storage medium for processing task Download PDF

Info

Publication number
CN112581069A
CN112581069A CN201910927587.3A CN201910927587A CN112581069A CN 112581069 A CN112581069 A CN 112581069A CN 201910927587 A CN201910927587 A CN 201910927587A CN 112581069 A CN112581069 A CN 112581069A
Authority
CN
China
Prior art keywords
task
proxy
server
message
information
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
Application number
CN201910927587.3A
Other languages
Chinese (zh)
Inventor
郭盼超
韦高鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huihai Automotive Technology Tianjin Co ltd
Original Assignee
Huihai Automotive Technology Tianjin Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huihai Automotive Technology Tianjin Co ltd filed Critical Huihai Automotive Technology Tianjin Co ltd
Priority to CN201910927587.3A priority Critical patent/CN112581069A/en
Publication of CN112581069A publication Critical patent/CN112581069A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/103Workflow collaboration or project management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90Details of database functions independent of the retrieved data types
    • G06F16/903Querying
    • G06F16/90335Query processing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46Multiprogramming arrangements
    • G06F9/54Interprogram communication
    • G06F9/546Message passing systems or structures, e.g. queues
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/109Time management, e.g. calendars, reminders, meetings or time accounting
    • G06Q10/1093Calendar-based scheduling for persons or groups
    • G06Q10/1097Task assignment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00Indexing scheme relating to G06F9/00
    • G06F2209/54Indexing scheme relating to G06F9/54
    • G06F2209/547Messaging middleware

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Tourism & Hospitality (AREA)
  • Quality & Reliability (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Economics (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computational Linguistics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A system, method, apparatus, and storage medium for processing tasks are disclosed. Wherein, the method comprises the following steps: sending a creating request for creating the agent task to a process server, wherein the process server is used for processing a process related to the agent task; pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler, and the message middleware is used for storing the task information; and transmitting task information of the proxy task related to the task handler to the terminal device in response to a query request for querying the proxy task received from the terminal device of the task handler.

Description

System, method, apparatus and storage medium for processing task
Technical Field
The present application relates to the field of computer technologies, and in particular, to a system, a method, an apparatus, and a storage medium for processing tasks.
Background
With the rapid development of the software industry, workflows are commonly applied to ERP and OA of various companies and some systems requiring approval processes. With the increase of the business volume, the mode of integrating the workflow in the business system cannot meet the daily requirements of the company, and most of the companies can independently use the workflow as a system to interact with the business system. The interactions mainly include flow initiation, proxy query, task processing and the like. The business system is mainly responsible for business data processing, and the workflow system is responsible for process data processing.
When the service system needs to initiate an approval process, an http request is sent to the workflow system, the workflow system receives the request and initiates the process according to the transmitted service number, and a proxy task is generated and distributed to designated personnel. When the service system displays the agent task, a request is sent to query the agent task in the workflow system, and then detailed service data is displayed through service number association according to the queried data. However, the workflow system is required to be queried first for each query agent of the business system, so that not only is the response time of the business system prolonged, but also the burden of the workflow system is increased, and particularly, the data volume is large, and the interaction is more frequent when the data is displayed in page paging. In addition, in a proxy list returned by the workflow system, information such as the name and address of the merchant is inquired in the business system according to the number of the merchant, and then the information is displayed in a page. Such a solution is time consuming and cumbersome.
In view of the technical problems in the prior art that the workflow system needs to be queried first for each query agent of the service system, thereby prolonging the response time of the service system and increasing the burden of the workflow system, no effective solution is proposed at present.
Disclosure of Invention
Embodiments of the present disclosure provide a system, a method, an apparatus, and a storage medium for processing tasks, so as to at least solve the technical problem existing in the prior art that a workflow system needs to be queried first for each query agent of a business system, thereby prolonging the response time of the business system and increasing the burden of the workflow system.
According to an aspect of an embodiment of the present disclosure, there is provided a system for processing a task, including: the system comprises a service server, a process server and a message server deployed with message middleware, wherein the service server is used for processing service data, the process server is used for processing processes related to a proxy task, the message server deployed with the message middleware is used for storing task information corresponding to the proxy task, and the service server is configured to execute the following operations: sending a creating request for creating a proxy task to a process server; pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler; in response to a query request for querying a proxy task received from a terminal device of a task handler, sending task information of the proxy task related to the task handler to the terminal device; the flow server is configured to perform the following operations: receiving a creating request for creating a proxy task sent by a service server; in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and pushing the task information corresponding to the proxy task to a message server deployed with message middleware.
According to another aspect of the embodiments of the present disclosure, there is also provided a method for processing a task, including: sending a creating request for creating the agent task to a process server, wherein the process server is used for processing a process related to the agent task; pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler, and the message middleware is used for storing the task information; and transmitting task information of the proxy task related to the task handler to the terminal device in response to a query request for querying the proxy task received from the terminal device of the task handler.
According to another aspect of the embodiments of the present disclosure, there is also provided a method for processing a task, including: receiving a creating request for creating a proxy task sent by a service server, wherein the service server is used for processing service data; in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and pushing the task information to a message server deployed with message middleware, wherein the message middleware is used for storing the task information.
According to another aspect of the embodiments of the present disclosure, there is also provided a storage medium including a stored program, wherein the method of any one of the above is performed by a processor when the program is executed.
According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for processing a task, including: the system comprises a sending module, a flow server and a processing module, wherein the sending module is used for sending a creating request for creating a proxy task to the flow server, and the flow server is used for processing a flow related to the proxy task; the system comprises an acquisition module, a task processing module and a task processing module, wherein the acquisition module is used for pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, the proxy task is processed by a corresponding task processor, and the message middleware is used for storing the task information; and the query module is used for responding to a query request for querying the proxy task received from the terminal equipment of the task processor and sending task information of the proxy task related to the task processor to the terminal equipment.
According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for processing a task, including: the receiving module is used for receiving a creation request for creating a proxy task sent by a service server, and the service server is used for processing service data; the creating module is used for responding to the creating request, creating the proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task processor; and the pushing module is used for pushing the task information to a message server which is provided with a message middleware, and the message middleware is used for storing the task information.
According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for processing a task, including: a first processor; and a first memory coupled to the first processor for providing instructions to the first processor to process the following processing steps: sending a creating request for creating the agent task to a process server, wherein the process server is used for processing a process related to the agent task; pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler, and the message middleware is used for storing the task information; and transmitting task information of the proxy task related to the task handler to the terminal device in response to a query request for querying the proxy task received from the terminal device of the task handler.
According to another aspect of the embodiments of the present disclosure, there is also provided an apparatus for processing a task, including: a second processor; and a second memory coupled to the second processor for providing instructions to the second processor to process the following processing steps: receiving a creating request for creating a proxy task sent by a service server, wherein the service server is used for processing service data; in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and pushing the task information to a message server deployed with message middleware, wherein the message middleware is used for storing the task information.
In the embodiment of the present disclosure, the process server may create a proxy task according to a request sent by the service server, and push a task message to the message server deployed with the message middleware. The service server can regularly pull the task message from the message middleware deployed by the message server, and then send the task related to the task processor to the terminal equipment of the processor according to the query request of the terminal equipment of the task processor. Therefore, the business system does not need to pass through the process server every time the agent task is acquired, and does not need to pass through the process server when the agent task is inquired. Therefore, the technical effects of reducing the workload of the workflow system, saving time and simplifying the flow are achieved. And the technical problems that the workflow system needs to be inquired firstly for each inquiry agency of the service system in the prior art, so that the response time of the service system is prolonged and the burden of the workflow system is increased are solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the disclosure and together with the description serve to explain the disclosure and not to limit the disclosure. In the drawings:
fig. 1 is a hardware block diagram of a computing device for implementing the method according to embodiment 1 of the present disclosure;
fig. 2 is a schematic diagram of a system for processing tasks according to a first aspect of embodiment 1 of the present disclosure;
FIG. 3 is a flow chart of a workflow of a system for processing tasks according to embodiment 1 of the present disclosure;
fig. 4 is a schematic flow chart of a method for processing tasks according to a second aspect of embodiment 1 of the present disclosure;
fig. 5 is a flowchart illustrating a method for processing tasks according to a third aspect of embodiment 1 of the present disclosure;
fig. 6 is a schematic diagram of an apparatus for processing tasks according to a first aspect of embodiment 2 of the present disclosure;
fig. 7 is a schematic diagram of an apparatus for processing tasks according to a second aspect of embodiment 2 of the present disclosure;
fig. 8 is a schematic diagram of an apparatus for processing tasks according to a first aspect of embodiment 3 of the present disclosure; and
fig. 9 is a schematic diagram of an apparatus for processing tasks according to a second aspect of embodiment 3 of the present disclosure.
Detailed Description
In order to make those skilled in the art better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure. It is to be understood that the described embodiments are merely exemplary of some, and not all, of the present disclosure. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
It should be noted that the terms "first," "second," and the like in the description and claims of the present disclosure and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein are capable of operation in sequences other than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
Example 1
According to the present embodiment, there is provided an embodiment of a method of processing tasks, it being noted that the steps illustrated in the flowchart of the figure may be performed in a computer system such as a set of computer-executable instructions, and that while a logical order is illustrated in the flowchart, in some cases the steps illustrated or described may be performed in an order different than here.
The method embodiments provided by the present embodiment may be executed in a mobile terminal, a computer terminal, a server or a similar computing device. Fig. 1 illustrates a hardware block diagram of a computing device for implementing a method of processing tasks. As shown in fig. 1, the computing device may include one or more processors (which may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory for storing data, and a transmission device for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 1 is only an illustration and is not intended to limit the structure of the electronic device. For example, the computing device may also include more or fewer components than shown in FIG. 1, or have a different configuration than shown in FIG. 1.
It should be noted that the one or more processors and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuitry may be a single, stand-alone processing module, or incorporated in whole or in part into any of the other elements in the computing device. As referred to in the disclosed embodiments, the data processing circuit acts as a processor control (e.g., selection of a variable resistance termination path connected to the interface).
The memory may be used to store software programs and modules of application software, such as program instructions/data storage devices corresponding to the method for processing tasks in the embodiments of the present disclosure, and the processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, the method for processing tasks of the application programs described above is implemented. The memory may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory located remotely from the processor, which may be connected to the computing device over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The transmission device is used for receiving or transmitting data via a network. Specific examples of such networks may include wireless networks provided by communication providers of the computing devices. In one example, the transmission device includes a Network adapter (NIC) that can be connected to other Network devices through a base station to communicate with the internet. In one example, the transmission device may be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.
The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the computing device.
It should be noted here that in some alternative embodiments, the computing device shown in fig. 1 described above may include hardware elements (including circuitry), software elements (including computer code stored on a computer-readable medium), or a combination of both hardware and software elements. It should be noted that FIG. 1 is only one example of a particular specific example and is intended to illustrate the types of components that may be present in a computing device as described above.
Fig. 2 is a schematic diagram of a system for processing tasks according to the first aspect of the present embodiment, and referring to fig. 2, the system includes: the task information processing system comprises a business server 210, a flow server 220 and a message server 230 with message middleware, wherein the business server 210 is used for processing business data, the flow server 220 is used for processing flows related to a proxy task, and the message server 230 with message middleware is used for storing task information corresponding to the proxy task. The business server 210, the process server 220, and the message server 230 communicate over a network. And fig. 3 shows a flow chart of the work flow of the system for processing tasks, the business server 210 is a server of the business system, the flow server 220 is a server of the workflow system, and the message middleware is deployed in the message server 230. The user 110 is a task handler in the system, and the task handler 110 (user 110) can communicate with the service server 210 through the terminal device 100 to perform a process of handling a task. It should be noted that the service server 210, the flow server 220, and the message server 230 in the system can all be applied to the above-described hardware structure.
As described in the background art, when a business system needs to initiate an approval process, an http request is sent to a workflow system, and the workflow system receives the request and initiates a process according to a transmitted business number, so as to generate a proxy task, which is allocated to designated personnel. When the service system displays the agent task, a request is sent to query the agent task in the workflow system, and then detailed service data is displayed through service number association according to the queried data. However, the workflow system is required to be queried first for each query agent of the business system, so that not only is the response time of the business system prolonged, but also the burden of the workflow system is increased, and particularly, the data volume is large, and the interaction is more frequent when the data is displayed in page paging. In addition, in a proxy list returned by the workflow system, information such as the name and address of the merchant is inquired in the business system according to the number of the merchant, and then the information is displayed in a page. Such a solution is time consuming and cumbersome.
In view of the technical problems in the background art, referring to fig. 2 and 3, the service server 210 is configured to perform the following operations:
first, the service server 210 transmits a creation request for creating a proxy task to the flow server 220. For example: the business system has a new merchant to be hosted, in which case the business server 210 sends a request (http request) for creating a proxy task to the process server 220, that is, the process server 220 is requested to create a merchant hosting examination and approval process for the new merchant, and a pending examination and approval task (proxy task) is generated. The transmitted request also comprises a service number which is used as the identifier of the proxy task.
Further, the business server 210 pulls task information related to the proxy task created by the flow server 220 from the message server 230 deployed with the message middleware, wherein the proxy task is processed by the corresponding task handler. The process server 220 creates an agent task (merchant enrollment approval), and assigns a corresponding task handler to the agent task during the process of creating the agent task, for example: the merchant's admitted tasks are approved by the task handler 110. After the proxy task is created, the flow server 220 pushes task information (a task notification) related to the proxy task to the message server 230 deployed with message middleware, where a message queue can store the task information. In this case, the service server 210 may periodically pull the task information from the message middleware (message queue) of the message server 230.
Finally, the service server 210 transmits task information of the proxy task related to the task handler 110 to the terminal device 100 in response to the query request for querying the proxy task received from the terminal device 100 of the task handler 110. That is, after the task handler 110 logs in the business system (the business server 210) through the terminal device 100, the business server 210 transmits task information of a proxy task related to the task handler to the terminal device of the task handler, for example: the approval task resident with the merchant is sent to the terminal device 100 of the task handler 110.
Further, the flow server 220 is configured to perform the following operations:
the flow server 220 receives a creation request for creating a proxy task transmitted by the service server 210. For example: the business system has a new merchant residence, and the business server 210 needs to create a proxy task related to the merchant residence. In this case, the flow server 220 receives the creation request for creating the proxy task transmitted by the service server 210.
Further, the flow server 220 creates a proxy task and generates task information corresponding to the proxy task in response to the creation request. That is, the process server 220 generates an approval process (merchant enrollment) and generates a message notification of the task, notifying the business system for processing. The process server 220 assigns a corresponding task handler to the agent task in the process of generating the agent task, for example: the merchant's admitted tasks are approved by the task handler 110. Finally, the flow server 220 pushes the task information corresponding to the proxy task to the message server 230 where the message middleware is deployed.
Thus, through the system, the process server 220 can create a proxy task according to the request sent by the business server 210 and push the task message to the message server 230 deployed with the message middleware. The service server 210 can periodically pull the task message from the message middleware deployed by the message server 230 and then send the task related to the task handler 110 to the terminal device 100 according to the query request of the terminal device 100 of the task handler 110. Therefore, the business system does not need to pass through the process server every time the agent task is acquired, and does not need to pass through the process server when the agent task is inquired. Therefore, the technical effects of reducing the workload of the workflow system, saving time and simplifying the flow are achieved. And the technical problems that the workflow system needs to be inquired firstly for each inquiry agency of the service system in the prior art, so that the response time of the service system is prolonged and the burden of the workflow system is increased are solved.
Optionally, after the operation that the service server pulls the task information related to the proxy task created by the flow server from the message server deployed with the message middleware, the method further includes: and storing the task information to a local business database for storing business data.
Specifically, after the service server 210 pulls the task information related to the proxy task created by the flow server 220 from the message server 230 deployed with the message middleware, the service server 210 stores the task information into the service database locally used for storing service data.
Thus, in this manner, the agent task is obtained in the local database without going through the workflow system when the business system processes the agent task. The processing time of the service system is saved, the processing flow is simplified, and the workload of the flow server is lightened.
Optionally, the operation of setting a corresponding task number for the agent task and sending task information of the agent task related to the task handler to the terminal device includes: determining a task number associated with a task handler; according to the task number related to the task processor, inquiring the task information of the corresponding proxy task in a service database; and sending task information of the proxy task to the terminal equipment.
Specifically, the proxy task generated by the flow server 220 has a corresponding task number, and in the operation of the service server 210 sending the task information of the proxy task related to the task handler 110 to the terminal device 100, the task server 210 first determines the task number related to the task handler 110, for example: and the task number of the agency task admitted by the merchant is described. Further, the service server 210 queries corresponding task information from a local service database according to the task number, for example: merchant name, address, contact. Finally, the service server 210 transmits the queried task information to the terminal device 100 of the task handler 110.
Thus, by this means, the proxy task can be associated with specific data in the business database without interaction with the workflow system. In addition, the tasks and the corresponding information are inquired in the local database, so that the resource occupation is saved, the inquiry efficiency is improved, and the inquiry is convenient.
In the above operating environment, according to the second aspect of the present embodiment, a method for processing tasks is provided, and the method is implemented by the service server 210 shown in fig. 2. Fig. 4 shows a flow diagram of the method, which, with reference to fig. 4, comprises:
s402: sending a creating request for creating the agent task to a process server, wherein the process server is used for processing a process related to the agent task;
s404: pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler, and the message middleware is used for storing the task information; and
s406: in response to a query request for querying a proxy task received from a terminal device of a task handler, task information of the proxy task related to the task handler is transmitted to the terminal device.
Specifically, as shown with reference to fig. 2 and 3, the business server 210 transmits a creation request for creating a proxy task to the flow server 220. For example: the business system has a new merchant to be hosted, in which case the business server 210 sends a request for creating a proxy task to the process server 220, that is, the process server 220 is requested to create a merchant hosting examination and approval process for the new merchant, and a pending examination and approval task (proxy task) is generated. The transmitted request also comprises a service number and an identifier of the proxy task.
Further, the business server 210 pulls task information related to the proxy task created by the flow server 220 from the message server 230 deployed with the message middleware, wherein the proxy task is processed by the corresponding task handler. The process server 220 creates an agent task (merchant enrollment approval), and assigns a corresponding task handler to the agent task during the process of creating the agent task, for example: the merchant's admitted tasks are approved by the task handler 110. After the proxy task is created, the flow server 220 pushes task information (a task notification) related to the proxy task to the message server 230 deployed with message middleware, where a message queue can store the task information. In this case, the service server 210 may periodically pull the task information from the message middleware (message queue) of the message server 230.
Finally, the service server 210 transmits task information of the proxy task related to the task handler 110 to the terminal device 100 in response to the query request for querying the proxy task received from the terminal device 100 of the task handler 110. That is, after the task handler 110 logs in the business system (the business server 210) through the terminal device 100, the business server 210 transmits task information of a proxy task related to the task handler to the terminal device of the task handler, for example: the approval task resident with the merchant is sent to the terminal device 100 of the task handler 110.
Therefore, by the mode, the business system does not need to pass through the process server when acquiring the proxy task every time, and does not need to pass through the process server when inquiring the proxy task. Therefore, the technical effects of reducing the workload of the workflow system, saving time and simplifying the flow are achieved. And the technical problems that the workflow system needs to be inquired firstly for each inquiry agency of the service system in the prior art, so that the response time of the service system is prolonged and the burden of the workflow system is increased are solved.
Optionally, after the operation of pulling task information related to the proxy task created by the flow server from the message server deployed with the message middleware, the method further includes: and storing the task information to a local business database for storing business data.
Specifically, after the service server 210 pulls the task information related to the proxy task created by the flow server 220 from the message server 230 deployed with the message middleware, the service server 210 stores the task information into the service database locally used for storing service data.
Thus, in this manner, the agent task is obtained in the local database without going through the workflow system when the business system processes the agent task. The processing time of the service system is saved, the processing flow is simplified, and the workload of the flow server is lightened.
Optionally, the operation of setting a corresponding task number for the agent task and sending task information of the agent task related to the task handler to the terminal device includes: determining a task number associated with a task handler; according to the task number related to the task processor, inquiring the task information of the corresponding proxy task in a service database; and sending task information of the proxy task to the terminal equipment.
Specifically, the proxy task generated by the flow server 220 has a corresponding task number, and in the operation of the service server 210 sending the task information of the proxy task related to the task handler 110 to the terminal device 100, the task server 210 first determines the task number related to the task handler 110, for example: and the task number of the agency task admitted by the merchant is described. Further, the service server 210 queries corresponding task information from a local service database according to the task number, for example: merchant name, address, contact. Finally, the service server 210 transmits the queried task information to the terminal device 100 of the task handler 110.
Thus, by this means, the proxy task can be associated with specific data in the business database without interaction with the workflow system. In addition, the tasks and the corresponding information are inquired in the local database, so that the resource occupation is saved, the inquiry efficiency is improved, and the inquiry is convenient.
Further, according to a third aspect of the present embodiment, there is provided a method of processing a task, which is implemented by the flow server 220 shown in fig. 2. Fig. 5 shows a flow diagram of the method, which, with reference to fig. 5, comprises:
s502: receiving a creating request for creating a proxy task sent by a service server, wherein the service server is used for processing service data;
s504: in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and
s506: and pushing the task information to a message server deployed with message middleware, wherein the message middleware is used for storing the task information.
Specifically, the flow server 220 receives a creation request for creating a proxy task sent by the business server 210. For example: the service system has a new merchant residence, and the service server 210 needs to create a proxy task related to the merchant residence. In this case, the flow server 220 receives the creation request for creating the proxy task transmitted by the service server 210.
Further, the flow server 220 creates a proxy task and generates task information corresponding to the proxy task in response to the creation request. That is, the process server 220 generates an approval process (merchant enrollment) and generates a message notification of the task, notifying the business system for processing. The process server 220 assigns a corresponding task handler to the agent task in the process of generating the agent task, for example: the merchant's admitted tasks are approved by the task handler 110. Finally, the flow server 220 pushes the task information corresponding to the proxy task to the message server 230 where the message middleware is deployed.
Further, referring to fig. 1, according to a fourth aspect of the present embodiment, there is provided a storage medium. The storage medium comprises a stored program, wherein the method of any of the above is performed by a processor when the program is run.
Thus, according to the present embodiment, the workflow server 220 may create a proxy task according to the request sent by the business server 210 and push the task message to the message server 230 deployed with the message middleware. The service server 210 can periodically pull the task message from the message middleware deployed by the message server 230 and then send the task related to the task handler 110 to the terminal device 100 according to the query request of the terminal device of the task handler 110. Therefore, the business system does not need to pass through the process server every time the agent task is acquired, and does not need to pass through the process server when the agent task is inquired. Therefore, the technical effects of reducing the workload of the workflow system, saving time and simplifying the flow are achieved. And the technical problems that the workflow system needs to be inquired firstly for each inquiry agency of the service system in the prior art, so that the response time of the service system is prolonged and the burden of the workflow system is increased are solved.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present invention is not limited by the order of acts, as some steps may occur in other orders or concurrently in accordance with the invention. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required by the invention.
Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present invention.
Example 2
Fig. 6 shows an apparatus 600 for processing tasks according to the first aspect of the present embodiment, which apparatus 600 corresponds to the method according to the second aspect of embodiment 1. Referring to fig. 6, the apparatus 600 includes: a sending module 610, configured to send a creation request for creating a proxy task to a process server, where the process server is configured to process a process related to the proxy task; an obtaining module 620, configured to pull task information related to a proxy task created by a process server from a message server deployed with message middleware, where the proxy task is processed by a corresponding task handler, and the message middleware is used to store the task information; and a query module 630 for transmitting task information of the proxy task related to the task handler to the terminal device in response to a query request for querying the proxy task received from the terminal device of the task handler.
Optionally, the method further comprises: and the storage module is used for storing the task information to a local service database for storing service data.
Optionally, the agent task is provided with a corresponding task number, and the query module 630 includes: a determination submodule for determining a task number associated with a task handler; the query submodule is used for querying the task information of the corresponding proxy task in the service database according to the task number related to the task processor; and the sending submodule is used for sending the task information of the proxy task to the terminal equipment.
Furthermore, fig. 7 shows an apparatus 700 for processing tasks according to the second aspect of the present embodiment, which apparatus 700 corresponds to the method according to the third aspect of embodiment 1. Referring to fig. 7, the apparatus 700 includes: a receiving module 710, configured to receive a creation request for creating a proxy task sent by a service server, where the service server is configured to process service data; a creating module 720, configured to create a proxy task in response to the creation request and generate task information corresponding to the proxy task, where the proxy task is processed by a corresponding task handler; and a pushing module 730, configured to push the task information to a message server deployed with message middleware, where the message middleware is configured to store the task information.
Thus, according to the present embodiment, with the apparatus for processing task 600 and the apparatus for processing task 700, the business system does not need to pass through the workflow system each time the agent task is acquired, and does not need to pass through the workflow system when querying the agent task. Therefore, the technical effects of reducing the workload of the workflow system, saving time and simplifying the flow are achieved. And the technical problems that the workflow system needs to be inquired firstly for each inquiry agency of the service system in the prior art, so that the response time of the service system is prolonged and the burden of the workflow system is increased are solved.
Example 3
Fig. 8 shows an apparatus 800 for processing tasks according to the first aspect of the embodiment, which apparatus 800 corresponds to the method according to the second aspect of the embodiment 1. Referring to fig. 8, the apparatus 800 includes: a first processor 810; and a first memory 820 coupled to the first processor 810 for providing instructions to the first processor 810 to process the following process steps: sending a creating request for creating the agent task to a process server, wherein the process server is used for processing a process related to the agent task; pulling task information related to a proxy task created by a process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler, and the message middleware is used for storing the task information; and transmitting task information of the proxy task related to the task handler to the terminal device in response to a query request for querying the proxy task received from the terminal device of the task handler.
Optionally, after the operation of pulling task information related to the proxy task created by the flow server from the message server deployed with the message middleware, the first memory 820 is further used for providing the first processor 810 with instructions for processing the following processing steps: and storing the task information to a local business database for storing business data.
Optionally, the operation of setting a corresponding task number for the agent task and sending task information of the agent task related to the task handler to the terminal device includes: determining a task number associated with a task handler; according to the task number related to the task processor, inquiring the task information of the corresponding proxy task in a service database; and sending task information of the proxy task to the terminal equipment.
Furthermore, fig. 9 shows an apparatus 900 for processing tasks according to the second aspect of the present embodiment, which apparatus 900 corresponds to the method according to the third aspect of embodiment 1. Referring to fig. 9, the apparatus 900 includes: a second processor 910; and a second memory 920, coupled to the second processor 910, for providing instructions to the second processor 910 to process the following steps: receiving a creating request for creating a proxy task sent by a service server, wherein the service server is used for processing service data; in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and pushing the task information to a message server deployed with message middleware, wherein the message middleware is used for storing the task information.
Thus, according to the present embodiment, with the device for processing a task 800 and the device for processing a task 900, the business system does not need to pass through the workflow system each time the proxy task is acquired, and does not need to pass through the workflow system when querying the proxy task. Therefore, the technical effects of reducing the workload of the workflow system, saving time and simplifying the flow are achieved. And the technical problems that the workflow system needs to be inquired firstly for each inquiry agency of the service system in the prior art, so that the response time of the service system is prolonged and the burden of the workflow system is increased are solved.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
In the above embodiments of the present invention, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed technology can be implemented in other ways. The above-described embodiments of the apparatus are merely illustrative, and for example, the division of the units is only one type of division of logical functions, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, units or modules, and may be in an electrical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present invention may be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.

Claims (10)

1. A system for processing tasks comprises a business server, a process server and a message server deployed with message middleware, wherein the business server is used for processing business data, the process server is used for processing processes related to a proxy task, the message server deployed with message middleware is used for storing task information corresponding to the proxy task, and the system is characterized in that,
the service server is configured to perform the following operations:
sending a creating request for creating a proxy task to the process server;
pulling task information related to a proxy task created by the process server from the message server deployed with the message middleware, wherein the proxy task is processed by a corresponding task handler;
in response to a query request for querying a proxy task received from a terminal device of the task handler, sending task information of the proxy task related to the task handler to the terminal device;
the process server is configured to perform the following operations:
receiving a creating request for creating a proxy task sent by the service server;
in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and
and pushing the task information corresponding to the proxy task to the message server with the message middleware.
2. The system of claim 1, wherein after the operation of the business server pulling task information related to the proxy task created by the process server from the message server deployed with message middleware, the business server further comprises: and storing the task information to a local service database for storing service data.
3. The system of claim 2, wherein the agent task is provided with a corresponding task number, and wherein the operation of sending task information of the agent task related to the task handler to the terminal device comprises:
determining a task number associated with the task handler;
according to the task number related to the task processor, searching task information of the corresponding proxy task in the service database; and
and sending the task information of the proxy task to the terminal equipment.
4. A method of processing a task, comprising:
sending a creation request for creating a proxy task to a process server, wherein the process server is used for processing a process related to the proxy task;
pulling task information related to a proxy task created by the process server from a message server deployed with message middleware, wherein the proxy task is processed by a corresponding task handler, and the message middleware is used for storing the task information; and
and sending task information of the proxy task related to the task processor to the terminal equipment in response to a query request for querying the proxy task, which is received from the terminal equipment of the task processor.
5. The method of claim 4, wherein after the operation of pulling task information related to the proxy task created by the flow server from the message server deployed with message middleware, further comprising: and storing the task information to a local service database for storing service data.
6. The method of claim 5, wherein the agent task is provided with a corresponding task number, and wherein the operation of sending task information of the agent task related to the task handler to the terminal device comprises:
determining a task number associated with the task handler;
according to the task number related to the task processor, searching task information of the corresponding proxy task in the service database; and
and sending the task information of the proxy task to the terminal equipment.
7. A method of processing a task, comprising:
receiving a creating request for creating a proxy task sent by a service server, wherein the service server is used for processing service data;
in response to the creation request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task handler; and
and pushing the task information to a message server deployed with message middleware, wherein the message middleware is used for storing the task information.
8. A storage medium comprising a stored program, wherein the method of any one of claims 4 to 7 is performed by a processor when the program is run.
9. An apparatus for processing tasks, comprising:
the system comprises a sending module, a flow server and a processing module, wherein the sending module is used for sending a creating request for creating an agent task to the flow server, and the flow server is used for processing a flow related to the agent task;
an acquisition module, configured to pull task information related to a proxy task created by the process server from a message server deployed with message middleware, where the proxy task is processed by a corresponding task handler, and the message middleware is configured to store the task information; and
and the query module is used for responding to a query request for querying the proxy task received from the terminal equipment of the task processor and sending task information of the proxy task related to the task processor to the terminal equipment.
10. An apparatus for processing tasks, comprising:
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a creating request for creating a proxy task sent by a service server, and the service server is used for processing service data;
the creating module is used for responding to the creating request, creating a proxy task and generating task information corresponding to the proxy task, wherein the proxy task is processed by a corresponding task processor; and
and the pushing module is used for pushing the task information to a message server deployed with a message middleware, and the message middleware is used for storing the task information.
CN201910927587.3A 2019-09-27 2019-09-27 System, method, apparatus and storage medium for processing task Pending CN112581069A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910927587.3A CN112581069A (en) 2019-09-27 2019-09-27 System, method, apparatus and storage medium for processing task

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910927587.3A CN112581069A (en) 2019-09-27 2019-09-27 System, method, apparatus and storage medium for processing task

Publications (1)

Publication Number Publication Date
CN112581069A true CN112581069A (en) 2021-03-30

Family

ID=75110150

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910927587.3A Pending CN112581069A (en) 2019-09-27 2019-09-27 System, method, apparatus and storage medium for processing task

Country Status (1)

Country Link
CN (1) CN112581069A (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113469801A (en) * 2021-06-30 2021-10-01 建信金融科技有限责任公司 Method and device for determining audit result

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103854168A (en) * 2014-02-17 2014-06-11 湖南中烟工业有限责任公司 Heterogeneous process to-do task centralized processing method and device
CN104270274A (en) * 2014-10-08 2015-01-07 广东电网公司汕头供电局 Fault processing method, device and system based on form
CN107545338A (en) * 2016-06-27 2018-01-05 百度在线网络技术(北京)有限公司 Business data processing method and business data processing system
CN109165106A (en) * 2018-08-24 2019-01-08 深圳乐信软件技术有限公司 Method for processing business, device, equipment, storage medium and process flow operation system
CN109819021A (en) * 2019-01-09 2019-05-28 网宿科技股份有限公司 The method of business backstage and its asynchronous process service request
CN110060190A (en) * 2019-04-18 2019-07-26 山东浪潮云信息技术有限公司 A kind of method and system that the auxiliary applied to administrative examination and approval field is handled affairs on the net

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103854168A (en) * 2014-02-17 2014-06-11 湖南中烟工业有限责任公司 Heterogeneous process to-do task centralized processing method and device
CN104270274A (en) * 2014-10-08 2015-01-07 广东电网公司汕头供电局 Fault processing method, device and system based on form
CN107545338A (en) * 2016-06-27 2018-01-05 百度在线网络技术(北京)有限公司 Business data processing method and business data processing system
CN109165106A (en) * 2018-08-24 2019-01-08 深圳乐信软件技术有限公司 Method for processing business, device, equipment, storage medium and process flow operation system
CN109819021A (en) * 2019-01-09 2019-05-28 网宿科技股份有限公司 The method of business backstage and its asynchronous process service request
CN110060190A (en) * 2019-04-18 2019-07-26 山东浪潮云信息技术有限公司 A kind of method and system that the auxiliary applied to administrative examination and approval field is handled affairs on the net

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113469801A (en) * 2021-06-30 2021-10-01 建信金融科技有限责任公司 Method and device for determining audit result

Similar Documents

Publication Publication Date Title
CN114051055B (en) Data transmission method and device in different systems
CN110688146A (en) Method, device and storage medium for dynamically configuring monitoring system
CN103957150A (en) Notification message synchronization method of electronic device, server and electronic equipment
EP3702915B1 (en) Data processing method and device, storage medium, processor, and system
CN110912814A (en) Interface data distribution method and device
CN113296871A (en) Method, equipment and system for processing container group instance
CN109828830B (en) Method and apparatus for managing containers
CN112817562A (en) Service processing method and device
CN104601448A (en) Method and device for handling virtual card
CN114398397A (en) Data processing method, device, storage medium and system
CN112581069A (en) System, method, apparatus and storage medium for processing task
CN108076110B (en) Electronic data exchange system and apparatus comprising an electronic data exchange system
CN110704207B (en) Data processing method and device of business application middleware and storage medium
CN111522617A (en) Method and device for maintaining system and electronic equipment
CN112948138A (en) Method and device for processing message
CN112486583A (en) System, method, apparatus and storage medium for configuring parameters
CN114417318A (en) Third-party page jumping method and device and electronic equipment
CN113535020A (en) Method, apparatus, device, medium and product for generating application icons
CN112836201A (en) Method, device, equipment and computer readable medium for multi-platform information intercommunication
CN112835962A (en) Information display method and device, electronic equipment and storage medium
CN108874553B (en) Message pushing method, device and system, storage medium and processor
CN108696472B (en) Request processing method and device
CN110609781A (en) Interface test method, device and storage medium
CN112559001A (en) Method and device for updating application
CN112785358A (en) Order fulfillment merchant access method and device

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

Application publication date: 20210330

RJ01 Rejection of invention patent application after publication