System integration method and device, computer equipment, storage medium and program product

Abstract

The invention relates to a system integration method and device, computer equipment, a storage medium and a program product, and the method comprises the steps that second computer equipment sends a service request to first computer equipment, and correspondingly, the first computer equipment receives the service request; the service request comprises a service identification code corresponding to the service system; the first computer device obtains registration information associated with the service identification code in response to the service request; the registration information comprises front-end framework information corresponding to the business system and identification information of the target embedded page; the first computer equipment generates a target embedded page matched with the front-end frame information based on the identification information of the target embedded page; and the first computer equipment sends the target embedded page to the second computer equipment, and correspondingly, the second computer equipment receives the target embedded page. By adopting the method, the integration speed between the task management system and the business system can be improved.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a system integration method, apparatus, computer equipment, storage medium and program product. Background Art

[0002] As a commonly used tool for enterprise operation management, the task management system realizes the control of the entire process of daily tasks. During the use of enterprises, there is often a need to integrate with multiple business systems of the enterprise. At present, the integration of task management systems and third-party systems is basically achieved through conventional traditional methods such as API interfaces on the market. However, this method requires a lot of development work for the integrated system, resulting in a slow integration speed.

[0003] Therefore, how to improve the integration speed between task management systems and business systems has become an urgent problem to be solved. Summary of the invention

[0004] The embodiments of the present application provide a system integration method, apparatus, computer equipment, storage medium and program product, which can improve the integration speed between a task management system and a business system.

[0005] In a first aspect, an embodiment of the present application provides a system integration method, which is applied to a first computer device deployed with a task management system, and the method includes:

[0006] Receiving a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system;

[0007] In response to the business request, obtaining registration information associated with the business identification code; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page;

[0008] Based on the identification information of the target embedded page, generate a target embedded page that matches the front-end framework information;

[0009] The target embedded page is sent to the second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

[0010] In one of the embodiments, before receiving a business request sent by a second computer device deployed with a business system, it also includes: receiving registration information sent by the second computer device; the registration information includes the name of the business system, the front-end framework information corresponding to the business system, the Internet Protocol address of the second computer device, and the identification information of the target embedded page associated with the business needs; based on the registration information, generating a business identification code corresponding to the business system; and sending the business identification code to the second computer device.

[0011] In one of the embodiments, the method also includes: when it is determined that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, updating the task management system so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system.

[0012] In one embodiment, after receiving the registration information sent by the second computer device, it also includes: storing the registration information in a database; and obtaining the registration information associated with the service identification code in response to the service request, including: obtaining the registration information corresponding to the second computer device from the database based on the service identification code in the service request.

[0013] In one of the embodiments, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0014] In a second aspect, the present application provides another system integration method, which is applied to a second computer device deployed with a business system, and the method includes:

[0015] In response to a trigger operation for generating an entry for a target embedded page in a user interface, a service request is sent to a first computer device where a task management system is deployed; the service request includes a service identification code corresponding to the service system;

[0016] receiving a target embedded page returned by the first computer device; the target embedded page is determined by the first computer device based on registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task;

[0017] Displays the target embed page in the user interface.

[0018] In a third aspect, the present application provides a system integration device, which is applied to a first computer device deployed with a task management system, and the device includes:

[0019] A receiving module is used to receive a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system;

[0020] The acquisition module is used to obtain the registration information associated with the business identification code in response to the business request; the registration information includes the front-end framework information corresponding to the business system and the identification information of the target embedded page;

[0021] A generation module, used to generate a target embedded page matching the front-end framework information based on the identification information of the target embedded page;

[0022] The sending module is used to send the target embedded page to the second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to realize the various functions of the task.

[0023] In a fourth aspect, the present application provides a system integration device, which is applied to a second computer device deployed with a business system, and the device includes:

[0024] A sending module, configured to send a business request to a first computer device where a task management system is deployed in response to a triggering operation of generating a portal for a target embedded page in a user interface; the business request includes a business identification code corresponding to the business system;

[0025] A receiving module, configured to receive a target embedded page returned by the first computer device, wherein the target embedded page is determined by the first computer device based on registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task;

[0026] The display module is used to display the target embedded page in the user interface.

[0027] In a fifth aspect, the present application provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method involved in the first aspect or the second aspect are implemented.

[0028] In a sixth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which implements the steps of the method involved in the first aspect or the second aspect when the computer program is executed by a processor.

[0029] In a seventh aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the method involved in the first aspect or the second aspect.

[0030] The above-mentioned system integration method, apparatus, computer equipment, storage medium and program product, the second computer equipment deployed with the business system (referred to as the second computer equipment for short) can respond to the trigger operation of generating an entry for the target embedded page in the user interface, and send a business request to the first computer equipment deployed with the task management system (referred to as the first computer equipment for short), and accordingly, the first computer equipment receives the business request sent by the second computer equipment; the business request is used to request the output of the target embedded page associated with the business demand, and the business request includes the business identification code corresponding to the business system; the first computer equipment responds to the business request, and obtains the registration information associated with the business identification code; the registration information includes the front-end framework information corresponding to the business system and the identification information of the target embedded page; the first computer equipment generates a target embedded page matching the front-end framework information based on the identification information of the target embedded page; the first computer equipment sends the target embedded page to the second computer equipment, and accordingly, the second computer equipment receives the target embedded page returned by the first computer equipment; the target embedded page is a function embedded page created for various functions of the task, and is used to realize various functions of the task; the second computer equipment displays the target embedded page in the user interface. By adopting this method, all task operations of the integrated system can be completed through the embedded page sent from the first computer device to the second computer device. The actual operation is performed in the first computer device where the task management system is deployed. In this way, the integrated system only needs to complete the embedded page access. For example, by docking the task dashboard embedded page and the task statistics analysis embedded page, various statistics and tracking of business system tasks can be achieved without a lot of development work, thereby improving the integration speed between the task management system and the business system. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0032] Figure 1 It is a schematic diagram of an application scenario of a system integration method provided in an embodiment of the present application;

[0033] Figure 2 It is a flowchart of a system integration method applied to a first computer device deployed with a task management system provided by an embodiment of the present application;

[0034] Figure 3 It is a flowchart of an integrated system method applied to a second computer device deployed with a business system provided by an embodiment of the present application;

[0035] Figure 4 It is a flowchart of a multi-terminal interactive system integration method provided in an embodiment of the present application;

[0036] Figure 5 is a schematic diagram of part of the content displayed in a user interface of a second computer device provided in an embodiment of the present application;

[0037] Figure 6 It is a structural schematic diagram of a system integration device provided in an embodiment of the present application;

[0038] Figure 7 is a structural schematic diagram of another system integration device provided in an embodiment of the present application;

[0039] Figure 8 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0041] First, the application scenario of the system integration method provided in the embodiment of the present application is introduced.

[0042] See also Figure 1 , Figure 1 Schematic diagram of an application scenario of a system integration method provided in an embodiment of the present application. Figure 1 As shown, the first computer device 101 ( Figure 1 In the figure, the first computer device 101 is a terminal device and the second computer device 102 ( Figure 1 In the figure, the second computer device 101 is drawn as an example of a terminal device, wherein the first computer device 101 is a computer device deployed with a task management system, and the second computer device 102 is a computer device deployed with a business system. Data can be transmitted between the first computer device 101 and the second computer device 102 through a network.

[0043] The second computer device 102 may send a business request to the first computer device 101 in response to a trigger operation for generating an entry for a target embedded page in the user interface, and accordingly, the first computer device 101 receives the business request sent by the second computer device 102; the business request is used to request output of a target embedded page associated with a business requirement, and the business request includes a business identification code corresponding to the business system; the first computer device 101 obtains registration information associated with the business identification code in response to the business request; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page; the first computer device 101 generates a target embedded page matching the front-end framework information based on the identification information of the target embedded page; the first computer device 101 sends the target embedded page to the second computer device 102, and accordingly, the second computer device 102 receives the target embedded page returned by the first computer device 101; the target embedded page is a function embedded page created for various functions of the task, and is used to implement various functions of the task; the second computer device 102 displays the target embedded page in the user interface. By adopting this method, all task operations of the integrated system can be completed through the embedded page sent from the first computer device to the second computer device. The actual operation is performed in the first computer device where the task management system is deployed. In this way, the integrated system only needs to complete the embedded page access. For example, by docking the task dashboard embedded page and the task statistics analysis embedded page, various statistics and tracking of business system tasks can be achieved without a lot of development work, thereby improving the integration speed between the task management system and the business system.

[0044] See also Figure 2 , Figure 2 1 is a flow chart of a system integration method for a first computer device equipped with a task management system provided by an embodiment of the present application. The method may be performed by the first computer device (e.g., Figure 1 The first computer device 101 in the embodiment is executed. Figure 2 As shown, the system integration method may include but is not limited to the following steps:

[0045] S201, receiving a business request sent by a second computer device deployed with a business system; the business request is used to request output of a target embedded page associated with a business requirement, and the business request includes a business identification code corresponding to the business system.

[0046] The target embedding page is a function embedding page created for various functions of the task, and is used to implement the various functions of the task.

[0047] In an optional implementation, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0048] Optionally, the business request may further include business information, such as a task title, where the task title is a task title associated with the business requirement.

[0049] S202: In response to the service request, obtain registration information associated with the service identification code; the registration information includes front-end framework information corresponding to the service system and identification information of the target embedded page.

[0050] In an optional embodiment, the first computer device obtains registration information associated with the service identification code in response to the service request, which may include: based on the service identification code in the service request, obtaining registration information corresponding to the second computer device from a database, wherein the registration information corresponding to the second computer device is stored in the database.

[0051] S203: Based on the identification information of the target embedded page, generate a target embedded page that matches the front-end framework information.

[0052] In this way, by generating a target embedded page that matches the front-end framework information, the overall style of the embedded page can be automatically adapted to ensure the consistency of the embedded page and the front-end framework page style of the integrated system. At the same time, it can meet the different needs of different business systems for different front-end framework styles and support a variety of popular front-end frameworks.

[0053] In an optional implementation, the first computer device may also update the task management system when determining that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system. In this way, rapid expansion can be achieved for new front-end frameworks.

[0054] S204: Send the target embedded page to the second computer device.

[0055] In an embodiment of the present application, the first computer device can receive a business request sent by the second computer device, and the business request is used to request the output of a target embedded page associated with the business demand; the business request includes a business identification code corresponding to the business system; in response to the business request, the registration information associated with the business identification code is obtained; the registration information includes the front-end framework information corresponding to the business system and the identification information of the target embedded page; based on the identification information of the target embedded page, a target embedded page matching the front-end framework information is generated; the target embedded page is sent to the second computer device; the target embedded page is a functional embedded page created for various functions of the task, and is used to implement various functions of the task. In this way, all task operations of the integrated system can be completed through the embedded page sent by the first computer device to the second computer device, and the actual operation is performed in the first computer device where the task management system is deployed, that is, the integrated system only needs to complete the embedded page access without a lot of development work, thereby improving the integration speed between the task management system and the business system.

[0056] See also Figure 3 , Figure 3 1 is a flow chart of an integrated system method for a second computer device with a business system deployed thereon provided in an embodiment of the present application. The method may be performed by the second computer device (e.g. Figure 1 The second computer device 102 in the embodiment executes. Figure 3 As shown, the system integration method may include but is not limited to the following steps:

[0057] S301, in response to a triggering operation of generating a portal for a target embedded page in a user interface, sending a service request to a first computer device where a task management system is deployed; the service request includes a service identification code corresponding to the service system.

[0058] The business request is used to request the output of a target embedding page associated with the business requirement. The target embedding page is a function embedding page created for various functions of the task, and is used to implement various functions of the task.

[0059] In an optional implementation, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0060] In an optional embodiment, before step S301, the second computer device may also send registration information to the first computer device on which the task management system is deployed, the registration information including the business system name, the front-end framework information corresponding to the business system, the Internet Protocol address of the second computer device, and identification information of the target embedded page associated with the business needs; and receive the business identification code returned by the first computer device; the business identification code is generated by the first computer device based on the registration information.

[0061] S302: Receive the target embedded page returned by the first computer device.

[0062] The target embedded page is determined by the first computer device based on registration information associated with the service identification code included in the received service request.

[0063] S303: Display the target embedding page on the user interface.

[0064] In an embodiment of the present application, the second computer device can respond to a trigger operation for generating an entry for a target embedded page in a user interface, and send a business request to a first computer device deployed with a task management system; the business request includes a business identification code corresponding to the business system; the target embedded page returned by the first computer device is received; the target embedded page is determined by the first computer device based on the registration information associated with the business identification code included in the received business request; the target embedded page is a function embedded page created for various functions of the task, used to implement various functions of the task; the target embedded page is displayed in the user interface. With this method, all task operations of the integrated system can be completed through the embedded page displayed in the user interface of the second computer device, and the actual operation is performed in the first computer device deployed with the task management system. In this way, compared with the traditional method of realizing system integration through an API interface, the integrated system only needs to complete the embedded page access, such as by docking the task board embedded page and the task statistics analysis embedded page, various statistics and tracking of business system tasks can be realized without a lot of development work, thereby improving the integration speed between the task management system and the business system.

[0065] In addition, compared with the traditional method of achieving system integration through API interface, in the system integration method provided by the present application, after the second computer device displays the target embedded page on the user interface, all task operations are performed on the embedded page provided by the second computer device where the business system is deployed. There is no need for the integrated system to be newly developed according to the API provided by the task management system, including the front-end page and interface docking. In this way, once the API interface changes, the business system needs to be modified synchronously. In other words, the present application does not require any adjustments to the business system, thereby reducing the coupling between systems.

[0066] See also Figure 4 , Figure 4 1 is a flowchart of a multi-terminal interactive system integration method provided by an embodiment of the present application. The first computer device is a computer device with a task management system deployed, and the second computer device is a computer device with a business system deployed. Figure 4 As shown, the system integration method may include but is not limited to the following steps:

[0067] S401. The second computer device sends a business request to the first computer device in response to a trigger operation for generating an entry for a target embedded page in a user interface. Correspondingly, the first computer device receives the business request sent by the second computer device. The business request is used to request output of a target embedded page associated with a business requirement, and the business request includes a business identification code corresponding to the business system.

[0068] The target embedding page is a function embedding page created for various functions of the task, and is used to implement the various functions of the task.

[0069] In an optional implementation, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0070] Taking the "task board embedding page" of the task management system integrated through the business system as an example, the user can generate an entry by clicking the business system task menu in the user interface of the second computer device, that is, the task board embedding page, such as Figure 5 The task management system-task board embedded page address in triggers the second computer device to access the embedded page of the task management system. Figure 5 The business identification code corresponding to the business system is also included.

[0071] In an optional implementation, before step S401, the second computer device may also send registration information to the first computer device, and accordingly, the first computer device receives the registration information sent by the second computer device; the registration information includes the name of the business system, the front-end framework information corresponding to the business system, the Internet protocol address of the second computer device, and the identification information of the target embedded page associated with the business demand; the first computer device generates a business identification code corresponding to the business system based on the registration information; the first computer device sends the business identification code to the second computer device, and accordingly, the second computer device receives the business identification code returned by the first computer device; the business identification code is generated by the first computer device based on the registration information. It can be understood that the business system can register and apply for a functional embedded page associated with the business demand according to the business demand.

[0072] In this implementation manner, the first computer device may further store the registration information in the database after receiving the registration information sent by the second computer device.

[0073] S402: The first computer device obtains registration information associated with the business identification code in response to the business request; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page.

[0074] In an optional implementation, the first computer device, in response to the service request, obtains registration information associated with the service identification code, which may include: obtaining registration information corresponding to the second computer device from a database based on the service identification code in the service request.

[0075] For example, after receiving the service request, the first computer device can identify the requesting system as a service system according to the service identification code corresponding to the service system, such as "SYSIdeCODE='PMS'". After that, the first computer device can obtain the registration information associated with the service identification code, and determine the front-end framework information corresponding to the service system and the identification information of the embedded page to be integrated based on the registration information.

[0076] S403: The first computer device generates a target embedded page that matches the front-end framework information based on the identification information of the target embedded page.

[0077] In an optional implementation, the relevant description of step S403 can refer to the description of the aforementioned step S203, which will not be repeated here.

[0078] S404: The first computer device sends the target embedded page to the second computer device, and correspondingly, the second computer device receives the target embedded page returned by the first computer device.

[0079] S405: The second computer device displays the target embedded page on the user interface.

[0080] Assuming that the target embedded page is the task board embedded page, that is, the business system integrates the task board embedded page of the task management system, then if there are subsequent tasks to be added, task information to be modified, tasks to be issued, etc., the user can directly operate on the task board embedded page displayed on the user interface of the second computer device where the business system is deployed.

[0081] In an embodiment of the present application, a second computer device (referred to as the second computer device) deployed with a business system may send a business request to a first computer device (referred to as the first computer device) deployed with a task management system in response to a trigger operation for generating an entry for a target embedded page in a user interface, and accordingly, the first computer device receives the business request sent by the second computer device; the business request is used to request output of a target embedded page associated with a business requirement, and the business request includes a business identification code corresponding to the business system; the first computer device obtains registration information associated with the business identification code in response to the business request; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page; the first computer device generates a target embedded page matching the front-end framework information based on the identification information of the target embedded page; the first computer device sends the target embedded page to the second computer device, and accordingly, the second computer device receives the target embedded page returned by the first computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement various functions of the task; the second computer device displays the target embedded page in the user interface. By adopting this method, all task operations of the integrated system can be completed through the embedded page sent from the first computer device to the second computer device, and the actual operation is carried out in the first computer device where the task management system is deployed. In this way, compared with the traditional method of realizing system integration through API interface, the integrated system in this application only needs to complete the embedded page access, such as by docking the task dashboard embedded page and the task statistics analysis embedded page, various statistics and tracking of business system tasks can be realized without a lot of development work, thereby improving the integration speed between the task management system and the business system, and completing the system integration quickly, seamlessly and flexibly.

[0082] In addition, compared with the traditional method of achieving system integration through API interface, the system integration method provided by the present application can realize the reuse of task function modules in the process of business system docking without the need for complete interaction design, such as the need to consider status changes between the two systems, how to synchronize new data, etc., thereby reducing costs.

[0083] Based on the same inventive concept, the embodiment of the present application also provides a system integration device for implementing the system integration method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more system integration device embodiments provided below can refer to the limitations on the system integration method above, and will not be repeated here.

[0084] See also Figure 6 , Figure 61 is a schematic diagram of the structure of a system integration device provided in an embodiment of the present application. The device can be used to implement the operations performed by the first computer device in the system integration method involved above. Figure 6 As shown, the system integration device may include but is not limited to:

[0085] Receiving module 601, used to receive a business request sent by a second computer device deployed with a business system; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system;

[0086] The acquisition module 602 is used to obtain the registration information associated with the business identification code in response to the business request; the registration information includes the front-end framework information corresponding to the business system and the identification information of the target embedded page;

[0087] A generating module 603 is used to generate a target embedded page matching the front-end framework information based on the identification information of the target embedded page;

[0088] The sending module 604 is used to send the target embedded page to the second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

[0089] In one embodiment, before receiving a business request sent by a second computer device deployed with a business system, the receiving module 601 is also used to: receive registration information sent by the second computer device; the registration information includes the name of the business system, the front-end framework information corresponding to the business system, the Internet Protocol address of the second computer device, and the identification information of the target embedded page associated with the business needs; the generating module 603 is also used to generate a business identification code corresponding to the business system based on the registration information; the sending module 604 is also used to send the business identification code to the second computer device.

[0090] In one embodiment, the device may further include an update module. The update module is used to update the task management system when it is determined that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system.

[0091] In one embodiment, the apparatus further includes a storage module. The storage module is used to store the registration information in a database after the receiving module 601 is used to receive the registration information sent by the second computer device; when the acquisition module 602 is used to respond to a service request and acquire the registration information associated with the service identification code, it is specifically used to: acquire the registration information corresponding to the second computer device from the database based on the service identification code in the service request.

[0092] In one embodiment, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0093] See also Figure 7 , Figure 7 1 is a schematic diagram of the structure of another system integration device provided in an embodiment of the present application. The device can be used to implement the operations performed by the second computer device in the system integration method involved above. Figure 7 As shown, the system integration device may include but is not limited to:

[0094] The sending module 701 is used to send a business request to a first computer device where a task management system is deployed in response to a trigger operation for generating a portal for a target embedded page in a user interface; the business request includes a business identification code corresponding to the business system;

[0095] The receiving module 702 is used to receive a target embedded page returned by the first computer device, where the target embedded page is determined by the first computer device based on the registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task;

[0096] The display module 703 is used to display the target embedded page on the user interface.

[0097] Each module in the above system integration device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of the processor in the terminal device in the form of hardware, or can be stored in the memory in the terminal device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0098] In an exemplary embodiment, the present application provides a computer device, which may be a terminal, and its internal structure diagram may be as follows: Figure 8As shown. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit and an input device. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface, the display unit and the input device are connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a system integration method is implemented.

[0099] Those skilled in the art will understand that Figure 8 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0100] In an exemplary embodiment, the present application provides a computer device, including a memory and a processor, wherein a computer program is stored in the memory.

[0101] In an optional implementation, when the processor executes the computer program, the steps performed by the first computer device in the above system integration method may be implemented, for example:

[0102] Receiving a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system;

[0103] In response to the business request, obtaining registration information associated with the business identification code; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page;

[0104] Based on the identification information of the target embedded page, generate a target embedded page that matches the front-end framework information;

[0105] The target embedded page is sent to the second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

[0106] In this embodiment, before the processor executes a computer program to receive a business request sent by a second computer device deployed with a business system, it also implements the following steps: receiving registration information sent by the second computer device; the registration information includes the name of the business system, the front-end framework information corresponding to the business system, the Internet Protocol address of the second computer device, and the identification information of the target embedded page associated with the business needs; based on the registration information, generating a business identification code corresponding to the business system; and sending the business identification code to the second computer device.

[0107] In this embodiment, the processor executes the computer program to further implement the following steps: when it is determined that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, the task management system is updated so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system.

[0108] In this implementation, after the processor executes the computer program to receive the registration information sent by the second computer device, it also implements the following steps: storing the registration information in a database; when the processor executes the computer program to respond to a service request and obtain the registration information associated with the service identification code, it specifically implements the following steps: based on the service identification code in the service request, obtaining the registration information corresponding to the second computer device from the database.

[0109] In this implementation, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0110] In another optional implementation, when the processor executes the computer program, the steps performed by the second computer device in the above system integration method may be implemented, for example:

[0111] In response to a trigger operation for generating an entry for a target embedded page in a user interface, a service request is sent to a first computer device where a task management system is deployed; the service request includes a service identification code corresponding to the service system;

[0112] receiving a target embedded page returned by the first computer device; the target embedded page is determined by the first computer device based on registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task;

[0113] Displays the target embed page in the user interface.

[0114] In an exemplary embodiment, the present application provides a computer-readable storage medium having a computer program stored thereon.

[0115] In an optional implementation, when the computer program is executed by a processor, the steps performed by the first computer device in the above system integration method may be implemented, for example:

[0116] Receiving a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system;

[0117] In response to the business request, obtaining registration information associated with the business identification code; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page;

[0118] Based on the identification information of the target embedded page, generate a target embedded page that matches the front-end framework information;

[0119] Sending a target embedded page to a second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

[0120] In this implementation, before the computer program is executed by the processor to implement receiving a business request sent by a second computer device deployed with a business system, the following steps are also implemented: receiving registration information sent by the second computer device; the registration information includes the name of the business system, the front-end framework information corresponding to the business system, the Internet Protocol address of the second computer device, and the identification information of the target embedded page associated with the business needs; based on the registration information, generating a business identification code corresponding to the business system; and sending the business identification code to the second computer device.

[0121] In this embodiment, the computer program executed by the processor also implements the following steps: when it is determined that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, the task management system is updated so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system.

[0122] In this implementation, after the computer program is executed by the processor to receive the registration information sent by the second computer device, the following steps are also implemented: the registration information is stored in a database; when the computer program is executed by the processor to respond to a service request and obtain the registration information associated with the service identification code, the following steps are specifically implemented: based on the service identification code in the service request, the registration information corresponding to the second computer device is obtained from the database.

[0123] In this implementation, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0124] In another optional implementation, when the computer program is executed by the processor, the steps performed by the second computer device in the above system integration method may be implemented, for example:

[0125] In response to a trigger operation for generating an entry for a target embedded page in a user interface, a service request is sent to a first computer device where a task management system is deployed; the service request includes a service identification code corresponding to the service system;

[0126] receiving a target embedded page returned by the first computer device; the target embedded page is determined by the first computer device based on registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task;

[0127] Displays the target embed page in the user interface.

[0128] In an exemplary embodiment, the present application provides a computer program product, including a computer program. In an optional implementation, when the computer program is executed by a processor, the steps performed by the first computer device in the above-mentioned system integration method can be implemented, for example:

[0129] Receiving a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system;

[0130] In response to the business request, obtaining registration information associated with the business identification code; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page;

[0131] Based on the identification information of the target embedded page, generate a target embedded page that matches the front-end framework information;

[0132] Sending a target embedded page to a second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

[0133] In this implementation, before the computer program is executed by the processor to implement receiving a business request sent by a second computer device deployed with a business system, the following steps are also implemented: receiving registration information sent by the second computer device; the registration information includes the name of the business system, the front-end framework information corresponding to the business system, the Internet Protocol address of the second computer device, and the identification information of the target embedded page associated with the business needs; based on the registration information, generating a business identification code corresponding to the business system; and sending the business identification code to the second computer device.

[0134] In this embodiment, the computer program executed by the processor also implements the following steps: when it is determined that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, the task management system is updated so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system.

[0135] In this implementation, after the computer program is executed by the processor to receive the registration information sent by the second computer device, the following steps are also implemented: the registration information is stored in a database; when the computer program is executed by the processor to respond to a service request and obtain the registration information associated with the service identification code, the following steps are specifically implemented: based on the service identification code in the service request, the registration information corresponding to the second computer device is obtained from the database.

[0136] In this implementation, the target embedded page includes any one of the following: a task creation embedded page, a task issuance embedded page, a task progress feedback embedded page, a task working hour feedback embedded page, a task tracking dashboard embedded page, and a task statistics analysis dashboard embedded page.

[0137] In another optional implementation, when the computer program is executed by the processor, the steps performed by the second computer device in the above system integration method may be implemented, for example:

[0138] In response to a trigger operation for generating an entry for a target embedded page in a user interface, a service request is sent to a first computer device where a task management system is deployed; the service request includes a service identification code corresponding to the service system;

[0139] receiving a target embedded page returned by the first computer device; the target embedded page is determined by the first computer device based on registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task;

[0140] Displays the target embed page in the user interface.

[0141] It should be noted that the data involved in this application (including but not limited to registration information, business identification codes, etc.) 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 relevant regulations.

[0142] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0143] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0144] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A system integration method, characterized in that: Applied to a first computer device deployed with a task management system, the method comprises: Receiving a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system; In response to the service request, obtaining registration information associated with the service identification code; the registration information includes front-end framework information corresponding to the service system and identification information of the target embedded page; Based on the identification information of the target embedded page, generating the target embedded page matching the front-end framework information; The target embedded page is sent to the second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

2. The method according to claim 1, characterized in that Before receiving the service request sent by the second computer device where the service system is deployed, the method further includes: receiving registration information sent by the second computer device; the registration information includes the name of the business system, front-end framework information corresponding to the business system, the Internet protocol address of the second computer device, and identification information of a target embedded page associated with the business requirement; Based on the registration information, generate a business identification code corresponding to the business system; The service identification code is sent to the second computer device.

3. The method according to claim 2, characterized in that The method further comprises: When it is determined that the front-end framework technology associated with the front-end framework information corresponding to the business system included in the registration information is not supported, the task management system is updated so that the updated task management system supports the front-end framework technology associated with the front-end framework information corresponding to the business system.

4. The method according to claim 2, characterized in that: After receiving the registration information sent by the second computer device, the method further includes: Storing the registration information in a database; The step of obtaining, in response to the service request, registration information associated with the service identification code includes: Based on the service identification code in the service request, registration information corresponding to the second computer device is obtained from the database.

5. The method according to any one of claims 1 to 4, characterized in that: The target embedded page includes any of the following: Task creation embedded page, task issuance embedded page, task progress feedback embedded page, task working hour feedback embedded page, task tracking dashboard embedded page, and task statistics analysis dashboard embedded page.

6. A system integration method, characterized in that: Applied to a second computer device on which a business system is deployed, the method comprises: In response to a trigger operation for generating an entry for a target embedded page in a user interface, a service request is sent to a first computer device where a task management system is deployed; the service request includes a service identification code corresponding to the service system; receiving a target embedded page returned by the first computer device; the target embedded page is determined by the first computer device based on the registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task; The target embedding page is displayed on the user interface.

7. A system integration device, characterized in that: Applied to a first computer device deployed with a task management system, the apparatus comprises: A receiving module, configured to receive a business request sent by a second computer device on which a business system is deployed; the business request is used to request output of a target embedded page associated with a business requirement; the business request includes a business identification code corresponding to the business system; An acquisition module, configured to acquire registration information associated with the business identification code in response to the business request; the registration information includes front-end framework information corresponding to the business system and identification information of the target embedded page; A generating module, used for generating the target embedded page matching the front-end framework information based on the identification information of the target embedded page; The sending module is used to send the target embedded page to the second computer device; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task.

8. A system integration device, characterized in that: Applied to a second computer device deployed with a business system, the device comprises: A sending module, configured to send a service request to a first computer device where a task management system is deployed in response to a trigger operation for generating an entry for a target embedded page in a user interface; the service request includes a service identification code corresponding to the service system; a receiving module, configured to receive a target embedded page returned by the first computer device, wherein the target embedded page is determined by the first computer device based on the registration information associated with the service identification code included in the received service request; the target embedded page is a function embedded page created for various functions of the task, and is used to implement the various functions of the task; A display module is used to display the target embedded page on the user interface.

9. A computer device, characterized in that: The method comprises a memory execution and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method according to any one of claims 1 to 5 using the computer program, or implements the steps of the method according to claim 6.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 5, or implements the steps of the method according to claim 6.

11. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the computer program implements the steps of the method according to any one of claims 1 to 5, or implements the steps of the method according to claim 6.

Images