Business task processing method and device based on multi-business system, and electronic equipment

Abstract

The invention discloses a business task processing method and device based on a multi-business system and electronic equipment, and the business task processing method comprises the steps: logging in a system account of each business system on a preset system, collecting task data associated with an account identifier from a preset task scheduler under the condition that the login succeeds, and sending the task data to a server; and generating a task queue, processing each piece of task data in the task queue to obtain task to-be-processed information, transmitting the task to-be-processed information to a preset display interface, and displaying the task to-be-processed information in a preset window of the preset display interface. The technical problem that the work efficiency is low due to the fact that the task arrival of each business system cannot be obtained in time in the related technology and the task cannot be processed in time is solved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a business task processing method based on a multi-business system and a device and electronic equipment thereof. Background Art

[0002] In the related technologies, the widely used unified authentication login system (for example, LDAP (Lightweight Directory Access Protocol)) has realized that multiple office systems (for example, TMS (Transportation Management System), OA (Office Automation System), PMS (Purchasing Management System), ITSM (IT (Internet Technology) Service Management), etc.) can log in with a unified set of accounts and passwords, thereby reducing the work efficiency loss caused by login failures due to forgotten accounts and passwords. In addition, the currently widely promoted unified login system (for example, SSO (Single Sign On)) can integrate the login pages of various office systems and support jumping to various office systems through the unified login system.

[0003] However, the above two solutions only realize the unified login of each office system, and cannot obtain the arrival of tasks of each office system and process the tasks in time, resulting in a long workflow and low work efficiency.

[0004] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0005] The embodiment of the present invention provides a business task processing method based on a multi-business system, a device and an electronic device thereof, so as to at least solve the technical problem in the related art that the arrival of tasks of each business system cannot be obtained in time, resulting in the inability to process tasks in time and causing low work efficiency.

[0006] According to one aspect of an embodiment of the present invention, a business task processing method based on a multi-business system is provided, comprising: logging in to a system account of each business system on a preset system, wherein the system account is associated with an account identifier; in case of successful login, collecting task data associated with the account identifier from a preset task scheduler to generate a task queue, wherein the task data is associated with the account identifier and a business system identifier; processing each of the task data in the task queue to obtain task pending information, wherein the task pending information is used to remind a target terminal logged in to the system account to process the task pending information; transmitting the task pending information to a preset display interface, and displaying the task pending information in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

[0007] Optionally, before logging into the system account of each business system on the preset system, it also includes: obtaining configuration information of the business system, wherein the configuration information includes: interface information, login information; based on the interface information, connecting the business system to the preset system; if the connection is successful, based on the login information, generating a system account number and a system password of the system account of the business system in the preset system, wherein the system account number and the system password are used to log in to the system account of the business system on the preset system.

[0008] Optionally, after logging into the system accounts of each business system on the preset system, it also includes: if the target system account of the target business system is not successfully logged in on the preset system, pausing the scheduling task program of the target business system, wherein the scheduling task program is used to add the business tasks of the target business system to the preset task scheduler, and the business tasks correspond to the task data; updating the system account and system password of the target system account in the preset system, and restarting the scheduling task program of the target business system when the update is completed.

[0009] Optionally, before collecting the task data associated with the account identifier from the preset task scheduler, it also includes: configuring the task refresh frequency of the business system, wherein the task refresh frequency is used to indicate the interval duration for collecting business tasks of the business system; configuring the task execution time of the business system, wherein the task execution time is used to indicate the time range for collecting the business tasks of the business system; and constructing a scheduling task program for the business system based on the task refresh frequency and the task execution time.

[0010] Optionally, the step of processing each task data in the task queue to obtain task to be processed information includes: determining a display strategy based on the business system identifier of the task data; and processing the task data according to the display strategy to obtain the task to be processed information.

[0011] Optionally, before passing the task to be processed information to the preset display interface, it also includes: constructing the preset display interface; dividing the interface of the preset display interface according to the number of systems of the business system connected to the preset system, and obtaining N preset windows, wherein N is a positive integer, N is equal to the number of systems, and the preset window is associated with the business system identifier.

[0012] Optionally, the business task processing method also includes: constructing a floating window, wherein the floating window is used to display the number of pending tasks of each of the business systems, the floating window including: M sub-windows, M is a positive integer, M is equal to the number of systems, and the sub-window is associated with the business system identifier; when the task pending information is received on the preset display interface, the number of pending tasks displayed in the sub-window indicated by the business system identifier associated with the task pending information is accumulated; when the number of pending tasks displayed in the sub-window is greater than a preset number threshold, the display color of the sub-window is updated to a preset color.

[0013] According to another aspect of an embodiment of the present invention, a business task processing device based on a multi-business system is also provided, including: a login unit, used to log in to the system account of each business system on a preset system, wherein the system account is associated with an account identifier; a collection unit, used to collect the task data associated with the account identifier from a preset task scheduler when the login is successful, and generate a task queue, wherein the task data is associated with the account identifier and the business system identifier; a processing unit, used to process each of the task data in the task queue to obtain task to be processed information, wherein the task to be processed information is used to remind the target terminal logged in to the system account to process the task to be processed information; a display unit, used to transmit the task to be processed information to a preset display interface, and display the task to be processed information in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

[0014] Optionally, the business task processing device also includes: a first acquisition module, used to acquire configuration information of the business system before logging into the system account of each business system on the preset system, wherein the configuration information includes: interface information, login information; a first access module, used to connect the business system to the preset system based on the interface information; a first generation module, used to generate a system account number and a system password of the system account of the business system in the preset system based on the login information when the access is successful, wherein the system account number and the system password are used to log in to the system account of the business system on the preset system.

[0015] Optionally, the business task processing device also includes: a first suspension module, used to suspend the scheduling task program of the target business system after logging into the system account of each business system on the preset system, if the target system account of the target business system is not successfully logged into the preset system, wherein the scheduling task program is used to add the business task of the target business system to the preset task scheduler, and the business task corresponds to the task data; a first update module, used to update the system account and system password of the target system account in the preset system, and restart the scheduling task program of the target business system when the update is completed.

[0016] Optionally, the business task processing device also includes: a first configuration module, used to configure the task refresh frequency of the business system before collecting the task data associated with the account identifier from a preset task scheduler, wherein the task refresh frequency is used to indicate the interval duration for collecting the business tasks of the business system; a second configuration module, used to configure the task execution time of the business system, wherein the task execution time is used to indicate the time range for collecting the business tasks of the business system; a first construction module, used to construct a scheduling task program for the business system based on the task refresh frequency and the task execution time.

[0017] Optionally, the processing unit includes: a first determination module, used to determine a display strategy based on the business system identifier of the task data; and a first processing module, used to process the task data according to the display strategy to obtain the task to-be-processed information.

[0018] Optionally, the business task processing device also includes: a second construction module, used to construct the preset display interface before passing the task to be processed information to the preset display interface; a first segmentation module, used to segment the interface of the preset display interface according to the number of systems of the business system connected to the preset system, to obtain N preset windows, wherein N is a positive integer, N is equal to the number of systems, and the preset window is associated with the business system identifier.

[0019] Optionally, the business task processing device also includes: a third construction module, used to construct a floating window, wherein the floating window is used to display the number of pending tasks of each business system, and the floating window includes: M sub-windows, M is a positive integer, M is equal to the number of systems, and the sub-window is associated with the business system identifier; a first accumulation module, used to accumulate the number of pending tasks displayed in the sub-window indicated by the business system identifier associated with the task pending information when the preset display interface receives the task pending information; a second update module, used to update the display color of the sub-window to a preset color when the number of pending tasks displayed in the sub-window is greater than a preset number threshold.

[0020] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is also provided, wherein the computer-readable storage medium includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute any one of the above-mentioned business task processing methods based on a multi-business system.

[0021] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement any one of the above-mentioned business task processing methods based on a multi-business system.

[0022] In the present disclosure, after successfully logging in to the system account of each business system on the preset system, the task data associated with the account identifier is collected from the preset task scheduler, a task queue is generated, each task data in the task queue is processed, task pending information is obtained, the task pending information is passed to the preset display interface, and the task pending information is displayed in a preset window of the preset display interface. In the present disclosure, after successfully logging in to the system account of each business system on the preset system, the task data associated with the system account can be collected from the preset task scheduler to generate a task queue, and then each task data in the task queue is processed to obtain task pending information, and then the task pending information is passed to the preset display interface to display the task pending information in the corresponding preset window on the preset display interface, so that the corresponding terminal can timely discover the arrival of the task and process the task in time, which can effectively shorten the workflow and improve work efficiency, thereby solving the technical problem that the arrival of tasks of each business system cannot be obtained in time in the related technology, resulting in the inability to process tasks in time, resulting in low work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings described herein are used to provide a further understanding of the present invention and constitute a part of this application. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the drawings:

[0024] Figure 1 is a flowchart of an optional business task processing method based on a multi-business system according to an embodiment of the present invention;

[0025] Figure 2 is a schematic diagram of an optional preset display interface structure according to an embodiment of the present invention;

[0026] Figure 3 is a schematic diagram of an optional floating window structure according to an embodiment of the present invention;

[0027] Figure 4 is a schematic diagram of an optional scheduling task flow according to an embodiment of the present invention;

[0028] Figure 5 is a schematic diagram of an optional task scheduler process according to an embodiment of the present invention;

[0029] Figure 6 is a schematic diagram of an optional service task processing device based on a multi-service system according to an embodiment of the present invention;

[0030] Figure 7 The present invention is a hardware structure block diagram of an electronic device (or mobile device) for a service task processing method based on a multi-service system according to an embodiment of the present invention. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0032] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0033] It should be noted that the relevant information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0034] In the present invention, in the process of project management, it is necessary to frequently use office systems such as TMS, OA, PMS, ITSM (i.e., business systems) to initiate processes and track the progress of approval flow processing. If there are interferences from other work, the work efficiency of a thing will be reduced. The reason why a process has a waiting time is more because the arrival of the work task is not discovered in time. Although many workflow systems have reminder functions, such as ITSM, which will send an email reminder when a work arrives, and an OA task will send a task message when it arrives, in order to shorten the workflow waiting time. However, office staff rarely log in to systems such as mailboxes frequently to check. Even if they frequently log in to various office systems for active checking, they still cannot avoid omissions of a few minutes or even hours.

[0035] In order to avoid frequent login to the office system to check, and to be able to intuitively discover the arrival of work tasks, so as to further shorten the workflow and improve work efficiency, the present invention proposes a "unified export plus automatic push" solution, which can realize the unified view management of pending tasks, and can timely obtain the arrival of tasks and process them, effectively shortening the workflow and eliminating the problem of reduced work efficiency caused by waiting time. In this way, office personnel do not need to frequently log in to office systems such as OA, PMS, and ITSM. Through the method of scheduled tasks, they can automatically discover the system and its related work tasks, and discover work tasks faster in a more intuitive way, reducing the task waiting time, and can do so at each execution node of the workflow, greatly improving the flow efficiency of the workflow.

[0036] After system development and basic environment construction, the present invention has carried out scenario and data simulation, so that after logging into the unified authentication portal (i.e., the preset system), users can realize login-free access to various docking systems (i.e., various office business systems connected to the preset system), normally receive task to-do items and process flow status of business systems such as PMS, OA, ITSM, MAIL (i.e., a mailbox system), and process them in a timely manner.

[0037] The present invention is described in detail below in conjunction with various embodiments.

[0038] Embodiment 1

[0039] According to an embodiment of the present invention, an embodiment of a business task processing method based on a multi-business system is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0040] Figure 1 is a flowchart of an optional business task processing method based on a multi-business system according to an embodiment of the present invention. Figure 1 As shown, the method comprises the following steps:

[0041] Step S101, logging into the system account of each business system on the preset system, wherein the system account is associated with an account identifier.

[0042] Step S102, when the login is successful, task data associated with the account identifier is collected from a preset task scheduler to generate a task queue, wherein the task data is associated with the account identifier and the business system identifier.

[0043] Step S103, processing each task data in the task queue to obtain task to be processed information, wherein the task to be processed information is used to remind the target terminal that logs into the system account to process the task to be processed information.

[0044] Step S104, transferring the pending task information to a preset display interface, and displaying the pending task information in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

[0045] Through the above steps, the system account of each business system can be logged in on the preset system. When the login is successful, the task data associated with the account identifier is collected from the preset task scheduler to generate a task queue, and the task data in the task queue is processed to obtain task pending information, and the task pending information is passed to the preset display interface, and the task pending information is displayed in the preset window of the preset display interface. In an embodiment of the present invention, after successfully logging in to the system account of each business system on the preset system, the task data associated with the system account can be collected from the preset task scheduler to generate a task queue, and then the task data in the task queue is processed to obtain task pending information, and then the task pending information is passed to the preset display interface to display the task pending information in the corresponding preset window on the preset display interface, so that the corresponding terminal can timely discover the arrival of the task and process the task in time, which can effectively shorten the workflow and improve work efficiency, thereby solving the technical problem that the arrival of tasks of each business system cannot be obtained in time in the related technology, resulting in the inability to process tasks in time, resulting in low work efficiency.

[0046] The embodiment of the present invention is described in detail below in combination with the above steps.

[0047] An optional embodiment, before logging into the system account of each business system on the preset system, also includes: obtaining configuration information of the business system, wherein the configuration information includes: interface information, login information; based on the interface information, connecting the business system to the preset system; if the connection is successful, generating a system account number and a system password of the system account of the business system in the preset system based on the login information, wherein the system account number and the system password are used to log in to the system account of the business system on the preset system.

[0048] In an embodiment of the present invention, configuration information (including: interface information, login information, etc.) of each business system that needs to be connected to a preset system (i.e., a login system that can perform unified authentication and login) can be obtained, so that the corresponding business system can be connected to the preset system according to the interface information, and after the business system is successfully connected to the preset system, the system account and system password of the corresponding system account of the business system are generated in the preset system according to the login information of the business system (including: account number and password, etc.), so that the corresponding system account of the business system can be logged in on the preset system through the system account and the system password.

[0049] In an embodiment of the present invention, in order to reduce the pressure on the preset system, the login operation of the preset system is only performed once when the task is started, and then maintained through the session to complete the subsequent information cycle collection and display. Between the scheduled tasks and the interface display, an event-driven design concept is adopted to enhance the real-time nature of the messages.

[0050] In the embodiment of the present invention, in order to ensure the security of the user's password in each business system, all business system login passwords are stored locally and will not be sent to other systems for storage in any way.

[0051] Step S101, logging into the system account of each business system on the preset system, wherein the system account is associated with an account identifier.

[0052] In the embodiment of the present invention, it is first necessary to log in to the system account of each business system on the preset system, and each system account is associated with an account identifier (for identifying the logged-in account).

[0053] Optionally, after logging into the system accounts of each business system on the preset system, it also includes: if the target system account of the target business system is not successfully logged into on the preset system, pausing the scheduling task program of the target business system, wherein the scheduling task program is used to add the business tasks of the target business system to the preset task scheduler, and the business tasks correspond to task data; updating the system account and system password of the target system account in the preset system, and restarting the scheduling task program of the target business system when the update is completed.

[0054] In an embodiment of the present invention, if the target system account of the target business system is not successfully logged in on the preset system, it is necessary to suspend the scheduling task program of the target business system (the scheduling task program is used to add the business tasks of the target business system to the preset task scheduler, and the business tasks correspond to task data). In this way, the risk of password lock caused by frequent automatic operations due to incorrect passwords and expired passwords can be prevented. The preset system will automatically remove the scheduling tasks from the scheduler under any abnormal circumstances, and manual restart is required for monitoring again. After that, the system account and system password of the target system account in the preset system can be updated. After the update is completed, re-login to the target system account, and then restart the scheduling task program of the target business system to automatically add the business tasks of the target business system to the preset task scheduler for task monitoring.

[0055] Optionally, before collecting task data associated with the account identifier from a preset task scheduler, it also includes: configuring the task refresh frequency of the business system, wherein the task refresh frequency is used to indicate the interval duration for collecting business tasks of the business system; configuring the task execution time of the business system, wherein the task execution time is used to indicate the time range for collecting business tasks of the business system; and constructing a scheduling task program for the business system based on the task refresh frequency and the task execution time.

[0056] In an embodiment of the present invention, the task refresh frequency and task execution time of the business system can be configured first. The task refresh frequency is used to indicate the interval duration of the business tasks of the collection business system, and the task execution time is used to indicate the time range of the business tasks of the collection business system. Then, the scheduling task program of the business system can be constructed according to the configured task refresh frequency and task execution time.

[0057] In the embodiment of the present invention, in order to further reduce the pressure of each business system, it is necessary to set the task scheduling refresh frequency (i.e., task refresh frequency) to be greater than or equal to the preset frequency threshold (e.g., 60 seconds), so as to prevent a large number of requests from causing access pressure to the relevant business system. In addition, the automatic task effective execution time (i.e., task execution time) of the scheduling task program can also be set, for example, the task is scheduled from 09:00:00 to 21:00:00 every day, and will not be executed at other times.

[0058] Step S102, when the login is successful, task data associated with the account identifier is collected from a preset task scheduler to generate a task queue, wherein the task data is associated with the account identifier and the business system identifier.

[0059] In an embodiment of the present invention, if the system account of the business system successfully logs in to the preset system, the task data associated with the account identifier of the logged-in system account can be collected from the preset task scheduler (the task data is associated with the account identifier (to identify the system account to which the task data belongs) and the business system identifier (to identify the business system to which the task data belongs)), and a task queue is generated in the order of collection.

[0060] Step S103, processing each task data in the task queue to obtain task to be processed information, wherein the task to be processed information is used to remind the target terminal that logs into the system account to process the task to be processed information.

[0061] Optionally, the step of processing each task data in the task queue to obtain task to be processed information includes: determining a display strategy based on a business system identifier of the task data; and processing the task data according to the display strategy to obtain task to be processed information.

[0062] In an embodiment of the present invention, each task data in the task queue can be processed in sequence according to the first-in-first-out principle of the task queue, and the task data can be processed into task pending information (the task pending information is used to remind the target terminal that logs into the system account to process the task pending information) for subsequent display. Specifically, the display strategy can be determined based on the business system identifier of the task data (for example, if the business system identified by the business system is only an OA system, the display strategy associated with the OA system can be obtained (which can be set in advance), such as displaying unarchived applications and displaying unoperated personnel, etc.), and then the task data can be processed according to the corresponding display strategy to obtain the task pending information (for example, the unarchived application is: ** meeting notice, the unoperated personnel is: Zhang San*, etc.).

[0063] Optionally, before passing the task to be processed information to the preset display interface, it also includes: constructing a preset display interface; dividing the interface of the preset display interface according to the number of business systems connected to the preset system to obtain N preset windows, where N is a positive integer, N is equal to the number of systems, and the preset window is associated with a business system identifier.

[0064] In the embodiment of the present invention, it is necessary to first construct a preset display interface (i.e., main window), which is used to roughly display relevant system task information, but does not have direct business processing capabilities. Then, it is necessary to divide the interface of the preset display interface according to the number of business systems connected to the preset system to obtain N (N is a positive integer and equal to the number of systems) preset windows, which are associated with a business system identifier and are used to display task information related to the business system indicated by the business system identifier.

[0065] In an embodiment of the present invention, the main window is also the entry point for system configuration and adding scheduling tasks (i.e., configuring the interface parameters of the business system to be connected and configuring the relevant parameters of the collection tasks of the business system to be connected, so as to access the business system at any time and monitor the tasks of the newly connected business system at any time), and closing the main window will not directly exit the application, but hide the main window. Double-clicking the taskbar icon of the main window or right-clicking the taskbar icon and selecting "Main Interface" can bring up the main window again.

[0066] In the embodiment of the present invention, if you click the business system icon on the main window, you can call the system default browser and jump to the login interface of the business system. Double-clicking each business system icon in the floating window also has this function.

[0067] Figure 2 is a schematic diagram of an optional preset display interface structure according to an embodiment of the present invention, such as Figure 2As shown, it is divided into four preset windows, including: OA system, mailbox system, PMS system, ITSM system, etc., among which the preset window of the OA system can display the pending task information in the display format of unarchived application, unoperated personnel, etc.; the preset window of the mailbox system can display the pending task information in the display format of inbox, unread mailbox, etc.; the preset window of the PMS system can display the pending task information in the display format of task name, current processor, task time, etc.; the preset window of the ITSM system can display the pending task information in the display format of submitted work order, current processor, current detention time, etc.

[0068] Step S104, transferring the pending task information to a preset display interface, and displaying the pending task information in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

[0069] In an embodiment of the present invention, after the pending task information is passed to the preset display interface, the pending task information can be displayed in a preset window of the preset display interface (which is a display window corresponding to the business system indicated by the business system identifier) ​​to remind relevant personnel that the task has been completed.

[0070] Optionally, the business task processing method also includes: constructing a floating window, wherein the floating window is used to display the number of pending tasks for each business system, the floating window includes: M sub-windows, M is a positive integer, M is equal to the number of systems, and the sub-window is associated with a business system identifier; when task pending information is received on a preset display interface, the number of pending tasks displayed in the sub-window indicated by the business system identifier associated with the task pending information is accumulated; when the number of pending tasks displayed in the sub-window is greater than a preset number threshold, the display color of the sub-window is updated to a preset color.

[0071] In an embodiment of the present invention, a floating window may also be constructed, and the floating window is used to display the number of pending tasks of each business system, and the floating window includes: M (M is a positive integer, which is equal to the number of systems) sub-windows (the sub-window is associated with a business system identifier, and is used to display the number of pending tasks of the business system to which it belongs). If the preset display interface receives task pending information, the number of pending tasks displayed in the sub-window indicated by the business system identifier associated with the task pending information can be accumulated, and after the number of pending tasks displayed in the sub-window is greater than a preset number threshold (such as 1), the display color of the sub-window is updated to a preset color (for example, from the original green to red).

[0072] In the embodiment of the present invention, each column of the floating window represents the number of pending tasks in a business system. When there are pending tasks, it is displayed in red, otherwise it is displayed in green, and supports displaying a preset number of records (such as 99). You can view the business system corresponding to each column by hovering the mouse over the floating window, double-click to jump to the login interface of the business system, right-click to hide the hovering window, and reopen it by operating in the right-click menu of the task bar.

[0073] Figure 3 is a schematic diagram of an optional floating window structure according to an embodiment of the present invention, such as Figure 3 As shown, the floating window can be divided into four sub-windows, including: OA system, MAIL system, PMS system, ITSM system, etc. The number of pending tasks of the corresponding business system is displayed in each sub-window. For example, the number of pending tasks of the OA system is 0, the number of pending tasks of the MAIL system is 1, the number of pending tasks of the PMS system is 4, the number of pending tasks of the ITSM system is 0, etc.

[0074] In an embodiment of the present invention, if the number of pending tasks displayed in the sub-window exceeds a preset processing threshold (which can be set according to actual conditions, for example, 10), the relevant terminal can be notified for processing. The relevant terminal is the terminal of the system account of the business system indicated by the business system identifier associated with the sub-window.

[0075] In an embodiment of the present invention, a unified export plus automatic push method is used to make the workflow more intuitive and quickly reach the target terminal. By implementing a scheduling task for each business system and adding it to the task scheduler Scheduler (i.e., the preset task scheduler), the preset system information collection is triggered regularly, and the collected information is passed to the comprehensive display interface (i.e., the preset display interface) through messages to achieve a unified display of work tasks. Among them, task scheduling is implemented through the corresponding scheduling task program of each business system, and the scheduling task program can perform data analysis and data collection on the business system. And the preset information (i.e., the interface information, login information, etc. of the business system) plus the method of dynamically adding tasks is adopted to realize separable data display (i.e., divided into multiple preset windows for task display of each business system). In this way, there is no need to frequently log in to each business system, and the task messages issued by the business system can be timely obtained.

[0076] Figure 4 is a schematic diagram of an optional scheduling task flow according to an embodiment of the present invention, such as Figure 4 As shown, the login system can collect information from the task scheduler, then send notifications for the collected information, and finally display the information.

[0077] Figure 5is a schematic diagram of an optional task scheduler process according to an embodiment of the present invention, such as Figure 5 As shown, OA, MAIL, PMS, ITSM and other office systems can add their own task data A to the task scheduler, and then log in to the system to collect data and generate a task queue P for information display.

[0078] In the embodiments of the present invention, the tasks and process processing of the office system can be managed in a unified manner, which not only reduces the waste of operating costs caused by frequent logging into multiple systems, but also can quickly process the incoming tasks and processes, reduce waiting time, and improve office efficiency. The following beneficial effects can be achieved: (1) There is no need to frequently log into multiple office systems. Only logging into the login system can realize an overview of the task progress of the related business systems. The operation is simple and the visual unified management of pending tasks can be realized; (2) The processing efficiency of the process is improved, the waiting time of the process is reduced, and the total floating time for subsequent work is increased.

[0079] The following is a detailed description in conjunction with another embodiment.

[0080] Embodiment 2

[0081] A service task processing device based on a multi-service system provided in this embodiment includes multiple implementation units, each of which corresponds to each implementation step in the above-mentioned embodiment 1.

[0082] Figure 6 is a schematic diagram of an optional service task processing device based on a multi-service system according to an embodiment of the present invention, such as Figure 6 As shown, the business task processing device may include: a login unit 60, a collection unit 61, a processing unit 62, and a display unit 63, wherein:

[0083] A login unit 60, used to log in to a system account of each business system on a preset system, wherein the system account is associated with an account identifier;

[0084] The collection unit 61 is used to collect task data associated with the account identifier from the preset task scheduler to generate a task queue when the login is successful, wherein the task data is associated with the account identifier and the business system identifier;

[0085] The processing unit 62 is used to process each task data in the task queue to obtain task pending information, wherein the task pending information is used to remind the target terminal of the login system account to process the task pending information;

[0086] The display unit 63 is used to transfer the pending task information to a preset display interface and display the pending task information in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

[0087] The above-mentioned business task processing device can log in the system account of each business system on the preset system through the login unit 60, and collect the task data associated with the account identifier from the preset task scheduler through the collection unit 61 when the login is successful, generate a task queue, process each task data in the task queue through the processing unit 62 to obtain task to be processed information, pass the task to be processed information to the preset display interface through the display unit 63, and display the task to be processed information in the preset window of the preset display interface. In the embodiment of the present invention, after successfully logging in the system account of each business system on the preset system, the task data associated with the system account can be collected from the preset task scheduler to generate a task queue, and then the task data in the task queue can be processed to obtain task to be processed information, and then the task to be processed information can be passed to the preset display interface to display the task to be processed information in the corresponding preset window on the preset display interface, so that the corresponding terminal can timely discover the arrival of the task and process the task in time, which can effectively shorten the workflow and improve work efficiency, thereby solving the technical problem that the arrival of tasks of each business system cannot be obtained in time in the related technology, resulting in the inability to process tasks in time, resulting in low work efficiency.

[0088] Optionally, the business task processing device also includes: a first acquisition module, used to obtain configuration information of the business system before logging into the system account of each business system on the preset system, wherein the configuration information includes: interface information, login information; a first access module, used to connect the business system to the preset system based on the interface information; a first generation module, used to generate a system account and system password of the system account of the business system in the preset system based on the login information when the access is successful, wherein the system account and system password are used to log in to the system account of the business system on the preset system.

[0089] Optionally, the business task processing device also includes: a first suspension module, which is used to suspend the scheduling task program of the target business system after logging into the system account of each business system on the preset system, if the target system account of the target business system is not successfully logged into the preset system, wherein the scheduling task program is used to add the business tasks of the target business system to the preset task scheduler, and the business tasks correspond to task data; a first update module, which is used to update the system account and system password of the target system account in the preset system, and restart the scheduling task program of the target business system when the update is completed.

[0090] Optionally, the business task processing device also includes: a first configuration module, used to configure the task refresh frequency of the business system before collecting task data associated with the account identifier from a preset task scheduler, wherein the task refresh frequency is used to indicate the interval duration for collecting business tasks of the business system; a second configuration module, used to configure the task execution time of the business system, wherein the task execution time is used to indicate the time range for collecting business tasks of the business system; a first construction module, used to construct a scheduling task program for the business system based on the task refresh frequency and the task execution time.

[0091] Optionally, the processing unit includes: a first determination module, used to determine a display strategy based on a business system identifier of the task data; and a first processing module, used to process the task data according to the display strategy to obtain task to-be-processed information.

[0092] Optionally, the business task processing device also includes: a second construction module, used to construct a preset display interface before passing the task to be processed information to the preset display interface; a first segmentation module, used to segment the interface of the preset display interface according to the number of business systems connected to the preset system, to obtain N preset windows, where N is a positive integer, N is equal to the number of systems, and the preset window is associated with a business system identifier.

[0093] Optionally, the business task processing device also includes: a third construction module, used to construct a floating window, wherein the floating window is used to display the number of pending tasks for each business system, and the floating window includes: M sub-windows, M is a positive integer, M is equal to the number of systems, and the sub-window is associated with a business system identifier; a first accumulation module, used to accumulate the number of pending tasks displayed in the sub-window indicated by the business system identifier associated with the task pending information when task pending information is received on a preset display interface; a second update module, used to update the display color of the sub-window to a preset color when the number of pending tasks displayed in the sub-window is greater than a preset number threshold.

[0094] The above-mentioned business task processing device may also include a processor and a memory. The above-mentioned login unit 60, collection unit 61, processing unit 62, display unit 63, etc. are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0095] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the task to be processed information is transferred to the preset display interface by adjusting the kernel parameters, and the task to be processed information is displayed in a preset window of the preset display interface.

[0096] The above-mentioned memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one storage chip.

[0097] The present application also provides a computer program product, which, when executed on a data processing device, is suitable for executing an initialization program having the following method steps: logging in to the system account of each business system on a preset system, and if the login is successful, collecting task data associated with the account identifier from a preset task scheduler, generating a task queue, processing each task data in the task queue, obtaining task pending information, transmitting the task pending information to a preset display interface, and displaying the task pending information in a preset window of the preset display interface.

[0098] According to another aspect of an embodiment of the present invention, a computer-readable storage medium is provided, which includes a stored computer program, wherein when the computer program is running, the device where the computer-readable storage medium is located is controlled to execute the above-mentioned business task processing method based on a multi-business system.

[0099] According to another aspect of an embodiment of the present invention, there is also provided an electronic device, comprising one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by one or more processors, the one or more processors implement the above-mentioned business task processing method based on a multi-business system.

[0100] Figure 7 1 is a hardware structure block diagram of an electronic device (or mobile device) for a business task processing method based on a multi-business system according to an embodiment of the present invention. Figure 7 As shown, the electronic device may include one or more ( Figure 7 , 702a, 702b, ..., 702n are used to illustrate) processor 702 (processor 702 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), memory 704 for storing data. In addition, it may also include: 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 keyboard, a power supply and / or a camera. It can be understood by those skilled in the art that Figure 7 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 7 More or fewer components as shown, or with Figure 7 Different configurations are shown.

[0101] The serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages or disadvantages of the embodiments.

[0102] In the above embodiments of the present invention, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0103] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0104] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0105] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0106] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

[0107] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A business task processing method based on a multi-business system, characterized in that: include: Logging into the system account of each business system on the preset system, wherein the system account is associated with an account identifier; In case of successful login, task data associated with the account identifier is collected from a preset task scheduler to generate a task queue, wherein the task data is associated with the account identifier and the business system identifier; Processing each of the task data in the task queue to obtain task pending information, wherein the task pending information is used to remind the target terminal logged into the system account to process the task pending information; The task to be processed information is transmitted to a preset display interface, and the task to be processed information is displayed in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

2. The business task processing method according to claim 1, characterized in that: Before logging into the system account of each business system on the preset system, it also includes: Acquire configuration information of the business system, wherein the configuration information includes: interface information and login information; Based on the interface information, connecting the business system to the preset system; If the access is successful, a system account number and a system password of the system account of the business system are generated in the preset system based on the login information, wherein the system account number and the system password are used to log in to the system account of the business system on the preset system.

3. The business task processing method according to claim 1, characterized in that: After logging into the system account of each business system on the preset system, it also includes: If the target system account of the target business system is not successfully logged in on the preset system, suspending the scheduling task program of the target business system, wherein the scheduling task program is used to add the business task of the target business system to the preset task scheduler, and the business task corresponds to the task data; The system account and system password of the target system account in the preset system are updated, and when the update is completed, the scheduling task program of the target business system is restarted.

4. The business task processing method according to claim 1, characterized in that: Before collecting the task data associated with the account identifier from the preset task scheduler, the method further includes: Configuring a task refresh frequency of the business system, wherein the task refresh frequency is used to indicate the interval duration for collecting business tasks of the business system; Configuring the task execution time of the business system, wherein the task execution time is used to indicate the time range for collecting the business tasks of the business system; Based on the task refresh frequency and the task execution time, a scheduling task program of the business system is constructed.

5. The business task processing method according to claim 1, characterized in that: The step of processing each of the task data in the task queue to obtain task to be processed information includes: Determining a display strategy based on the business system identifier of the task data; According to the display strategy, the task data is processed to obtain the task to be processed information.

6. The business task processing method according to claim 1, characterized in that: Before transmitting the task to-be-processed information to the preset display interface, the method further includes: Constructing the preset display interface; According to the number of the business systems connected to the preset system, the interface of the preset display interface is divided to obtain N preset windows, where N is a positive integer, N is equal to the number of the systems, and the preset window is associated with the business system identifier.

7. The business task processing method according to claim 6, characterized in that: The business task processing method further includes: Constructing a floating window, wherein the floating window is used to display the number of pending tasks of each of the business systems, the floating window comprising: M sub-windows, M is a positive integer, M is equal to the number of the systems, and the sub-windows are associated with the business system identifiers; When the task to be processed information is received on the preset display interface, the number of the tasks to be processed displayed in the sub-window indicated by the business system identifier associated with the task to be processed information is accumulated; When the number of the tasks to be processed displayed in the sub-window is greater than a preset number threshold, the display color of the sub-window is updated to a preset color.

8. A business task processing device based on a multi-business system, characterized in that: include: A login unit, used to log in to a system account of each business system on a preset system, wherein the system account is associated with an account identifier; A collection unit, configured to collect task data associated with the account identifier from a preset task scheduler and generate a task queue when the login is successful, wherein the task data is associated with the account identifier and the business system identifier; A processing unit, used for processing each of the task data in the task queue to obtain task to be processed information, wherein the task to be processed information is used to remind the target terminal logged into the system account to process the task to be processed information; A display unit is used to transfer the pending task information to a preset display interface and display the pending task information in a preset window of the preset display interface, wherein the preset window is a display window corresponding to the business system indicated by the business system identifier.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored computer program, wherein when the computer program is executed, the device where the computer-readable storage medium is located is controlled to execute the business task processing method based on a multi-business system according to any one of claims 1 to 7.

10. An electronic device, characterized in that: It includes one or more processors and a memory, wherein the memory is used to store one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the business task processing method based on a multi-business system as described in any one of claims 1 to 7.

Images