Information processing method, task approval method and information processing device

Abstract

The present application provides an information processing method, comprising the following steps: obtaining the pending tasks of a third-party system and the unique code of the third-party system, and forming an association; grouping the pending tasks according to the approvers and storing them in a task pool; generating processing results according to the operations of the approvers; updating the task status of the pending tasks in the task pool according to the processing results; and synchronizing the task status to the corresponding third-party system based on the unique code. According to the information processing method of the present application, the pending tasks in multiple third-party systems can be integrated in a configurable manner. On the one hand, the pending tasks can be centralized to form a unified management model, improving the user experience and office efficiency of the approvers; on the other hand, there is no need to make a lot of modifications to the existing third-party systems, and the existing resources can be fully utilized to save costs.

Description

Technical Field

[0001] The present application relates to the field of computer technology and can be used in the financial field. Specifically, it relates to an information processing method, a task approval method, an information processing device, an electronic device, a medium and a product. Background Art

[0002] With the widespread application of information and digital technologies, a large number of management information systems have been built within enterprises to realize online business management and daily management. Task approval modules are set up in these management information systems to realize the online circulation and approval of work items. However, according to the function settings of each management information system, the task approval module in each management information system is often only responsible for the approval of tasks in a specific field. Approver as a user needs to log in to multiple management information systems for review, which makes the operation cumbersome. Summary of the invention

[0003] In view of the above technical problems, this application provides an information processing method, which realizes the integrated management of tasks to be approved in multiple third-party systems by utilizing data integration and task scheduling technology, and solves the problems of scattered tasks to be approved and inconvenient operation for approvers.

[0004] The first aspect of the present application provides an information processing method, comprising the following steps:

[0005] Obtaining the pending approval tasks of the third-party system and the unique code of the third-party system, and forming an association;

[0006] The tasks to be approved are grouped according to the approvers and stored in the task pool;

[0007] Generate a processing result according to the approver's operation;

[0008] According to the processing result, the task status of the pending tasks in the task pool is updated;

[0009] Based on the unique code, the task status is synchronized to a corresponding third-party system.

[0010] According to the information processing method of this application, the pending approval tasks in multiple third-party systems can be integrated in a configurable manner. On the one hand, the pending approval tasks can be centralized to form a unified management model, improving the user experience and office efficiency of the approvers; on the other hand, there is no need to make a lot of modifications to the existing third-party systems, which can make full use of existing resources and save costs.

[0011] Furthermore, before obtaining the pending approval task of the third-party system and the unique code of the third-party system, the following steps are included:

[0012] Set the calling frequency parameters of each interface;

[0013] A task acquisition request is sent to a third-party system according to the calling frequency parameter.

[0014] Furthermore, the method further comprises:

[0015] Recording the update time of the task status of each pending task in the task pool; and

[0016] Record the section time of each synchronization with the third-party system.

[0017] Further, based on the unique code, synchronizing the task status to a corresponding third-party system includes:

[0018] Obtaining the update time of the task status of each pending task in the task pool;

[0019] Get the section time of the last synchronization with the third-party system;

[0020] According to the section time and the update time, the tasks to be approved that are later than the section time are screened out;

[0021] Grouping the pending approval tasks according to the unique codes;

[0022] The corresponding interface is called according to the unique code, and the task status is synchronized to a third-party system.

[0023] Furthermore, the interface includes: an event interface, a task interface and a synchronization interface.

[0024] Furthermore, the task status includes at least one of pending approval, under approval, and approved.

[0025] Furthermore, before calling the corresponding interface according to the unique code and synchronizing the task status to the third-party system, it also includes:

[0026] The tasks to be approved in each group are classified according to the matter identifiers or task identifiers of the tasks to be approved.

[0027] Furthermore, the method further includes: controlling the opening and closing of the interface to control the access of the third-party system.

[0028] The second aspect of the present application provides a task approval method, comprising the following steps:

[0029] The approver logs in to his personal homepage;

[0030] Based on the personal information of the approver, the server pushes the pending approval tasks of the approver in the task pool, wherein the pending approval tasks have been grouped according to the approver and associated with the approver;

[0031] The server generates a processing result according to the operation of the approver;

[0032] The server updates the task status of the pending tasks in the task pool according to the processing result.

[0033] Furthermore, the operation of the approver includes one of approval, rejection and designation of other approvers.

[0034] Furthermore, the method further includes: the approver viewing the task details of the task to be approved.

[0035] Furthermore, the approver views the task details of the task to be approved, including:

[0036] The server initiates a request to view the task details to the corresponding third-party system according to the unique code of the third-party system, wherein the unique code is obtained while obtaining the task to be approved, and an association is formed;

[0037] The server receives a link to the third-party system;

[0038] The approver views the task details through the link.

[0039] The third aspect of the present application provides an information processing device, including: an acquisition module, the acquisition module is used to: acquire the pending tasks of a third-party system and the unique code of the third-party system, and form an association; a grouping module, the grouping module is used to: group the pending tasks according to the approvers and store them in a task pool; a processing module, the processing module is used to generate processing results according to the operations of the approvers; an update module, the update module is used to: update the task status of the pending tasks in the task pool according to the processing results; and a synchronization module, the synchronization module is used to: synchronize the task status to the corresponding third-party system based on the unique code.

[0040] The fourth aspect of the present application provides an electronic device, comprising: one or more processors; a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the data processing method.

[0041] The fifth aspect of the present application also provides a computer-readable storage medium on which executable instructions are stored, and when the instructions are executed by a processor, the processor executes the data processing method.

[0042] The sixth aspect of the present application also provides a computer program product, including a computer program, which implements the data processing method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] The above contents and other purposes, features and advantages of the present application will become more apparent through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:

[0044] Figure 1 A diagram schematically shows an application scenario of an approver using an information processing device according to an embodiment of the present application;

[0045] Figure 2 A flowchart of an information processing method according to an embodiment of the present application is schematically shown;

[0046] Figure 3 The following schematically shows the basic components of the information processing method according to the embodiment of the present application;

[0047] Figure 4 The flowchart before step S201 according to an embodiment of the present application is schematically shown;

[0048] Figure 5 A flowchart schematically illustrates the synchronization of task status to a third-party system according to an embodiment of the present application;

[0049] Figure 6 A flowchart of a task approval method according to an embodiment of the present application is schematically shown;

[0050] Figure 7 A flowchart of an approver viewing task details according to an embodiment of the present application is schematically shown;

[0051] Figure 8 A block diagram schematically shows a structure of an information processing device according to an embodiment of the present application; and

[0052] Fig. 9 A block diagram of an electronic device for implementing the information processing method according to an embodiment of the present application is schematically shown. DETAILED DESCRIPTION

[0053] Below, embodiments of the present application will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present application. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present application. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present application.

[0054] The terms used herein are only for describing specific embodiments and are not intended to limit the present application. The terms "include", "comprising", etc. used herein indicate the existence of the features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.

[0055] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.

[0056] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0057] With the widespread application of information and digital technologies, a large number of management information systems have been built within enterprises to realize online business management and daily management. Task approval modules are set up in these management information systems to realize the online circulation and approval of work items. However, according to the settings of the functions of each management information system, the task approval module in each management information system is often only responsible for the approval of tasks in a specific field. For example, the financial reimbursement system is responsible for approving reimbursement documents, and the leave approval system is responsible for approving leave items. As a user, the approver needs to log in to multiple management information systems to review them one by one, which makes the operation cumbersome. In addition, the tasks to be approved are scattered in various management information systems, and it is impossible to form a unified view of the approval items.

[0058] In order to solve the above problems, some enterprises currently use portal integration technology. With the help of single sign-on and menu integration, they can effectively avoid logging into multiple management information systems. However, the approver still needs to enter the menu page corresponding to the task to be approved. Multiple menu pages make it impossible to centrally process the tasks to be approved.

[0059] In response to the problems existing in the related technologies, the present application retains the task approval flow mechanism within the third-party system, and through an information processing device and an interface that can be uniformly adapted to the information processing device, it is possible to integrate and manage the pending approval tasks in multiple third-party systems in a unified manner within the information processing device, and through scheduling technology, the information processing device of the present application and the third-party system are driven to coordinate the flow of pending approval tasks.

[0060] It should be noted that the third-party system is a general term for management information systems, and different management information systems integrate different businesses. For example, the financial reimbursement system is a third-party system responsible for approving reimbursement documents, and the leave approval system is a third-party system responsible for approving leave requests.

[0061] Figure 1 The following schematically shows an application scenario diagram of an approver using an information processing device according to an embodiment of the present application.

[0062] like Figure 1 As shown, the application scenario 100 according to this embodiment may include: after the approver logs into the information processing device, the server 105 extracts the schematic diagram of the to-be-approved task content associated with the approver from the task pool.

[0063] The network 104 is used to provide a medium for communication links between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links or optical fiber cables.

[0064] The approver can use the terminal devices 101, 102, 103 to interact with the server 105 through the network 104 to receive or send messages, etc. Various communication client applications can be installed on the terminal devices 101, 102, 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only for example).

[0065] The terminal devices 101 , 102 , and 103 may be various electronic devices having a display screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers.

[0066] The server 105 may be a server that provides various services, for example, a background management server that provides support for the pages of pending approval tasks browsed by the approvers using the terminal devices 101, 102, and 103 (for example only). The background management server may analyze and process the received data such as the approver's request, and feed back the processing results (such as the webpages, information, or data obtained or generated according to the approver's request) to the terminal device.

[0067] It should be noted that the information processing method and task approval method provided in the embodiments of the present application can generally be executed by the server 105. Accordingly, the information processing device provided in the embodiments of the present application can generally be set in the server 105. The information processing method and task approval method provided in the embodiments of the present application can also be executed by a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105. Accordingly, the information processing device provided in the embodiments of the present application can also be set in a server or server cluster that is different from the server 105 and can communicate with the terminal devices 101, 102, 103 and / or the server 105.

[0068] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0069] The following will be based on Figure 1 The scene described by Figure 2 to Figure 7 The information processing method of the application embodiment is described in detail.

[0070] Figure 2 The flowchart of the information processing method according to the embodiment of the present application is schematically shown. The method is a technical solution for extracting and integrating tasks to be approved from a third-party system and synchronizing with the third-party system after approval. The method includes steps S201 to S205.

[0071] Combination Figure 2 , Figure 3 The basic components of the information processing method according to the embodiment of the present application are schematically shown.

[0072] In step 201, the tasks to be approved in the third-party system and the unique code of the third-party system are obtained and associated.

[0073] The third-party system accesses the information processing device of the present application through an interface, and assigns a unique code as an identifier to each third-party system accessed to distinguish different third-party systems. The pending tasks extracted by calling the interface of each third-party system will be associated with the unique code of the relevant third-party system. It can be understood that each pending task has a mark (unique code) from the relevant third-party system, and the third-party system that sent the pending task can be obtained through the mark on each pending task. For example: the reimbursement document (pending task) that needs to be approved obtained from the financial reimbursement system (third-party system) is marked with the unique code of this financial reimbursement system. Through the unique code on the reimbursement document, the financial reimbursement system that provides the reimbursement document can be found.

[0074] In a pending approval task, there are two parts: approval items and approval links. Among them, approval items correspond to business items that need to be approved, such as visitor approval, business trip approval, leave approval, financial reimbursement approval, etc.; approval links correspond to specific approval steps, involving approvers, and multiple approval links are combined to form an approval process, that is, an approval process includes multiple approval links. For example: in the pending approval task of Zhang San's business trip, the approval of the project manager and the department manager is required. Therefore, the approval process of this pending approval task includes two approval links, the project manager approval link and the department manager approval link.

[0075] In step 202, the tasks to be approved are grouped according to the approvers and stored in a task pool.

[0076] During the approval process, a pending approval task may need to be reviewed by multiple people, that is, it will involve multiple approval links. In order to facilitate the review of the approvers, the pending approval tasks with multiple approval items obtained in step S201 are grouped and classified according to the approvers, so that when the same approver approves, all the pending approval tasks involving this approver can be processed centrally, which is convenient for the approver to manage the approval tasks in a unified manner.

[0077] The task pool contains pending approval tasks obtained from third-party systems and unsynchronized approval tasks that have been completed. When the approver is not logged in, the grouped pending approval tasks are stored in the task pool so that multiple related pending approval tasks can be sent in response to the approver's login request or when the pending approval tasks are obtained.

[0078] In step 203, a processing result is generated according to the operation of the approver.

[0079] Based on the operation results of the approver in each approval link, the processing results are generated during or after the approver's operation. The processing results include passing the task to be approved to the next link, ending the process, and other operations.

[0080] The operations of the approver include approval, rejection, and designation of other approvers. Specifically, during the approval process, the approver at any stage can handle the pending approval tasks by themselves, or designate other approvers to handle the pending approval tasks. The operation of handling the pending approval tasks by themselves is to directly approve or reject the approval tasks, and the pending approval tasks will enter the next stage or end the process; designating other approvers to handle the pending approval tasks means that after the approver operates, the pending approval tasks will be transferred to the designated other approvers.

[0081] In Example 1, a pending task includes multiple approval links, each link corresponds to a relevant approver. In one link, after the approver agrees, the pending task will be executed and transferred to the next link and processed according to the approver group of the next link.

[0082] It should be noted that the approver of the next stage can be designated by the approver of this stage, or it can be the default set in the approval stage.

[0083] In Example 2, a task to be approved includes multiple approval links, and each link corresponds to a relevant approver. In the last link, after the approver agrees, the processing result of the process end will be executed.

[0084] In embodiment 3, a task to be approved includes multiple approval links, each link corresponds to a relevant approver. If the approver refuses in one of the links, the process will be terminated.

[0085] In embodiment 4, a pending approval task includes multiple approval links, each link corresponds to a relevant approver. In one link, after the approver specifies other approvers, the processing result of the pending approval task will be transmitted to the specified approver.

[0086] Furthermore, approvers at any stage can also comment on related tasks to be approved.

[0087] Approver may approve, reject or designate other approvers. Before executing the operation, the approver may write a comment on the task to be approved or the reason why he / she is going to perform one of the above operations to convey relevant opinions.

[0088] In step 204, the task status of the pending tasks in the task pool is updated according to the processing result.

[0089] According to the processing result in step S203, the task status of the task to be approved is updated, wherein the task status includes at least one of to be approved, in approval, and approved.

[0090] The pending tasks in the task pool will update their task status at a set frequency. After the processing results of each link are generated, the task status of the pending tasks in the entire approval process will be updated. Alternatively, after the processing results of each link are generated, only the task status of the relevant link will be updated.

[0091] A pending task includes multiple approval links, and each link corresponds to a relevant approver. When a pending task is being approved in one of the links, the processing status of the pending task in the task pool can be updated to "under approval"; when the pending task has not yet been approved by the relevant approver of one of the links, the task status of the pending task in the task pool is set to "pending approval", which means that the previous link has not generated a processing result and the pending task is still in the approval of the previous link; when the pending task in one of the links has been approved by the relevant approver, the task status of the pending task in the task pool is updated to "approved", which means that the processing result of the current link has been obtained.

[0092] In step 205, the task status is synchronized to the corresponding third-party system based on the unique code.

[0093] Based on the unique code, that is, group processing is performed based on the third-party system as the dimension. During the synchronization process, the corresponding third-party system interface is called according to the unique code to push the task status change information. The third-party system performs internal processing and circulation of tasks based on the pushed task status information and combined with its own business rules. The processing and circulation within the third-party system does not fall within the scope of protection of this application and will not be repeated here.

[0094] This application realizes the integrated management of tasks to be approved in multiple third-party systems by utilizing the integration and task scheduling technology of tasks to be approved. After the tasks to be approved are pushed in groups by approvers, the approvers can handle them centrally through one page, solving the problems of scattered tasks to be approved and inconvenient operations for approvers.

[0095] Figure 4 The flowchart that can be executed before obtaining the tasks to be approved of the third-party system and the unique code of the third-party system according to the embodiment of the present application is schematically shown.

[0096] like Figure 4 As shown, the information processing method of this embodiment includes steps S301 and S302.

[0097] It should be noted that before using the information processing method of the present application, steps S301-S302 are non-essential steps. That is, on the premise that steps S301-S302 have been executed, the information processing method of the present application can be used directly each time the information processing method of the present application is used thereafter, without the need to execute steps S301-S302 each time the information processing method of the present application is used.

[0098] In step S301, the calling frequency parameters of each interface are set.

[0099] Each third-party system will register a different interface, and one third-party system corresponds to one interface. In this application, the scheduling of pending tasks involving multiple third-party systems can set the calling frequency parameters of each third-party system in step S301, for example: each interface is set to be scheduled once an hour; or some interfaces are scheduled once an hour, and other interfaces are scheduled once every eight hours.

[0100] Of course, the interface of this application needs to meet the prerequisite of being adapted to the information processing device of this application. The information processing device connected to this application needs to develop the interface of the third-party system interface in advance according to the interface adaptation requirements of the information processing device. It can also be understood that as long as the interface of the third-party system meets the adaptation specification requirements, it can be connected to the information processing device of this application through configuration to uniformly manage the tasks to be approved.

[0101] In step S302, a task acquisition request is sent to a third-party system according to the calling frequency parameter.

[0102] The calling frequency parameter is equivalent to a timer, which can periodically send a task acquisition request to a third-party system. The interface of the third-party system responds to the request and sends the task to be approved to the information processing device.

[0103] It should be noted that, considering the situation that the interface is unavailable or anomalies occur, the present application can automatically repeat sending requests for task synchronization, and the number and frequency of retries can be configured in step S301.

[0104] In one embodiment, the information processing method further includes: controlling the opening and closing of the interface to control the access of a third-party system.

[0105] The interface has two states: enabled and disabled. This method can control the opening and closing of the interface. After the interface is disabled, it will no longer send task acquisition requests to the third-party system according to the call frequency parameter, that is, it will no longer receive pending tasks from the third-party system.

[0106] Regarding the interface enable and disable functions, some interfaces in multiple third-party systems can be disabled separately, or all related interfaces in multiple third-party systems can be disabled.

[0107] It should be noted that the control interface is enabled and disabled to control the access of third-party systems, which also applies to the synchronization of task status. The principle is the same as above. After the interface is disabled, synchronization with the third-party system will stop.

[0108] According to one embodiment of the present application, the information processing method further includes:

[0109] Recording the update time of the task status of each pending task in the task pool; and

[0110] Record the section time of each synchronization with the third-party system.

[0111] In the information processing method of the present application, in order to avoid data duplication and data omission when the task status of the pending task is synchronized with the third-party system, it is necessary to record the update time of each task status and the cross-sectional time of each synchronization with the third-party system.

[0112] The update time represents the time information when the task status of the pending task is updated after the related pending task is approved.

[0113] The cross-sectional time represents the time information when the information processing device of the present application is synchronized with the related third-party system.

[0114] Based on the updated time information and the synchronization time information, the pending tasks whose task status is updated after the section time can be screened out to avoid the phenomenon of the same pending task being updated multiple times in the third-party system, which helps to reduce resource usage.

[0115] It should be noted that since the synchronization process is a data transfer that occurs over a period of time, the "section time" in this application refers to the time node when the information processing device and the third-party system are just connected. In addition, since this application involves multiple third-party systems, it is necessary to record the section time of each third-party system each time it synchronizes with the information processing device.

[0116] Figure 5 The flowchart schematically shows the synchronization of the task status to the third-party system in step S205 according to an embodiment of the present application.

[0117] like Figure 5 As shown, the task status synchronization of this embodiment includes steps S401 to S405.

[0118] In step S401, the update time of the task status of each task to be approved in the task pool is obtained.

[0119] In step S402, the cross-sectional time of the last synchronization with the third-party system is obtained.

[0120] Synchronization with third-party systems occurs based on the frequency of interface calls. The cross-sectional time of the last synchronization with the third-party system is obtained. Using this as the time boundary, pending approval tasks that have been synchronized and updated with relevant third-party systems can be divided into pending approval tasks that have not been synchronized and updated with relevant third-party systems.

[0121] In step S403, based on the section time and the update time, the tasks to be approved that are later than the section time are screened out.

[0122] In this step, the update time of the pending approval tasks is divided into two groups, one before the time limit and one after the time limit, with the section time as the time limit. Among them, the pending approval tasks before the time limit are the pending approval tasks that have been synchronized and updated with the relevant third-party system, and the pending approval tasks after the time limit are the pending approval tasks that have not been synchronized and updated with the relevant third-party system. Therefore, the pending tasks corresponding to each update time in the group after the time limit are found as the task content to be updated with the third-party system, that is, the pending approval tasks later than the section time are the task content to be updated with the third-party system.

[0123] For example, each time the pending tasks are screened, the section time is passed as a parameter to the relevant interface of the third-party system. After the third-party system is connected, only the task status of the pending tasks whose time is after the relevant section time is synchronously updated, which can ensure the consistency of data during the transmission of the pending tasks across systems.

[0124] In step S404, the tasks to be approved are grouped according to the unique codes.

[0125] In step S201, the pending approval tasks and the unique code have been associated. In the synchronization process, the unique code can be used as a grouping mark to group the pending approval tasks screened in step S403. It can also be understood that the pending approval tasks updated with the third-party system are grouped based on the third-party system.

[0126] In step S405, the corresponding interface is called according to the unique code, and the task status is synchronized to the third-party system.

[0127] After the pending tasks are grouped, the corresponding interface is called according to the unique code to synchronize with the third-party system. It can be understood that the unique code is used as an association, the pending tasks are obtained from the relevant third-party system, and during synchronization, the task status of the pending tasks is also synchronized to the relevant third-party system.

[0128] It should be noted that the synchronization of the third-party system with the information processing device of this application and the secure calling of the interface depend on the unification of the user system and the unification of login authentication. The related technologies such as unified authentication and single sign-on are the basic technologies of this application. The specific operation and explanation of this related technology can be obtained from the existing technology and will not be explained in detail.

[0129] Furthermore, before calling the corresponding interface according to the unique code and synchronizing the task status to the third-party system, it also includes:

[0130] Classify the pending approval tasks in each group according to the matter identification or task identification of the pending approval tasks.

[0131] A pending approval task includes an item ID and a task ID. The item ID is used to distinguish approval items, such as visitor approval, business trip approval, leave approval, financial reimbursement approval, etc. The task ID is used to distinguish approval tasks, such as project manager approval tasks and department manager approval tasks.

[0132] The third-party system includes multiple matter approval modules. For example, the employee leave approval system includes business trip approval, personal leave approval, and sick leave approval. Therefore, during the synchronization process, after the approval tasks are grouped according to the unique code, the approval tasks need to be further classified according to the matter ID or task ID to quickly locate the location that needs to be synchronized in the third-party system.

[0133] It should be noted that in order to avoid duplicate classification of tasks to be approved, this application will select one of the categories of matter identification or task identification.

[0134] According to the information processing method of this application, the pending approval tasks in multiple third-party systems can be integrated in a configurable manner. On the one hand, the pending approval tasks can be centralized to form a unified management model, improving the approver's review experience and office efficiency; on the other hand, there is no need to make a lot of modifications to the existing third-party system, which can make full use of existing resources and save costs.

[0135] Figure 6 The flowchart of the task approval method according to the embodiment of the present application is schematically shown, which reflects the interaction process between the approver and the information processing device of the present application.

[0136] like Figure 6 As shown, the task approval method of this embodiment includes steps S501 to S504.

[0137] In step S501, the approver logs into the personal homepage.

[0138] In step S502, based on the personal information of the approver, the server pushes the tasks to be approved of the approver in the task pool, wherein the tasks to be approved have been grouped according to the approver and are associated with the approver.

[0139] After the approver successfully logs in, the server obtains the approver's personal information, which includes the approver's department, position and name. Based on the personal information, the server links the group of related tasks to be approved that match the approver from the task pool, and pushes the tasks to be approved to the front end for the approver to process.

[0140] That is to say, after the approver logs in to his personal homepage, all pending approval tasks related to the approver will be displayed on the homepage, and the approver can handle them centrally on one page, which solves the problem in the prior art that pending approval tasks are scattered and the approver needs to open multiple menus to view them.

[0141] In step S503, the server generates a processing result according to the approver's operation.

[0142] The approver's operation includes one of approval and rejection. After the approver's operation, the server generates a corresponding processing result. This process is the same as step 203 and will not be repeated here.

[0143] In step S504, the server updates the task status of the pending tasks in the task pool according to the processing result.

[0144] According to the processing result in step S503, the task status of the pending task is updated, wherein the task status includes at least one of pending, under review and approved. This process is the same as step 204 and will not be repeated here.

[0145] It should be noted that the information processing device of the present application is installed in the server, and the information processing method of the present application can be executed.

[0146] According to an embodiment of the present application, the task approval method further includes: the approver viewing the task details of the task to be approved.

[0147] During the approval process, the approver can view the task details of the task to be approved to assist the approver in making operational decisions.

[0148] The task details of different tasks to be approved are different. For example, in a reimbursement approval of Zhang San, the difference information and reimbursement amount information will be displayed in the task details, while in a leave approval of Li Si, the leave time and reason will be displayed in the task details.

[0149] Figure 7 The flowchart schematically shows the interaction between the server and the approver when the approver views the task details of the task to be approved according to the embodiment of the present application.

[0150] like Figure 7 As shown, the task details viewing of this embodiment includes steps S601 to S603.

[0151] In step S601, the server initiates a request to view task details to the corresponding third-party system according to the unique code of the third-party system, wherein the unique code is obtained while obtaining the task to be approved, and an association is formed.

[0152] There is a unique code associated with each pending item. Approver can view it according to business needs and send a request to the server to view task details. After receiving the request, the server sends a request to the corresponding third-party system based on the unique code of the pending item.

[0153] In step S602, the server receives a link from a third-party system.

[0154] The third-party system provides a link to view the task details based on the request sent by the server. The server passes this link to the front end for the approver to choose whether to click it.

[0155] In step S603, the approver views the task details through the link.

[0156] The approver can click the link to view the task details of the relevant tasks to be approved. Providing links not only solves the universality of third-party systems, but also meets personalized actual needs.

[0157] The personalization here means that the task details in the third-party system may be form S interfaces, pictures, charts, etc. that conform to the business characteristics of the system. For example, the details interface of a business trip task is different from that of a reimbursement task, and invoices are displayed in the format of invoices.

[0158] It should be noted that the above embodiment provides a method for viewing task details through a link. In another embodiment, the task details can also be viewed through the task pool, and the task details will be directly displayed on the homepage. In other words, the task pool can only provide a general interface to display text task details on the homepage, and the content format is unified, which cannot achieve the personalization and visualization of the third-party system, but it can still realize the technical solution of viewing task details of this application, and the method of viewing the task details of related pending tasks through the task pool is also within the protection scope of this application.

[0159] According to the task approval method of this application, multiple items to be approved of different types can be displayed on one page, and the approvers can centrally handle multiple items to be approved on the page, saving the approvers' operating procedures and improving approval efficiency.

[0160] Based on the above information processing method, the present application also provides an information processing device. Figure 8 The device is described in detail.

[0161] Figure 8 The figure schematically shows a structural block diagram of an information processing device according to an embodiment of the present application.

[0162] like Figure 8 As shown, the information processing device 700 of this embodiment includes an acquisition module 701 , a grouping module 702 , a processing module 703 , an updating module 704 and a synchronization module 705 .

[0163] Specifically, the acquisition module 701 is used to: acquire the pending approval task of the third-party system and the unique code of the third-party system, and form an association. In one embodiment, the acquisition module 701 can be used to execute the step S201 described above, which will not be repeated here.

[0164] The grouping module 702 is used to group the pending approval tasks according to the approvers and store them in the task pool. In one embodiment, the grouping module 702 can be used to execute the step S202 described above, which will not be described in detail here.

[0165] The processing module 703 is used to generate a processing result according to the operation of the approver. In one embodiment, the processing module 703 can be used to execute the step S203 described above, which will not be described in detail here.

[0166] The updating module 704 is used to update the task status of the pending tasks in the task pool according to the processing result. In one embodiment, the updating module 704 can be used to execute the step S204 described above, which will not be described in detail here.

[0167] The synchronization module 705 is used to synchronize the task status to the corresponding third-party system based on the unique code. In one embodiment, the synchronization module 705 can be used to execute the step S205 described above, which will not be described in detail here.

[0168] According to the information processing device of the present application, the information processing method of the application can be implemented, and the pending approval tasks in multiple third-party systems can be integrated in a configurable manner. On the one hand, the pending approval tasks can be centralized to form a unified management model, improving the user experience and office efficiency of the approver; on the other hand, there is no need to make a lot of modifications to the existing third-party system, which can make full use of existing resources and save costs.

[0169] According to an embodiment of the present application, any multiple modules in the acquisition module 701, the grouping module 702, the processing module 703, the update module 704 and the synchronization module 705 can be combined in one module for implementation, or any one of the modules can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present application, at least one of the acquisition module 701, the grouping module 702, the processing module 703, the update module 704 and the synchronization module 705 can be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application specific integrated circuit (ASIC), or can be implemented by hardware or firmware such as any other reasonable way of integrating or packaging the circuit, or by any one of the three implementation methods of software, hardware and firmware or by a suitable combination of any of them. Alternatively, at least one of the acquisition module 701, the grouping module 702, the processing module 703, the updating module 704 and the synchronization module 705 may be at least partially implemented as a computer program module, and when the computer program module is executed, the corresponding function may be performed.

[0170] Fig. 9 A block diagram of an electronic device suitable for implementing an information processing method according to an embodiment of the present application is schematically shown.

[0171] like Fig. 9 As shown, the electronic device 800 according to an embodiment of the present application includes a processor 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage part 808 into a random access memory (RAM) 803. The processor 801 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 801 may also include an onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present application.

[0172] In RAM 803, various programs and data required for the operation of electronic device 800 are stored. Processor 801, ROM 802 and RAM 803 are connected to each other via bus 804. Processor 801 performs various operations of the method flow according to the embodiment of the present application by executing the program in ROM 802 and / or RAM 803. It should be noted that the program can also be stored in one or more memories other than ROM 802 and RAM 803. Processor 801 can also perform various operations of the method flow according to the embodiment of the present application by executing the program stored in the one or more memories.

[0173] According to an embodiment of the present application, the electronic device 800 may further include an input / output (I / O) interface 805, which is also connected to the bus 804. The electronic device 800 may further include one or more of the following components connected to the I / O interface 805: an input portion 806 including a keyboard, a mouse, etc.; an output portion 807 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 808 including a hard disk, etc.; and a communication portion 809 including a network interface card such as a LAN card, a modem, etc. The communication portion 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to the I / O interface 805 as needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed, so that a computer program read therefrom is installed into the storage portion 808 as needed.

[0174] The present application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present application is implemented.

[0175] According to an embodiment of the present application, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present application, a computer-readable storage medium may include the ROM 802 and / or RAM 803 described above and / or one or more memories other than ROM 802 and RAM 803.

[0176] The embodiments of the present application also include a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the item recommendation method provided in the embodiments of the present application.

[0177] The above functions defined in the system / device of the embodiment of the present application are performed when the computer program is executed by the processor 801. According to the embodiment of the present application, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0178] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 809, and / or installed from a removable medium 811. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0179] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, the above functions defined in the system of the embodiment of the present application are performed. According to the embodiment of the present application, the system, device, means, module, unit, etc. described above can be implemented by a computer program module.

[0180] According to an embodiment of the present application, the program code for executing the computer program provided in the embodiment of the present application can be written in any combination of one or more programming languages, specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on a personnel computing device, partially on a personnel device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the personnel computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (e.g., using an Internet service provider to connect through the Internet).

[0181] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0182] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present application may be combined in a variety of ways and / or combinations, even if such combinations or combinations are not explicitly described in the present application. In particular, without departing from the spirit and teachings of the present application, the features described in the various embodiments and / or claims of the present application may be combined in a variety of ways and / or combinations. All of these combinations and / or combinations fall within the scope of the present application.

[0183] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0184] The embodiments of the present application are described above. However, these embodiments are only for the purpose of illustration, and are not intended to limit the scope of the present application. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination. The scope of the present application is limited by the attached claims and their equivalents. Without departing from the scope of the present application, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present application.

Claims

1. An information processing method, characterized in that: The following steps are involved: Obtaining the pending approval tasks of the third-party system and the unique code of the third-party system, and forming an association; The tasks to be approved are grouped according to the approvers and stored in the task pool; Generate a processing result according to the approver's operation; According to the processing result, the task status of the pending tasks in the task pool is updated; Based on the unique code, the task status is synchronized to the corresponding third-party system, wherein based on the unique code, the task status is synchronized to the corresponding third-party system, including: obtaining the update time of the task status of each pending task in the task pool; obtaining the section time of the last synchronization with the third-party system; based on the section time and the update time, filtering out the pending tasks that are later than the section time; grouping the pending tasks according to the unique code; calling the corresponding interface according to the unique code, and synchronizing the task status to the third-party system; Recording the update time of the task status of each pending task in the task pool; and Record the section time of each synchronization with the third-party system.

2. The information processing method according to claim 1, characterized in that: Before obtaining the pending approval tasks of the third-party system and the unique code of the third-party system, including: Set the calling frequency parameters of each interface; A task acquisition request is sent to a third-party system according to the calling frequency parameter.

3. The information processing method according to claim 1, characterized in that: The task status includes at least one of pending approval, under approval, and approved.

4. The information processing method according to claim 1, characterized in that: Before calling the corresponding interface according to the unique code and synchronizing the task status to the third-party system, the method further includes: The tasks to be approved in each group are classified according to the matter identifiers or task identifiers of the tasks to be approved.

5. The information processing method according to any one of claims 1 to 4, characterized in that: The method further includes: controlling the opening and closing of the interface to control the access of the third-party system.

6. A task approval method, characterized in that: The following steps are involved: The approver logs in to his personal homepage; Based on the personal information of the approver, the server pushes the pending approval tasks of the approver in the task pool, wherein the pending approval tasks have been grouped according to the approver and associated with the approver; The server generates a processing result according to the operation of the approver; The server updates the task status of the pending tasks in the task pool according to the processing result.

7. The task approval method according to claim 6, characterized in that: The operations of the approver include approval, rejection, and designation of another approver.

8. The task approval method according to claim 6, characterized in that: The method further includes: the approver viewing task details of the task to be approved.

9. The task approval method according to claim 8, characterized in that: The approver views the task details of the task to be approved, including: The server initiates a request to view the task details to the corresponding third-party system according to the unique code of the third-party system, wherein the unique code is obtained while obtaining the task to be approved, and an association is formed; The server receives a link to the third-party system; The approver views the task details through the link.

10. An information processing device, characterized in that: include: An acquisition module, the acquisition module is used to: acquire the pending approval tasks of the third-party system and the unique code of the third-party system, and form an association; A grouping module, the grouping module is used to: group the tasks to be approved according to the approvers and store them in a task pool; A processing module, the processing module is used to generate a processing result according to the operation of the approver; An updating module, the updating module being used to: update the task status of the pending tasks in the task pool according to the processing result; A synchronization module, the synchronization module is used to: synchronize the task status to the corresponding third-party system based on the unique code, wherein, based on the unique code, synchronizing the task status to the corresponding third-party system includes: obtaining the update time of the task status of each pending task in the task pool; obtaining the section time of the last synchronization with the third-party system; based on the section time and the update time, filtering out the pending tasks that are later than the section time; grouping the pending tasks according to the unique code; calling the corresponding interface according to the unique code, and synchronizing the task status to the third-party system; Recording the update time of the task status of each pending task in the task pool; and Record the section time of each synchronization with the third-party system.

11. An electronic device, comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors execute the information processing method according to any one of claims 1 to 5.

12. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the information processing method according to any one of claims 1 to 5.

13. A computer program product, comprising a computer program, wherein when the computer program is executed by a processor, the information processing method according to any one of claims 1 to 5 is implemented.

Images