Configurable message notification system based on code-free platform

Abstract

The invention relates to the technical field of communication, and discloses a configurable message notification system based on a code-free platform, which comprises the following steps of strategy configuration, data change monitoring and message processing and sending. Configuring a message strategy in the code-free platform, wherein the message strategy comprises an associated custom form, a triggering condition of a message, a triggering rule, a message template and a receiver; according to the method, a mechanism for realizing the cyclic message by using the delay queue is utilized, the development complexity is reduced, the service response speed is improved, the next trigger time point is recalculated after sending through the cyclic message and is submitted to the delay queue again to form a cycle, convenient service is provided for a user, and the user experience is improved. A positioning function in an existing APP is used for detecting the existing position of a user for positioning and comparing the existing position with a fixed working position, and the sending frequency of the cyclic information is changed, so that the user is convenient to use, and the user is prevented from missing information notification.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and in particular to a configurable message notification system based on a no-code platform. Background Technology

[0002] A no-code platform-based configurable message notification system is a system that can implement message notifications through a visual interface without writing code. It can quickly build automated notification processes according to business needs. In today's fast-paced business environment, message notification systems are crucial for improving work efficiency and user experience. However, traditional message notification functions rely heavily on coding, resulting in long development and maintenance cycles, high costs, poor flexibility, and difficulty in quickly adjusting to changes in business needs. While there are some message middleware and change data capture tools in the existing technology, they usually require complex integration by professional developers and cannot be used directly by business personnel. For example, in daily work, the system will automatically remind you to clock in and out, but if you miss it or do not pay attention due to overtime or other reasons, the information notification will be delayed and you will miss the clock-in information when you receive it again. Summary of the Invention

[0003] To address the shortcomings of existing technologies, this invention provides a configurable message notification system based on a no-code platform. By deeply integrating no-code configuration capabilities with technologies such as CDC and message queues, business personnel can quickly and flexibly define and adjust message notification strategies, significantly reducing technical barriers and development costs. By recalculating the next trigger time and resubmitting to the delay queue, a loop is formed, providing convenient services to users.

[0004] To achieve the above objectives, the present invention adopts the following technical solution: In a first aspect, the present invention provides a configurable message notification method based on a no-code platform, comprising the following steps: S1. Strategy Configuration: Configure message strategies in the no-code platform. The message strategy includes associated custom forms, message triggering conditions, triggering rules, message templates, and recipients. S2. Data Change Monitoring: Monitor the changes in values ​​of the database table corresponding to the custom form in real time through the CDC service, and encapsulate the changed data as a message event and submit it to the Kafka message queue; S3. Message Processing and Sending: The message sending and receiving service consumes message events in Kafka and generates messages to be sent according to the triggering rules and message templates of the message strategy. If it is an immediate message, it is sent directly to the recipient; if it is a delayed message, it is submitted to the delayed message queue, which pushes it to the recipient at a specified time according to the delay strategy.

[0005] Furthermore, the triggering rules include time-based patterns and field-based patterns: The time mode is used to trigger delayed or cyclical messages based on the time field specified in the custom form. The field pattern is used to trigger a message immediately based on the value change of a specified field in the custom form.

[0006] Furthermore, configuring the time mode includes configuring a time field, advance reminder time, and a cycle parameter; wherein the cycle parameter includes no cycle, daily cycle, weekly cycle, monthly cycle, or yearly cycle.

[0007] Furthermore, configuring the field mode includes configuring a trigger field and field conditions; wherein, when the CDC service monitors that the value change of the trigger field meets the field conditions, an instant message is triggered.

[0008] Furthermore, in the strategy configuration step, configuring the recipient includes one of the following two methods or a combination thereof: manually selecting a user from the organizational structure list; specifying the user field in the custom form and parsing the value of the field to determine the recipient when the message is triggered.

[0009] Furthermore, in the data change monitoring step, the CDC service uses the Debezium platform to monitor changes to the database tables, including additions, modifications, and deletions; the message queue is a Kafka distributed message queue.

[0010] Furthermore, in the message processing and sending steps, the delayed message queue is implemented using a Redis ordered set.

[0011] Furthermore, in the message processing and sending steps, if the triggering rule is a time-based mode and a loop parameter is configured, then after the delayed message queue pushes the message to the recipient, the next triggering time is recalculated, and the message is submitted to the delayed message queue again to achieve cyclic message sending.

[0012] Furthermore, the message strategy is configured to enable WeChat Work messages; during the message processing and sending steps, the sent message is simultaneously pushed to the user corresponding to the recipient in WeChat Work.

[0013] In a second aspect, the present invention provides a system for implementing the above method, comprising: The policy configuration service provides a visual interface for users to configure message policies, including associated custom forms, trigger conditions, trigger rules, message templates, and recipients. The CDC data capture service non-intrusively monitors changes in values ​​of the database table corresponding to the custom forms and encapsulates the changed data as message events to the message queue. The message sending and receiving service consumes message events from the message queue, generates and routes messages according to the trigger rules and message templates of the message policy. The delayed message queue receives and stores delayed messages from the message sending and receiving service and pushes the messages to the recipients according to the calculated trigger time.

[0014] Compared with the prior art, the beneficial effects of the present invention are as follows: 1. This invention combines the no-code configuration concept with technologies such as CDC and message queues to construct a brand-new message notification paradigm. By allowing business personnel to directly configure message policies and associate them with business forms, it achieves automatic binding between message triggering logic and business data changes.

[0015] 2. This invention reduces development complexity and improves business response speed by using a "no-code configuration + CDC real-time monitoring" approach to separate time-based and field-based modes and to implement a circular message mechanism using a delayed queue. This solves the technical problems of high coupling and inflexibility in traditional systems. Through circular messages, the next trigger time is recalculated after sending and submitted to the delayed queue again to form a loop, providing convenient services to users. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the overall architecture of a configurable message notification system based on a no-code platform proposed in this invention. Figure 2 This is a flowchart of a message policy configuration process for a no-code platform-based configurable message notification system proposed in this invention. Figure 3 This is a flowchart illustrating the message processing and sending process of a configurable message notification system based on a no-code platform, as proposed in this invention. Detailed Implementation

[0017] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0018] The following is a detailed description of the present invention. Please refer to [link / reference]. Figure 1 As shown.

[0019] This invention is a configurable method for implementing message notifications on a no-code platform, which requires the following steps: System Architecture The system of this invention mainly includes the following core services: Policy configuration service: Provides a web-based visual interface that allows users to define various parameters of message policies, making it convenient for users to customize settings according to their daily work habits.

[0020] CDC Data Capture Service: Employs the Debezium engine to connect to the business database and capture database add, delete, and modify operations in real time.

[0021] Kafka message queue: As the system's message bus, it receives events from the CDC service and distributes them to downstream services.

[0022] Message sending and receiving service: The core processing unit, responsible for parsing events, executing rules, generating and delivering messages.

[0023] Delayed message queue: Implemented using Redis Sorted Set, used to process and schedule delayed messages; CDC data capture, Kafka message queue, Debezium engine and Redis Sorted Set are all existing technologies, and the system framework is constructed using existing technologies.

[0024] Implementation process 1. Policy configuration process (corresponding to) Figure 2 ) Users can perform the following operations through the policy configuration service: S201: Define policy basic information: Enter the policy name and description, and select the message type and set the enabled status.

[0025] S202: Associated Forms and Filtering Conditions: Select a target form from the list of forms created by the no-code platform; data filtering conditions can be further set, and only data changes that meet the conditions will trigger a message.

[0026] S203: Configure reminder rules: Select "Time Mode" or "Field Mode".

[0027] If you choose the time mode (S203a), you need to specify the time field, advance reminder time, and cycle period (none, daily, weekly, etc.).

[0028] If you choose the field mode (S203b), you need to specify the trigger field to be monitored and set the trigger condition (such as "when the status field changes to 'approved'").

[0029] S204: Configure message content and recipient: Define message templates, and use expressions to dynamically insert data in the templates; specify message recipients, which can be manually selected from the organizational structure or automatically obtained from user fields in associated forms.

[0030] 2. Message processing and sending process (corresponding to) Figure 3 ) S301: Users manipulate (add or modify) custom form data in the business system.

[0031] S302: When the CDC service detects changes in a database table, it sends the changed data (including the values ​​before and after the change) as a message event to Kafka.

[0032] S303: The message sending and receiving service pulls this event from Kafka.

[0033] S304: The service queries the associated message policy based on the form ID in the event.

[0034] S305: Determine the trigger rule type of the strategy.

[0035] If it is a field mode (S305→S306), check whether the changed data meets the configured field conditions; if it does, execute S307.

[0036] If it is a time mode (S305→S308), a precise message triggering time is calculated based on the configured time field, lead time, and loop rules.

[0037] S307 / S309: Based on the message template and current data, render and generate the final message content, and determine the final list of recipients.

[0038] S310: Determine the message type again. If it is an instant message triggered by a field pattern, execute S311 directly, store the message in the database and push it to the user's message center (such as DingTalk or WeChat Work). If it is a delayed message triggered by a time pattern, execute S312, submit the message and its trigger time to the Redis delayed queue.

[0039] S313: The delayed message queue service polls and checks messages that have reached their trigger time. Once a message arrives, it executes S311 to send it. If it is a circular message, the next trigger time is recalculated after sending and submitted to the delayed queue again (S312), forming a loop. For example, in daily work, the system will automatically remind you to clock in and out. If you miss the message due to overtime or other reasons, the system will recalculate the next trigger time after sending and submit it to the delayed queue again (S312), forming a loop. When you receive the message again, you will miss the clock-in information.

[0040] As can be seen from the above, the working principle of this application is as follows: Configure messaging strategies in a no-code platform. These strategies include associated custom forms, message triggering conditions, triggering rules, message templates, and recipients, which users can customize.

[0041] The CDC service monitors changes in values ​​in the database table corresponding to the custom form in real time and encapsulates the changed data as message events and submits them to the Kafka message queue.

[0042] The message sending and receiving service consumes message events in Kafka and generates messages to be sent according to the triggering rules and message templates of the message strategy. If it is an immediate message, it is sent directly to the recipient; if it is a delayed message, it is submitted to the delayed message queue, which pushes it to the recipient at a specified time according to the delay strategy. The mechanism of implementing a circular message using a delayed queue reduces development complexity and improves business response speed. Through circular messages, the next trigger time is recalculated after sending and submitted to the delayed queue again to form a loop, providing convenient services to users. The existing location function in the app is used to detect the user's current location and compare it with the fixed work location to change the sending frequency of the circular message, making it convenient for users and preventing them from missing information notifications. If the user completes the check-in, the circular message ends and the delayed queue stops.

[0043] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the claimed invention.

Claims

1. A configurable message notification system based on a no-code platform, characterized in that, Includes the following steps: S1: Strategy configuration, configuring message strategies in the no-code platform. The message strategy includes associated custom forms, message triggering conditions, triggering rules, message templates, and recipients. S2: Data change monitoring, through the change data capture CDC service, monitors the value changes of the database table corresponding to the custom form in real time, and encapsulates the change data as a message event and submits it to the message queue; S3: Message processing and sending. The message sending and receiving service consumes message events in the message queue and generates a message to be sent according to the triggering rules and message templates of the message policy. If the triggering rule indicates an immediate message, the message to be sent is sent directly to the recipient. If the triggering rule indicates a delayed message, it is submitted to the delayed message queue, which pushes it to the recipient at a specified time according to the delay policy.

2. The configurable message notification system based on a no-code platform according to claim 1, characterized in that, In the S1 strategy configuration step, the triggering rules include a time mode and a field mode: the time mode is used to trigger delayed or cyclical messages based on the time field specified in the custom form; The field pattern is used to trigger a message immediately based on the value change of a specified field in the custom form.

3. A configurable message notification system based on a no-code platform according to claim 2, characterized in that, Configuring the time mode includes configuring a time field, advance reminder time, and cycle parameters; wherein, the cycle parameters include no cycle, daily cycle, weekly cycle, monthly cycle, or yearly cycle.

4. A configurable message notification system based on a no-code platform according to claim 2, characterized in that, Configuring the field mode includes configuring the trigger field and field conditions; wherein, when the CDC service detects that the value change of the trigger field meets the field conditions, an instant message is triggered.

5. A configurable message notification system based on a no-code platform according to claim 1, characterized in that, In the strategy configuration step, configuring the recipient includes one of the following two methods or a combination thereof: manually selecting a user from the organizational structure list; specifying the user field in the custom form and parsing the value of the field to determine the recipient when the message is triggered.

6. A configurable message notification system based on a no-code platform according to claim 1, characterized in that, In the data change monitoring step, the CDC service uses the Debezium platform to monitor changes to the database tables, including additions, modifications, and deletions; the message queue is a Kafka distributed message queue.

7. A configurable message notification system based on a no-code platform according to claim 1, characterized in that, In the message processing and sending steps, the delayed message queue is implemented using a Redis ordered set.

8. A configurable message notification system based on a no-code platform according to claim 1, characterized in that, In the message processing and sending steps, if the triggering rule is a time mode and a loop parameter is configured, after the delayed message queue pushes the message to the recipient, the next triggering time is recalculated, and the message is submitted to the delayed message queue again to achieve cyclic message sending.

9. A no-code platform-configurable message notification system based on the method of any one of claims 1 to 8, characterized in that, The message policy is configured to enable WeChat Work messages; during the message processing and sending steps, the sent message is simultaneously pushed to the user corresponding to the recipient in WeChat Work.

10. A no-code platform-configurable message notification system for implementing the method as described in any one of claims 1 to 9, characterized in that, include: The strategy configuration service provides a visual interface for users to configure message policies, including associated custom forms, trigger conditions, trigger rules, message templates, and recipients. The CDC data capture service is used to non-intrusively monitor changes in values ​​of the database table corresponding to the custom form and encapsulate the changed data as message events and submit them to the message queue. A message sending and receiving service is used to consume message events in the message queue and generate and route messages according to the triggering rules and message templates of the message policy. A delayed message queue is used to receive and store delayed messages from the message sending and receiving service, and to push the messages to the recipient according to the calculated trigger time.

Images