A document business processing method and device based on rule configuration and process linkage
Patent Information
- Application Number
- CN202610793315.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-06-03
- Publication Date
- 2026-10-16
AI Technical Summary
[0003]境内外机构之间没有直接的业务系统联动,现有技术中信息传递通常依赖由环球银行金融电信协会网络传输的报文方式进行交互,且每个处理环节需要固定的人工或半人工操作,缺乏可配置的自动化联动机制
[0008] According to another aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements any of the document business processing methods based on rule configuration and process linkage provided in the embodiments of this application.
Smart Images

Figure CN122928241A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology and can be applied to the field of financial technology. Specifically, it relates to a method and apparatus for processing document business based on rule configuration and process linkage. Background Technology
[0002] In the banking system view, the documentation system is primarily responsible for managing the entire lifecycle of international settlement and trade finance products, serving as the unified operation and management platform for the bank's documentation business. International settlement and trade finance product business processes are characterized by cross-border interaction of transaction information and numerous subsequent transaction stages.
[0003] There is no direct business system linkage between domestic and foreign institutions. In the existing technology, information transmission usually relies on message transmission through the SWIFT network for interaction, and each processing link requires fixed manual or semi-manual operation, lacking a configurable automated linkage mechanism. Summary of the Invention
[0004] This application provides a document business processing method and apparatus based on rule configuration and process linkage, so as to realize the configurable customization of linkage processing logic under different business scenarios, reduce manual data entry and information waiting time, and improve the efficiency of document business processing.
[0005] According to one aspect of this application, a method for document processing based on rule configuration and process linkage is provided, the method comprising: Based on the current transaction type and current transaction context information of the current document business, determine the target linkage business scenario identifier that matches the current document business; Based on the target linkage business scenario identifier, at least two target linkage business process rules corresponding to the target linkage business scenario identifier are determined from the pre-configured linkage business process rule library. For each target linkage business process rule, based on the process work item identifier of the target linkage business process rule, at least one linkage business processing action corresponding to the process work item identifier is determined from the pre-configured linkage business processing rule library. Based on the processing type of the linked business processing action and the atomic service it points to, the corresponding atomic service is invoked to execute the linked business processing operation.
[0006] According to another aspect of this application, a document processing device based on rule configuration and process linkage is provided, the device comprising: The target linkage business scenario identification determination module is used to determine the target linkage business scenario identification that matches the current document business based on the current transaction type and current transaction context information of the current document business. The target linkage business process rule determination module is used to determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier from a pre-configured linkage business process rule library based on the target linkage business scenario identifier. The linkage business processing action determination module is used to determine at least one linkage business processing action corresponding to the process work item identifier from a pre-configured linkage business processing rule library for each target linkage business process rule, based on the process work item identifier of the target linkage business process rule. The linkage business processing operation execution module is used to call the corresponding atomic service to execute the linkage business processing operation based on the processing type of the linkage business processing action and the atomic service it points to.
[0007] According to another aspect of this application, an electronic device is provided, the electronic device comprising: One or more processors; Memory, used to store one or more programs; When one or more programs are executed by one or more processors, the one or more processors implement any of the document processing methods based on rule configuration and process linkage provided in the embodiments of this application.
[0008] According to another aspect of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements any of the document business processing methods based on rule configuration and process linkage provided in the embodiments of this application.
[0009] According to another aspect of this application, a computer program product is provided, including a computer program that, when executed by a processor, implements any of the document processing methods based on rule configuration and process linkage provided in the embodiments of this application.
[0010] This application determines a target linkage business scenario identifier that matches the current document business based on the current transaction type and current transaction context information; based on the target linkage business scenario identifier, it determines at least two target linkage business process rules corresponding to the target linkage business scenario identifier from a pre-configured linkage business process rule library; for each target linkage business process rule, it determines at least one linkage business processing action corresponding to the process work item identifier from a pre-configured linkage business processing rule library based on the process work item identifier of the target linkage business process rule; and based on the processing type and atomic service pointer of the linkage business processing action, it calls the corresponding atomic service to execute the linkage business processing operation. The above solution enables customization of international business scenarios involving internal and external collaboration through rule-based configuration. By driving internal and external collaboration in document processing with rules and atomic execution, it allows for configurable customization of the collaborative processing logic under different business scenarios. After processing a transaction in a scenario, it can automatically trigger the registration of pre-transaction information for the target transaction, automatically preparing the transaction site in advance. Business preparation can begin without waiting for messages to arrive, effectively shortening the overall processing time. It also enables mutual information retrieval between domestic and international parties in cases of disputed terms, reducing manual entry and information waiting time, and improving the efficiency of document processing. Furthermore, when the rules are clear, it can automatically complete the processing of the target transaction, reducing the sending and receiving of messages in internal and external collaboration scenarios within the group, lowering message costs for users, and ultimately reducing costs and increasing efficiency for them. Attached Figure Description
[0011] Figure 1 This is a flowchart of a document processing method based on rule configuration and process linkage provided in Embodiment 1 of this application; Figure 2 This is a flowchart of a document processing method based on rule configuration and process linkage, according to Embodiment 2 of this application; Figure 3 This is a schematic diagram of a document processing device based on rule configuration and process linkage, according to Embodiment 3 of this application. Figure 4 This is a schematic diagram of the structure of an electronic device that implements the document business processing method based on rule configuration and process linkage according to Embodiment 4 of this application. Detailed Implementation
[0012] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.
[0013] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0014] Furthermore, it should be noted that the information collected in the technical solution of this application is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data all comply with the relevant laws, regulations and standards of the relevant countries and regions, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Corresponding operation portals are provided for users to choose to authorize or refuse.
[0015] Example 1 Figure 1 This is a flowchart illustrating a document processing method based on rule configuration and process linkage according to Embodiment 1 of this application. This embodiment is applicable to document processing based on rule configuration and supporting full-scenario internal and external process linkage. It can be executed by a document processing device based on rule configuration and process linkage, which can be implemented in hardware and / or software. This device can be configured in a computer device, such as a server. Figure 1 As shown, the method includes: S110. Based on the current transaction type and current transaction context information of the current document business, determine the target linkage business scenario identifier that matches the current document business.
[0016] The current document transaction refers to a specific document transaction being processed in the bank's international settlement and trade finance business, which may include international letters of credit, collection and agency services, international guarantees, and international trade finance. The current transaction type identifies the specific product transaction category of the current document transaction, such as the issuance of an import letter of credit, amendment of an import letter of credit, notification of an export letter of credit, and outward remittance. The current transaction context information mainly describes the business status data of the current document transaction processing environment, participant attributes, and transaction conditions, and may include: transaction institution information, transaction amount and currency, business channel, participant information, relationship between the issuing bank and the advising bank, and regulatory indicators. The target linkage business scenario identifier is used to determine what kind of linkage processing the current transaction needs to trigger, such as the issuance of an import letter of credit in international settlement business triggering the notification of an export letter of credit transaction, and the amendment of an import letter of credit in international settlement business triggering the notification of an amendment of an export letter of credit transaction.
[0017] Optionally, determining the target linkage business scenario identifier matching the current document business based on the current transaction type and current transaction context information includes: determining candidate linkage business scenario rules matching the current transaction type from a pre-configured linkage business scenario rule library based on the current transaction type of the current document business; and determining the linkage business scenario identifier corresponding to the candidate linkage business scenario rules that meet the preset linkage business scenario activation conditions as the target linkage business scenario identifier matching the current document business based on the current transaction context information of the current document business.
[0018] Among them, the candidate linkage business scenario rules are multiple linkage business scenario rules that are initially matched with the current transaction type in the pre-configured linkage business scenario rule library, and whose triggering transaction type is equal to the current transaction type. The preset linkage business scenario activation conditions can be manually preset according to actual conditions or experience values. This application embodiment does not make specific limitations on this. For example, the condition can be that the issuing bank and the advising bank belong to the same group, or whether the advising bank is on a specified list, etc.
[0019] Specifically, the rules for linked business scenarios in the pre-configured linked business scenario rule base are shown in Table 1 below: Table 1. Rules Base for Linked Business Scenarios Among them, the effective flag in the linked business scenario rule library table is used to indicate whether the scenario rule is currently in effect. Specifically, 0 indicates effective and 1 indicates ineffective.
[0020] S120. Based on the target linkage business scenario identifier, determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier from the pre-configured linkage business process rule library.
[0021] Specifically, workflow items are defined for collaborative scenarios to flexibly support the differentiated needs of overseas institutions based on local regulatory requirements, enabling configurable customization and flexibility of collaborative processing logic across different business scenarios. Furthermore, the pre-configured collaborative business process rules in the rule library are shown in Table 2 below: Table 2. Linked Business Process Rule Base Table The process work items in the Linked Business Process Rules Library table define the detailed work items within a process, such as transaction site preparation, internal system messages, blacklist checks, automatic processing of target transactions, and automatic review of target transactions. The applicable institutions in the Linked Business Process Rules Library table specify the institutions to which the process work item applies. Setting it to "all" indicates application to all institutions; if a specific institution code is specified, it applies only to that institution. The inapplicable institutions in the Linked Business Process Rules Library table explicitly define the institutions to which the work item does not apply. When the applicable institutions are set to "all," the institution codes set for inapplicable institutions also do not apply. The settings for inapplicable institutions have higher priority than those for applicable institutions. The activation flag in the Linked Business Process Rules Library table is used to enable or disable the rule from a management perspective. If the activation flag of a rule is 1 (invalid), the rule will never be executed, regardless of whether the activation conditions are met. All content in the Linked Business Process Rules Library table can be customized according to the different processes of each overseas institution.
[0022] Optionally, determining at least two target linkage business process rules corresponding to the target linkage business scenario identifier from a pre-configured linkage business process rule library based on the target linkage business scenario identifier includes: matching from the pre-configured linkage business process rule library based on the target linkage business scenario identifier to obtain a subset of candidate linkage business process rules associated with the linkage business scenario identifier; performing transaction institution adaptation filtering on the subset of candidate linkage business process rules based on the current transaction institution identifier of the current document business to obtain a subset of institution-adapted linkage business process rules; and determining at least two target linkage business process rules corresponding to the target linkage business scenario identifier based on the business activation status of the current document business and the subset of institution-adapted linkage business process rules.
[0023] The candidate linkage business process rule subset is a collection of all process rule records whose scenario identifier is equal to the target linkage business scenario identifier, matched against a pre-configured linkage business process rule library. The current transaction institution identifier is the bank institution code to which the currently processed document transaction belongs, such as 0010900000 (a code for an overseas branch). This identifier is used to determine whether a process rule applies to the current institution. In intra-group linkage scenarios, domestic branches and overseas branches have different institution identifiers. The business effectiveness status refers to the current business lifecycle stage of the document transaction, such as: registered, processed, reviewed, rejected, etc. This status is used to determine whether the preset effectiveness conditions in each process rule are met. For example, if a rule requires "transaction status = reviewed" to execute, and the current transaction status is "registered," then the rule does not meet the effectiveness conditions.
[0024] S130. For each target linkage business process rule, based on the process work item identifier of the target linkage business process rule, determine at least one linkage business processing action corresponding to the process work item identifier from the pre-configured linkage business processing rule library.
[0025] Optionally, the pre-configured linked business processing rule library contains multiple linked business processing rules. Each linked business processing rule is configured with at least the process work item identifier, linked business processing action, processing type, atomic service pointer, and linked business processing rule number.
[0026] Specifically, the pre-configured linkage business processing rules in the rule base are shown in Table 3 below: Table 3. Rules for Linked Business Processing In the linked business processing rule base table, the processing type is categorized as follows: Table for table data processing and Fun for function extension processing. The atomic service in the linked business processing rule base table points to the path and name of the program atomic service used to set the processing rule, and the corresponding atomic service is called based on this pointer. Specifically, TableFun is the table data processing atomic service; BlackCheckFun01 is the blacklist check atomic service.
[0027] S140. Based on the processing type of the linked business processing action and the atomic service pointer, call the corresponding atomic service to execute the linked business processing operation.
[0028] The processing types for linked business operations can include: table data processing type and non-table data processing type. Table data processing type requires reading data from the source data table and writing it to the target linked data table through field mapping rules to complete data preparation. Non-table data processing type does not involve table data mapping and directly calls program functions or services to complete specific functions, such as inspection, processing, and review.
[0029] This application determines the target linkage business scenario identifier matching the current document business based on the current transaction type and current transaction context information. Based on the target linkage business scenario identifier, it determines at least two target linkage business process rules corresponding to that identifier from a pre-configured linkage business process rule library. For each target linkage business process rule, it determines at least one linkage business processing action corresponding to that identifier from a pre-configured linkage business processing rule library based on the process work item identifier of that rule. Based on the processing type and atomic service pointer of the linkage business processing action, it calls the corresponding atomic service to execute the linkage business processing operation. This solution, through rule-driven and atomic execution of internal and external linkage processing of document business, enables configurable customization of linkage processing logic under different business scenarios. After processing a scenario transaction, it can automatically trigger the pre-registration of information for the target linkage transaction, automatically preparing the transaction site for the target transaction in advance. Business preparation can begin without waiting for messages to arrive, effectively shortening the overall business processing time, reducing manual data entry and information waiting time, and improving the efficiency of document business processing.
[0030] Example 2 Figure 2 This is a flowchart of a document processing method based on rule configuration and process linkage, according to Embodiment 2 of this application. Based on the technical solutions of the above embodiments, this embodiment refines "calling the corresponding atomic service to execute the linkage business processing operation according to the processing type and atomic service pointer of the linkage business processing action" into "if the processing type of the linkage business processing action is a table data processing type, then according to the linkage business processing rule number of the linkage business processing action, the field mapping rule is determined from the pre-configured linkage field element mapping rule library, and the table data processing atomic service is called according to the atomic service pointer. Based on the field mapping rule, data is read from the source data table and written to the target linkage data table; if the processing type of the linkage business processing action is a non-table data processing type, then the corresponding atomic service is called to execute the linkage business processing operation according to the atomic service pointer." It should be noted that for parts not detailed in this embodiment, please refer to the relevant descriptions in other embodiments. Figure 2 As shown, the method includes: S210. Based on the current transaction type and current transaction context information of the current document business, determine the target linkage business scenario identifier that matches the current document business.
[0031] S220. Based on the target linkage business scenario identifier, determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier from the pre-configured linkage business process rule library.
[0032] S230. For each target linkage business process rule, based on the process work item identifier of the target linkage business process rule, determine at least one linkage business processing action corresponding to the process work item identifier from the pre-configured linkage business processing rule library.
[0033] S240. If the processing type of the linked business processing action is table data processing type, then according to the linked business processing rule number of the linked business processing action, the field mapping rule is determined from the pre-configured linked field element mapping rule library, and the table data processing atomic service is called according to the atomic service pointer. Based on the field mapping rule, data is read from the source data table and written to the target linked data table.
[0034] Specifically, the linked field element mapping rules in the pre-configured linked field element mapping rule base are shown in Table 4 below: Table 4 Linked Field Element Mapping Rule Base The target transaction table name is the name of the table that needs to be registered in conjunction with the transaction. The target transaction table field elements are the table fields that need to be registered in conjunction with the transaction.
[0035] S250. If the processing type of the linked business processing action is a non-table data processing type, then the corresponding atomic service is called to execute the linked business processing operation according to the atomic service pointer.
[0036] Optionally, if the processing type of the linked business processing action is a non-table data processing type, then the linked business processing operation is executed by calling the corresponding atomic service according to the atomic service pointer, including: if the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the blacklist check service, then the blacklist check atomic service is called to perform compliance screening on the transaction participant information of the current document business according to the target linked business scenario identifier; if the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the automatic transaction handling service, then the automatic transaction handling atomic service is called to automatically fill in the handling information and complete the handling submission according to the target transaction pending handling business data generated by the current document business; if the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the automatic transaction review service, then the automatic transaction review atomic service is called to perform rule verification and review on the target transaction data that has been submitted.
[0037] Non-table data processing types do not require inter-table data writing operations through field mapping rules. These operations typically call independent atomic services to complete specific business functions, such as blacklist checks, automated transaction processing, automated transaction review, and sending internal system messages. The blacklist check service is used to conduct compliance screening of all parties involved in a transaction (such as applicants, beneficiaries, issuing banks, advising banks, and intermediary banks). Target transaction pending processing business data refers to business data that has been automatically generated and written into the relevant data tables of the target transaction through the table data processing atomic service (based on field mapping rules). The automated transaction processing service is used to automatically complete the processing stage of the target transaction. This service reads the target transaction pending processing business data, automatically fills in the required information such as the handler, processing time, and processing comments on the processing interface, and simulates a manual click of the "Submit Processing" button to advance the target transaction status from "Pending Processing" to "Pending Review." This service can reduce manual operations and shorten processing time. The target transaction data that has been submitted after processing refers to the complete business data of the target transaction that has been submitted after processing by the automated transaction processing service (or manual processing) and is in the "pending review" status. The automated transaction review service is used to automatically complete the review process of the target transaction. This service reads the target transaction data that has been submitted after processing and verifies it according to preset review rules (such as data consistency, amount limit, time limit compliance, etc.).
[0038] This application determines the target linkage business scenario identifier matching the current document business based on the current transaction type and current transaction context information. Based on the target linkage business scenario identifier, it determines at least two target linkage business process rules corresponding to that identifier from a pre-configured linkage business process rule library. For each target linkage business process rule, it determines at least one linkage business processing action corresponding to that identifier from a pre-configured linkage business processing rule library based on the process work item identifier of that rule. Based on the processing type and atomic service pointer of the linkage business processing action, it calls the corresponding atomic service to execute the linkage business processing operation. This solution, through rule-driven and atomic execution of internal and external linkage processing of document business, enables configurable customization of linkage processing logic under different business scenarios. After processing a scenario transaction, it can automatically trigger the pre-registration of information for the target linkage transaction, automatically preparing the transaction site for the target transaction in advance. Business preparation can begin without waiting for messages to arrive, effectively shortening the overall business processing time, reducing manual data entry and information waiting time, and improving the efficiency of document business processing.
[0039] Example 3 Figure 3 This is a schematic diagram of a document processing device based on rule configuration and process linkage, according to Embodiment 3 of this application. This embodiment is applicable to document processing based on rule configuration and supporting internal and external process linkage across all scenarios. This document processing device based on rule configuration and process linkage can be implemented in hardware and / or software, and can be configured in a computer device, such as a server. Figure 3 As shown, the device includes: The target linkage business scenario identification determination module 310 is used to determine the target linkage business scenario identification that matches the current document business based on the current transaction type and current transaction context information of the current document business. The target linkage business process rule determination module 320 is used to determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier from a pre-configured linkage business process rule library based on the target linkage business scenario identifier. The linkage business processing action determination module 330 is used to determine at least one linkage business processing action corresponding to the process work item identifier from a pre-configured linkage business processing rule library for each target linkage business process rule, based on the process work item identifier of the target linkage business process rule. The linkage business processing operation execution module 340 is used to call the corresponding atomic service to execute the linkage business processing operation according to the processing type of the linkage business processing action and the atomic service pointer.
[0040] Optionally, the linkage business processing operation execution module 340 includes: The table data processing type execution unit is used to determine the field mapping rule from the pre-configured linkage field element mapping rule library according to the linkage business processing rule number of the linkage business processing action if the processing type of the linkage business processing action is table data processing type, and call the table data processing atomic service according to the atomic service pointer, and read data from the source data table and write it to the target linkage data table based on the field mapping rule. The non-table data processing type execution unit is used to execute the linked business processing operation by calling the corresponding atomic service according to the atomic service pointer if the processing type of the linked business processing action is a non-table data processing type.
[0041] Optional, non-table data processing type execution unit, specifically used for: If the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the blacklist check service, then according to the target linked business scenario identifier, the blacklist check atomic service is invoked to perform compliance screening on the transaction participant information of the current document business. If the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the automatic transaction processing service, then based on the target transaction pending processing business data generated by the current document business, the automatic transaction processing atomic service is called to automatically fill in the processing information and complete the processing submission. If the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the transaction automatic review service, then the transaction automatic review atomic service is invoked to perform rule verification and review on the target transaction data that has been submitted by the handler.
[0042] Optional, the target linkage business process rule determination module 320 is specifically used for: Based on the target linkage business scenario identifier, a matching process is performed from a pre-configured linkage business process rule library to obtain a subset of candidate linkage business process rules associated with the linkage business scenario identifier. Based on the current transaction institution identifier of the current document business, the candidate linkage business process rule subset is filtered for transaction institution adaptation to obtain the institution-adapted linkage business process rule subset. Based on the current business activation status of the document business and the subset of the institution's adapted linkage business process rules, determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier.
[0043] Optionally, the target linkage business scenario identification determination module 310 is specifically used for: Based on the current transaction type of the current document business, determine the candidate linked business scenario rules that match the current transaction type from the pre-configured linked business scenario rule library; Based on the current transaction context information of the current document business, the linkage business scenario identifier corresponding to the candidate linkage business scenario rule that meets the preset linkage business scenario effective conditions is determined as the target linkage business scenario identifier that matches the current document business.
[0044] Optionally, the pre-configured linked business processing rule library contains multiple linked business processing rules. Each linked business processing rule is configured with at least the process work item identifier, linked business processing action, processing type, atomic service pointer, and linked business processing rule number.
[0045] This application determines the target linkage business scenario identifier matching the current document business based on the current transaction type and current transaction context information. Based on the target linkage business scenario identifier, it determines at least two target linkage business process rules corresponding to that identifier from a pre-configured linkage business process rule library. For each target linkage business process rule, it determines at least one linkage business processing action corresponding to that identifier from a pre-configured linkage business processing rule library based on the process work item identifier of that rule. Based on the processing type and atomic service pointer of the linkage business processing action, it calls the corresponding atomic service to execute the linkage business processing operation. This solution, through rule-driven and atomic execution of internal and external linkage processing of document business, enables configurable customization of linkage processing logic under different business scenarios. After processing a scenario transaction, it can automatically trigger the pre-registration of information for the target linkage transaction, automatically preparing the transaction site for the target transaction in advance. Business preparation can begin without waiting for messages to arrive, effectively shortening the overall business processing time, reducing manual data entry and information waiting time, and improving the efficiency of document business processing.
[0046] The document processing device based on rule configuration and process linkage provided in this application can execute the document processing method based on rule configuration and process linkage provided in any embodiment of this application, and has the corresponding functional modules and beneficial effects for executing each document processing method based on rule configuration and process linkage.
[0047] According to embodiments of this application, this application also provides an electronic device, a readable storage medium, and a computer program product.
[0048] Example 4 Figure 4This is a schematic diagram of the structure of an electronic device 410 implementing the document processing method based on rule configuration and process linkage according to embodiments of this application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the application described and / or claimed herein.
[0049] like Figure 4 As shown, the electronic device 410 includes at least one processor 411 and a memory, such as a read-only memory 412 or a random access memory 413, communicatively connected to the at least one processor 411. The memory stores computer programs executable by the at least one processor. The processor 411 can perform various appropriate actions and processes based on the computer program stored in the read-only memory 412 or loaded from storage unit 418 into the random access memory 413. The random access memory 413 can also store various programs and data required for the operation of the electronic device 410. The processor 411, read-only memory 412, and random access memory 413 are interconnected via a bus 414. An input / output interface 415 is also connected to the bus 414.
[0050] Multiple components in electronic device 410 are connected to input / output interface 415, including: input unit 416, such as keyboard, mouse, etc.; output unit 417, such as various types of monitors, speakers, etc.; storage unit 418, such as disk, optical disk, etc.; and communication unit 419, such as network card, modem, wireless transceiver, etc. Communication unit 419 allows electronic device 410 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0051] Processor 411 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 411 include, but are not limited to, central processing units, graphics processing units, various special-purpose artificial intelligence computing chips, various processors running machine learning model algorithms, digital signal processors, and any suitable processor, controller, microcontroller, etc. Processor 411 executes the various methods and processes described above, such as document business processing methods based on rule configuration and process linkage.
[0052] In some embodiments, the document processing method based on rule configuration and process linkage can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 418. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 410 via read-only memory 412 and / or communication unit 419. When the computer program is loaded into random access memory 413 and executed by processor 411, one or more steps of the document processing method based on rule configuration and process linkage described above can be performed. Alternatively, in other embodiments, processor 411 can be configured for the document processing method based on rule configuration and process linkage by any other suitable means (e.g., by means of firmware).
[0053] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays, application-specific integrated circuits (ASICs), application-specific standard products (ASICs), systems-on-a-chip (SoCs), payload programmable logic devices, computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0054] Computer programs used to implement the methods of this application may be written in any combination of one or more programming languages. These computer programs may be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable document processing device based on rule configuration and process linkage, such that when executed by the processor, the computer programs enable the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs may execute entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0055] In the context of this application, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium can be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory, read-only memory, erasable programmable read-only memory, optical fibers, portable compact disk read-only memory, optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0056] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a cathode ray tube or liquid crystal display monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0057] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.
[0058] A computing system can include requesters and servers. Requesters and servers are generally geographically separated and typically interact via communication networks. The relationship between a requester and a server is established by computer programs running on their respective computers and having a requester-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a host product within the cloud computing service system to address the shortcomings of traditional physical hosts and virtual private servers, such as high management difficulty and weak business scalability.
[0059] It should be understood that the various forms of processes shown above can be used to rearrange, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this application can be achieved, and this is not limited herein.
[0060] The specific embodiments described above do not constitute a limitation on the scope of protection of this application. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this application should be included within the scope of protection of this application.
Claims
1. A document processing method based on rule configuration and process linkage, characterized in that, include: Based on the current transaction type and current transaction context information of the current document business, determine the target linkage business scenario identifier that matches the current document business; Based on the target linkage business scenario identifier, at least two target linkage business process rules corresponding to the target linkage business scenario identifier are determined from the pre-configured linkage business process rule library. For each target linkage business process rule, based on the process work item identifier of the target linkage business process rule, at least one linkage business processing action corresponding to the process work item identifier is determined from the pre-configured linkage business processing rule library. Based on the processing type of the linked business processing action and the atomic service it points to, the corresponding atomic service is invoked to execute the linked business processing operation.
2. The method according to claim 1, characterized in that, The step of invoking the corresponding atomic service to execute the linked business processing operation based on the processing type and atomic service pointer of the linked business processing action includes: If the processing type of the linked business processing action is table data processing type, then according to the linked business processing rule number of the linked business processing action, the field mapping rule is determined from the pre-configured linked field element mapping rule library, and the table data processing atomic service is called according to the atomic service pointing to it. Based on the field mapping rule, data is read from the source data table and written to the target linked data table. If the processing type of the linked business processing action is a non-table data processing type, then the corresponding atomic service is called to execute the linked business processing operation according to the atomic service pointer.
3. The method according to claim 2, characterized in that, If the processing type of the linked business processing action is a non-table data processing type, then the linked business processing operation is executed by calling the corresponding atomic service according to the atomic service pointer, including: If the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the blacklist check service, then according to the target linked business scenario identifier, the blacklist check atomic service is invoked to perform compliance screening on the transaction participant information of the current document business. If the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the automatic transaction processing service, then based on the target transaction pending processing business data generated by the current document business, the automatic transaction processing atomic service is called to automatically fill in the processing information and complete the processing submission. If the processing type of the linked business processing action is a non-table data processing type and the atomic service points to the transaction automatic review service, then the transaction automatic review atomic service is invoked to perform rule verification and review on the target transaction data that has been submitted by the handler.
4. The method according to claim 1, characterized in that, The step of determining at least two target linkage business process rules corresponding to the target linkage business scenario identifier from a pre-configured linkage business process rule base, based on the target linkage business scenario identifier, includes: Based on the target linkage business scenario identifier, a matching process is performed from a pre-configured linkage business process rule library to obtain a subset of candidate linkage business process rules associated with the linkage business scenario identifier. Based on the current transaction institution identifier of the current document business, the candidate linkage business process rule subset is filtered for transaction institution adaptation to obtain the institution-adapted linkage business process rule subset. Based on the current business activation status of the document business and the subset of the institution's adapted linkage business process rules, determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier.
5. The method according to claim 1, characterized in that, The step of determining the target linkage business scenario identifier that matches the current document business based on the current transaction type and current transaction context information includes: Based on the current transaction type of the current document business, determine the candidate linked business scenario rules that match the current transaction type from the pre-configured linked business scenario rule library; Based on the current transaction context information of the current document business, the linkage business scenario identifier corresponding to the candidate linkage business scenario rule that meets the preset linkage business scenario effective conditions is determined as the target linkage business scenario identifier that matches the current document business.
6. The method according to claim 1, characterized in that, The pre-configured linked business processing rule library contains multiple linked business processing rules. Each linked business processing rule is configured with at least the process work item identifier, linked business processing action, processing type, atomic service pointer, and linked business processing rule number.
7. A document processing device based on rule configuration and process linkage, characterized in that, include: The target linkage business scenario identification determination module is used to determine the target linkage business scenario identification that matches the current document business based on the current transaction type and current transaction context information of the current document business. The target linkage business process rule determination module is used to determine at least two target linkage business process rules corresponding to the target linkage business scenario identifier from a pre-configured linkage business process rule library based on the target linkage business scenario identifier. The linkage business processing action determination module is used to determine at least one linkage business processing action corresponding to the process work item identifier from a pre-configured linkage business processing rule library for each target linkage business process rule, based on the process work item identifier of the target linkage business process rule. The linkage business processing operation execution module is used to call the corresponding atomic service to execute the linkage business processing operation based on the processing type of the linkage business processing action and the atomic service it points to.
8. An electronic device, characterized in that, include: One or more processors; Memory, used to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the document business processing method based on rule configuration and process linkage as described in any one of claims 1-6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the document business processing method based on rule configuration and process linkage as described in any one of claims 1-6.
10. A computer program product, comprising a computer program, wherein the computer program, when executed by a processor, implements the document business processing method based on rule configuration and process linkage according to any one of claims 1-6.