Timing mail merging method and device, computer equipment and storage medium

Abstract

The invention relates to the field of cloud monitoring and financial science and technology, and discloses a timed mail merging method and device, computer equipment and a storage medium. The method comprises the following steps: acquiring a plurality of to-be-merged timing mails, and generating merged mail information; setting the to-be-combined timing mails to be in a failure state; configuring a combined mail template; the combined mail information is loaded to the combined mail template; and generating and sending a combined mail according to the combined mail template. According to the invention, the state of the to-be-merged mail is set as the failure state, so that the to-be-merged mail cannot be sent, the content of the to-be-merged mail is configured to the merged mail template, and the merged mail is generated without changing the content of the to-be-merged mail, so that the difficulty of regular mail merging is simplified, and the efficiency of regular mail merging is improved by reducing the number of sent regular mails. The auditing burden of the receiver is reduced, and information confusion caused by frequent mail processing of the receiver is avoided.

Description

Technical Field

[0001] The present invention relates to the fields of cloud monitoring and financial technology, and in particular to a timed mail merging method, device, computer equipment and storage medium. Background Art

[0002] The financial industry involves a large amount of capital flow and transactions. Financial institutions need to monitor specific types of transactions or activities in order to detect and respond to potential transaction risks and abnormal activities. Scheduled emails, as part of the risk warning mechanism, can help financial institutions detect and respond to potential risks in a timely manner. For example, when the system detects abnormal transactions or account activities, by sending a scheduled alarm email, relevant personnel can be quickly notified so that they can take measures to prevent the risk from further expanding.

[0003] Currently, most scheduled emails used for monitoring are fixed-time and single-content monitoring data. If the recipient frequently receives scheduled emails with medium or low alarm levels, the recipient will have to review a large amount of information and the information will be confusing. This can easily lead to problems such as untimely email processing and interference with normal work. However, most scheduled email information used for monitoring is fixed in the background, making it difficult to modify the content of scheduled emails, and thus unable to send them at a unified time.

[0004] Therefore, the industry is in urgent need of a scheduled email merging method, device, computer equipment and storage medium that can easily merge multiple scheduled emails and enable simultaneous sending of multiple scheduled emails. Summary of the invention

[0005] The present invention provides a timed mail merging method, device, computer equipment and storage medium to solve the technical problem that the existing timed mails are difficult to modify the content and thus cannot be sent at a unified time.

[0006] In a first aspect, a timed mail merge method is provided, including:

[0007] Get several scheduled emails to be merged and generate merged email information;

[0008] Setting the scheduled email to be merged to an invalid state;

[0009] Configure the mail merge template;

[0010] Loading the merged mail information into the merged mail template;

[0011] Generate and send a merge mail according to the merge mail template.

[0012] In a second aspect, a timed mail merge device is provided, comprising:

[0013] The acquisition module acquires several scheduled emails to be merged and generates merged email information;

[0014] A disabling module is used to set the scheduled email to be merged to an invalid state;

[0015] Configuration module, configure the merge email template;

[0016] A loading module is used to load the merged mail information into the merged mail template;

[0017] A generation module generates and sends a merged email according to the merged email template.

[0018] In a third aspect, 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 implements the steps of the above-mentioned scheduled mail merge method when executing the computer program.

[0019] In a fourth aspect, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned scheduled mail merge method are implemented.

[0020] Compared with the prior art, the beneficial effects of the present invention are as follows: the present invention sets the status of the mail to be merged to an invalid status so that the mail to be merged cannot be sent, and configures the content of the mail to be merged to the merge mail template, thereby generating a merge mail without changing the content of the mail to be merged, thereby simplifying the difficulty of scheduled mail merging, and by reducing the number of scheduled mails sent, reducing the server burden and network congestion, reducing operating costs, thereby reducing the review burden of the recipient, and avoiding information confusion caused by the recipient's frequent processing of mails. The merged mail makes the results of multiple monitoring tasks clear at a glance, helps to conveniently analyze and compare monitoring data, optimizes the workflow, and improves the efficiency of scheduled mail processing. At the same time, the merged mail is not limited to fixed content and sending time, and can flexibly adjust the mail content and format to meet the needs of different scenarios.

[0021] The above description is only an overview of the technical solution of the present invention. In order to more clearly understand the technical means of the present invention, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present invention more obvious and easy to understand, the following preferred embodiments are specifically cited and described in detail as follows. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1 It is a schematic diagram of an application environment of a timed mail merging method in one embodiment of the present invention;

[0023] Figure 2 is a flow chart of a timed mail merging method according to an embodiment of the present invention;

[0024] Figure 3 yes Figure 2A schematic flow chart of a specific implementation of step S10;

[0025] Figure 4 yes Figure 2 A schematic flow chart of a specific implementation of step S20;

[0026] Figure 5 yes Figure 2 A schematic flow chart of a specific implementation of step S30;

[0027] Figure 6 yes Figure 2 A schematic flow chart of a specific implementation of step S40;

[0028] Figure 7 yes Figure 2 A schematic flow chart of a specific implementation of step S50;

[0029] Figure 8 It is a structural schematic diagram of a timed mail merging device in one embodiment of the present invention;

[0030] Fig. 9 is a schematic diagram of a structure of a computer device in one embodiment of the present invention;

[0031] Fig.10 It is another structural schematic diagram of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention is further described in detail in conjunction with the accompanying drawings and specific implementation methods. The technical solution in the embodiment of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiment of the present invention. Obviously, the described embodiment is a part of the embodiment of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0033] It should be understood that when used in this specification and the appended claims, the terms "include" and "comprises" indicate the presence of described features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or combinations thereof.

[0034] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, the singular forms "a", "an" and "the" are intended to include plural forms unless the context clearly indicates otherwise.

[0035] It should be further understood that the term "and / or" used in the present description and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0036] See also Figure 1 and Figure 2 , Figure 1 Schematic diagram of the application scenario of the scheduled mail merge method provided in an embodiment of the present invention. The client communicates with the server through a network. The server can receive a merge instruction through the client, and obtain a number of scheduled mails to be merged according to the merge instruction, and generate merge mail information; set the scheduled mails to be merged to an invalid state; configure a merge mail template; load the merge mail information to the merge mail template; generate and send a merge mail according to the merge mail template. Among them, the client can be but is not limited to various personal computers, laptops, smart phones, tablet computers and portable wearable devices. The server can be implemented with an independent server or a server cluster composed of multiple servers. The present invention is described in detail below through specific embodiments.

[0037] See also Figure 2 As shown, Figure 2 A schematic flow chart of a timed mail merge method provided by an embodiment of the present invention. The timed mail merge method comprises the following steps:

[0038] S10: Obtain a number of scheduled emails to be merged and generate merged email information.

[0039] By searching or custom filtering, multiple scheduled emails that need to be merged are selected to provide data support for subsequent email merge operations. The merged email information is generated through the data instead of directly modifying the scheduled email information. It neither disrupts the progress of monitoring and alarm tasks nor requires complex and redundant read and write operations. It simplifies the difficulty of merging scheduled emails and realizes the simple merging of multiple scheduled emails.

[0040] Among them, Figure 3 As shown, step S10, that is, obtaining a number of scheduled emails to be merged and generating merged email information, includes the following steps S11-S13.

[0041] S11: Query and obtain information of several scheduled emails to be merged from a data source.

[0042] For step S11, the data source includes but is not limited to Excel tables, databases, etc. This embodiment takes the database as an example to illustrate the scheduled mail merging method. The scheduled mail information to be merged includes but is not limited to: the scheduled mail identification to be merged, the scheduled mail title to be merged, the sender of the scheduled mail to be merged, the recipient of the scheduled mail to be merged, the cc of the scheduled mail to be merged, the sending time of the scheduled mail to be merged, the body of the scheduled mail to be merged, the attachments of the scheduled mail to be merged, the activation status of the scheduled mail to be merged, and the trigger status of the scheduled mail to be merged.

[0043] Among them, the monitoring data table is associated with the body of the scheduled email to be merged or the attachment of the scheduled email to be merged, and the information in the monitoring data table can be displayed in the body or attachment of the scheduled email when it is sent. The data items of the monitoring data table include at least: monitoring task identification, monitoring task name, monitoring result; if the monitoring result is abnormal, the trigger status of the scheduled email to be merged is triggered, otherwise it is not triggered. The activation status of the scheduled email to be merged includes normal activation and invalidation. When it is normally activated, the trigger status of the scheduled email to be merged is triggered, and the scheduled email is sent according to the sending time of the scheduled email to be merged; when it is invalid, even if the trigger status of the scheduled email to be merged is triggered, the scheduled email to be merged cannot be triggered.

[0044] S12: According to the scheduled email information to be merged, setting the merged email information.

[0045] The merged email information includes: email identification, email title, email sender, email recipients, email carbon copy recipients, and email sending time.

[0046] It is understandable that the email ID, email sender and email recipient are necessary information and need to be set completely. The email ID can be automatically generated according to the program; the email title, email CC and email sending time are non-essential preset options. The email title, email sender, email recipient, CC and email sending time are all modifiable data and can be reset in the subsequent configuration and editing process to facilitate flexible adjustment according to needs.

[0047] Specifically, the merged email information further includes: email body. The email body is used to display the information of the monitoring task corresponding to the scheduled email to be merged.

[0048] S13: Create a new merged mail information table in the database, and write the merged mail information into the merged mail information table.

[0049] The merged mail information is stored in the database to facilitate reading and modifying the merged mail information, so as to provide data support for displaying the merged mail information on the page.

[0050] S20: Setting the scheduled email to be merged to an invalid state.

[0051] Setting the status of the pending merged email to an invalid state makes the pending merged email unable to be sent, avoiding the problem of repeated sending of the pending merged scheduled email and the merged email, making it easier to merge multiple pending merged scheduled emails into one merged email for sending, and enhancing the controllability of email management.

[0052] Among them, Figure 4 As shown, step S20, that is, setting the scheduled email to be merged to an invalid state, includes the following steps:

[0053] S21: Query the database for the activation status of the scheduled email to be merged.

[0054] S22: Setting the activation state to invalid, so that the scheduled email to be merged cannot be sent.

[0055] For steps S21-S22, the enabled state is set to invalid, and the scheduled email to be merged is in the disabled state. No matter the trigger state of the scheduled email to be merged is triggered or not triggered, that is, the corresponding monitoring task is abnormal or normal, the scheduled email to be merged cannot be sent.

[0056] S30: Configure the merge email template.

[0057] Configure the merge email template to provide a highly flexible definition space for the content and style of the merge email, so that the merge email can deliver information as needed.

[0058] Among them, Figure 5 As shown, step S30, namely configuring the merged email template, includes the following steps S31-S34.

[0059] S31: Generate a template data table in the database.

[0060] The structured space is used to save and manage the relevant information of the email template, providing a basis for the subsequent configuration and calling of the email template. It also facilitates data backup and recovery, improving the management efficiency and security of the email template data.

[0061] S32: defining and storing the format and structure of the merged mail template in the template data table.

[0062] Defining the format and structure of the email template directly in the template data table, such as the email header, body, footer, and the layout and style of each part, helps to quickly and accurately render an email template that meets the requirements.

[0063] S33: Generate an email editing page.

[0064] A visual email editing page is generated based on the defined email template format and structure, which allows users to preview, edit and modify email content through a graphical interface without having to directly operate codes or data tables, thereby improving the convenience and ease of use of email editing.

[0065] S34: Rendering the email editing page according to the format and structure of the merged email template, and generating corresponding information tags.

[0066] For example, an information tag is an email title input box, which is associated with the em_title field in the template data table. If there is preset content in the em_title field, the preset content can be mapped to the email title input box.

[0067] S40: Loading the merged email information into the merged email template.

[0068] The merged email information is loaded into the merged email template so that the merged email information is displayed on the email editing page to facilitate editing and modification of the merged email information.

[0069] Among them, Figure 6 As shown, step S40, that is, loading the merged email information into the merged email template, includes the following steps S41-S42.

[0070] S41: Query the content corresponding to the information tag from the merged mail information table.

[0071] S42: Replace the query result into the value of the template data table to update the template data table.

[0072] For steps S41-S42, the merged mail information table, the template data table and the information tag are sequentially associated to display the contents of the merged mail information table in the mail editing page. For example, the information tag "recipient" on the mail editing page is associated with the em_to field in the template data table. The mail recipient has been determined in the merged mail information table and is first updated to the em_to field in the template data table, so that it can be displayed in the information tag "recipient" when the page is rendered.

[0073] In addition to the merged email information, the body of the merged email can display the content of each email to be merged. More specifically, this embodiment uses the PeriodicTask table provided by the Django framework, which renders the content of the email to be merged into the merged email body information tag corresponding to the email editing page.

[0074] The PeriodicTask table is a database model provided by the Django-Celery-Beat extension, which is used to store and manage information about periodic tasks. The PeriodicTask table can be used to manage several emails to be merged. For example, the fields in the PeriodicTask table include task name (name), whether to schedule this scheduled task (enabled), email content (mail_content), email title (task_info), sender (mail_sender), recipient (mail_receivers), carbon copy (cc_to), scheduled task time (work_time), and scheduled task configuration parameters (kwargs). Several emails to be merged form a list, and the information of the emails to be merged is associated with the above fields. According to the field matching, the data can be directly displayed on the email editing page, and the contents of several emails to be merged are displayed in the form of a table.

[0075] S50: Generate and send a merge email according to the merge email template.

[0076] The complete merged email content is automatically generated using the configured merged email template and loaded merged email information. Subsequently, the system triggers the email sending mechanism to deliver the merged email to the designated recipient's mailbox. Merged emails reduce the number of scheduled emails sent, reduce server burden and network congestion, and reduce operating costs, thereby reducing the recipient's review burden and avoiding information confusion caused by the recipient's frequent handling of emails. Merged emails make the results of multiple monitoring tasks clear at a glance, which helps to conveniently analyze and compare monitoring data, optimize the workflow, and improve the efficiency of scheduled email processing. At the same time, merged emails are not limited to fixed content and sending time, and can flexibly adjust email content and format to meet the needs of different scenarios.

[0077] Among them, Figure 7 As shown, step S50, i.e. generating and sending a merged email according to the merged email template, includes the following steps:

[0078] S51: Determine whether the content of the information tag on the email editing page needs to be modified; if so, modify and update the template data table, and generate a merged email after the modification is completed; otherwise, generate a merged email.

[0079] S52: Confirm the content of the information tag.

[0080] S53: Sending the merged email to the email recipient according to the email sending time.

[0081] For steps S51-S52, the merged email before sending can be modified by the user, and the modified information is saved in the template data table. The template data table is updated through association operations to realize the change and storage of the merged email information, which is conducive to accurate archiving and facilitates subsequent operation, maintenance and search.

[0082] It can be seen that in the above scheme, by setting the status of the mail to be merged to an invalid state, the mail to be merged cannot be sent, and the content of the mail to be merged is configured to the merge mail template, and then the merge mail is generated. There is no need to change the content of the mail to be merged, which simplifies the difficulty of scheduled mail merging. By reducing the number of scheduled mails sent, the server burden and network congestion are reduced, and the operating costs are reduced, thereby reducing the review burden of the recipient and avoiding information confusion caused by the recipient's frequent processing of mails. The merged mail makes the results of multiple monitoring tasks clear at a glance, which helps to conveniently analyze and compare monitoring data, optimizes the workflow, and improves the efficiency of scheduled mail processing. At the same time, the merged mail is not limited to fixed content and sending time, and can flexibly adjust the mail content and format to meet the needs of different scenarios.

[0083] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0084] In one embodiment, the present invention provides a timed mail merging device, which corresponds one-to-one to the timed mail merging method in the above embodiment. Figure 8 As shown, the timed mail merging device includes. The detailed description of each functional module is as follows:

[0085] The acquisition module 101 acquires a number of scheduled emails to be merged and generates merged email information.

[0086] The disabling module 102 sets the scheduled email to be merged to an invalid state.

[0087] Configuration module 103, configures the merged email template.

[0088] The loading module 104 loads the merged email information into the merged email template.

[0089] The generating module 105 generates and sends a merged email according to the merged email template.

[0090] In one embodiment, the acquisition module 101 is specifically configured to:

[0091] Query and obtain information of several scheduled emails to be merged from the data source;

[0092] According to the scheduled email information to be merged, setting the merged email information;

[0093] A new merge mail information table is created in the database, and the merge mail information is written into the merge mail information table.

[0094] The merged email information includes: email identification, email title, email sender, email recipients, email carbon copy recipients, and email sending time.

[0095] In one embodiment, the disabling module 102 is specifically configured to:

[0096] Querying the database for the activation status of the scheduled email to be merged;

[0097] The enabling state is set to invalid, so that the scheduled mail to be merged cannot be sent.

[0098] In one embodiment, the configuration module 103 is specifically configured to:

[0099] Generate a template data table in the database;

[0100] Defining and storing the format and structure of the merge mail template in the template data table;

[0101] Generate email editing page;

[0102] The email editing page is rendered according to the format and structure of the merged email template, and corresponding information tags are generated.

[0103] In one embodiment, the loading module 104 is specifically used to:

[0104] Query the content corresponding to the information tag from the merged mail information table;

[0105] The query results are replaced into the values ​​of the template data table to update the template data table.

[0106] In one embodiment, the generating module 105 is specifically configured to:

[0107] Determine whether the content of the information tag on the email editing page needs to be modified; if so, modify and update the template data table, and generate a merged email after the modification is completed; otherwise, generate a merged email;

[0108] confirming the content of the information label;

[0109] The merged email is sent to the email recipient according to the email sending time.

[0110] The specific definition of the scheduled mail merge device can be found in the definition of the scheduled mail merge method above, which will not be repeated here. Each module in the above-mentioned scheduled mail merge device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0111] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Fig. 9 As shown. The computer device includes a processor, a memory, a network interface and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client through a network connection. When the computer program is executed by the processor, the functions or steps of a server of a timed mail merge method are implemented.

[0112] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as follows: Fig.10 As shown. The computer device includes a processor, a memory, a network interface, a display screen and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, the functions or steps on the client side of a timed mail merge method are implemented.

[0113] In one embodiment, 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 implements the following steps when executing the computer program:

[0114] Get several scheduled emails to be merged and generate merged email information;

[0115] Setting the scheduled email to be merged to an invalid state;

[0116] Configure the mail merge template;

[0117] Loading the merged mail information into the merged mail template;

[0118] Generate and send a merge mail according to the merge mail template.

[0119] In one embodiment, a computer readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0120] Get several scheduled emails to be merged and generate merged email information;

[0121] Setting the scheduled email to be merged to an invalid state;

[0122] Configure the mail merge template;

[0123] Loading the merged mail information into the merged mail template;

[0124] Generate and send a merge mail according to the merge mail template.

[0125] It should be noted that the above functions or steps that can be implemented by the computer-readable storage medium or computer device can refer to the relevant description in the aforementioned method embodiment. In order to avoid repetition, they will not be described one by one here.

[0126] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0127] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0128] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A timed mail merge method, characterized in that: include: Get several scheduled emails to be merged and generate merged email information; Setting the scheduled email to be merged to an invalid state; Configure the mail merge template; Loading the merged mail information into the merged mail template; Generate and send a merge mail according to the merge mail template.

2. The timed mail merging method according to claim 1, characterized in that: The step of obtaining a plurality of scheduled emails to be merged and generating merged email information includes: Query and obtain information of several scheduled emails to be merged from the data source; According to the scheduled email information to be merged, setting the merged email information; A new merge mail information table is created in the database, and the merge mail information is written into the merge mail information table.

3. The timed mail merging method according to claim 2, characterized in that: The merged email information includes: email identification, email title, email sender, email recipients, email carbon copy recipients, and email sending time.

4. The timed mail merging method according to claim 3, characterized in that: The step of setting the scheduled email to be merged to an invalid state includes: Querying the database for the activation status of the scheduled email to be merged; The enabling state is set to invalid, so that the scheduled mail to be merged cannot be sent.

5. The timed mail merging method according to claim 4, characterized in that: The configuration of the merged email template includes: Generate a template data table in the database; Defining and storing the format and structure of the merged mail template in the template data table; Generate email editing page; The email editing page is rendered according to the format and structure of the merged email template, and corresponding information tags are generated.

6. The timed mail merging method according to claim 5, characterized in that: The step of loading the merged email information into the merged email template includes: Query the content corresponding to the information tag from the merged mail information table; The query results are replaced into the values ​​of the template data table to update the template data table.

7. The timed mail merging method according to claim 6, characterized in that: The step of generating and sending a merged email according to the merged email template includes: Determine whether the content of the information tag on the email editing page needs to be modified; if so, modify and update the template data table, and generate a merged email after the modification is completed; otherwise, generate a merged email; confirming the content of the information label; The merged email is sent to the email recipient according to the email sending time.

8. A timed mail merging device, characterized in that: include: The acquisition module acquires several scheduled emails to be merged and generates merged email information; A disabling module is used to set the scheduled email to be merged to an invalid state; Configuration module, configure the merge email template; A loading module is used to load the merged mail information into the merged mail template; A generation module generates and sends a merged email according to the merged email template.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the scheduled mail merge method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the scheduled mail merge method according to any one of claims 1 to 7 are implemented.

Images