Event-driven heterogeneous system to-do message multi-channel fusion method and device

Abstract

The invention relates to the technical field of informatization and system integration, and provides a heterogeneous system to-be-handled message multichannel fusion method and device based on event driving, and the method comprises the steps: monitoring a to-be-handled task state change event through a universal adapter deployed in a heterogeneous business system, and converting the captured event into a preset standard message model; according to an event type and a task type in the standard message model, dynamically assembling differentiated message loads which are uniform in structure and are matched with different push channels; pushing the differentiated message load to a unified message platform through a security authentication interface for multi-channel touch, and establishing bidirectional state synchronization containing precise service semantics between the heterogeneous service system and the unified message platform based on a standard message model; a cross-system state closed loop is realized through bidirectional state synchronization, and non-intrusive access expansion of a new service system is realized through a universal adapter and a standard message model. According to the invention, the unification and the efficiency improvement of cross-system user experience can be realized.

Description

Technical Field

[0001] This invention relates to the field of information technology and system integration, and in particular to a method and device for multi-channel fusion of pending messages from heterogeneous systems based on event-driven principles. Background Technology

[0002] During the digital transformation of large enterprises or organizations, multiple business systems are typically introduced or independently developed to meet the specialized management needs of different business departments. These systems include supplier management systems, enterprise resource planning (ERP) systems, office automation (OA) systems, customer relationship management (CRM) systems, and contract management systems. Each of these systems carries its own core business processes, operates independently, and manages its internal workflows and to-do items. Employees, especially managers and key business personnel, frequently need to log into multiple systems in their daily work to view and process to-do tasks scattered across various locations, such as approval processes, pending notifications, and transaction processing.

[0003] The main approaches to solving the problem of multi-system task aggregation in existing technologies and their significant drawbacks are as follows:

[0004] 1. Point-to-point hard-coded integration: This was a common early integration model. When it was necessary to push tasks from system A to portal B, the development team would directly write code in system A's code to call portal B's specific API. This method has extremely high coupling. Any change, upgrade, or migration of any system's interface could cause the integration point to fail, requiring a large investment of development and testing resources for synchronous modification and maintenance, resulting in huge costs and making system upgrades difficult. As the number of integrated systems increases, the complexity of this mesh structure grows exponentially, eventually becoming difficult to maintain.

[0005] 2. Simple Integration Based on Intermediate Databases or Message Queues: To reduce direct coupling, some solutions use shared database tables or general message queues as intermediaries. System A writes to-do information into an intermediate table or queue, which is then periodically polled or monitored by portal B. While this approach decouples the system to some extent, it only achieves one-way, asynchronous information push and lacks a proactive mechanism for sensing and responding to task processing results. For example, when a user processes a to-do item from a supplier's system on the portal side, the status change cannot be automatically and reliably synchronized back to the original supplier's system, resulting in the task remaining in the "to-do" status in the original system, creating a long-term "zombie to-do." This not only causes data inconsistency but also interferes with the original system's statistical analysis and process monitoring.

[0006] 3. Simple Link Aggregation in a Unified Portal: This approach aggregates entry links from various systems on a unified portal using Single Sign-On (SSO) technology and displays the number of unread tasks for each system on the portal's homepage. However, this method doesn't truly aggregate task content and context. Users still need to click links to return to the original system interface to perform actions. Essentially, it's "login aggregation" rather than "task aggregation," resulting in a fragmented user experience, low operational efficiency, and failing to address the core pain point of users frequently switching between different system interfaces.

[0007] 4. Limited and unreliable message delivery channels: Existing integration solutions typically select only one primary channel for notifications, such as sending to-do reminders solely via email or internal system messaging. Emails may be overlooked in the inbox, while internal messages require users to actively log in to view them. This limited reach fails to guarantee that critical and urgent approval tasks will reach the attention of relevant personnel in a timely and effective manner, compromising message timeliness and coverage, and leading to business process delays.

[0008] Chinese patent CN121187820A discloses a centralized task processing system and method based on message-driven construction. However, this method cannot meet the requirements of practical applications in terms of ensuring strong consistency of real-time status across systems, conveying fine business semantics, and achieving low-intrusion integration.

[0009] Therefore, how to provide a to-do message fusion solution that can achieve loose coupling, standardization, support bidirectional state synchronization, and have reliable multi-channel reach capabilities to break down system barriers, improve collaboration efficiency, ensure the consistency of business data, and optimize the end-user's operating experience has become an urgent technical problem to be solved. Summary of the Invention

[0010] In view of this, in order to overcome the shortcomings of the prior art, the present invention aims to provide a method and device for multi-channel fusion of pending messages in heterogeneous systems based on event-driven principles.

[0011] According to a first aspect of the present invention, a method for multi-channel fusion of pending messages in heterogeneous systems based on event-driven mechanisms is provided, the method comprising:

[0012] Step S1: Listen for changes in the status of pending tasks by deploying a general adapter in a heterogeneous business system, and convert the captured events into a preset standard message model;

[0013] Step S2: Based on the event type and task type in the standard message model, dynamically assemble differentiated message payloads with a unified structure that are adapted to different push channels;

[0014] Step S3: Push the differentiated message payload to the unified messaging platform through the security authentication interface for multi-channel delivery, and establish bidirectional state synchronization with precise business semantics between the heterogeneous business system and the unified messaging platform based on the standard message model;

[0015] Step S4: Achieve cross-system state closed loop through bidirectional state synchronization, and achieve non-intrusive access extension of new business systems through universal adapters and standard message models.

[0016] Optionally, in the event-driven heterogeneous system to-do message multi-channel fusion method of the present invention, in step S1, the to-do task status change event is monitored in the following manner: using the to-do function extension interface provided by the heterogeneous business system, the event listener is registered by the general adapter, and the native system event is captured by the registered time listener. The native system event includes to-do task creation, task completion, task deletion and task attribute update.

[0017] Optionally, in the event-driven heterogeneous system to-do message multi-channel fusion method of the present invention, in step S2, differentiated message payloads are dynamically assembled in the following manner: parsing the standard message model to determine the nature of the task; for new events of notification tasks, assembling a lightweight payload for real-time message push; for new events of processing tasks, assembling in parallel a first payload for creating structured to-do entries in a unified portal and a second payload for generating rich media interactive cards on mobile devices; wherein, all payloads share the core business data in the standard message model.

[0018] Optionally, in the event-driven heterogeneous system pending message multi-channel fusion method of the present invention, the business access link in the first payload is generated in the following manner: according to the pre-configured environment-independent Uniform Resource Locator prefix, it is dynamically concatenated with the business data identifier carried in the standard message model to form a business detail access address that can be correctly addressed in different deployment environments.

[0019] Optionally, in the event-driven heterogeneous system pending message multi-channel fusion method of the present invention, in step S3, the differentiated message payload is pushed to the unified messaging platform through the security authentication interface for multi-channel access in the following manner: before initiating the request, the general adapter generates a digital signature based on the sender identifier, shared key and timestamp, and attaches the digital signature to the request. After receiving the request, the unified messaging platform uses the same rules to verify the validity of the digital signature and timestamp.

[0020] Optionally, in the event-driven heterogeneous system pending message multi-channel fusion method of the present invention, step S3 establishes a bidirectional state synchronization containing precise business semantics in the following manner: when a task completion or deletion event is captured, the general adapter queries the final business processing result of the original business document corresponding to the task; maps the final business processing result to a predefined state code; pushes the state update instruction carrying the state code to the unified messaging platform, and the unified messaging platform provides feedback on the processing conclusion with specific business meaning.

[0021] Optionally, in the event-driven heterogeneous system pending message multi-channel fusion method of the present invention, step S3, establishing bidirectional state synchronization containing precise business semantics, further includes: pre-setting a callback interface on the unified messaging platform side. When a user directly processes a task on the unified messaging platform side, the unified messaging platform sends a status update notification carrying the processing result to the corresponding heterogeneous business system through the pre-set callback interface. The heterogeneous business system updates its internal task status and business data according to the status update notification.

[0022] Optionally, in the event-driven heterogeneous system pending message multi-channel fusion method of the present invention, in step S3, the state synchronization and standard message model are cross-system identity mapped in the following manner: the unified user identifier across systems is used as the primary key, the general adapter fills in the user identifier obtained based on the current business context when generating the standard message model, and the unified message platform performs user matching and message routing based on the user identifier.

[0023] Optionally, in the event-driven heterogeneous system to-do message multi-channel fusion method of the present invention, step S4 involves achieving non-intrusive access extension of new business systems through a universal adapter and a standard message model. This includes: the universal adapter only relies on the standard external interface of the target business system to operate; when a new business system is added, an adapter component that implements the same standard message model conversion and event listening logic is deployed, and registration and configuration are completed on the unified message platform to achieve fused access of to-do tasks.

[0024] According to a second aspect of the present invention, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in the first aspect of the present invention.

[0025] The present invention provides a method and apparatus for multi-channel fusion of pending messages in heterogeneous systems based on event-driven principles, which has the following beneficial technical effects:

[0026] 1. Achieve a unified user experience and a leap in efficiency across systems.

[0027] Users no longer need to log in to or switch between various isolated business systems. All pending tasks and tasks from different vendor systems are automatically and in real time aggregated into a unified entry platform and presented in a standardized format. This reduces the time and cognitive load spent on system switching, repeated logins, and interface adaptation, thereby improving the overall efficiency of daily office work and business processing.

[0028] 2. Ensure strong consistency and accuracy of cross-system business data.

[0029] Establishing a two-way closed-loop state synchronization mechanism can not only push tasks from the source system to the unified platform, but also synchronize the processing results and precise business semantic status of the tasks at either end back to the other end in real time and reliably. This fundamentally eliminates the phenomenon of "zombie tasks" caused by state asynchrony and ensures that the state view of the same business entity remains strictly consistent in different systems.

[0030] 3. Improve the reach of key messages and the flexibility of push strategies.

[0031] It greatly improves the coverage and timeliness of critical task notifications, ensuring that information is delivered, and can adapt to differentiated push strategies, achieving a balance between resource optimization and user experience.

[0032] 4. Achieve a loosely coupled, highly scalable integrated architecture between systems.

[0033] By simplifying complex mesh integration into a star topology, all systems only need to communicate with their internal adapters and the external unified platform through a standardized model. When a new business system needs to be integrated, it can be quickly connected by simply deploying a new adapter following the same model specifications, without affecting the existing system cluster or requiring only minimal configuration. This significantly reduces the complexity of system integration and long-term maintenance costs, and endows the entire IT architecture with a high degree of scalability and agility.

[0034] 5. Enhance the security, reliability, and maintainability of enterprise-level integration.

[0035] This effectively prevents interface requests from being tampered with or subjected to replay attacks during transmission, ensuring data transmission security and preventing system instability even when messages are repeatedly delivered under abnormal network conditions. Simultaneously, end-to-end critical operation logging enhances system observability and maintainability, guaranteeing stable and continuous business operation. Attached Figure Description

[0036] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0037] Figure 1 This is a flowchart illustrating an event-driven multi-channel fusion method for pending messages in heterogeneous systems according to an exemplary embodiment 1 of the present invention.

[0038] Figure 2 This is a schematic diagram illustrating the technical principle of an event-driven multi-channel fusion method for pending messages in heterogeneous systems according to an exemplary embodiment 2 of the present invention.

[0039] Figure 3 This is a schematic diagram of the structure of the device provided by the present invention. Detailed Implementation

[0040] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0041] It should be noted that, unless otherwise specified, the following embodiments and features can be combined with each other; and, based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0042] It should be noted that various aspects of embodiments within the scope of the appended claims are described below. It will be apparent that the aspects described herein can be embodied in a wide variety of forms, and any particular structure and / or function described herein is merely illustrative. Based on this disclosure, those skilled in the art will understand that one aspect described herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, any number of aspects set forth herein can be used to implement the device and / or practice the method. Additionally, this device and / or method can be implemented using structures and / or functionalities other than one or more of the aspects set forth herein.

[0043] Example 1

[0044] Exemplary embodiment 1 of the present invention provides a method for multi-channel fusion of pending messages in heterogeneous systems based on event-driven principles. Figure 1 This is a flowchart illustrating an event-driven multi-channel fusion method for pending messages in heterogeneous systems according to an exemplary embodiment 1 of the present invention. Figure 1 As shown in this embodiment, the event-driven multi-channel fusion method for pending messages in heterogeneous systems is implemented as follows:

[0045] Step S1: Listen for changes in the status of pending tasks by deploying a general adapter in a heterogeneous business system, and convert the captured events into a preset standard message model.

[0046] In this embodiment, the status change events of pending tasks are monitored in the following manner: using the pending function extension interface provided by the heterogeneous business system, the general adapter registers the event listener, and captures the native system events through the registered time listener. These native system events include pending task creation, task completion, task deletion, and task attribute update.

[0047] Step S2: Based on the event type and task type in the standard message model, dynamically assemble differentiated message payloads with a unified structure that are adapted to different push channels.

[0048] In this embodiment, differentiated message payloads are dynamically assembled in the following manner: the standard message model is parsed to determine the nature of the task; for new events in notification-type tasks, a lightweight payload for real-time message push is assembled; for new events in processing-type tasks, a first payload for creating structured to-do items in the unified portal and a second payload for generating rich media interactive cards on the mobile device are assembled in parallel; wherein, all payloads share the core business data in the standard message model.

[0049] It should be noted that in this embodiment, the service access link in the first payload is generated in the following way: based on the pre-configured environment-independent Uniform Resource Locator prefix, it is dynamically concatenated with the service data identifier carried in the standard message model to form a service detail access address that can be correctly addressed in different deployment environments.

[0050] Step S3: Push the differentiated message payload to the unified messaging platform through the secure authentication interface for multi-channel delivery, and establish bidirectional state synchronization with precise business semantics between the heterogeneous business system and the unified messaging platform based on the standard message model.

[0051] In this embodiment, the differentiated message payload is pushed to the unified messaging platform through the security authentication interface for multi-channel delivery in the following manner: Before initiating a request, the general adapter generates a digital signature based on the sender identifier, shared key and timestamp, and attaches the digital signature to the request. After receiving the request, the unified messaging platform uses the same rules to verify the validity of the digital signature and timestamp.

[0052] In this embodiment, a bidirectional state synchronization containing precise business semantics is established as follows: when a task completion or deletion event is captured, the general adapter queries the final business processing result of the original business document corresponding to the task; maps the final business processing result to a predefined state code; and pushes a state update instruction carrying the state code to the unified messaging platform, through which the unified messaging platform provides feedback on a processing conclusion with specific business meaning.

[0053] In practical applications, establishing bidirectional state synchronization that includes precise business semantics also includes: pre-setting a callback interface on the unified messaging platform side. When a user directly processes a task on the unified messaging platform side, the unified messaging platform sends a state update notification carrying the processing result to the corresponding heterogeneous business system through the pre-set callback interface. The heterogeneous business system updates its internal task status and business data according to the state update notification.

[0054] It should be noted that in this embodiment, state synchronization and standard message model are mapped across systems in the following way: the unified user identifier across systems is used as the primary key, the general adapter fills in the user identifier obtained based on the current business context when generating the standard message model, and the unified message platform performs user matching and message routing based on the user identifier.

[0055] Step S4: Achieve cross-system state closed loop through bidirectional state synchronization, and achieve non-intrusive access extension of new business systems through universal adapters and standard message models.

[0056] In this embodiment, a non-intrusive access extension for new business systems is achieved through a universal adapter and a standard message model. This includes: the universal adapter only relies on the standard external interface of the target business system to operate; when a new business system is added, an adapter component that implements the same standard message model conversion and event listening logic is deployed and registered and configured on the unified messaging platform to achieve the integrated access of pending tasks.

[0057] Example 2

[0058] Exemplary Example 2 of the present invention provides a multi-channel fusion method for to-do messages in heterogeneous systems based on event-driven approaches. In this embodiment, a general adapter based on the to-do event extension points of the supplier system is constructed. This adapter listens to the to-do lifecycle events (creation, completion, deletion) within the supplier system and converts these events into a standardized message model, which is then pushed to an external integrated platform through a secure and reliable interface. Figure 2 This is a schematic diagram illustrating the technical principle of an event-driven multi-channel fusion method for pending messages in heterogeneous systems according to an exemplary embodiment 2 of the present invention. Figure 2 As shown, the method of this embodiment is implemented in the following manner:

[0059] 1. Monitor the entire lifecycle of pending tasks.

[0060] By utilizing the standard to-do event extension interface provided by the supplier's system, a custom to-do handler is registered. This handler can accurately capture four core to-do events: add to-do / read, mark as done, delete to-do, and update to-do. This constitutes the driving force of the entire integration process.

[0061] 2. Construct standardized, multi-channel message payloads

[0062] For different event and message types (to-do vs. to-read), the adapter dynamically assembles differentiated but structurally uniform message payloads.

[0063] For "Add to-do": Two sets of message bodies are generated simultaneously. One set is used to create portal to-dos (including title, penetrating link, initiator, creation time, etc.), and the other set is used to send mobile instant messaging cards (displayed in the form of rich text cards to improve user experience).

[0064] For "New to be Read": Generate a real-time message body to ensure that the information is delivered immediately.

[0065] All messages contain complete business context, such as unique task ID, system registration code, recipient list, and business document number, providing a basis for subsequent status synchronization.

[0066] 3. Refined business status mapping

[0067] It not only synchronizes whether the application has been processed, but also further refines the semantics of business processing. In the "set as processed" or "delete" events, the adapter actively queries the final status of the original business document (such as a contract application) (e.g., "rejected" or "approved"). Based on the query results, it transmits precise sub-status codes to the external platform (e.g., "3" represents rejection, and "7" represents deletion). This allows the external platform to accurately present the true result of the approval, rather than simply "processed".

[0068] 4. Establish a two-way closed-loop state synchronization mechanism

[0069] Forward synchronization: When a user performs a task in the supplier's system (such as clicking "Agree"), the event is triggered, and the adapter immediately pushes the "Completed" or "Delete" instruction along with the sub-status to the external platform to achieve real-time status updates.

[0070] Reverse synchronization guarantee: The overall architecture design includes provisions for reverse synchronization capabilities. If external platforms support direct user processing in the future, the system can be notified to update its internal state via a callback interface, forming a complete closed loop.

[0071] 5. Enterprise-level security and reliability design

[0072] Secure signature: All outbound requests use the SHA224 signature mechanism of "product code + key + timestamp" to prevent requests from being tampered with or replay attacks.

[0073] Account matching: Use the user's login name as the primary key for cross-system identity mapping to ensure that messages are accurately delivered to the target user.

[0074] Link penetration: The penetration links for PC and mobile devices are dynamically concatenated using a unified URL prefix, ensuring consistency between the testing and production environments.

[0075] Idempotency and Logging: Using a third-party task key (taskId) as the unique identifier, it is inherently idempotent; all key operations in the entire chain are logged in detail, which facilitates auditing and problem tracking.

[0076] Example 3

[0077] Exemplary Example 3 of the present invention provides a method for multi-channel fusion of pending messages in heterogeneous systems based on event-driven approaches. In this embodiment, the method for multi-channel fusion of pending messages in heterogeneous systems based on event-driven approaches is further described in a specific scenario.

[0078] In this scenario, a large enterprise group has deployed multiple core business systems, including a supplier management system, a contract management system, and an ERP system, and has established a unified enterprise portal as a one-stop work entry point for employees. To overcome the problems of scattered tasks and asynchronous statuses among the various systems, this enterprise has implemented the event-driven multi-channel fusion method for heterogeneous system task messages, as described in this embodiment.

[0079] This embodiment uses the entire lifecycle of a typical "purchase contract approval" pending task in a supplier management system as an example to illustrate the implementation process of this method in detail.

[0080] 1. System Architecture and Component Deployment

[0081] First, a general-purpose adapter is deployed within the supplier management system. This adapter is designed as a standalone, lightweight service that does not modify the core code of the supplier management system, but only interfaces with the system's open "To-Do Center Event Extension API." Simultaneously, the enterprise has established a unified messaging platform responsible for receiving standardized messages from various systems and pushing messages to employees' portal to-do lists, enterprise instant messaging tools, and mobile office apps.

[0082] 2. Event Triggering and Standardization

[0083] When a purchasing agent drafts and submits a purchase contract in the supplier management system, the system's internal workflow engine generates a to-do task and automatically calls its "To-Do Center Event Extension API" to trigger a "Add To-Do" event.

[0084] The general-purpose adapter deployed on this system is pre-registered to listen for this API. Upon capturing this event, the adapter immediately extracts raw data from the event parameters, including: task ID (task_2023_1101_001), task title ("Approval: Purchase Contract for XX Equipment"), initiator ("Purchaser Zhang San"), recipient list ("Approver Li Si"), associated business document number (PO-20231101-001), and creation time, etc.

[0085] Subsequently, the adapter, following the company's established "Standard Model V1.0 for To-Do Messages," transforms and encapsulates this heterogeneous data into a standard message model (JSON format). This model consistently includes the following core fields: eventType (event type, here "CREATE"), taskId (task ID), bizId (business document number), receiverIds (list of recipients, here ["lisi"]), title, creator, createTime, etc. This step transforms the internal events of the supplier management system into a "common language" that all systems can understand.

[0086] 3. Polymorphic assembly of message payloads

[0087] The generic adapter parses the generated standard message model. It determines that the eventType is "CREATE" and the task type is "Pending" requiring approval (rather than the mere notification "Pending Reading"). Therefore, the adapter initiates the polymorphic assembly process:

[0088] Generate Portal To-Do Payload (First Payload): The adapter assembles a structured message for creating a to-do item in the unified portal. In addition to the basic information in the standard model, this payload dynamically generates a business penetration link based on configuration rules. The link is in the form of https: / / portal.company.com / redirect?sys=SUPPLIER&bizId=PO-20231101-001. When a user clicks this link, the portal redirects them to the details page of the contract approval form in the supplier management system.

[0089] Generate a mobile card payload (second payload): Simultaneously, the adapter assembles a rich text card message suitable for mobile devices such as WeChat Work / DingTalk. The card design is more eye-catching, including a title, key summary, and a prominent "Approve Now" button, which, when clicked, will also take you to the approval page.

[0090] Although these two payloads have different forms of presentation, their core business data (such as taskId, bizId, receiverIds) are completely consistent and both originate from the same standard message model.

[0091] 4. Secure push notifications and multi-channel reach

[0092] Before sending a message, the general adapter performs a secure signature: it concatenates the system's encoding (SUPPLIER), a key pre-shared with the unified messaging platform, and the current timestamp, and then generates a signature, signature_abc123, using the SHA-224 algorithm.

[0093] Subsequently, the adapter sends the two message payloads, along with the signature, timestamp, and system code, to the designated receiving interface of the unified messaging platform via the HTTPS protocol.

[0094] Upon receiving a request, the unified messaging platform first verifies the validity of the signature and timestamp to prevent forged or expired requests. Once verification is successful, the platform uses the receiverIds (i.e., "lisi") in the message to perform user identity mapping and locate the unified account of employee Li Si.

[0095] Next, the platform executes multi-channel push notifications:

[0096] In the enterprise portal, add a new structured record to Li Si's to-do list.

[0097] Send a reminder message to Li Si's company instant messaging tool.

[0098] Send a rich text card message to the mobile office app linked to Li Si.

[0099] At this point, the approver, Li Si, had received this pending notification through three channels.

[0100] 5. Precise business semantic state synchronization

[0101] 5.1 Forward semantic synchronization:

[0102] Suppose Li Si clicks the "Reject" button within the supplier management system. After the system completes the processing, the "Processed" event is triggered again.

[0103] After the general adapter captures this event, it does not immediately send only a "completed" status. It first calls the internal service interface of the supplier management system based on the taskId or bizId to query the final business status of the contract document and finds that the result is "rejected".

[0104] The adapter then maps the business semantic "rejection" to a predefined sub-status code of the unified messaging platform, such as "3". It generates a new standard message model where eventType is "COMPLETE", taskId remains unchanged, and carries a statusCode field with a value of "3".

[0105] After being securely signed, this status update message is pushed to the unified messaging platform. Upon receiving it, the platform not only marks the corresponding to-do item in Li Si's portal as "processed," but can also display it as "rejected," accurately reflecting the business outcome.

[0106] 5.2 Reverse synchronization guarantee (closed loop):

[0107] Let's consider another scenario: Li Si directly clicks the "Agree" button after the procurement contract approval task in the to-do list on the company portal.

[0108] At this point, the unified messaging platform, acting as the processing entry point, first calls the callback interface pre-registered by the supplier management system through the general adapter, passing the taskId and the processing action "agree".

[0109] After receiving the request, the callback processor inside the supplier management system verifies its legitimacy, then simulates the user's operation, executes the "agree" approval in its internal workflow engine, and updates the contract document status.

[0110] Once completed, the supplier management system will trigger a "Pending Task Processed" event, just like in a normal process. The general adapter captures this event and executes the query and synchronization process described in section 5.1 above, synchronizing the final status (which is now "Agreed") back to the unified messaging platform. This ensures that even though the processing entry point is in the portal, the data status of the two systems is completely consistent, forming a closed processing loop.

[0111] 6. System scalability and reliability

[0112] When an enterprise needs to integrate its contract management system into this unified system, there is no need to modify the unified messaging platform or other existing systems. Simply deploy a universal adapter within the contract management system that implements the same conversion logic as the supplier management system, and listen for its own events. Then, on the unified messaging platform's management interface, register the contract management system as a new source (encoded CONTRACT) and configure the key. At this point, the contract management system's to-do tasks can be seamlessly integrated into the existing system, achieving loose coupling and highly scalable access.

[0113] Throughout the process, a globally unique taskId is used as the criterion to ensure the idempotency of message processing and prevent network retries from causing tasks to be created or processed repeatedly. All critical steps, such as event capture, model transformation, API calls, and status queries, are logged in detail to form a complete traceability chain, facilitating operation and maintenance auditing and problem troubleshooting.

[0114] By implementing this embodiment, enterprises can unify and aggregate scattered to-do information and ensure its reach through multiple channels. At the same time, a cross-system, two-way status synchronization mechanism with precise business semantics is established to completely eliminate information silos and "zombie to-dos", significantly improving collaborative work efficiency and data consistency.

[0115] In practical applications, the method of the embodiments of the present invention has the following beneficial technical effects:

[0116] 1. Achieve a unified user experience and a leap in efficiency across systems.

[0117] Users no longer need to log in to or switch between various isolated business systems. All pending and unread tasks from different vendor systems (such as contracts, ERP, OA, etc.) are automatically and in real time aggregated into a unified entry platform (such as an enterprise portal or mobile workbench) and presented in a standardized format. This provides users with a truly "one-stop" task processing experience, reducing the time and cognitive load spent on system switching, repeated logins, and interface adaptation, and improving the overall efficiency of daily office work and business processing.

[0118] 2. Ensure strong consistency and accuracy of cross-system business data.

[0119] Establishing a two-way closed-loop state synchronization mechanism not only pushes pending tasks from the source system to the unified platform, but also reliably and in real time synchronizes the processing results and precise business semantic status (such as "agree," "reject," and "revoke") of the tasks at either end (source system or unified platform) back to the other end. This fundamentally eliminates the phenomenon of "zombie tasks" (i.e., tasks that have been processed on one side but are still displayed as unprocessed on the other) caused by state asynchrony, ensuring that the state view of the same business entity remains strictly consistent across different systems.

[0120] 3. Improve the reach of key messages and the flexibility of push strategies.

[0121] Employing a multi-channel integrated push strategy, it can flexibly select and deliver messages through various channels such as portal to-do lists, instant messaging tools (such as WeChat Work and DingTalk), and mobile push notification cards, based on the urgency, importance, and user scenario of the task. This greatly improves the coverage and timeliness of critical task notifications, ensuring that information is delivered. Simultaneously, it differentiates between tasks that need to be processed and those that need to be read (notification only), adapting to different push strategies and achieving a balance between resource optimization and user experience.

[0122] 4. Achieve a loosely coupled, highly scalable integrated architecture between systems.

[0123] By designing a "universal adapter" based on a standard event interface as the core intermediary component, low-intrusion integration of heterogeneous business systems is achieved. The adapter requires no modification to the core code of the business systems, operating solely through their standard extension points. This simplifies complex mesh integration into a star topology, where all systems communicate only with their internal adapters and the external unified platform via a standardized model. When a new business system needs to be integrated, simply deploying a new adapter following the same model specification allows for rapid integration, with no impact on the existing system cluster or requiring only minimal configuration. This significantly reduces the complexity of system integration and long-term maintenance costs, while endowing the entire IT architecture with high scalability and agility.

[0124] 5. Enhance the security, reliability, and maintainability of enterprise-level integration.

[0125] By employing a secure signature mechanism based on keys and timestamps, the system effectively prevents interface requests from being tampered with or subjected to replay attacks during transmission, ensuring data transmission security. An idempotent design centered on a globally unique task ID ensures that the system state remains stable even when messages are repeatedly delivered under abnormal network conditions. Simultaneously, end-to-end critical operation log recording provides comprehensive data support for system operation status monitoring, rapid problem localization, and operation auditing, improving system observability and maintainability, and ensuring stable operation of business continuity.

[0126] like Figure 3 As shown, the present invention also provides a device including a processor 310, a communication interface 320, a memory 330 for storing processor-executable computer programs, and a communication bus 340. The processor 310, communication interface 320, and memory 330 communicate with each other via the communication bus 340. The processor 310 executes the executable computer program to implement the aforementioned event-driven heterogeneous system pending message multi-channel fusion method.

[0127] The computer program in memory 330, when implemented as a software functional unit and sold or used as an independent product, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, a portable hard drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0128] The system embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected based on actual needs to achieve the purpose of this embodiment. Those skilled in the art can understand and implement this without any creative effort.

[0129] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods of various embodiments or some parts of embodiments.

[0130] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A method for multi-channel fusion of pending messages in heterogeneous systems based on event-driven principles, characterized in that, The method includes: Step S1: Listen for changes in the status of pending tasks by deploying a general adapter in a heterogeneous business system, and convert the captured events into a preset standard message model; Step S2: Based on the event type and task type in the standard message model, dynamically assemble differentiated message payloads with a unified structure that are adapted to different push channels; Step S3: Push the differentiated message payload to the unified messaging platform through the security authentication interface for multi-channel delivery, and establish bidirectional state synchronization with precise business semantics between the heterogeneous business system and the unified messaging platform based on the standard message model; Step S4: Achieve cross-system state closed loop through bidirectional state synchronization, and achieve non-intrusive access extension of new business systems through universal adapters and standard message models.

2. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 1, characterized in that, In step S1, the status change events of the pending tasks are monitored in the following way: using the pending function extension interface provided by the heterogeneous business system, the general adapter registers the event listener, and captures the native system events through the registered time listener. These native system events include pending task creation, task completion, task deletion, and task attribute update.

3. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 1, characterized in that, In step S2, the differentiated message payload is dynamically assembled as follows: the standard message model is parsed to determine the nature of the task; For new events in notification-type tasks, assemble a lightweight payload for real-time message push. For new events in processing tasks, a first payload for creating structured to-do items in a unified portal and a second payload for generating rich media interactive cards on mobile devices are assembled in parallel; all payloads share core business data in the standard messaging model.

4. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 3, characterized in that, The service access link in the first payload is generated as follows: based on the pre-configured environment-independent Uniform Resource Locator prefix, it is dynamically concatenated with the service data identifier carried in the standard message model to form a service detail access address that can be correctly addressed in different deployment environments.

5. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 1, characterized in that, In step S3, the differentiated message payload is pushed to the unified messaging platform through the security authentication interface for multi-channel delivery in the following manner: Before initiating the request, the general adapter generates a digital signature based on the sender identifier, shared key and timestamp, and attaches the digital signature to the request. After receiving the request, the unified messaging platform uses the same rules to verify the validity of the digital signature and timestamp.

6. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 1, characterized in that, In step S3, a bidirectional state synchronization containing precise business semantics is established as follows: when a task completion or deletion event is captured, the general adapter queries the final business processing result of the original business document corresponding to the task. Map the final business processing result to a predefined state code; The status update instruction carrying the status code is pushed to the unified messaging platform, which then provides a processing conclusion with specific business implications.

7. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 6, characterized in that, In step S3, establishing bidirectional state synchronization with precise business semantics also includes: pre-setting a callback interface on the unified messaging platform side. When a user directly processes a task on the unified messaging platform side, the unified messaging platform sends a state update notification carrying the processing result to the corresponding heterogeneous business system through the pre-set callback interface. The heterogeneous business system updates its internal task status and business data according to the state update notification.

8. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 1, characterized in that, In step S3, the state synchronization and standard message model are mapped across systems in the following way: the unified user identifier across systems is used as the primary key, the general adapter fills in the user identifier obtained based on the current business context when generating the standard message model, and the unified message platform performs user matching and message routing based on the user identifier.

9. The event-driven multi-channel fusion method for pending messages in heterogeneous systems according to claim 1, characterized in that, In step S4, a non-intrusive access extension for new business systems is achieved through a universal adapter and a standard message model. This includes: the universal adapter only relies on the standard external interface of the target business system to run; when a new business system is added, an adapter component that implements the same standard message model conversion and event listening logic is deployed and registered and configured on the unified messaging platform to achieve the integrated access of pending tasks.

10. A computer device, characterized in that, The computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the method according to any one of claims 1-9.

Images