A customer-oriented zero-code form process automation construction method and system
By using a microservice architecture and a zero-code form process automation construction method, the problems of long construction cycles and poor adaptability to compliance scenarios in government and enterprise process management are solved, enabling rapid response to changes in business rules, reducing operating costs and improving system linkage capabilities.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- BEIJING TIANYUAN DIKE NETWORK TECHNOLOGY CO LTD
- Filing Date
- 2026-04-28
- Publication Date
- 2026-07-21
AI Technical Summary
Existing government and enterprise process management relies on customized development, which results in long setup cycles, difficulty in adapting to compliance scenarios, insufficient collaboration flexibility, high labor costs, and complex external system integration, leading to low process setup efficiency, high costs, and poor adaptability.
The platform adopts a four-layer structure built with a microservice architecture, including a form design center, a process configuration center, an intelligent engine, and a system integration layer. It enables zero-code form construction by visually dragging and dropping to configure government and enterprise secondary development components. Combined with flexible signature rules, branch routing strategies, and full-coverage event-driven rules, it supports intelligent form filling and cross-system linkage.
Significantly shortens the process development cycle, improves process iteration efficiency, reduces operating costs, enhances cross-departmental collaboration flexibility, strengthens system linkage capabilities, and meets the compliance needs of government and enterprises.
Smart Images

Figure CN122431645A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of digital process automation technology for government and enterprises, specifically to a zero-code form process automation construction method and system for customers. Background Technology
[0002] The digital transformation of government and enterprises has now entered a stage of in-depth implementation, with process approval, form filling, cross-departmental collaboration, and system integration becoming core business necessities. Existing government and enterprise process management mainly relies on customized development, general low-code platforms, or manual offline workflows. This involves using technical coding to build processes, manual data entry and task allocation, and point-to-point cross-departmental collaboration and external system integration to meet daily business approval and data flow needs.
[0003] In practical applications, existing traditional solutions and general platforms suffer from several drawbacks. Process setup heavily relies on technology development, with delivery cycles lasting 2-4 weeks, hindering rapid responses to dynamic and personalized business rule changes. They lack dedicated components for government and enterprise scenarios, exhibiting poor adaptability to compliance scenarios such as real-name authentication and qualification verification, resulting in high costs for secondary modifications. Form and process data are fragmented, lacking flexible signature capabilities, branching, and exception handling, leading to low efficiency in cross-departmental collaboration. Form filling, dispatching, and approval processes rely excessively on manual operations, resulting in repetitive data entry, unreasonable task allocation, and delayed timeout warnings, leading to high operational costs. Furthermore, system integration capabilities are weak, lacking standardized event-driven mechanisms, and integration with external systems such as OA and order centers is complex and inefficient, making full-chain automation difficult to achieve.
[0004] Therefore, there is an urgent need for a zero-code, customer-oriented method to automate form and workflow construction, in order to address the problems of poor adaptability, low intelligence, and weak system linkage in existing technologies. Summary of the Invention
[0005] To address these issues, this invention provides a zero-code form workflow automation construction method and system for customers, solving problems such as existing government and enterprise workflow management relying on customized development, long setup cycles, difficulty in adapting to compliance scenarios, insufficient collaboration flexibility, high labor costs, and complex external system integration.
[0006] To achieve the above objectives, the present invention provides the following technical solution: a zero-code form workflow automation construction method for customers, characterized in that it includes:
[0007] A four-layer platform structure consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer is built based on a microservice architecture.
[0008] In the form design center, government and enterprise secondary development components and multi-field nested condition groups can be configured through visual drag and drop to build zero-code forms and realize field linkage, data validation, semantic recognition and de-identified permission control.
[0009] Based on the zero-code form, flexible signature rules, branch routing strategies, and full-coverage event-driven rules are configured through the process configuration center to build a zero-code visual process.
[0010] Based on the zero-code form and the zero-code visualization process, the intelligent engine performs optical character recognition and large-scale intelligent form filling on the user-uploaded documents, and completes intelligent task allocation; it also performs real-time flow monitoring, blockage identification, and timeout warning and reminder for the submitted process, and generates optimization suggestions by statistically analyzing the process operation data.
[0011] Based on the full-coverage event-driven rules, the process nodes are connected to external systems through the standard interface of the system integration layer to achieve low-latency data linkage and full-link automated execution.
[0012] As a preferred solution for a zero-code form workflow automation construction method for customers, the government and enterprise secondary development component is equipped with a secondary development component extension framework, which enables attribute customization, logic extension, and cross-form reuse; the government and enterprise secondary development component includes a real-name authentication component and a qualification verification component;
[0013] The multi-field nested condition group uses "AND / OR" logic combination to realize field linkage control, display / hide switching and data validity verification.
[0014] As a preferred solution for a zero-code form workflow automation construction method for customers, the flexible signing rules include single-person signing, multi-person signing, and temporary signing rules; the signing node is inserted into the current workflow node or a new workflow node, and the workflow adjustment takes effect without restarting;
[0015] The branch routing strategy includes nested condition judgments and dynamic rule adjustments, and the dynamic rule modifications take effect within minutes.
[0016] The full-coverage event-driven rule includes three types of triggering events: pre-events, post-events, and exception events. Custom triggering rules and callback parameters can be configured through the full-coverage event-driven rule.
[0017] As a preferred solution for a zero-code form workflow automation method for customers, the intelligent engine performs optical character recognition and large-scale intelligent form filling on user-uploaded documents and completes intelligent task allocation. It also identifies, extracts, and semantically analyzes the images of user-uploaded ID cards and business licenses, and automatically backfills them into the corresponding fields of the form in a structured manner. Based on machine learning algorithms, it combines the efficiency of the processor, the load status, and professional tags to match the optimal processor and complete intelligent task allocation.
[0018] The machine learning algorithm is a fusion algorithm of multi-objective weighted optimization and online learning; the expression of the fusion algorithm of multi-objective weighted optimization and online learning is:
[0019]
[0020]
[0021] In the formula, To process the overall matching score of person i; To handle the historical efficiency normalization index of person i; To handle the inverse load index of person i; Matching the task with the professional tags of the person handling it; These are the weighting coefficients for efficiency, load, and label, respectively.
[0022] As a preferred solution for a zero-code form process automation construction method for customers, the system integration layer provides standardized event interfaces and component development SDKs. The system integration layer interfaces with OA systems, order centers, and customer management systems. When a process node triggers an external system operation, it performs process intervention, personnel handover, anomaly investigation, and node / field-level permission control.
[0023] This invention also provides a customer-oriented zero-code form workflow automation construction system, employing the above-mentioned customer-oriented zero-code form workflow automation construction method, including:
[0024] The platform structure building module is used to build a four-layer platform structure based on a microservice architecture, consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer.
[0025] The form building module is used in the form design center to configure government and enterprise secondary development components and multi-field nested condition groups through visual drag and drop, build zero-code forms, and realize field linkage, data validation, semantic recognition and de-identification permission control.
[0026] The process configuration module is used to construct a zero-code visual process by configuring flexible signature rules, branch routing strategies, and full-coverage event-driven rules through the process configuration center based on the zero-code form.
[0027] The intelligent processing module is used to perform optical character recognition and large-scale intelligent form filling on the user-uploaded documents based on the zero-code form and the zero-code visualization process, and to complete intelligent task allocation through the intelligent engine; to perform real-time flow monitoring, blockage identification and timeout warning reminders on the submitted process, and to generate optimization suggestions by statistically analyzing process operation data.
[0028] The system interface module is used to connect process nodes with external systems through the standard interface of the system integration layer based on the full-coverage event-driven rules, so as to realize low-latency data linkage and full-link automated execution.
[0029] As a preferred solution for a customer-oriented zero-code form workflow automation building system, the form building module includes a government and enterprise secondary development component equipped with a secondary development component extension framework. The secondary development component extension framework enables attribute customization, logic extension, and cross-form reuse. The government and enterprise secondary development component includes a real-name authentication component and a qualification verification component.
[0030] The multi-field nested condition group uses "AND / OR" logic combination to realize field linkage control, display / hide switching and data validity verification.
[0031] As a preferred solution for a customer-oriented zero-code form workflow automation building system, the flexible signing rules in the workflow configuration module include single-person signing, multi-person signing, and temporary signing rules; the signing node can be inserted into the current workflow node or a new workflow node can be added, and the workflow adjustment will take effect without restarting;
[0032] The branch routing strategy includes nested condition judgments and dynamic rule adjustments, and the dynamic rule modifications take effect within minutes.
[0033] The full-coverage event-driven rule includes three types of triggering events: pre-events, post-events, and exception events. Custom triggering rules and callback parameters can be configured through the full-coverage event-driven rule.
[0034] As a preferred solution for a zero-code form workflow automation system for customers, the intelligent processing module performs optical character recognition and large-scale intelligent form filling on user-uploaded documents through the intelligent engine, and completes intelligent task allocation. It also identifies, extracts, and semantically analyzes user-uploaded ID card and business license images, automatically backfilling them into the corresponding fields of the form in a structured manner. Based on machine learning algorithms, it matches the optimal processor based on processor efficiency, load status, and professional tags, thus completing intelligent task allocation.
[0035] The machine learning algorithm is a fusion algorithm of multi-objective weighted optimization and online learning; the expression of the fusion algorithm of multi-objective weighted optimization and online learning is:
[0036]
[0037]
[0038] In the formula, To process the overall matching score of person i; To handle the historical efficiency normalization index of person i; To handle the inverse load index of person i; Matching the task with the professional tags of the person handling it; These are the weighting coefficients for efficiency, load, and label, respectively.
[0039] As a preferred solution for a customer-oriented zero-code form workflow automation system, the system integration layer in the system interface module provides standardized event interfaces and component development SDKs, and the system integration layer interfaces with OA systems, order centers, and customer management systems; when a workflow node triggers an external system operation, it performs workflow intervention, personnel handover, anomaly investigation, and node / field-level permission control.
[0040] The present invention has the following advantages:
[0041] First, by adopting a zero-code visual configuration approach, coupled with a reusable component library, the process setup cycle is significantly shortened. Business can be launched without extensive technical development, enabling rapid response to changes in government and enterprise business rules and improving process iteration efficiency.
[0042] Secondly, it has built-in customizable components for government and enterprise use, which can directly support compliant scenarios such as real-name authentication and qualification verification, reducing the difficulty and investment of secondary modifications and improving the platform's adaptability to government and enterprise business.
[0043] Third, it supports flexible signature, dynamic branch routing, and nested condition judgment. Process adjustments take effect without restarting, improving the flexibility of cross-departmental collaboration and enhancing the experience of complex business workflows.
[0044] Fourth, intelligent form filling is achieved by combining optical character recognition with large models, intelligent order dispatch is achieved by relying on multi-objective weighted algorithms, and process timeout warnings and automatic reminders are supported, which significantly reduces manual operation and lowers the overall operating cost.
[0045] Fifth, by adopting an event-driven architecture and standardized interfaces, it can be smoothly connected with external systems such as OA and order centers, enabling more timely data linkage, lower system integration costs, and facilitating the automation of the entire business chain.
[0046] Sixth, it provides field-level data masking, fine-grained access control, and full-process data monitoring capabilities to enhance data security and business compliance, and better meet the data and process management requirements of government and enterprise units. Attached Figure Description
[0047] To more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are merely exemplary, and those skilled in the art can derive other embodiments based on the provided drawings without creative effort.
[0048] The structures, proportions, sizes, etc. illustrated in this specification are only for the purpose of assisting those skilled in the art in understanding and reading the content disclosed herein, and are not intended to limit the conditions under which the present invention can be implemented. Therefore, they have no substantial technical significance. Any modifications to the structure, changes in the proportions, or adjustments to the size, without affecting the effects and objectives that the present invention can produce, should still fall within the scope of the technical content disclosed in the present invention.
[0049] Figure 1 This is a flowchart illustrating a zero-code form workflow automation construction method for customers provided in Embodiment 1 of the present invention;
[0050] Figure 2 This is a schematic diagram of the platform technology architecture in a customer-oriented zero-code form process automation construction method provided in Embodiment 1 of the present invention;
[0051] Figure 3 This is a schematic diagram of the form design center function flow in a zero-code form process automation construction method for customers provided in Embodiment 1 of the present invention;
[0052] Figure 4 This is a schematic diagram of the process configuration center and event-driven architecture in a customer-oriented zero-code form process automation construction method provided in Embodiment 1 of the present invention;
[0053] Figure 5 This is a schematic diagram of the intelligent engine workflow in a customer-oriented zero-code form process automation construction method provided in Embodiment 1 of the present invention;
[0054] Figure 6 This is a schematic diagram of the architecture of a customer-oriented zero-code form process automation construction system provided in Embodiment 2 of the present invention. Detailed Implementation
[0055] The following specific embodiments illustrate the implementation of the present invention. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.
[0056] Example 1
[0057] See Figure 1 Embodiment 1 of the present invention provides a zero-code form workflow automation construction method for customers, including the following steps:
[0058] S1. Based on a microservice architecture, a four-layer platform structure is built, consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer.
[0059] S2. In the form design center, configure the government and enterprise secondary development components and multi-field nested condition groups through visual drag and drop, build a zero-code form, and realize field linkage, data validation, semantic recognition and desensitized permission control.
[0060] S3. Based on the zero-code form, configure flexible signature rules, branch routing strategies, and full-coverage event-driven rules through the process configuration center to construct a zero-code visual process;
[0061] S4. Based on the zero-code form and the zero-code visualization process, the intelligent engine performs optical character recognition and large-model intelligent form filling on the user-uploaded documents, and completes intelligent task allocation; it performs real-time flow monitoring, blockage identification and timeout warning reminders on the submitted process, and generates optimization suggestions by statistically analyzing process operation data.
[0062] S5. Based on the full-coverage event-driven rules, the process nodes are connected to external systems through the standard interface of the system integration layer to achieve low-latency data linkage and full-link automated execution.
[0063] In this embodiment, in step S1, a four-layer platform structure consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer is built based on a microservice architecture.
[0064] Specifically, such as Figure 2 As shown, this invention uses a layered and decoupled microservice architecture to build the platform's basic capabilities.
[0065] The architecture comprises several layers: a Form Design Center, a visual form designer and engine service based on Formily, providing core capabilities for zero-code form creation; a Process Configuration Center, a visual process editor and engine service based on Flowable, providing core execution capabilities for zero-code process configuration; an Intelligent Engine, an independent algorithm service layer integrating optical character recognition, large language models, and machine learning algorithm modules, providing computing power and algorithm support for intelligent processing across the entire process; and a System Integration Layer, a standard API gateway and integration service, providing a standardized channel for external system integration. Simultaneously, the architecture includes permission services, operation and maintenance monitoring services, and a storage layer comprising a MySQL business database, a Redis cache database, and MinIO attachment storage. It also covers a multi-terminal adaptive responsive front-end layer for PC / APP / mini-programs, forming a complete closed-loop technical architecture that provides underlying support for subsequent full-process capabilities in forms, processes, intelligent processing, and system integration.
[0066] In this embodiment, in step S2, the government and enterprise secondary development components and multi-field nested condition groups are configured through visual drag-and-drop in the form design center to build a zero-code form and realize field linkage, data verification, semantic recognition and desensitized permission control.
[0067] Specifically, such as Figure 3 As shown, after completing platform login and role permission authentication, business personnel officially enter the form design stage: First, the form reuse logic is judged; if the business personnel choose to reuse an existing template, a standardized template corresponding to the industry and scenario is selected from the government and enterprise exclusive form template library, which supports template reuse across forms, and directly enters the template basic information and component editing stage; if the business personnel do not need to reuse the template, they directly enter the visual canvas in the form design center to start building a brand new form from scratch.
[0068] Select the corresponding components from the categorized component library as needed. These are divided into two categories: basic field components and government / enterprise-specific secondary development components. The basic field components include general form components such as single-line text, numbers, dates, single selection, and multiple selection. The government / enterprise-specific secondary development components include components specific to government and enterprise compliance scenarios such as real-name authentication, qualification verification, official seal verification, and electronic signature. These components are equipped with a secondary development component extension framework, supporting attribute customization, business logic extension, and cross-form reuse. After dragging and dropping the components, adjust the component layout and configure the basic attributes in the visual canvas to complete the construction of the basic form framework.
[0069] After completing the basic form framework, prioritize configuring multi-field nested condition groups to support multi-level "AND / OR" logic combinations, providing the underlying rule foundation for subsequent field linkage and branch control. Based on the configured nested condition groups, complete the full-dimensional rule configuration for form fields in sequence: First, configure field linkage rules to achieve linkage control between different fields for display, hiding, assignment, and disabling; second, configure field data validation rules, covering basic validation capabilities such as format validation, numerical range validation, and non-empty / required field validation; third, configure large-model semantic validation rules, integrating a large language model to achieve intelligent recognition and validation of the compliance and rationality of form data; fourth, configure field-level desensitization rules, setting corresponding desensitization display rules for sensitive fields such as ID cards, mobile phone numbers, and unified social credit codes; fifth, configure refined permission control rules, setting viewing, editing, and hiding permissions for form fields according to roles and departments, completing the configuration of full business rules for the form.
[0070] After completing all rule configurations, proceed to the multi-platform visual preview stage to adapt the display effect to multiple terminals such as PC, APP, and mini-program. After the preview is completed, conduct full-scenario testing of the form functionality, covering all dimensions of field linkage testing, data validation testing, permission control testing, and desensitization rule testing. If the test fails, roll back to the corresponding configuration stage for modification and optimization. After modification, re-execute the testing process until the test passes.
[0071] After the test is passed, the system automatically saves all the form configuration information and performs the form publishing operation. The system automatically generates a unique identifier and calling address for the zero-code form. After publishing, the system automatically enables the form version management function, supporting the viewing of historical form versions, version rollback, and iterative updates. At the same time, the published form information is synchronized to the process configuration center for subsequent process building stages to call, completing the closed loop of the entire lifecycle of zero-code forms from building, configuration, testing, publishing to reuse.
[0072] In this embodiment, in step S3, based on the zero-code form, flexible signature rules, branch routing strategies, and full-coverage event-driven rules are configured through the process configuration center to construct a zero-code visual process.
[0073] Specifically, such as Figure 4 As shown, after completing platform login and role permission authentication, you enter the visual process canvas in the process configuration center; bind the zero-code form published in step S2, complete the permission mapping and data flow relationship configuration between form fields and process nodes, and ensure the synchronous call and compliance control of form data during the process flow; after completing the form binding, add standardized process nodes such as initiation node, approval node, copy node, conditional branch node, and end node in the canvas through visual drag and drop, complete the construction of the basic topology framework of the process, and clarify the core flow link of the process.
[0074] Based on the established workflow framework, and addressing the high-frequency needs of inter-departmental temporary collaboration and supplementary approvals between government and enterprises, flexible signature rules are configured for all scenarios. These rules support three core modes: single-person signature, multi-person countersigning / or signing, and temporary signature. The insertion position of signature nodes can be customized, including placing them before or after the current approval node, or adding independent workflow approval nodes. Detailed parameters such as the approval authority scope, processing time, rollback rules, and countersigning approval ratio of the signature personnel can also be configured. The core capability is seamless workflow adjustment: after the signature rules are configured, existing in-transit workflows and newly added workflows take effect simultaneously without restarting existing workflow instances, completely resolving the pain point of traditional workflow platforms requiring workflow restarts and business interruptions when adjusting rules.
[0075] Based on the multi-field nested condition groups configured in step S2, configure the full-link branch routing strategy for the process. It supports multi-level nested condition judgment and can set branch trigger conditions based on multi-dimensional data such as form field values, initiator role / department, approval results of previous nodes, and business scenario type. It also supports multi-level "AND / OR" logic combinations to realize automated branch flow in different business scenarios and adapt to the multi-scenario differentiated approval needs of complex government and enterprise businesses. It also realizes the ability to make dynamic rules effective within minutes. The trigger conditions and flow rules of branch routing can be modified online at any time. After the modification, there is no need to redeploy the entire process or interrupt the running process instance. The system automatically completes rule parsing, model update and cache synchronization. The rule modification can take full effect in as little as 1 minute, and quickly respond to the dynamic change needs of government and enterprise business rules.
[0076] Based on the entire lifecycle nodes of the process, a comprehensive event-driven rule system is built, covering three types of scenarios: pre-processing, post-processing, and exceptions. This system provides underlying triggering capabilities for automated process execution and cross-system collaboration. The configuration details for the three types of rules are as follows:
[0077] First, there are pre-event rules, which are configured to be triggered before the execution of a process node. These rules can be set to trigger actions such as pre-validation of form data, secondary verification of initiator permissions, pre-query of business data from external systems, and secondary verification of required fields. Second, there are post-event rules, which are configured to be triggered after the execution of a process node. These rules can be set to trigger actions such as multi-channel notification of approval results, automatic archiving of form data, synchronous updating of business status, and automatic activation of downstream nodes. Third, there are exception event rules, which are configured to be triggered in abnormal scenarios such as errors during the execution of process nodes, approval timeouts, and rejection rollbacks. These rules can be set to trigger actions such as exception alarm notifications, automatic timeout reassignment, automatic process rollback, and automatic backup of abnormal data.
[0078] All event rules support custom trigger conditions, callback parameters, and retry mechanisms for execution failures. They can be directly connected to the system integration layer of subsequent steps S5 to achieve automated linkage between the process and external systems.
[0079] In this embodiment, after completing the full rule configuration, a visual topology preview of the process is performed first. This can simulate the process flow path under different business scenarios and different form parameters, and intuitively verify the accuracy of branch routing, signing rules, and event triggering logic. After the preview is correct, a full-scenario closed-loop test of the process is executed, covering all business scenarios such as normal approval flow, supplementary approval with signing, multi-branch conditional jumps, and abnormal event triggering. If rule configuration errors or flow logic deviations are found during the test, the system supports one-click rollback to the corresponding configuration stage for modification and optimization. After the modification is completed, the test process is re-executed until the full-scenario test is passed.
[0080] After the test is passed, the system automatically saves all the process configuration information, automatically converts the visually configured process rules into a standard BPMN2.0 format process model, and synchronously caches it in the Redis database to improve call efficiency. After the release operation is performed, the process can be fully deployed and take effect in as little as 1 minute. The system automatically generates a unique identifier, initiation entry point, and permission control rules for the process. After the release is completed, the system synchronously enables the process version management function, supports viewing historical versions of the process, one-click version rollback, and retention of iteration update records. At the same time, the released process model and rule information are synchronized to the intelligent engine and system integration layer, providing a calling basis for the intelligent processing of the subsequent step S4 and the cross-system integration of step S5. Finally, the system completes the closed loop of the zero-code visual process from building, configuring, testing, releasing to dynamic effectiveness.
[0081] In this embodiment, in step S4, based on the zero-code form and the zero-code visualization process, the intelligent engine performs optical character recognition and large-model intelligent form filling on the user-uploaded documents, and completes intelligent task allocation; it also performs real-time flow monitoring, blockage identification, and timeout warning reminders on the submitted process, and generates optimization suggestions by statistically analyzing the process operation data.
[0082] Specifically, after a user initiates a process instance on the front end, they enter the document image collection and uploading stage, uploading documents such as their ID card and business license to the platform. The intelligent engine calls the optical character recognition module to extract text from the image, completes key information location, character segmentation and recognition output, and then uses a large model to perform semantic error correction, structured parsing and field mapping on the recognition results, automatically backfilling the name, document number, unified social credit code and other content into the corresponding positions of the zero-code form, realizing intelligent form filling without manual input, reducing input errors and improving filling efficiency.
[0083] After the form is submitted, various characteristic data of the person currently awaiting assignment are collected, including historical completion efficiency, current task load, department and position, professional business tags, etc. A comprehensive matching score for each person is calculated through a multi-objective weighted optimization and online learning fusion algorithm. The optimal person is automatically selected according to the score and the pending tasks are pushed to them, so as to achieve balanced task allocation and intelligent task dispatch, avoiding the problems of task backlog and mismatch between processing capacity.
[0084] The expression for the multi-objective weighted optimization and online learning fusion algorithm is as follows:
[0085]
[0086]
[0087] In the formula, To process the overall matching score of person i; To handle the historical efficiency normalization index of person i; To handle the inverse load index of person i; Matching the task with the professional tags of the person handling it; These are the weighting coefficients for efficiency, load, and label, respectively.
[0088] In this embodiment, once the process enters the workflow stage, the intelligent engine activates a real-time workflow monitoring and anomaly identification mechanism. It continuously monitors the processing status, dwell time, and workflow trajectory of each node, automatically identifying situations such as node timeouts, workflow blockages, approval rejections, and abnormal interruptions. When a timeout or blockage risk is detected, the engine automatically executes warnings and reminders according to preset strategies, pushing reminders via in-system messages, SMS, etc., and supports automatic reassignment, additional signing, or escalation reporting according to rules to ensure the continuous progress of the process.
[0089] Throughout the entire process, the intelligent engine simultaneously collects and statistically analyzes operational data, summarizing indicators such as process initiation volume, time consumption at each node, pass rate, anomaly rate, and handler performance. Through data modeling, it forms a process operation profile, automatically identifies inefficient nodes, bottlenecks, and optimizable points, and ultimately generates process optimization suggestions. This provides data support for process rule adjustments, node simplification, and permission optimization, enabling continuous iteration and efficiency improvement of business processes.
[0090] In this embodiment, in step S5, based on the full-coverage event-driven rules, the process nodes are connected to external systems through the standard interface of the system integration layer to achieve low-latency data linkage and full-link automated execution.
[0091] Specifically, through the standardized event interface provided by the system integration layer, the linkage rules between process nodes and external systems are configured. Based on the pre-process, post-process, and exception event-driven rules configured in the process, external system interface calls are automatically triggered when process nodes are executed, completing data synchronization and business linkage without manual intervention. The standardized event interface can achieve seamless integration with commonly used government and enterprise external systems such as OA systems, order centers, and customer management systems, with data linkage latency of less than 100ms, and the cycle for adapting to new scenarios is shortened from monthly to weekly. At the same time, the system integration layer provides an open component development SDK, which supports rapid expansion of industry-specific components, covering more than 15 government and enterprise business scenarios. It also provides supporting operation and maintenance capabilities such as process intervention, personnel handover, anomaly investigation, and node / field-level permission control, ensuring the stable operation of cross-system linkage, and ultimately achieving full-link automated execution from form filling and process approval to cross-system business linkage.
[0092] The application scenarios of this invention are as follows:
[0093] In government service scenarios, this invention can quickly build business forms and processes for administrative approval, qualification application, and material verification, enabling intelligent form filling and cross-departmental collaborative approval, thereby improving the efficiency of government processing.
[0094] In enterprise internal management scenarios, this invention can build standardized processes such as personnel approval, financial reimbursement, and procurement application, reducing manual operations and lowering enterprise operating costs.
[0095] In cross-system business linkage scenarios, this invention enables data exchange between process nodes and external systems such as OA and customer management through event-driven and interface integration, supporting automated business operations.
[0096] In customized service scenarios for government and enterprise clients, this invention relies on zero-code configuration and dedicated components to quickly adapt to the business needs of different industries and shorten the project delivery cycle.
[0097] In high-compliance data processing scenarios, this invention ensures the security of sensitive information and meets the compliance management requirements of government and enterprises through field anonymization and access control.
[0098] It should be noted that the method of this disclosure embodiment can be executed by a single device, such as a computer or server. The method of this embodiment can also be applied to a distributed scenario, where multiple devices cooperate to complete the task. In such a distributed scenario, one of these devices may execute only one or more steps of the method of this disclosure embodiment, and the multiple devices will interact with each other to complete the method described.
[0099] It should be noted that the above description describes some embodiments of this disclosure. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
[0100] Example 2
[0101] See Figure 6 Embodiment 2 of the present invention also provides a customer-oriented zero-code form workflow automation construction system, comprising:
[0102] Platform structure building module 001 is used to build a four-layer platform structure based on microservice architecture, consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer;
[0103] The form construction module 002 is used in the form design center to configure government and enterprise secondary development components and multi-field nested condition groups through visual drag and drop, build zero-code forms, and realize field linkage, data validation, semantic recognition and desensitized permission control.
[0104] The process configuration module 003 is used to construct a zero-code visual process by configuring flexible signature rules, branch routing strategies and full-coverage event-driven rules through the process configuration center based on the zero-code form.
[0105] The intelligent processing module 004 is used to perform optical character recognition and large-scale intelligent form filling on the user-uploaded documents based on the zero-code form and the zero-code visualization process, and to complete intelligent task allocation; to perform real-time flow monitoring, blockage identification and timeout warning reminders on the submitted process, and to generate optimization suggestions by statistically analyzing process operation data.
[0106] The system interface module 005 is used to interface with external systems through the standard interface of the system integration layer based on the full-coverage event-driven rules, so as to realize low-latency data linkage and full-link automated execution.
[0107] In this embodiment, the form construction module 002 includes a government and enterprise secondary development component equipped with a secondary development component extension framework. The secondary development component extension framework enables attribute customization, logic extension, and cross-form reuse. The government and enterprise secondary development component includes a real-name authentication component and a qualification verification component.
[0108] The multi-field nested condition group uses "AND / OR" logic combination to realize field linkage control, display / hide switching and data validity verification.
[0109] In this embodiment, in the process configuration module 003, the flexible signing rules include single-person signing, multi-person signing, and temporary signing rules; the signing node is inserted into the current process node or a new process node is added, and the process adjustment takes effect without restarting;
[0110] The branch routing strategy includes nested condition judgments and dynamic rule adjustments, and the dynamic rule modifications take effect within minutes.
[0111] The full-coverage event-driven rule includes three types of triggering events: pre-events, post-events, and exception events. Custom triggering rules and callback parameters can be configured through the full-coverage event-driven rule.
[0112] In this embodiment, the intelligent processing module 004 performs optical character recognition and large-model intelligent form filling on the user-uploaded documents through the intelligent engine, and completes the intelligent task allocation process. It identifies, extracts, and semantically analyzes the user-uploaded ID card and business license images, and automatically backfills them into the corresponding fields of the form in a structured manner. Based on machine learning algorithms, it performs optimal processing personnel matching by combining processing efficiency, load status, and professional tags to complete the intelligent task allocation.
[0113] The machine learning algorithm is a fusion algorithm of multi-objective weighted optimization and online learning; the expression of the fusion algorithm of multi-objective weighted optimization and online learning is:
[0114]
[0115]
[0116] In the formula, To process the overall matching score of person i; To handle the historical efficiency normalization index of person i; To handle the inverse load index of person i; Matching the task with the professional tags of the person handling it; These are the weighting coefficients for efficiency, load, and label, respectively.
[0117] In this embodiment, the system integration module 005 provides a standardized event interface and component development SDK. The system integration layer interfaces with the OA system, order center, and customer management system. When a process node triggers an external system operation, it performs process intervention, personnel handover, anomaly investigation, and node / field-level permission control.
[0118] It should be noted that the information interaction and execution process between the modules of the above system are based on the same concept as the method embodiment in Embodiment 1 of this application, and the resulting technical effects are the same as those in the method embodiment of this application. For details, please refer to the description in the method embodiment shown above in this application, and it will not be repeated here.
[0119] Example 3
[0120] Embodiment 3 of the present invention provides a non-transitory computer-readable storage medium storing program code for a client-oriented zero-code form process automation construction method. The program code includes instructions for executing the client-oriented zero-code form process automation construction method of Embodiment 1 or any possible implementation thereof.
[0121] Computer-readable storage media can be any available medium that a computer can access, or a data storage device such as a server or data center that integrates one or more available media. The available medium can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).
[0122] Example 4
[0123] Embodiment 4 of the present invention provides an electronic device, including: a memory and a processor;
[0124] The processor and the memory communicate with each other via a bus; the memory stores program instructions that can be executed by the processor, and the processor can execute a zero-code form process automation construction method for clients, as described in Embodiment 1 or any possible implementation thereof.
[0125] Specifically, a processor can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. This memory can be integrated into the processor or located outside the processor and exist independently.
[0126] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present invention are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable system. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.
[0127] It is obvious to those skilled in the art that the modules or steps of the present invention described above can be implemented using general-purpose computing systems. They can be centralized on a single computing system or distributed across a network of multiple computing systems. Optionally, they can be implemented using program code executable by a computing system, thereby storing them in a storage system for execution by the computing system. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, the present invention is not limited to any particular combination of hardware and software.
[0128] Although the present invention has been described in detail above with general descriptions and specific embodiments, modifications or improvements can be made to it, which will be obvious to those skilled in the art. Therefore, all such modifications or improvements made without departing from the spirit of the present invention fall within the scope of protection claimed by the present invention.
Claims
1. A customer-oriented, zero-code form workflow automation construction method, characterized in that, include: A four-layer platform structure consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer is built based on a microservice architecture. In the form design center, government and enterprise secondary development components and multi-field nested condition groups can be configured through visual drag and drop to build zero-code forms and realize field linkage, data validation, semantic recognition and de-identification permission control. Based on the zero-code form, flexible signature rules, branch routing strategies, and full-coverage event-driven rules are configured through the process configuration center to build a zero-code visual process. Based on the zero-code form and the zero-code visualization process, the intelligent engine performs optical character recognition and large-scale intelligent form filling on the user-uploaded documents, and completes intelligent task allocation. The system performs real-time monitoring of the submitted process flow, identifies blockages, issues timeout warnings and reminders, and generates optimization suggestions based on process operation data. Based on the full-coverage event-driven rules, the process nodes are connected to external systems through the standard interface of the system integration layer to achieve low-latency data linkage and full-link automated execution.
2. The customer-oriented zero-code form workflow automation construction method according to claim 1, characterized in that, The government and enterprise secondary development component is equipped with a secondary development component extension framework, which enables attribute customization, logic extension, and cross-form reuse; the government and enterprise secondary development component includes a real-name authentication component and a qualification verification component. The multi-field nested condition group uses "AND / OR" logic combination to realize field linkage control, display / hide switching and data validity verification.
3. The customer-oriented zero-code form workflow automation construction method according to claim 2, characterized in that, The flexible signature rules include single-person signature, multi-person signature, and temporary signature rules; the signature node can be inserted into the current process node or a new process node, and the process adjustment will take effect without restarting. The branch routing strategy includes nested condition judgments and dynamic rule adjustments, and the dynamic rule modifications take effect within minutes. The full-coverage event-driven rule includes three types of triggering events: pre-events, post-events, and exception events. Custom triggering rules and callback parameters can be configured through the full-coverage event-driven rule.
4. The customer-oriented zero-code form workflow automation construction method according to claim 3, characterized in that, During the process of using the intelligent engine to perform optical character recognition and large-scale intelligent form filling on the user-uploaded documents and to complete the intelligent task allocation, the images of the user-uploaded ID card and business license are identified, extracted, and semantically analyzed, and automatically and structurally filled back into the corresponding fields of the form. Based on machine learning algorithms, the system combines the efficiency, workload, and professional tags of the processors to match the optimal processors and intelligently allocate tasks. The machine learning algorithm is a fusion algorithm of multi-objective weighted optimization and online learning; the expression of the fusion algorithm of multi-objective weighted optimization and online learning is: In the formula, To process the overall matching score of person i; To handle the historical efficiency normalization index of person i; To handle the inverse load index of person i; Matching the task with the professional tags of the person handling it; These are the weighting coefficients for efficiency, load, and label, respectively.
5. The customer-oriented zero-code form workflow automation construction method according to claim 4, characterized in that, The system integration layer provides standardized event interfaces and component development SDKs. The system integration layer interfaces with the OA system, order center, and customer management system. When a process node triggers an external system operation, it performs process intervention, personnel handover, anomaly investigation, and node / field-level permission control.
6. A customer-oriented zero-code form workflow automation construction system, employing the customer-oriented zero-code form workflow automation construction method according to any one of claims 1-5, characterized in that, include: The platform structure building module is used to build a four-layer platform structure based on a microservice architecture, consisting of a form design center, a process configuration center, an intelligent engine, and a system integration layer. The form building module is used in the form design center to configure government and enterprise secondary development components and multi-field nested condition groups through visual drag and drop, build zero-code forms, and realize field linkage, data validation, semantic recognition and de-identification permission control. The process configuration module is used to construct a zero-code visual process by configuring flexible signature rules, branch routing strategies, and full-coverage event-driven rules through the process configuration center based on the zero-code form. The intelligent processing module is used to perform optical character recognition and large-scale intelligent form filling on the user-uploaded documents through the intelligent engine based on the zero-code form and the zero-code visualization process, and to complete intelligent task allocation. The system performs real-time monitoring of the submitted process flow, identifies blockages, issues timeout warnings and reminders, and generates optimization suggestions based on process operation data. The system interface module is used to connect process nodes with external systems through the standard interface of the system integration layer based on the full-coverage event-driven rules, so as to realize low-latency data linkage and full-link automated execution.
7. A customer-oriented zero-code form workflow automation construction system according to claim 6, characterized in that, In the form construction module, the government and enterprise secondary development component is equipped with a secondary development component extension framework, which enables attribute customization, logic extension, and cross-form reuse; the government and enterprise secondary development component includes a real-name authentication component and a qualification verification component; The multi-field nested condition group uses "AND / OR" logic combination to realize field linkage control, display / hide switching and data validity verification.
8. A customer-oriented zero-code form workflow automation construction system according to claim 7, characterized in that, In the process configuration module, the flexible signing rules include single-person signing, multi-person signing, and temporary signing rules; the signing node can be inserted into the current process node or a new process node, and the process adjustment will take effect without restarting; The branch routing strategy includes nested condition judgments and dynamic rule adjustments, and the dynamic rule modifications take effect within minutes. The full-coverage event-driven rule includes three types of triggering events: pre-events, post-events, and exception events. Custom triggering rules and callback parameters can be configured through the full-coverage event-driven rule.
9. A customer-oriented zero-code form workflow automation construction system according to claim 8, characterized in that, In the intelligent processing module, during the process of performing optical character recognition and large-scale intelligent form filling on the user-uploaded documents through the intelligent engine and completing intelligent task allocation, the user-uploaded ID card and business license document images are identified, extracted, and semantically parsed, and automatically structured and backfilled into the corresponding fields of the form. Based on machine learning algorithms, the system combines the efficiency, workload, and professional tags of the processors to match the optimal processors and intelligently allocate tasks. The machine learning algorithm is a fusion algorithm of multi-objective weighted optimization and online learning; the expression of the fusion algorithm of multi-objective weighted optimization and online learning is: In the formula, To process the overall matching score of person i; To handle the historical efficiency normalization index of person i; To handle the inverse load index of person i; Matching the task with the professional tags of the person handling it; These are the weighting coefficients for efficiency, load, and label, respectively.
10. A customer-oriented zero-code form workflow automation construction system according to claim 9, characterized in that, In the system integration module, the system integration layer provides standardized event interfaces and component development SDKs. The system integration layer interfaces with the OA system, order center, and customer management system. When a process node triggers an external system operation, it performs process intervention, personnel handover, anomaly investigation, and node / field-level permission control.