Enterprise portal cross-platform unified to-do implementation method, system, medium and device

Abstract

The invention provides an enterprise portal cross-platform unified pending implementation method, system, medium and device, and the method comprises the steps: constructing a unified business platform information management page based on enterprise portal personnel organization data, and registering each business system to a unified pending platform; a business platform unified personnel organization structure is constructed, and timing synchronization is carried out; assembling corresponding unified authentication information based on the business platform; judging whether each service platform is an unchangeable service platform or not, and performing unified docking of the service platforms; responding to the data query request by adopting a thread pool technology so as to call information of each service platform, and obtaining latest data information; and processing the to-be-handled process based on the latest data information, and skipping to a processing address of the to-be-handled information provided by the service platform in the interface, so that the service process is automatically processed in each service platform. According to the method and the device, the to-be-handled process of each business platform is managed through one platform management, and the traditional mode that the to-be-handled process of the system can be handled only by logging in each business platform is replaced.

Description

Technical Field

[0001] The present application belongs to the technical field of developing unified to-do items for various business platforms on web and mobile terminals, and relates to a method for implementing a unified to-do item, and in particular to a method, system, medium and device for implementing a unified to-do item across platforms for an enterprise portal. Background Art

[0002] As enterprises expand in size and businesses diversify, more and more business platforms are gradually connected to traditional enterprise portals, and business processes are scattered across different business platforms and systems, leading to a series of problems. For example, different business platforms have inconsistent views and operation interfaces, as well as different interaction methods. Different business platforms may have different authentication methods, requiring customers to log in multiple times and authenticate repeatedly before they are authorized to access the business system. This leads to problems such as the existing enterprise portals processing pending tasks, low efficiency, data silos, and poor user experience.

[0003] Therefore, how to solve the problem that after the enterprise portal is connected to multiple business platforms, different interfaces, interaction methods, and authentication methods appear, which requires users to log in or authenticate multiple times to access, and then causes problems such as low efficiency of enterprise portal cross-platform processing of to-do items, data islands, and poor user experience, is an urgent problem that needs to be solved. Summary of the invention

[0004] In view of the shortcomings of the prior art mentioned above, the purpose of the present application is to provide a method, system, medium and device for implementing a unified to-do list across platforms of an enterprise portal, so as to solve the problems in the existing cross-platform processing technology, that is, after the enterprise portal is connected to multiple business platforms, different interfaces, interaction methods, and authentication methods appear, so that users need to log in or authenticate multiple times to access, which in turn causes problems such as low efficiency of cross-platform processing of to-do lists by the enterprise portal, data islands, and poor user experience.

[0005] To achieve the above-mentioned purpose and other related purposes, in the first aspect, the present application provides a method for implementing a unified to-do task across platforms of an enterprise portal, comprising the following steps: obtaining personnel organization data of the enterprise portal; constructing a unified business platform information management page based on the personnel organization data of the enterprise portal and the business platform information, and registering each business system to the unified to-do platform; the business platform information includes: a combination of one or more of the platform domain name information, the business platform name, and the business platform available status information; constructing a unified personnel organization structure of the business platform, and performing regular synchronization of the personnel organization structure information; the personnel organization structure information includes: a combination of one or more of the personnel organization information, the personnel organization backup, and the personnel role initialization; assembling corresponding unified authentication information based on the business platform; judging whether each business platform is an unchangeable business platform based on the unified authentication information, and performing unified docking of the business platforms; using thread pool technology to respond to data query requests to call the information of each business platform to obtain the latest data information; processing the to-do process based on the latest data information, and jumping to the processing address of the to-do information provided by the business platform in the interface, so that the business process can be processed by each business platform.

[0006] In one implementation of the first aspect, registering each business system to a unified to-do platform includes: a unified organizational structure for personnel organizations, unified registration configuration information for business systems, a unified authentication method, a unified interface implementation, and database encapsulation for business systems that cannot provide an interface; the interface includes: a business platform process to-do interface and a business platform process completed interface.

[0007] In an implementation method of the first aspect, it also includes: using a unified Hypertext Transfer Protocol Security Protocol to integrate the development platforms of various development languages, exchanging information between the server and the client, and performing identity authentication; the key information of the identity authentication includes: one or more combinations of authentication method, interface name, and interface parameters.

[0008] In an implementation method of the first aspect, the corresponding unified authentication information assembled based on the business platform can adopt web-side unified authentication and mobile-side authentication; the web-side unified authentication method includes: a combination of one or more of form authentication, OAuth2 authentication, SAML2 authentication and API authentication; the mobile-side authentication can adopt a third-party SDK authentication method.

[0009] In an implementation of the first aspect, it is determined based on the unified authentication information whether the business platform can provide corresponding business path services according to the unified interface description and the unified authentication method; when it is determined that the business platform is not an unchangeable business platform, it is determined that docking and packaging can be performed; when it is determined that the business platform is an unchangeable business platform, it is determined that it is impossible to dock with the unified interface and the unified authentication method, and service packaging is performed to complete the unified docking of the business platform.

[0010] In one implementation of the first aspect, the service encapsulation of the business system database adopts the method of providing a to-do interface to the outside world, linking the data of each business system through a unified to-do system, and directly reading the to-do data of the corresponding process table in the database; the to-do data of each business process system is obtained through a unified to-do portal, so that the business data can be managed by each business system.

[0011] In one implementation of the first aspect, thread pool technology is used to respond to data query requests to call the information of each business platform. When the user logs in to the to-do page, each business platform is requested to obtain the to-do data, and the obtained data is summarized into a unified task list to provide a unified page display; wherein, when calling, the to-do items scattered in different systems are concentrated on the to-do page for display and management.

[0012] In the second aspect, the present application provides a cross-platform unified to-do implementation system for an enterprise portal, including: an acquisition module for acquiring the personnel organization data of the enterprise portal; a platform construction module for constructing a unified business platform information management page based on the personnel organization data of the enterprise portal and the business platform information, and registering each business system to the unified to-do platform; the business platform information includes: a combination of one or more of the platform domain name information, the business platform name, and the business platform available status information; an organizational structure construction module for constructing a unified personnel organizational structure for the business platform, and performing regular synchronization of the personnel organizational structure information; the personnel organizational structure information includes: a combination of one or more of the personnel organization information, the personnel organization backup, and the personnel role initialization; an assembly corresponding module for assembling corresponding unified authentication information based on the business platform; a judgment module for judging whether each business platform is an unchangeable business platform based on the unified authentication information, and performing unified docking of the business platform; a query calling module for using thread pool technology to respond to data query requests to call the information of each business platform to obtain the latest data information; a business processing module for processing the to-do process based on the latest data information, and jumping to the processing address of the to-do information provided by the business platform in the interface, so that the business process can be processed by each business platform.

[0013] In a third aspect, the present application provides a device for implementing a unified to-do list across platforms of an enterprise portal, comprising: a processor and a memory. The memory is used to store a computer program; the processor is connected to the memory and is used to execute the computer program stored in the memory, so that the device for implementing a unified to-do list across platforms of an enterprise portal executes the method for implementing a unified to-do list across platforms of an enterprise portal.

[0014] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by an electronic device, implements the above-mentioned method for implementing a unified to-do list across platforms of an enterprise portal.

[0015] As described above, the enterprise portal cross-platform unified to-do implementation method, system, medium and device of the present application have the following

[0016] Beneficial effects:

[0017] (1) This application provides a method for implementing a unified to-do list across multiple platforms for an enterprise portal. By encapsulating the business process management of different business platforms in a unified interface, business developers no longer need to repeatedly develop process management interfaces for multiple business platforms, effectively reducing development costs, improving the quality of development code, and improving the level of product code reuse. At the same time, for enterprise portal users, it effectively reduces the time it takes to learn and adapt to different business systems, allowing them to quickly get started and improve work efficiency.

[0018] (2) The cross-platform unified to-do implementation of the enterprise portal adopted in this application only needs to add new business process management configuration information and a unified interface for new business process management for subsequent access to new business process management. This will not affect the codes of other business management platforms, reduce code coupling, improve code security, and facilitate expansion. It adopts a unified personnel organizational structure, a unified web authentication method (such as OAuth2), and a mobile authentication method (third-party SDK, such as enterprise WeChat authentication, etc.), making the integration between different business platforms simpler. It mainly follows the same model, thereby enhancing the consistency and integrity of the platform data structure, reducing the inconvenience of authorization and authentication, supporting mobile devices and remote access, processing to-do items anytime and anywhere, and improving the efficiency of business processes. At the same time, it uniformly manages the to-do items of each business platform, uses thread pool (ThreasPool) pooling technology to manage a group of working threads, and concurrently executes multiple tasks to obtain to-do data of business platforms, which can save system resources and improve response speed.

[0019] (3) This application obtains the pending process data of the business platform in real time to improve the accuracy and timeliness of information; it can realize the self-management of service data of each business platform, reduce data synchronization between services, and improve data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 Shown is a schematic diagram of the method for implementing a cross-platform unified to-do list for an enterprise portal as described in this application, in which web / mobile users use the portal to handle various business management platforms.

[0021] Figure 2 Shown is a flow chart of an embodiment of the method for implementing a cross-platform unified to-do list for an enterprise portal described in this application.

[0022] Figure 3 Shown is a flow chart of a method for implementing a cross-platform unified to-do list on an enterprise portal in one embodiment of the present application, in which an enterprise portal solves a cross-platform unified to-do list solution.

[0023] Figure 4 Shown is a schematic diagram of the principle structure of an implementation system of a cross-platform unified to-do list for an enterprise portal described in this application in one embodiment.

[0024] Figure 5 Shown is a schematic diagram of the principle structure of an implementation device for a cross-platform unified to-do list for an enterprise portal described in this application in one embodiment.

[0025] Component number description

[0026] 11 Mobile

[0027] 12 Web page

[0028] 13 Enterprise Portal

[0029] 14 Scientific research management business platform

[0030] 15 History Management Business Platform

[0031] 1n Human management business platform

[0032] 41 Get Module

[0033] 42 Platform Building Blocks

[0034] 43 Organizational Structure Building Blocks

[0035] 44 Assemble the corresponding modules

[0036] 45 Judgment Module

[0037] 46 Query call module

[0038] 47 Business Processing Module

[0039] 51 Processor

[0040] 52 Memory

[0041] Steps S1 to S7 DETAILED DESCRIPTION

[0042] The following describes the embodiments of the present application through specific examples, and those skilled in the art can easily understand other advantages and effects of the present application from the contents disclosed in this specification. The present application can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present application. It should be noted that the following embodiments and features in the embodiments can be combined with each other without conflict.

[0043] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present application, and thus the drawings only show components related to the present application rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed at will, and the component layout may also be more complicated.

[0044] See also Figure 1 , showing a schematic diagram of the enterprise portal cross-platform unified to-do implementation method described in this application for web / mobile users to use the portal to handle various business management platforms.

[0045] The real-time example of this application provides two main user access methods: web-based unified authentication and mobile authentication. Figure 1 In the electronic device shown, component 11 represents access from a mobile terminal (such as a mobile phone), component 12 represents access from a network terminal (such as a computer), and component 13 serves as a unified entry point for the enterprise portal, allowing users to access different business management platforms based on their permissions. This requires the portal to have efficient access management (Access Control) and a unified user authentication mechanism (User Authentication Mechanism, UAM). Both of these points require a unified corporate personnel organizational structure and a unified authentication method. Logging in to the enterprise portal handles cross-platform business process management systems, allowing customers to experience access without perception and simplifying the operating process.

[0046] The mobile terminal in this application may include a mobile phone 11, a computer (or tablet) 12, etc. with a wireless charging function. The embodiments of this application do not impose any restrictions on the specific types of electronic devices. It is only necessary to make the embodiments accessible to the Internet and access the network. For the embodiments, multi-platform support needs to be considered, and responsive design or special applications are required to adapt to different devices to ensure that users can get a consistent experience no matter which device they access. The unified to-do portal of the enterprise No. 13 and other business systems interact in a unified manner, which requires relying on a unified interface service. For systems No. 15 that have no source code, cannot be operated and maintained, or cannot provide interfaces, it is necessary to encapsulate unified interface interactions according to the corresponding system data sources, so as to achieve unified management and compatibility of various business systems. Formulating a unified interface service, taking into account the scalability of the system, is also conducive to allowing more business management platforms to be involved in the future, with simple access methods and operations.

[0047] The following will describe in detail the method for implementing a cross-platform unified to-do list for an enterprise portal provided in the embodiment of the present application in conjunction with the drawings in the embodiment of the present application.

[0048] See also Figure 2 and Figure 3 , respectively showing a flow chart of a method for implementing a unified to-do list across platforms in an enterprise portal described in this application in one embodiment and a flow chart of a method for implementing a unified to-do list across platforms in an enterprise portal described in this application in one embodiment. Figure 2 and Figure 3 As shown, this embodiment provides a method for implementing a cross-platform unified to-do list for an enterprise portal.

[0049] The enterprise portal cross-platform unified to-do implementation method specifically includes the following steps:

[0050] S1, obtain the personnel organization data of the enterprise portal.

[0051] In this embodiment, according to user needs, the core purpose of establishing the enterprise portal personnel organization data is clearly defined, such as improving management efficiency, supporting business decisions, promoting teamwork, etc.; then determine the scope of data coverage, including which departments, positions, and personnel need to be included in the system, and what specific information needs to be collected (such as name, position, department, contact information, date of employment, job responsibilities, etc.). Next, by identifying existing data sources, such as HR systems, OA systems, financial systems, etc., the data quality, integrity, and accessibility of each data source can be evaluated; it is also possible to select appropriate collection methods based on the characteristics of the data source, such as API interface calls, direct database connections, file imports (such as CSV, Excel), or manual entry, etc.

[0052] It should be noted that when selecting or developing data collection tools, it is necessary to ensure efficient and stable data collection, consider encrypted data transmission, and protect data privacy.

[0053] S2, building a unified business platform information management page based on the enterprise portal personnel organization data and business platform information, and registering each business system to the unified to-do platform.

[0054] In this embodiment, the service platform information includes: service platform process domain name information, service platform name, service platform availability status information and other contents.

[0055] Build a unified business platform information management page, where each business platform registers domain name information, status information, etc. Registering each business system to the unified to-do platform includes: unified organizational structure of personnel organization, unified registration configuration information of business systems, unified authentication method, unified interface implementation, and database encapsulation for business systems that cannot provide interfaces.

[0056] Specifically, for the business platform information, an editing webpage independent of the business platform is constructed. The platform domain information, business platform name, and business platform availability status information of the custom business platform are customized. The backend code polls and calls the standard interface of each business system according to the configuration information of the page to obtain the to-do information. The interface includes: business platform process to-do interface and business platform process completed interface.

[0057] It should be noted that business platform information management enables unified configuration of various business platforms. The unified to-do platform can call the interfaces of various business platforms through configuration information, and there is no need to change the code when adding or deleting business systems.

[0058] S3, construct a unified personnel organization structure of the business platform, and synchronize the personnel organization structure information regularly. The personnel organization structure information includes: personnel organization information, personnel organization backup, personnel role initialization, etc.

[0059] In this embodiment, a unified personnel organization structure is constructed for each business platform, and functions such as regular synchronization of personnel organization information, personnel organization backup, and personnel role initialization are provided to facilitate the universality of personnel organization information in subsequent cross-platform operations.

[0060] It should be noted that the use of a unified management personnel organizational structure can build a comprehensive and efficient account management system to ensure that the relationship between team members and their accounts in the business management system is accurately matched and effectively managed, and to solve problems such as cross-platform authentication; it is also convenient to determine the unified authentication protocol and parameters, so as to generate customized unified authentication call code for use in different business platforms. At the same time, the use of RBAC (Role-Based Access Control) security policies is used to limit resource access, reduce the risk of data leakage and abuse, facilitate tracking of user activities and permission changes, and improve security.

[0061] S4, assemble the corresponding unified authentication information based on the business platform.

[0062] In this application, the unified authentication information corresponding to the business platform assembly can adopt the web-side unified authentication and mobile-side authentication. Among them, the web-side unified authentication methods include: form authentication (Form-Based Authentication), OAuth2 (Open Authorization 2.0, open authorization) authentication, OpenID Connect (OpenID Connect), SAML2 (Security Assertion Markup Language 2.0, Security Assertion Markup Language) authentication and API (American Petroleum Institute) authentication; the mobile-side authentication can adopt the third-party SDK authentication method.

[0063] In this embodiment, corresponding unified authentication information is assembled for each web-end or mobile-end business platform.

[0064] First, you need to build an authentication environment. According to the selected authentication scheme, you need to build an authentication server or choose the authentication service of a cloud service provider, and configure the necessary hardware and software resources. Then, you need to set the authentication parameters. In the authentication system, you need to configure parameters such as user management, authority allocation, and authentication policies to ensure that the authentication process meets business requirements and security standards.

[0065] Specifically, there are many ways of unified authentication on the web, such as form authentication, the traditional username and password login form, and the server verifies after the user submits; the industry standard protocol OAuth2.0 is used to authorize third-party applications to access user information stored on other services; the XML-based standard SAML2 is used to exchange user authentication and authorization data between identity providers and business platforms; the method of transmitting URL security between the two parties (JWT, JSON Web Tokens) is often used for API authentication, etc. The authentication method used in this application is mainly OAuth2.0, which realizes the authentication method between the enterprise portal and various business platform systems.

[0066] In addition, the request protocol in this application uses the HTTPS (Hypertext Transfer Protocol Secure) protocol. It is a unified secure communication network protocol that can integrate the development platforms of various development languages. You only need to pay attention to the authentication method, interface name, interface parameters and other contents exposed to the outside.

[0067] That is to say, a unified Hypertext Transfer Protocol Security Protocol is used here to integrate the development platforms of various development languages, exchange information between the server and the client, and perform identity authentication; wherein the key information of the identity authentication includes: authentication method, interface name, interface parameters and other information.

[0068] S5, judging whether each business platform is an unchangeable business platform based on the unified authentication information, and performing unified connection of the business platforms.

[0069] In this embodiment, for the management of all business platforms, it is necessary to determine whether the business platform can provide corresponding business path services according to the unified interface description and unified authentication method. If there are some irresistible factors (such as: historical services are no longer maintained, service information is accessed from a third party, there is no specific code content, and it cannot be modified, etc.), which make the business platform unable to connect to the unified interface and unified authentication method, service encapsulation is performed to indirectly achieve unified connection of the business platform.

[0070] Specifically, based on the unified authentication information, it is determined whether the business platform can provide corresponding business path services according to the unified interface description and the unified authentication method.

[0071] The judgment criteria are:

[0072] When it is determined that the business platform is not an immutable business platform, it is considered that docking and packaging can be performed;

[0073] When it is determined that the business platform is an unchangeable business platform, it is determined that it is impossible to connect to the unified interface and unified authentication method, and service packaging is performed to complete the unified connection of the business platform.

[0074] The service encapsulation of the business system database adopts the method of providing a to-do interface to the outside world, linking the data of each business system through a unified to-do system, and directly reading the to-do data of the corresponding process table in the database; the to-do data of each business process system is obtained through a unified to-do portal, so that the business data can be managed by each business system.

[0075] S6, using thread pool technology to respond to data query requests to call each of the business platform information to obtain the latest data information.

[0076] In this embodiment, thread pool technology is used to respond to data query requests to call the information of each business platform. When the user logs in to the to-do page, each business platform is requested to obtain the to-do data, and the obtained data is summarized into a unified task list to provide a unified page display. Among them, when calling, the to-do items scattered in different systems are concentrated on the to-do page for display and management.

[0077] When querying the business process management data of each business platform, thread pool technology is used in the enterprise portal to concurrently acquire data to ensure the timeliness of the display of to-do information after connecting to multiple systems, and to handle exceptions properly to prevent a system from crashing and causing access exceptions to the entire portal to-do list.

[0078] Specifically, the method of using business system registration and thread pool polling to access the to-do information of each system replaces the message push method. The main reason is that the thread pool can respond to data query requests in a timely manner and obtain the latest data, while message push may have delays; the data accuracy is higher, and data is obtained directly from the data source, reducing the delay of messages in the transmission process; data loss is reduced, and the method of directly obtaining data through the thread pool calling the interface may cause message loss due to network problems or system failures. The fault tolerance is higher. If a query task fails, the thread pool can automatically retry or reallocate the task to ensure the continuity of data acquisition; the system responsiveness is improved. Under high load conditions, the thread pool can maintain the responsiveness of the system, avoid message queue squeezing, and improve user satisfaction with the enterprise portal.

[0079] It should be noted that the use of real-time query uses thread pool (ThreadPool) pooling technology to concurrently access each business process system to obtain real-time data information; the consistency of data is improved, because the unified to-do platform is only responsible for obtaining the to-do data of each business process system, and does not update and synchronize the data, so that the service data can be managed (modified, etc.) by itself, reducing data synchronization, thereby achieving data consistency. At the same time, this application provides a technical solution to reduce data loss, using real-time query instead of obtaining data by sending messages to notify, reducing the possibility of data loss and repeated processing in each business process system due to network and service anomalies.

[0080] S7, based on the latest data information, processes the pending process, jumps to the processing address of the pending information provided by the business platform in the interface, so that the business process can be processed by each business platform.

[0081] In this embodiment, the to-do process is processed and the processing address of the to-do information provided by the business platform in the interface is jumped, so that the business process is processed by each business platform itself, and the enterprise unified to-do does not store any to-do information.

[0082] Specifically, it is mainly to avoid the mutual push of platform data when the unified to-do is realized by the message push method and when the data is modified. In the process of mutual push of multiple data sources, the consistency of data in each business management system may be affected; the strategy of using one data source, "whoever manages the data" (Data Management by the Data Owner), emphasizes that the ownership and responsibility of the data belongs to the data owner. Improve data security, the data owner is responsible for implementing security measures to protect the data from unauthorized access or leakage; reduce data management costs, the data owner directly manages the data, which can reduce intermediate links and reduce management costs; strong adaptability, the data owner can quickly adapt to changes in the business environment, update the data management strategy in a timely manner, and reduce dependence on external data service providers.

[0083] Therefore, it can be seen that the enterprise portal cross-platform unified to-do implementation method provided by this application provides unified enterprise portal personnel organization data, providing a calling premise for the unified portal to call various business systems; the basic information of each business system configured in the unified to-do platform realizes the function of registering each business system to the unified to-do platform; each business system interface has a unified authentication method; each business system provides a unified interface to ensure the consistency of information such as method name, input parameters, and output parameters. When calling, the to-do items scattered in different systems can be concentrated on the to-do page for display and management, improving work efficiency and reducing task omissions; when the user enters the to-do page, the to-do task display module requests the to-do item interface from each business system in real time, and then displays it on the unified to-do page; for services that have no source code, cannot be maintained or cannot be modified, a database encapsulation service function is added, and an interface that meets the requirements of the unified to-do platform is provided to realize the function of a unified to-do.

[0084] The present application provides a method for implementing a cross-platform unified to-do list for an enterprise portal, which realizes unified management of business process management (BPM) of multiple business platforms in the enterprise portal through one platform, so as to improve the internal management efficiency and user experience of the enterprise. The scheme mainly includes: building a page for managing relevant information of each business platform in the unified to-do platform (setting the docking business platform information content, such as: business platform domain name, name, available status, etc.); each business system implements the to-do interface required by the unified to-do platform, including interface name, return parameters, to-do page address, etc., so that the unified to-do platform can request the to-do process data of each business system in real time, and display the to-do process data of each business system on the page of the unified to-do platform; based on a unified personnel organizational structure, the interface uses a unified OAuth2 authentication and a third-party SDK (such as enterprise WeChat, etc.) authentication method for the Web and mobile terminals respectively; using the programming idea of ​​unified registration and unified release, regardless of the specific implementation details, and adapting to business platforms built in various languages ​​(such as: C#, JAVA, Python, etc.); for program platforms that cannot be maintained or modified without source code, add encapsulation services, and encapsulate different data sources to make them interface-based, thereby realizing the transformation of the unified to-do.

[0085] The protection scope of the method for implementing a unified to-do list across platforms for an enterprise portal described in the embodiment of this application is not limited to the execution order of the steps listed in this embodiment. All solutions implemented by adding, reducing or replacing steps in the prior art based on the principles of this application are included in the protection scope of this application.

[0086] This embodiment further provides a computer-readable storage medium on which a computer program is stored. When the program is executed by a processor, the following is achieved: Figure 1 The enterprise portal implements a cross-platform unified to-do method.

[0087] At any possible level of technical detail combination, the present application may be a system, method and / or computer program product. The computer program product may include a computer-readable storage medium carrying computer-readable program instructions for causing a processor to implement various aspects of the present application.

[0088] Computer readable storage medium can be a tangible device that can hold and store instructions used by an instruction execution device. Computer readable storage medium can be, for example, (but not limited to) an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. More specific examples (non-exhaustive list) of computer readable storage medium include: 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 static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device, for example, a punch card or a convex structure in a groove on which instructions are stored, and any suitable combination thereof. The computer readable storage medium used here is not interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated by a waveguide or other transmission medium (for example, a light pulse by an optical fiber cable), or an electrical signal transmitted by a wire.

[0089] The computer-readable program described herein can be downloaded from a computer-readable storage medium to each computing / processing device, or downloaded to an external computer or external storage device through a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network can include copper transmission cables, optical fiber transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives a computer-readable program instruction from the network, and forwards the computer-readable program instruction for storage in the computer-readable storage medium in each computing / processing device. The computer program instruction for performing the operation of the present application can be an assembly instruction, an instruction set architecture (ISA) instruction, a machine instruction, a machine-related instruction, a microcode, a firmware instruction, a state setting data, an integrated circuit configuration data, or a source code or object code written in any combination of one or more programming languages, wherein the programming language includes an object-oriented programming language, such as Smalltalk, C++, etc., and a procedural programming language, such as "C" language or similar programming language. Computer readable program instructions can be executed completely on a user's computer, partially on a user's computer, as an independent software package, partially on a user's computer, partially on a computer, or completely on a computer or server. In the case of a computer, the computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (e.g., using an Internet service provider to connect through the Internet). In some embodiments, by using the state information of computer readable program instructions to personalize electronic circuits, such as programmable logic circuits, field programmable gate arrays (FPGAs) or programmable logic arrays (PLAs), the electronic circuits can execute computer readable program instructions, thereby realizing various aspects of the present application.

[0090] The embodiment of the present application also provides a cross-platform unified to-do implementation system for an enterprise portal, which can implement the cross-platform unified to-do implementation method for an enterprise portal described in the present application. However, the implementation device of the cross-platform unified to-do implementation method for an enterprise portal described in the present application includes but is not limited to the structure of the cross-platform unified to-do implementation system for an enterprise portal listed in the present embodiment. All structural deformations and replacements of the prior art made according to the principles of the present application are included in the protection scope of the present application.

[0091] The following will describe in detail the cross-platform unified to-do implementation system for enterprise portals provided by this embodiment with reference to the diagrams.

[0092] This embodiment provides a cross-platform unified to-do implementation system for an enterprise portal, including:

[0093] See also Figure 4 , which is a schematic diagram of the principle structure of the cross-platform unified to-do implementation system of the enterprise portal described in this application in one embodiment. Figure 4 As shown, the enterprise portal cross-platform unified to-do implementation system includes: an acquisition module 41, a platform construction module 42, an organizational structure construction module 43, an assembly corresponding module 44, a judgment module 45, a query calling module 46 and a business processing module 47.

[0094] The acquisition module 41 is used to acquire the personnel organization data of the enterprise portal.

[0095] In this embodiment, according to user needs, the core purpose of establishing the enterprise portal personnel organization data is clearly defined, such as improving management efficiency, supporting business decisions, promoting teamwork, etc.; then determine the scope of data coverage, including which departments, positions, and personnel need to be included in the system, and what specific information needs to be collected (such as name, position, department, contact information, date of employment, job responsibilities, etc.). Next, by identifying existing data sources, such as HR systems, OA systems, financial systems, etc., the data quality, integrity, and accessibility of each data source can be evaluated; it is also possible to select appropriate collection methods based on the characteristics of the data source, such as API interface calls, direct database connections, file imports (such as CSV, Excel), or manual entry, etc.

[0096] The platform construction module 42 is connected to the acquisition module 41 and is used to build a unified business platform information management page based on the enterprise portal personnel organization data and business platform information, and register each business system to the unified to-do platform. The business platform information includes: platform domain name information, business platform name, business platform availability status information, etc.

[0097] In this embodiment, the service platform information includes: service platform process domain name information, service platform name, service platform availability status information and other contents.

[0098] Build a unified business platform information management page, where each business platform registers domain name information, status information, etc. Registering each business system to the unified to-do platform includes: unified organizational structure of personnel organization, unified registration configuration information of business systems, unified authentication method, unified interface implementation, and database encapsulation for business systems that cannot provide interfaces.

[0099] The organizational structure construction module 43 is used to construct a unified personnel organizational structure of the business platform and synchronize the personnel organizational structure information at regular intervals. The personnel organizational structure information includes: personnel organization information, personnel organization backup, personnel role initialization, etc.

[0100] In this embodiment, a unified personnel organization structure is constructed for each business platform, and functions such as regular synchronization of personnel organization information, personnel organization backup, and personnel role initialization are provided to facilitate the universality of personnel organization information in subsequent cross-platform operations.

[0101] The assembling corresponding module 44 is used to assemble corresponding unified authentication information based on the business platform.

[0102] In this application, the unified authentication information corresponding to the business platform assembly can adopt the web-side unified authentication and mobile-side authentication. Among them, the web-side unified authentication methods include: form authentication, OAuth2 authentication, open ID connection, SAML2 authentication and API authentication. The mobile-side authentication can adopt the third-party SDK authentication method.

[0103] In this embodiment, corresponding unified authentication information is assembled for each web-end or mobile-end business platform.

[0104] First, you need to build an authentication environment. According to the selected authentication scheme, you need to build an authentication server or choose the authentication service of a cloud service provider, and configure the necessary hardware and software resources. Then, you need to set the authentication parameters. In the authentication system, you need to configure parameters such as user management, authority allocation, and authentication policies to ensure that the authentication process meets business requirements and security standards.

[0105] The judgment module 45 is used to judge whether each business platform is an unchangeable business platform based on the unified authentication information, and to perform unified connection of the business platforms.

[0106] In this embodiment, for the management of all business platforms, it is necessary to determine whether the business platform can provide corresponding business path services according to the unified interface description and unified authentication method. If there are some irresistible factors (such as: historical services are no longer maintained, service information is accessed from a third party, there is no specific code content, and it cannot be modified, etc.), which make the business platform unable to connect to the unified interface and unified authentication method, service encapsulation is performed to indirectly achieve unified connection of the business platform.

[0107] Specifically, based on the unified authentication information, it is determined whether the business platform can provide corresponding business path services according to the unified interface description and the unified authentication method.

[0108] The judgment criteria are:

[0109] When it is determined that the business platform is not an immutable business platform, it is considered that docking and packaging can be performed;

[0110] When it is determined that the business platform is an unchangeable business platform, it is determined that it is impossible to connect to the unified interface and unified authentication method, and service packaging is performed to complete the unified connection of the business platform.

[0111] The service encapsulation of the business system database adopts the method of providing a to-do interface to the outside world, linking the data of each business system through a unified to-do system, and directly reading the to-do data of the corresponding process table in the database; the to-do data of each business process system is obtained through a unified to-do portal, so that the business data can be managed by each business system.

[0112] The query calling module 46 is used to respond to data query requests by using thread pool technology to call the information of each business platform to obtain the latest data information.

[0113] In this embodiment, thread pool technology is used to respond to data query requests to call the information of each business platform. When the user logs in to the to-do page, each business platform is requested to obtain the to-do data, and the obtained data is summarized into a unified task list to provide a unified page display. Among them, when calling, the to-do items scattered in different systems are concentrated on the to-do page for display and management.

[0114] When querying the business process management data of each business platform, thread pool technology is used in the enterprise portal to concurrently acquire data to ensure the timeliness of the display of to-do information after connecting to multiple systems, and to handle exceptions properly to prevent a system from crashing and causing access exceptions to the entire portal to-do list.

[0115] The business processing module 47 is used to process the pending process based on the latest data information, jump to the processing address of the pending information provided by the business platform in the interface, so that the business process can be processed by each business platform.

[0116] In this embodiment, the to-do process is processed and the processing address of the to-do information provided by the business platform in the interface is jumped, so that the business process is processed by each business platform itself, and the enterprise unified to-do does not store any to-do information.

[0117] Specifically, it is mainly to avoid the mutual push of platform data when the unified to-do list is realized by message push method and when the data is modified. In the process of mutual push of multiple data sources, the consistency of data in each business management system may be affected; use the strategy of one data source, "whoever has the data manages it", emphasizing that the ownership and responsibility of the data belongs to the data owner. Improve data security, the data owner is responsible for implementing security measures to protect the data from unauthorized access or leakage; reduce data management costs, the data owner directly manages the data, which can reduce the intermediate links and reduce management costs; strong adaptability, the data owner can quickly adapt to changes in the business environment, update the data management strategy in a timely manner, and reduce dependence on external data service providers.

[0118] The cross-platform unified to-do implementation model of the enterprise portal builds a cross-platform unified to-do implementation system for the enterprise portal, which realizes the unified management of business processes of multiple business platforms in the enterprise portal through one platform, so as to improve the internal management efficiency and user experience of the enterprise.

[0119] It should be noted that it should be understood that the division of the various modules of the above system is only a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements; they can also be all implemented in the form of hardware; some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. For example, the x module can be a separately established processing element, or it can be integrated in a certain chip of the above system for implementation. In addition, it can also be stored in the memory of the above system in the form of program code, and called and executed by a certain processing element of the above system. The implementation of other modules is similar. In addition, these modules can be fully or partially integrated together, or they can be implemented independently. The processing element described here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0120] The above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASIC), or one or more digital signal processors (DSP), or one or more field programmable gate arrays (FPGA). For another example, when a module is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0121] See also Figure 5 , which is a schematic diagram of the principle structure of the cross-platform unified to-do implementation device for the enterprise portal described in this application in one embodiment. Figure 5As shown, this embodiment provides a device for implementing a cross-platform unified to-do list for an enterprise portal, and the device for implementing a cross-platform unified to-do list for an enterprise portal includes: a processor 51 and a memory 52; the memory 52 is used to store computer programs; the processor 51 is connected to the memory 52, and is used to execute the computer programs stored in the memory 52, so that the device for implementing a cross-platform unified to-do list for an enterprise portal executes each step of the method for implementing a cross-platform unified to-do list for an enterprise portal as described above.

[0122] Preferably, the memory may include a random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0123] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0124] In summary, the method, system, medium and device for implementing cross-platform unified to-do items on enterprise portals provided by this application have the following beneficial effects:

[0125] The cross-platform unified to-do implementation method for enterprise portals provided in the present application can encapsulate the business process management of different business platforms into a unified interface, so that business developers no longer need to repeatedly develop process management interfaces for multiple business platforms, effectively reducing development costs, improving the quality of development code, and improving the level of product code reuse. At the same time, for enterprise portal users, it can effectively reduce the time to learn and apply different business systems, quickly get started, and improve work efficiency; at the same time, it can enhance the consistency and integrity of the platform data structure, reduce the inconvenience of authorization and authentication, support mobile devices and remote access, process to-do items anytime and anywhere, and improve the efficiency of business processes and responses; and obtain business platform to-do process data in real time to improve the accuracy and timeliness of information; it can enable each business platform service data to manage its own data, reduce data synchronization between services, and improve data security.

[0126] The above embodiments are merely illustrative of the principles and effects of the present application and are not intended to limit the present application. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present application. Therefore, all equivalent modifications or changes made by a person of ordinary skill in the art without departing from the spirit and technical ideas disclosed in the present application shall still be covered by the claims of the present application.

Claims

1. A method for implementing a cross-platform unified to-do list for an enterprise portal, characterized in that: The following steps are involved: Obtain enterprise portal personnel organization data; Building a unified business platform information management page based on the enterprise portal personnel organization data and business platform information, and registering each business system to the unified to-do platform; The service platform information includes: a combination of one or more of platform domain name information, service platform name, and service platform availability status information; Construct a unified personnel organization structure for the business platform and synchronize the personnel organization structure information regularly; the personnel organization structure information includes: one or more combinations of personnel organization information, personnel organization backup, and personnel role initialization; Assemble the corresponding unified authentication information based on the business platform; Based on the unified authentication information, determine whether each business platform is an unchangeable business platform, and perform unified docking of the business platforms; Using thread pool technology to respond to data query requests to call the information of each business platform and obtain the latest data information; Process pending processes based on the latest data information, jump to the processing address of pending information provided by the business platform in the interface, so that the business process can be processed by each business platform.

2. The method for implementing a cross-platform unified to-do list for an enterprise portal according to claim 1, characterized in that: Registering each business system to the unified to-do platform includes: unified organizational structure of personnel organization, unified registration configuration information of business systems, unified authentication method, unified interface implementation, and database encapsulation for business systems that cannot provide interfaces; The interfaces include: a business platform process to-be-done interface and a business platform process completed interface.

3. The method for implementing a cross-platform unified to-do list for an enterprise portal according to claim 1, characterized in that: It also includes: using a unified hypertext transfer security protocol to integrate the development platforms of various development languages, exchanging information between the server and the client, and performing identity authentication; The key information of the identity authentication includes: one or more combinations of authentication method, interface name, and interface parameters.

4. The method for implementing cross-platform unified to-do items on enterprise portal according to claim 1, characterized in that: The corresponding unified authentication information assembled based on the business platform can be used for unified authentication on the web page and mobile terminal; The web page unified authentication method includes: one or more combinations of form authentication, OAuth2 authentication, SAML2 authentication and API authentication; The mobile terminal authentication may adopt a third-party SDK authentication method.

5. The method for implementing cross-platform unified to-do items on enterprise portal according to claim 1, characterized in that: Based on the unified authentication information, it is determined whether the business platform can provide corresponding business route services according to the unified interface description and unified authentication method; When it is determined that the business platform is not an immutable business platform, it is considered that docking and packaging can be performed; When it is determined that the business platform is an unchangeable business platform, it is determined that it is impossible to connect to the unified interface and unified authentication method, and service packaging is performed to complete the unified connection of the business platform.

6. The method for implementing cross-platform unified to-do items on enterprise portal according to claim 5, characterized in that: The service encapsulation of the business system database adopts the method of providing a to-do interface to the outside world, linking the data of each business system through a unified to-do system, and directly reading the to-do data of the corresponding process table in the database; The to-do data of each business process system can be obtained through the unified to-do portal, so that the business data can be managed by each business system.

7. The method for implementing cross-platform unified to-do items on enterprise portal according to claim 1, characterized in that: Thread pool technology is used to respond to data query requests to call the information of each business platform. When the user logs in to the to-do page, each business platform is requested to obtain the to-do data, and the obtained data is summarized into a unified task list to provide a unified page display; wherein, when calling, the to-do items scattered in different systems are concentrated on the to-do page for display and management.

8. A cross-platform unified to-do system for enterprise portals, characterized in that: include: The acquisition module is used to obtain the personnel organization data of the enterprise portal; A platform construction module, used to build a unified business platform information management page based on the enterprise portal personnel organization data and business platform information, and register each business system to the unified to-do platform; The service platform information includes: a combination of one or more of platform domain name information, service platform name, and service platform availability status information; An organizational structure construction module is used to construct a unified personnel organizational structure of the business platform and synchronize the personnel organizational structure information regularly; the personnel organizational structure information includes: a combination of one or more of personnel organization information, personnel organization backup, and personnel role initialization; Assemble corresponding modules to assemble corresponding unified authentication information based on the business platform; A judgment module, used to judge whether each business platform is an unchangeable business platform based on the unified authentication information, and to perform unified docking of the business platforms; A query calling module, used to respond to data query requests by using thread pool technology to call the information of each business platform and obtain the latest data information; The business processing module is used to process pending processes based on the latest data information, jump to the processing address of the pending information provided by the business platform in the interface, so that the business process can be processed by each business platform.

9. A device for realizing cross-platform unified to-do list for enterprise portal, characterized in that: include: Processor and memory; The memory is used to store computer programs; The processor is connected to the memory and is used to execute the computer program stored in the memory, so that the enterprise portal cross-platform unified to-do implementation device executes the enterprise portal cross-platform unified to-do implementation method described in any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, it implements the method for implementing a cross-platform unified to-do list for an enterprise portal as described in any one of claims 1 to 7.

Images