Rule logic operation engine based on FTL
Through the FTL-based rule logic computing engine, the problem of high maintenance costs and low coding efficiency of RPA tools in rule logic computing is solved, low code configuration and multi-platform compatibility are achieved, and the quality and stability of the workflow are improved.
Patent Information
- Application Number
- CN202410978260.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-22
- Publication Date
- 2024-11-08
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing RPA tools rely on recording scripts in terms of rule logic operations, resulting in high maintenance costs, low coding efficiency and high error rates, especially when complex business processes change, requiring frequent rewriting of script logic.
The FTL-based rule logic computing engine is adopted to obtain logical execution rules through data structure combination and features, support low-code configuration and dynamic rendering, replace traditional script writing methods, and realize automatic execution and binding of rule logic.
It reduces the threshold and complexity of the rule engine, improves configuration efficiency and workflow stability, supports multiple configurations and uses at one time, reduces the possibility of errors, and is suitable for multi-platform environments.
Smart Images

Figure CN118916025A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of robotic process automation technology, and in particular to a rule logic operation engine based on FTL. Background Art
[0002] With the rapid development of information technology, enterprises are facing increasingly complex business processes and huge data processing needs. Traditional manual processing methods can no longer meet the business needs of efficiency, accuracy and speed. Therefore, Robotic Process Automation (RPA) technology came into being. RPA technology simulates human operations on computers to realize the automatic execution of business processes, greatly improving work efficiency and reducing operating costs.
[0003] In recent years, RPA technology has developed rapidly and is widely used in finance, manufacturing, retail, medical and other fields. Various process automation tools continue to emerge. The RPA platform provides a powerful process design and execution engine. Users can easily build complex business processes through drag and drop, configuration, etc. The execution engine is responsible for automatically executing corresponding operations such as data input, data extraction, data verification, etc. according to the preset process rules.
[0004] At present, the mainstream RPA tools all adopt the method of recording scripts. Recording scripts is only a single operation flow. For the rule logic operations in the scripts, professional engineers are required to write them. When the corresponding business process changes, the process rules corresponding to the recorded scripts may become invalid, and the script rule logic needs to be rewritten. When there are many RPA scripts, modifying the rule logic in the scripts will be complicated and tedious, which will lead to an increase in maintenance costs. In addition, when the rule logic is relatively complex, it is also a big challenge to improve the coding efficiency of the rule logic and reduce the coding error rate.
[0005] Currently, no effective solution has been proposed for the problems in the related technologies. Summary of the invention
[0006] In view of the problems in the related art, the present invention proposes a rule logic operation engine based on FTL to overcome the above technical problems existing in the existing related art.
[0007] The technical solution of the present invention is achieved in this way:
[0008] A rule logic operation engine based on FTL includes the following steps:
[0009] Step S1, the FTL rule engine restructures the captured data to obtain a data set, and obtains the corresponding logic execution rules in the specified target through data features to obtain a rule set;
[0010] Step S2, the FTL rule engine binds the data set, the rule set and the feature variables defined by the FTL logic operation template, inputs them into the FTL logic operation template, performs binding rendering, inserts the data value into the corresponding position in the FTL logic operation template, and completes the FTL rule engine rendering;
[0011] Step S3: The FTL execution engine performs a syntax execution operation on the rendered FTL rule engine instance object to obtain an execution output result.
[0012] Furthermore, the method further comprises the following steps:
[0013] Step S101, when the captured data needs to execute rule logic operation, the data set is traversed and submitted to the FTL rule engine for judgment;
[0014] Step S102: After receiving the data, the FTL rule engine determines whether a rule set needs to be captured based on the data.
[0015] Furthermore, the step of determining whether a set of rules needs to be captured based on the data includes the following steps:
[0016] If the data needs to capture a rule set, the judgment is true, and the rule set corresponding to the data is submitted to the FTL execution engine for rendering and execution;
[0017] If the data does not need to capture the rule set, the judgment is false, and the remaining data will continue to be traversed.
[0018] Furthermore, if the data needs to capture a set of rules, the steps include the following steps:
[0019] After the FTL execution engine performs the rule logic operation, it marks the obtained rule execution result as true or false and returns it to the FTL rule engine;
[0020] The FTL rule engine binds the results and data and submits them to the front end.
[0021] Furthermore, the feature variables include: input variables and dynamic rendering logic.
[0022] Furthermore, the FTL execution engine performs a syntax execution operation on the rendered FTL rule engine instance object, including the following steps:
[0023] Step S301, if the execution output result is compliance, it indicates that the rule execution is successful and the corresponding data is automatically processed;
[0024] Step S302: If the execution output result is an error, it indicates that the rule execution fails, and the corresponding data prompts manual processing.
[0025] Beneficial effects of the present invention:
[0026] 1. The present invention supports the front-end low-code method to configure rule logic data, facilitates configuration and modification, reduces the threshold and difficulty of using the rule engine, and supports the function of one-time configuration and multiple uses. Users can create and save multiple configuration templates as needed. These templates can be reused in different scenarios and projects, avoiding the tedious process of repeated configuration.
[0027] 2. The present invention has excellent cross-platform compatibility, and users can easily use the system to perform configuration operations on different operating systems and devices. The present invention replaces the traditional script writing rule operation logic method, greatly improves the efficiency of configuration, and reduces the possibility of errors, thereby improving the quality and stability of the entire workflow. BRIEF DESCRIPTION OF THE DRAWINGS
[0028] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0029] Figure 1 FIG. 1 is a schematic diagram of a process of a rule logic operation engine based on FTL according to an embodiment of the present invention. Figure 1 ;
[0030] Figure 2 FIG. 1 is a schematic diagram of a process of a rule logic operation engine based on FTL according to an embodiment of the present invention. Figure 2 ;
[0031] Figure 3 FIG. 1 is a schematic diagram of a process of a rule logic operation engine based on FTL according to an embodiment of the present invention. Figure 3 . DETAILED DESCRIPTION
[0032] The following will be combined with the accompanying drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of the present invention.
[0033] According to an embodiment of the present invention, a rule logic operation engine based on FTL (Freemarker Template Language) is provided.
[0034] like Figure 1 As shown, the rule logic operation engine based on FTL according to an embodiment of the present invention includes the following steps:
[0035] Step S1, the FTL rule engine restructures the captured data to obtain a data set, and obtains the corresponding logic execution rules in the specified target through data features to obtain a rule set;
[0036] This technical solution also includes the following steps:
[0037] Step S101, when the captured data needs to execute rule logic operation, the data set is traversed and submitted to the FTL rule engine for judgment.
[0038] like Figure 2 As shown, in step S102, after the FTL rule engine receives the data, it determines whether it is necessary to capture the rule set according to the data, including the following steps:
[0039] If the data needs to capture a rule set, the judgment is true, and the rule set corresponding to the data is submitted to the FTL execution engine for rendering and execution;
[0040] If the data does not need to capture the rule set, the judgment is false, and the remaining data will continue to be traversed;
[0041] This technical solution, if the data needs to capture a set of rules, includes the following steps:
[0042] After the FTL execution engine performs the rule logic operation, it marks the obtained rule execution result as true or false and returns it to the FTL rule engine;
[0043] The FTL rule engine binds the results and data and submits them to the front end.
[0044] Step S2, the FTL rule engine binds the data set, the rule set and the feature variables defined by the FTL logic operation template, inputs them into the FTL logic operation template, performs binding rendering, inserts the data value into the corresponding position in the FTL logic operation template, and completes the FTL rule engine rendering;
[0045] Among them, feature variables include: input variables and dynamic rendering logic;
[0046] This technical solution uses the FTL logic operation template language to write rule logic operations. By defining input variables and dynamic rendering logic in the FTL logic operation template, the FTL rule engine renders the extracted data to the corresponding position of the FTL logic operation template, and then calculates the expression in the FTL logic operation template, judges the conditional statements, and iterates the loop structure, and finally forms an output result that is output to the FTL execution engine.
[0047] This technical solution specifically includes the following steps:
[0048] Template writing: FTL logic operation templates use special syntax to define the output format. FTL logic operation templates can contain static content, such as HTML tags and text, and dynamic content, which is associated with variables through FTL syntax.
[0049] Data insertion: During the rendering of the FTL logic operation template, the FTL rule engine will grab relevant data from a specific target according to the given conditions, combine it into a data model (usually an object or data structure containing multiple attributes) and pass it to the FTL logic operation template. The FTL rule engine will parse the FTL syntax and insert the data values in the data model into the corresponding positions of the FTL logic operation template.
[0050] Rendering output: When the FTL rule engine completes data value insertion, it generates the final output text. This process usually involves calculating expressions in the FTL logic operation template, judging conditional statements, and iterating loop structures.
[0051] like Figure 3 As shown, in step S3, the FTL execution engine performs a syntax execution operation on the rendered FTL rule engine instance object to obtain the execution output result.
[0052] The steps include:
[0053] Step S301, if the execution output result is compliance, it indicates that the rule execution is successful and the corresponding data is automatically processed;
[0054] Step S302: If the execution output result is an error, it indicates that the rule execution fails, and the corresponding data prompts manual processing.
[0055] In summary, with the help of the above technical solution of the present invention, the following effects can be achieved:
[0056] 1. The present invention supports the front-end low-code method to configure rule logic data, facilitates configuration and modification, reduces the threshold and difficulty of using the rule engine, and supports the function of one-time configuration and multiple uses. Users can create and save multiple configuration templates as needed. These templates can be reused in different scenarios and projects, avoiding the tedious process of repeated configuration.
[0057] 2. The present invention has excellent cross-platform compatibility, and users can easily use the system to perform configuration operations on different operating systems and devices. The present invention replaces the traditional script writing rule operation logic method, greatly improves the efficiency of configuration, and reduces the possibility of errors, thereby improving the quality and stability of the entire workflow.
[0058] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. After considering the disclosure of the specification and the examples, those skilled in the art will easily think of other embodiments of the present disclosure. This application is intended to cover any modification, use or adaptation of the present disclosure, which follows the general principles of the present disclosure and includes common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and the examples are only regarded as exemplary, and the true scope and spirit of the present disclosure are indicated by the claims.
[0059] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims
1. A rule logic operation engine based on FTL, characterized in that: The following steps are involved: The FTL rule engine restructures the captured data to obtain a data set, and obtains the corresponding logic execution rules in the specified target through data features to obtain a rule set; The FTL rule engine binds the data set, rule set and feature variables defined by the FTL logic operation template, inputs them into the FTL logic operation template, performs binding rendering, inserts the data value into the corresponding position in the FTL logic operation template, and completes the FTL rule engine rendering; The FTL execution engine performs syntax execution operations on the rendered FTL rule engine instance object to obtain the execution output result.
2. The FTL-based rule logic operation engine according to claim 1, characterized in that: The following steps are also included: When the captured data needs to execute rule logic operations, the data set is traversed and submitted to the FTL rule engine for judgment; After receiving the data, the FTL rule engine determines whether the rule set needs to be captured based on the data.
3. The FTL-based rule logic operation engine according to claim 2, characterized in that: The step of determining whether a crawling rule set is required based on the data includes the following steps: If the data needs to capture a rule set, the judgment is true, and the rule set corresponding to the data is submitted to the FTL execution engine for rendering and execution; If the data does not need to capture the rule set, the judgment is false, and the remaining data will continue to be traversed.
4. The FTL-based rule logic operation engine according to claim 3, characterized in that: If the data needs to capture a set of rules, the following steps are included: After the FTL execution engine performs the rule logic operation, it marks the obtained rule execution result as true or false and returns it to the FTL rule engine; The FTL rule engine binds the results and data and submits them to the front end.
5. The FTL-based rule logic operation engine according to claim 1, characterized in that: The feature variables include: input variables and dynamic rendering logic.
6. The FTL-based rule logic operation engine according to claim 1, characterized in that: The FTL execution engine performs a syntax execution operation on the rendered FTL rule engine instance object, including the following steps: If the execution output result is in compliance, it means that the rule execution is successful and the corresponding data is automatically processed; If the execution output result is an error, it means that the rule execution fails, and the corresponding data prompts manual processing.
Citation Information
Patent Citations
Content generation method and device, computer equipment and storage medium
CN110069737A
Workflow engine and rule engine conversion control system
CN115964055A
Deployment scheme based on low codes and rules, storage medium and electronic equipment
CN116009882A
Application system and method based on cloud native, and storage medium
CN117289946A
