Outbound Message Processing Method, Device, Storage Medium, and Electronic Device

Abstract

The present application discloses a method and apparatus for processing outbound messages, a storage medium, and an electronic device. The method includes pre-configuring an outbound message, where the outbound message at least includes an outbound message type; when an outbound message event is triggered by a service, an outbound message service is called according to the outbound message type matching the outbound message event to send a message to a third-party service for docking with the third-party service. The present application solves the technical problem that outbound messages cannot be customized and need secondary development to meet the requirements of third-party systems. Through the interface standards and specifications provided by the outbound messages in the present application, documents and business object data can be linked with a third party under certain conditions, and system docking can be quickly achieved without secondary development.

Description

Technical Field

[0001] This application relates to the field of outbound message processing. Specifically, it relates to an outbound message processing method, device, storage medium, and electronic device. Background Art

[0002] Saas products face multiple enterprises, and different enterprises have different integration requirements. To improve the docking efficiency and reduce the docking cost, the technical solution of outbound messages can be used to meet the requirements of the docking between enterprise Saas products and third-party systems.

[0003] Regarding the problem that outbound messages in the related art cannot be customized and configured and require secondary development to meet the needs of third-party systems, no effective solution has been proposed yet. Summary of the Invention

[0004] The main purpose of this application is to provide an outbound message processing method, device, storage medium, and electronic device to solve the problem that outbound messages cannot be customized and configured and require secondary development to meet the needs of third-party systems.

[0005] To achieve the above purpose, according to one aspect of this application, an outbound message processing method is provided.

[0006] The outbound message processing method according to this application includes:

[0007] Pre-configure outbound messages, where the outbound messages at least include outbound message types;

[0008] When an outbound message event is triggered by a business service, call the outbound message service to send a message to a third-party service according to the outbound message type matching the outbound message event for docking with the third-party service.

[0009] Furthermore, the outbound message types at least include one of the following: approval event, business object data change, message center, lending-related.

[0010] Among them, the approval event includes to-be-approved, approved, reminder, rejected, copied, to-be-paid, paid. An outbound message is triggered and generated through a business service. For the message generation of the approval event of the outbound message, it is generated according to global fields, and the global fields are generated based on user-defined configurations and are automatically rendered as corresponding message contents according to the global fields selected in the outbound message configuration when the outbound message event is triggered.

[0011] The business object data change includes the addition and change of business objects, and an outbound message is triggered through an outbound message event when there is a change. [[ID=3⑧]]

[0012] The message center includes an Ebot node based on the approval process. After configuring the outbound message at the Ebot interface and when the approval process of the document flows to the Ebot node, it is triggered.

[0013] The loan-related items include manual repayment, repayment reminder, and repayment write-off, which are triggered by outbound message events and generate outbound messages.

[0014] Further, the message center includes an Ebot node based on the approval process, which is used to select the outbound message of the Ebot category and trigger the outbound message when the document approval process flows to the corresponding Ebot node.

[0015] Further, the outbound message is pre-configured. Among them, the outbound message at least includes the outbound message type, and also includes:

[0016] Configure the Url called in the outbound message as the third-party callback address;

[0017] Configure the signature secret key in the outbound message as the authentication credential for both parties' interfaces, which cannot be modified;

[0018] Configure the document fields to be sent selected in the outbound message as user-defined global fields, and render the corresponding message when triggered;

[0019] Configure the success status code in the outbound message, including the http status code;

[0020] Configure the keyword matching in the outbound message. After it is enabled, if the response message contains the set keyword, it is considered that the response is successful;

[0021] Configure the recalculation times in the outbound message for the number of retries after failure;

[0022] Configure the network interval duration in the outbound message for the interval duration of retries;

[0023] Configure the data structure in the outbound message to generate a message according to the configuration.

[0024] Further, after the outbound message event is triggered by the business service, the outbound message service is called according to the outbound message type matching the outbound message event to send the message to the third-party service for docking with the third-party service, including:

[0025] According to the interface specifications and standards set by the outbound message, the generated outbound message event is parsed by a preset trigger to obtain user-defined global fields, and a message is generated and sent to the third party again when the business document and business object data meet the conditions.

[0026] Further, after the outbound message event is triggered by the business service, an outbound message service is called according to the outbound message type matching the outbound message event to send a message to a third-party service for docking with the third-party service, including:

[0027] The outbound message trigger automatically sends a Post interface request to the third-party service through a message generated by user-defined fields, and monitors the situation where the third-party service can be called on the monitoring page.

[0028] Further, after the outbound message event is triggered by the business service, an outbound message service is called according to the outbound message type matching the outbound message event to send a message to a third-party service for docking with the third-party service, and further includes:

[0029] Obtain the message sending details according to the message parameters, and manually retry the failed message;

[0030] And view the call record of the outbound message service according to the outbound message type in the message log.

[0031] To achieve the above object, according to another aspect of the present application, an outbound message processing device is provided.

[0032] The outbound message processing device according to the present application includes:

[0033] A configuration module for pre-configuring an outbound message, where the outbound message at least includes an outbound message type;

[0034] A docking module for, after the outbound message event is triggered by the business service, calling an outbound message service according to the outbound message type matching the outbound message event for docking with a third-party service.

[0035] In the embodiment of the present application, by adopting the method of pre-configuring the outbound message, after the outbound message event is triggered by the business service, an outbound message service is called according to the outbound message type matching the outbound message event to send a message to the third-party service for docking with the third-party service, achieving the purpose of linking documents and business object data with the third party under certain conditions through the interface standards and specifications provided by the outbound message, thus realizing the technical effect that the outbound message trigger automatically sends a Post interface request to an external system through a message generated by user-defined fields, and further solving the technical problem that the outbound message cannot be customized and requires secondary development to meet the requirements of the third-party system. Description of the Drawings

[0036] The accompanying drawings, which form a part of this application, are used to provide a further understanding of this application, making other features, objectives, and advantages of this application more apparent. The schematic embodiments and descriptions of the accompanying drawings of this application are used to explain this application and do not constitute an improper limitation of this application. In the drawings:

[0037] Figure 1 is a schematic flowchart of an outbound message processing method according to an embodiment of this application;

[0038] Figure 2 is a schematic structural diagram of an outbound message processing device according to an embodiment of this application;

[0039] Figure 3 is a business architecture diagram in the outbound message processing method according to an embodiment of this application;

[0040] Figure 4 is a schematic flowchart of an outbound message triggering process in the outbound message processing method according to an embodiment of this application;

[0041] Figure 5 is a schematic diagram of the call relationship between outbound message systems in the outbound message processing method according to an embodiment of this application;

[0042] Figure 6 is a schematic diagram of a repeated request for an outbound message service in the outbound message processing method according to an embodiment of this application. Detailed implementation manners

[0043] In order to enable those skilled in the art of this technology to better understand the solution of this application, the following will clearly and completely describe the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

[0044] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned accompanying drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances for the embodiments of this application described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units does not necessarily need to be limited to those clearly listed steps or units, but may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or devices.

[0045] In this application, the orientation or positional relationship indicated by terms such as "upper", "lower", "left", "right", "front", "rear", "top", "bottom", "inner", "outer", "middle", "vertical", "horizontal", "lateral", "longitudinal", etc. is based on the orientation or positional relationship shown in the drawings. These terms are mainly used to better describe this application and its embodiments, and are not used to limit that the indicated devices, elements or components must have a specific orientation, or be constructed and operated in a specific orientation.

[0046] Moreover, in addition to being able to represent the orientation or positional relationship, some of the above terms may also be used to represent other meanings. For example, the term "upper" may also be used to represent a certain attachment relationship or connection relationship in some cases. For those of ordinary skill in the art, the specific meanings of these terms in this application can be understood according to specific circumstances.

[0047] In addition, the terms "install", "set", "be provided with", "connect", "be connected", "be sleeved" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral structure; it can be a mechanical connection or an electrical connection; it can be directly connected, or indirectly connected through an intermediate medium, or there is an internal connection between two devices, elements or components. For those of ordinary skill in the art, the specific meanings of the above terms in this application can be understood according to specific circumstances.

[0048] It should be noted that, without conflict, the embodiments in this application and the features in the embodiments can be combined with each other. The following will refer to the drawings and combine with embodiments to detail this application.

[0049] As Figure 1 shown, the method includes the following steps S110 to step S120:

[0050] Step S110, pre-configure an outbound message, where the outbound message at least includes an outbound message type.

[0051] The outbound message at least includes an outbound message type to obtain a pre-configured outbound message. At the same time, it should be noted that the pre-configured outbound message is user-defined. First, at the outbound message entry, and by setting in the system, select the outbound message to create a new outbound message.

[0052] After that, select the outbound message category, such as: approval event. And the following parameters can be configured:

[0053] a, the called Url: the third-party callback address.

[0054] b, the signature secret key: the credential for mutual interface authentication, which cannot be modified.

[0055] c. Select the document fields to be sent: globally defined fields customized by the user, and render the corresponding message when triggered.

[0056] d. Success status code: HTTP status code, supporting 204, 200, 201.

[0057] e. Keyword matching: After enabling, only when the set keyword exists in the response message is the response considered successful.

[0058] f. Number of recalculations: The number of retries after failure.

[0059] g. Network interval duration: The interval duration for retries, up to 10 seconds.

[0060] h. Data structure: Generate messages according to the configuration.

[0061] Finally, verify whether the third-party interface is unblocked, and generate the metadata of the outbound message configuration after saving.

[0062] Through the interface standards and specifications provided by the outbound message, the document and business object data are linked with the third party under certain conditions, and the docking between systems can be quickly realized without secondary development.

[0063] Step S120, when the outbound message event is triggered by the business service, call the outbound message service to send a message to the third-party service according to the outbound message type matching the outbound message event, so as to dock with the third-party service.

[0064] When the outbound message event is triggered by the business service, call the outbound message service to send a message to the third-party service according to the outbound message type matching the outbound message event. For example, when events such as to-do, processed, rejected, and paid of the document match the events selected by the outbound message, the message is automatically sent to the third-party interface.

[0065] After calling the outbound message service to send a message to the third-party service, it can be used to dock with the third-party service.

[0066] From the above description, it can be seen that the present application has achieved the following technical effects:

[0067] By adopting the method of pre-configuring outbound messages, when an outbound message event is triggered by a business service, the outbound message service is called according to the outbound message type that matches the outbound message event to send a message to a third-party service for docking with the third-party service, thereby achieving the purpose of linking the document and business object data with the third party under the conditions provided by the interface standards and specifications provided by the outbound message, thereby realizing the technical effect of the outbound message trigger automatically sending a Post interface request to the external system through the message generated by the user-defined field, thereby solving the technical problem that the outbound message cannot be customized and requires secondary development to meet the needs of the third-party system.

[0068] As a preference in this embodiment, the outbound message type includes at least one of the following: approval events, business object data changes, message center, and loan related, wherein the approval events include pending approval, approved, urged, rejected, copied, pending payment, and paid, which are triggered and generate outbound messages through business services, and the message generation of the approval event of the outbound message is generated based on global fields, and the global fields are generated based on user-defined configurations, and are automatically rendered as corresponding message content according to the global fields selected in the outbound message configuration when the outbound message event is triggered; the business object data changes include the addition and change of business objects, which trigger outbound messages through outbound message events; the message center includes an Ebot node based on the approval flow, which is triggered after the outbound message is configured on the Ebot interface and when the approval flow of the document flows to the Ebot node; the loan related includes manual repayment, repayment reminder, and repayment cancellation, which are triggered and generate outbound messages through outbound message events.

[0069] When implementing it specifically, Figure 3 As shown, approval events, business object change events, and Ebot approval events are triggered by business services, calling the RPC interface provided by the outbound message service. The outbound message service completes the connection with the third-party service interface.

[0070] Event types supported by outbound messages include but are not limited to:

[0071] Ebot refers to the Ebot node in the approval flow. After the outbound message is configured on the ebot interface, it is triggered when the document approval flow is transferred to this node.

[0072] Approval events include, but are not limited to, triggering outbound messages such as pending approval, approved, urged, rejected, copied, pending payment, and paid.

[0073] Business object changes include, but are not limited to, business object additions and change events triggering outbound messages.

[0074] The borrowing events include, but are not limited to, outbound messages triggered by events such as manual repayment, repayment reminder, and repayment write-off.

[0075] Preferably in this embodiment, the message center includes an Ebot node based on the approval process, which is used to select outbound messages of the Ebot category and trigger outbound messages when the document approval process flows to the corresponding Ebot node.

[0076] In specific implementation, based on the Ebot node (Ebot event) of the approval process, outbound messages of the Ebot category are selected, and outbound messages are triggered when the document approval process flows to the corresponding Ebot node.

[0077] Preferably in this embodiment, the outbound messages are pre-configured. Among them, the outbound messages at least include the outbound message type, and also include: configuring the Url called in the outbound message as the third-party callback address; configuring the signature secret key in the outbound message as the credential for bilateral interface authentication, which cannot be modified; configuring the document fields to be sent selected in the outbound message as user-defined global fields, and rendering the corresponding message when triggered; configuring the successful status code in the outbound message, including the http status code; configuring the keyword matching in the outbound message, and if there is a set keyword in the response message after it is enabled, the response is considered successful; configuring the number of recalculation times in the outbound message for the number of retries after failure; configuring the network interval duration in the outbound message for the interval duration of retries; configuring the data structure in the outbound message for generating the message according to the configuration.

[0078] In specific implementation, by pre-configuring the outbound messages, the called Url, signature secret key, selected document fields to be sent, successful status code (http status code, supporting 204, 200, 201), keyword matching, number of recalculation times, network interval duration (interval duration of retries, up to 10 seconds), data structure, etc. can be obtained.

[0079] Furthermore, data structure: The message generated according to the configuration (this message can be generated according to user-defined) has the following format:

[0080]

[0081]

[0082]

[0083] Preferably in this embodiment, after the outbound message event is triggered by the service, the outbound message service is called according to the outbound message type matching the outbound message event to send a message to the third-party service for docking with the third-party service, including: according to the interface specifications and standards set for the outbound message, the generated outbound message event is parsed by a preset trigger to obtain user-defined global fields, and a message is regenerated and sent to the third party when the business document and business object data meet the conditions.

[0084] In specific implementation, the generated outbound message event is parsed by a preset trigger to obtain user-defined global fields, and a message is regenerated and sent to the third party when the business document and business object data meet the conditions. The message generation of the outbound message approval event is generated according to the global fields, where the global fields are generated by user-defined configuration and are automatically rendered as the corresponding message content according to the global fields selected in the outbound message configuration when the outbound message event is triggered, and various scenarios of system docking can be satisfied without secondary development.

[0085] Preferably in this embodiment, after the outbound message event is triggered by the service, the outbound message service is called according to the outbound message type matching the outbound message event to send a message to the third-party service for docking with the third-party service, including: the outbound message trigger automatically sends a Post interface request to the third-party service through the message generated by the user-defined field, and the situation of the callable third-party service can be monitored on the monitoring page.

[0086] In specific implementation, after the subscription event is triggered, the outbound message trigger automatically sends a Post interface request to the external system through the message generated by the user-defined field, and the callable situation can be monitored on the monitoring page.

[0087] Preferably in this embodiment, after the outbound message event is triggered by the service, the outbound message service is called according to the outbound message type matching the outbound message event to send a message to the third-party service for docking with the third-party service, further including: obtaining the message sending details according to the message parameters, and manually retrying the failed message;

[0088] And, viewing the call record of the outbound message service according to the outbound message type in the message log.

[0089] In specific implementation, the message sending details can be seen in the parameters, and the failed ones can be manually retried. The outbound message call record can be viewed in the message log.

[0090] It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0091] According to an embodiment of the present application, there is also provided an outbound message processing device 200 for implementing the above method, as Figure 2 shown, the device includes:

[0092] A configuration module 210, configured to pre-configure an outbound message, where the outbound message at least includes an outbound message type;

[0093] A docking module 220, configured to, after an outbound message event is triggered by a service, call an outbound message service according to the outbound message type matching the outbound message event for docking with a third-party service.

[0094] In the configuration module 210 in the embodiment of the present application, the outbound message at least includes an outbound message type to obtain a pre-configured outbound message. At the same time, it should be noted that the pre-configured outbound message is user-defined. First, at the outbound message entry, and by selecting the outbound message in the system settings, an outbound message can be newly created.

[0095] After that, select the outbound message category, such as: approval event. And the following parameters can be configured:

[0096] a. The called Url: the third-party callback address.

[0097] b. The signature secret key: the credential for authentication of both interfaces, which cannot be modified.

[0098] c. Select the document fields to be sent: user-defined global fields, and render the corresponding message when triggered.

[0099] d. The successful status code: the http status code, supporting 204, 200, 201.

[0100] e. Keyword matching: After enabling, only when the set keyword exists in the response message is the response considered successful.

[0101] f. The number of recalculation times: the number of times to retry after failure.

[0102] g. The network interval duration: the interval duration for retry, up to 10 seconds.

[0103] h. The data structure: generate a message according to the configuration.

[0104] Finally, verify whether the third-party interface is unblocked, and generate the metadata of the outbound message configuration after saving.

[0105] The interface standards and specifications provided through outbound messages enable the linkage of documents and business object data with third parties under certain conditions, allowing for the rapid implementation of system docking without secondary development.

[0106] In the docking module 220 of the embodiments of the present application, when the outbound message event is triggered by a business service, the outbound message service is called according to the outbound message type that matches the outbound message event to send a message to a third-party service. For example, when events such as the to-do, processed, rejected, and paid events of a document match the events selected by the outbound message, a message is automatically sent to the third-party interface.

[0107] After calling the outbound message service to send a message to a third-party service, it can be used to dock with the third-party service.

[0108] Obviously, those skilled in the art should understand that the various modules or steps of the present application described above can be implemented using a general-purpose computing device. They can be concentrated on a single computing device or distributed across a network composed of multiple computing devices. Optionally, they can be implemented using program code executable by the computing device, so that they can be stored in a storage device and executed by the computing device, or they can be separately fabricated into individual integrated circuit modules, or multiple modules or steps among them can be fabricated into a single integrated circuit module for implementation. In this way, the present application is not limited to any specific combination of hardware and software.

[0109] Figure 3 It is the business architecture diagram in the outbound message processing method according to the embodiments of the present application. The outbound message event includes approval events, business object data changes, message centers, and lending-related matters.

[0110] When an approval event, business object data change, message center, or lending-related matter in the outbound message event is triggered by a business service, the outbound message service is called according to the outbound message type that matches the outbound message event to send a message to a third-party service for docking with the third-party service.

[0111] Figure 4 It is the schematic diagram of the outbound message triggering process in the outbound message processing method according to the embodiments of the present application. Figure 5 It is the schematic diagram of the call relationship between outbound message systems in the outbound message processing method according to the embodiments of the present application.

[0112] Outbound message nodes of the approval flow Ebot, approval events, business object changes, and outbound message events related to lending start the outbound message service.

[0113] The outbound information service will be logged.

[0114] After a request is sent to a third-party interface, the number of retries is recorded. Figure 6 It is a schematic diagram of repeated requests of the outbound message service in the outbound message processing method according to an embodiment of the present application, specifically including:

[0115] 1. The returned status code is a status code selected from (200, 201, 204);

[0116] 2. Whether the keyword configured by the user is matched in the returned message.

[0117] An embodiment of the present application also provides a storage medium, in which a computer program is stored, and the computer program is set to execute the steps in any one of the above method embodiments when running.

[0118] Optionally, in this embodiment, the above storage medium may be set to store a computer program for executing the following steps:

[0119] S1, pre-configure an outbound message, where the outbound message includes at least an outbound message type;

[0120] S2, when an outbound message event is triggered by a business service, call an outbound message service to send a message to a third-party service according to the outbound message type matching the outbound message event for docking with the third-party service.

[0121] Optionally, in this embodiment, the above storage medium may include, but is not limited to: various media such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disc that can store a computer program.

[0122] An embodiment of the present application also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is set to run the computer program to execute the steps in any one of the above method embodiments.

[0123] Optionally, the above electronic device may further include a transmission device and an input / output device, where the transmission device is connected to the above processor, and the input / output device is connected to the above processor.

[0124] Optionally, in this embodiment, the above processor may be set to execute the following steps through a computer program:

[0125] S1, pre-configure an outbound message, where the outbound message includes at least an outbound message type;

[0126] S2. After the outbound message event is triggered by the business service, call the outbound message service according to the outbound message type that matches the outbound message event to send a message to the third-party service for docking with the third-party service.

[0127] Optionally, for specific examples in this embodiment, reference may be made to the examples described in the above embodiments and optional implementation manners, and details are not described herein again.

[0128] The foregoing are only preferred embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the protection scope of the present application.

Claims

1. A method for processing outbound messages, characterized in that The method includes: Pre-configuring an outbound message, where the outbound message at least includes an outbound message type; after an outbound message event is triggered by a business service, an outbound message service is called according to the outbound message type matching the outbound message event to send a message to a third-party service for docking with the third-party service; The outbound message type at least includes one of the following: approval event, business object data change, message center, lending-related; Among them, the approval event includes to-be-approved, approved, reminder, rejection, carbon copy, to-be-paid, paid. An outbound message is triggered and generated by a business service. The message for the approval event of the outbound message is generated according to global fields, and the global fields are generated based on user-defined configurations, and are automatically rendered as corresponding message contents according to the global fields selected in the outbound message configuration when the outbound message event is triggered; The business object data change includes that an outbound message is triggered by an outbound message event when a business object is newly added or changed; The message center includes, based on an approval flow Ebot node, after configuring an outbound message in the Ebot interface, and when the approval flow of a document flows to the Ebot node, it is triggered; The lending-related includes manual repayment, repayment reminder, repayment write-off, and an outbound message is triggered and generated by an outbound message event; The message center includes, based on an approval flow Ebot node, for selecting an outbound message of the Ebot category, and triggering an outbound message when the document approval flow reaches the corresponding Ebot node; The outbound message at least includes an outbound message type, and further includes: Configuring the Url called in the outbound message as a third-party callback address; Configuring the signature secret key in the outbound message as a credential for mutual interface authentication, which cannot be modified; Configuring the selected document fields to be sent in the outbound message as user-defined global fields, and rendering corresponding messages when triggered; Configuring the success status code in the outbound message, including the http status code; Configuring keyword matching in the outbound message, which is used to consider the response successful if the set keyword exists in the response message after it is enabled; Configuring the number of recalculations in the outbound message, which is used for the number of retries after failure; Configuring the network interval duration in the outbound message, which is used for the interval duration of retries; Configuring the data structure in the outbound message, which is used to generate a message according to the configuration.

2. The method according to claim 1, wherein After the outbound message event is triggered by a business service, calling an outbound message service according to the outbound message type matching the outbound message event to send a message to a third-party service for docking with the third-party service includes: According to the interface specifications and standards set in the outbound message, the generated outbound message event is parsed by a preset trigger to obtain user-defined global fields, and a message is generated and sent to the third party again when the business document and business object data meet the conditions.

3. The method according to claim 1, wherein After the outbound message event is triggered by a business service, calling an outbound message service according to the outbound message type matching the outbound message event to send a message to a third-party service for docking with the third-party service includes: The outbound message trigger automatically sends a Post interface request to a third-party service through the message generated by user-defined fields, and the situation of calling the third-party service can be monitored on the monitoring page.

4. The method according to claim 1, wherein When the outbound message event is triggered by the business service, the outbound message service is called according to the outbound message type matching the outbound message event to send the message to the third-party service for docking with the third-party service. It further includes: Obtaining the message sending details according to the message parameters, and manually retrying the failed messages; And viewing the call records of the outbound message service by the outbound message type according to the message log.

5. An outbound message processing device, characterized in that a configuration module for pre-configuring outbound messages, where the outbound messages at least include outbound message types; a docking module for, when the outbound message event is triggered by the business service, calling the outbound message service according to the outbound message type matching the outbound message event for docking with the third-party service; the outbound message types at least include one of the following: approval event, business object data change, message center, loan-related; wherein, the approval event includes to-be-approved, approved, reminder, rejected, copied, to-be-paid, paid. The outbound message is triggered by the business service and generated. The message for the approval event of the outbound message is generated according to the global fields, and the global fields are generated based on user-defined configurations, and are automatically rendered as the corresponding message content according to the global fields selected in the outbound message configuration when the outbound message event is triggered; the business object data change includes adding a business object and triggering an outbound message when the business object is changed; the message center includes based on the approval flow Ebot node, after configuring the outbound message in the Ebot interface, and triggering when the approval flow of the document flows to the Ebot node; the loan-related includes manual repayment, repayment reminder, repayment write-off, and triggers an outbound message through the outbound message event; the message center includes based on the approval flow Ebot node, for selecting the outbound message of the Ebot category, and triggering the outbound message when the document approval flow reaches the corresponding Ebot node; the outbound message at least includes the outbound message type, and further includes: configuring the Url called in the outbound message as the third-party callback address; configuring the signature secret key in the outbound message as the authentication credential for both interfaces, which cannot be modified; configuring the selected document fields to be sent in the outbound message as user-defined global fields, and rendering the corresponding message when triggered; configuring the success status code in the outbound message, including the http status code; configuring the keyword matching in the outbound message, and considering the response successful if the set keyword exists in the response message after it is enabled; configuring the recalculation times in the outbound message for the number of retries after failure; configuring the network interval duration in the outbound message for the interval duration of retries; configuring the data structure in the outbound message for generating the message according to the configuration.

6. A computer-readable storage medium, characterized in that, A computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute the method according to any one of claims 1 to 4 when running.

7. An electronic device, comprising a memory and a processor, characterized in that, A computer program is stored in the memory, and the processor is configured to run the computer program to execute the method according to any one of claims 1 to 4.

Images