Business process extensible configuration method and system based on annotation
By reserving business expansion points in the application and using annotations and visual orchestration, the problem of traditional business process design relying on hard coding is solved, and flexible configuration and rapid adaptation to business needs are achieved, development costs and maintenance complexity are reduced, and maintenance complexity is improved. System flexibility and user experience.
Patent Information
- Application Number
- CN202410924899.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-11
- Publication Date
- 2024-11-08
AI Technical Summary
Traditional business process design and implementation methods rely on hard coding, resulting in in-depth modification of code when business needs change, increasing development and maintenance costs, which is not conducive to the flexibility and scalability of the system. The existing technology is handling complex business processes. The configuration process is abstract, which requires high user requirements and is inconvenient.
Adopt annotation-based business process scalable configuration method, and use a graphical interface to reserve business expansion points to complete the visual orchestration of business processes, supporting non-technical personnel to understand and configure the functional characteristics of business expansion points. Register and manage business expansion points for flexible configuration.
It realizes rapid adaptation to changes in business demand without changing the underlying code, reduces development cycle, reduces system maintenance costs, improves teamwork efficiency and user experience, and enhances the flexibility and maintainability of the system.
Smart Images

Figure CN118916020A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of software engineering, and in particular to an annotation-based business process extensible configuration method and system. Background Art
[0002] In today's software engineering field, with the rapid iteration and changes in business needs, higher requirements are placed on the flexibility and scalability of software systems. Traditional business process design and implementation methods mainly rely on hard coding, that is, solidifying business processes in program source code. When business needs change, the development team needs to go deep into the code level to modify and refactor. This approach not only increases development and maintenance costs, but also may reduce system stability due to frequent changes in core code, and is also not conducive to the long-term evolution and expansion of the system.
[0003] At present, some improvement measures have appeared in the market to meet this challenge. For example, some business process management systems use rule engine technology, allowing users to achieve a certain degree of flexible configuration of business logic by configuring rules. Nevertheless, when these solutions deal with complex, multi-branch, multi-step business processes, the configuration process is relatively abstract, which requires certain business understanding and programming capabilities of users, and there are limitations in process visualization, data flow and intuitive display of control flow.
[0004] Another common technical approach is to use a plug-in architecture or open API interface to reserve extension points, so that external services or components can be seamlessly connected to the existing system, thereby achieving partial expansion and personalized customization of business processes. Although this method improves the openness and scalability of the system to a certain extent, in actual operation, how to efficiently and accurately design and integrate complex business processes still requires the intervention of professional technical teams, and the dynamic configuration and real-time adjustment of business processes are not truly friendly and convenient.
[0005] Although there have been many attempts in the existing technologies to improve the scalability and configurability of business processes, they still have much room for improvement in providing intuitive and easy-to-use visual configuration tools, seamlessly connecting business extension points, and fully supporting the customization of complex business processes. Summary of the invention
[0006] In view of the needs and shortcomings of current technological development, the present invention provides an annotation-based extensible business process configuration method and system to achieve high flexibility and maintainability of the software system, especially in coping with ever-changing business needs.
[0007] In the first aspect, the present invention provides an annotation-based business process extensible configuration method, and the technical solution adopted to solve the above technical problems is as follows:
[0008] An annotation-based business process extensible configuration method includes the following steps:
[0009] S1. Reserve and define at least one interface or module with metadata as a business extension point in the original application where business changes are expected to occur, so as to add new functions or change existing business processes as needed in the future;
[0010] S2. When the application is started, the valid business extension points are identified and registered. The registered business extension points form a configurable service resource pool.
[0011] S3. The registered service extension point information is summarized and presented on a graphical interface, which allows non-technical personnel to view and understand the functional characteristics and configuration details of the registered service extension points;
[0012] S4. Based on the configurable service resource pool, users can add components representing various business extension points on the canvas by dragging and dropping on the graphical interface, and configure corresponding parameters to complete the visual arrangement of business processes.
[0013] Optionally, execute step S1, reserve and define at least one interface or module with metadata as a business extension point at the location where business changes are expected to occur in the original application, and the method is: define an empty method in the project, and add a custom annotation @BusiRule to the defined empty method. The custom annotation @BusiRule contains metadata that describes the characteristics of the business extension point, including function name, rule ID, rule name, input format and output format, providing a detailed information basis for subsequent configuration and orchestration.
[0014] Further optionally, the step S2 specifically includes the following operations:
[0015] S2.1. Trigger scanning at startup: When the application starts, the built-in scanner component is activated. The scanner component traverses the entire application class path and searches for all methods marked with the @BusiRule annotation;
[0016] S2.2. For each @BusiRule annotation found, the scanner component extracts its metadata and performs a validity check. In this process, the extracted metadata includes the function name, rule ID, rule name, input format, and output format. The performed validity checks include: checking that the rule ID is unique and checking whether the input and output formats meet the expected standards.
[0017] S2.3. After extracting and verifying that the information is correct, the scanner component registers these methods marked with the annotation @BusiRule as business extension points in the Redis database.
[0018] Further optionally, step S4 is performed, where the user completes the visual arrangement of the business process by dragging and dropping on the graphical interface, including: connecting to new third-party services, adjusting the order of existing processes, and implementing new business processes;
[0019] The components added by users on the canvas by dragging and dropping on the graphical interface include business components and script components. Among them: business components encapsulate the interface of the business system and hide the technical details; script components support multiple programming languages such as Java, Groovy, JavaScripter and AviatorScript, and are used to process input and output parameters.
[0020] Further optionally, after the user completes the visual orchestration of the business process by dragging and dropping on the graphical interface, when a function in the business process is triggered, the application identifies and runs the corresponding business extension point, the application framework uses the annotation processor to find and execute the business process that matches the business extension point ID at runtime, and the execution engine executes the preset logic according to the configured process.
[0021] In a second aspect, the present invention provides an annotation-based business process extensible configuration system, and the technical solution adopted to solve the above technical problems is as follows:
[0022] An annotation-based business process extensible configuration system, comprising:
[0023] Predefined modules are used to reserve and define at least one interface or module with metadata as a business extension point in the original application where business changes are expected to occur, so as to add new functions or change existing business processes as needed in the future;
[0024] The identification and registration module is used to identify and register valid business extension points when the application is started. The registered business extension points form a configurable service resource pool;
[0025] A summary presentation module is used to summarize the registered business extension point information and present it on a graphical interface, which allows non-technical personnel to view and understand the functional characteristics and configuration details of the registered business extension points;
[0026] The visual orchestration module is used to add components representing various business extension points on the canvas by dragging and dropping on the graphical interface according to the configurable service resource pool, and configure the corresponding parameters to complete the visual orchestration of the business process.
[0027] Optionally, reserve at least one interface or module as a business extension point at the location in the original program where business changes are expected to occur. The specific operation is: define an empty method in the project, and add a custom annotation @BusiRule to the defined empty method. The custom annotation @BusiRule contains metadata that describes the characteristics of the business extension point, including function name, rule ID, rule name, input format, and output format, providing a detailed information basis for subsequent configuration and orchestration.
[0028] Further optionally, the identification and registration module involved specifically includes:
[0029] Trigger scanning unit, which is used to activate the built-in scanner component when the application starts. The scanner component traverses the entire application class path and searches for all methods marked with @BusiRule annotations.
[0030] The extraction check unit is used to extract metadata from the @BusiRule annotation found by the scanner component and perform a validity check. In this process, the extracted metadata includes the function name, rule ID, rule name, input format, and output format. The performed validity checks include: checking that the rule ID is unique and checking whether the input and output formats meet the expected standards.
[0031] The tag registration module is used to register the methods marked with the @BusiRule annotation as business extension points in the Redis database through the scanner component after extracting and verifying that the information is correct.
[0032] Further optionally, the visual arrangement module involved assists the user to complete the visual arrangement of the business process through dragging and dropping operations on the graphical interface, including: connecting to new third-party services, adjusting the order of existing processes, and implementing new business processes;
[0033] The visual orchestration module involved assists users in adding components on the canvas by dragging and dropping on the graphical interface, including business components and script components, among which: the business component encapsulates the interface of the business system and hides the technical details; the script component supports multiple programming languages such as Java, Groovy, JavaScripter and AviatorScript, and is used to process input and output parameters.
[0034] Further optionally, after the user completes the visual orchestration of the business process by dragging and dropping on the graphical interface, when a function in the business process is triggered, the application identifies and runs the corresponding business extension point, the application framework uses the annotation processor to find and execute the business process that matches the business extension point ID at runtime, and the execution engine executes the preset logic according to the configured process.
[0035] The annotation-based business process extensible configuration method and system of the present invention have the following beneficial effects compared with the prior art:
[0036] 1. The present invention introduces the design concept of "business extension point", which can quickly adapt to changes in business needs without changing the underlying code, making it simple and quick to add, adjust or delete business process links, significantly reducing the development cycle caused by demand changes, accelerating product iteration, and enhancing the company's ability to adapt to market changes; the introduction of visual process orchestration tools allows project members with non-technical backgrounds to participate in the design and optimization of business processes, greatly broadening the boundaries of teamwork, not only simplifying the complexity of technical implementation, but also promoting communication and collaboration across departments, and improving overall work efficiency;
[0037] 2. The present invention greatly reduces the workload of development and operation and maintenance through an automated extension point scanning and registration mechanism, avoids repeated manual registration and configuration work, and saves human resources; at the same time, since the adjustment of business logic no longer frequently touches the core code, the system maintenance cost and potential error risks are effectively controlled; the predefined extension points and standardized metadata descriptions provide clear interfaces and specifications for future upgrades and expansions of the system, ensure the openness and modularity of the software architecture, facilitate maintenance and continuous integration of new business functions, and extend the life cycle of software products;
[0038] 3. The present invention arranges the process in a visual way, so that the software system can meet the personalized needs of users more agilely, enhancing the user experience; at the same time, it reduces the downtime caused by system upgrades or business adjustments, ensuring the continuity and stability of the service. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] Attached Figure 1 is a flow chart of a method according to Embodiment 1 of the present invention;
[0040] Attached Figure 2 is a module connection block diagram of the second embodiment of the present invention;
[0041] Attached Figure 3 It is the registered service extension point information displayed on the graphical interface in the embodiment of the present invention. DETAILED DESCRIPTION
[0042] In order to make the technical solution, the technical problem solved and the technical effect of the present invention more clearly understood, the technical solution of the present invention is clearly and completely described below in conjunction with specific embodiments.
[0043] Embodiment 1:
[0044] Combined with Figure 1This embodiment proposes an annotation-based business process extensible configuration method, which includes the following steps:
[0045] S1. Reserve and define at least one interface or module with metadata as a business extension point in the original application where business changes are expected to occur, so as to add new functions or change existing business processes as needed in the future.
[0046] The method used in this step is: define an empty method in the project, and add a custom annotation @BusiRule to the defined empty method. The custom annotation @BusiRule contains metadata that describes the characteristics of the business extension point, including the function name (menuName), rule ID (ruleID), rule name (ruleName), input format (input) and output format (output), providing a detailed information basis for subsequent configuration and orchestration.
[0047] S2. When the application is started, identify and register valid business extension points. The registered business extension points form a configurable service resource pool, which specifically includes the following operations:
[0048] S2.1. Trigger scanning at startup: When the application starts, the built-in scanner component is activated. The scanner component traverses the entire application class path and searches for all methods marked with the @BusiRule annotation;
[0049] S2.2. For each @BusiRule annotation found, the scanner component extracts its metadata and performs a validity check. In this process, the extracted metadata includes the function name (menuName), rule ID (ruleID), rule name (ruleName), input format (input) and output format (output). The performed validity checks include: checking that the rule ID is unique and checking whether the input and output formats meet the expected standards.
[0050] S2.3. After extracting and verifying that the information is correct, the scanner component registers these methods marked with the annotation @BusiRule as business extension points in the Redis database.
[0051] S3. The registered service extension point information is summarized and presented on a graphical interface, which allows non-technical personnel to view and understand the functional characteristics and configuration details of the registered service extension points. Figure 3 ;
[0052] S4. Based on the configurable service resource pool, users can add components representing various business extension points on the canvas by dragging and dropping on the graphical interface, and configure corresponding parameters to complete the visual arrangement of business processes.
[0053] In this step, users can complete the visual arrangement of business processes by dragging and dropping on the graphical interface, including: connecting to new third-party services, adjusting the order of existing processes, and implementing new business processes. All they need to do is simply add components representing each extension point (such as HTTP request nodes) to the canvas and configure the corresponding parameters.
[0054] It should be added that the visual business process orchestration platform can implement multiple types of nodes, such as business components and script components. The components in the business component node are actually interfaces in the business system, which are developed according to the development specifications of the business middle platform; the visual process orchestration framework encapsulates these interfaces, so that the technical details behind the interface can be hidden, such as the request address and request method. In this way, when using these components for process orchestration, you don’t need to care about the technical details behind them, you only need to focus on the business. The script node is mainly used to process input parameters and output parameters, and can support four scripting languages: Java, Groovy, JavaScript, and AviatorScript.
[0055] After the user completes the visual orchestration of the business process by dragging and dropping on the graphical interface, when a function in the business process is triggered, the application identifies and runs the corresponding business extension point. The application framework uses the annotation processor to find and execute the business process that matches the business extension point ID at runtime, and the execution engine executes the preset logic according to the configured process.
[0056] This embodiment takes integral calculation as an example, and reserves the following extension points in the integral calculation function:
[0057] @BusiRule(menuName = "Integral Calculation", ruleId = "integral-rule", ruleName = "Integral Rule",
[0058] input="{\"orderAmount\":100}",output="{\"integral\":1}")
[0059] public String flowConfig(String input){
[0060] return "";
[0061] }
[0062] The input and output in the metadata are input and output samples of process orchestration for reference by process configuration personnel.
[0063] The following code is an example of calling a business extension point. The method calls the reserved business extension point method flowConfig(). In addition to calling this method, the program can also contain other business codes, which are the same as the original development method and are not affected by the extension point:
[0064] / **
[0065] *Calculate points
[0066] * /
[0067] @Override
[0068] public Map caclInteger(BigDecimal orderAmount){
[0069] Map resultMap=new HashMap();
[0070] resultMap.put("orderAmount",orderAmount);
[0071] / / Call process configuration method
[0072] String output=flowConfig(JSONObject.toJSONString(resultMap));
[0073] JSONObject jsonObject=JSONObject.parseObject(output);
[0074] resultMap.put("integral",jsonObject.get("integral"));
[0075] return resultMap;
[0076] }
[0077] In this embodiment, the method of parsing annotations can refer to the following code:
[0078] / **
[0079] * Get all the method names containing annotation in the class
[0080] *
[0081] *@paraminClassList needs to filter the class collection of methods
[0082] *@param annotation annotation class
[0083] * /
[0084] public List <map>getBusiRuleAnnotationInfo(List<Class<?>>inClassList,Class<?extends Annotation>annotation){
[0085] List <map>resultList=new ArrayList<>();
[0086] for(Class<?>myClasss:inClassList){
[0087] Method[]methods=myClasss.getMethods();
[0088] for(Method method:methods){
[0089] if(null!=method&&null!=AnnotationUtils.findAnnotation(method,annotation)){
[0090] try{
[0091] BusiRule busiRule=((BusiRule)AnnotationUtils.findAnnotation(method,annotation));
[0092] Map tempMap=new HashMap();
[0093] tempMap.put("menuName",busiRule.menuName());
[0094] tempMap.put("input",busiRule.input());
[0095] tempMap.put("output",busiRule.output());
[0096] tempMap.put("ruleId",busiRule.ruleId());
[0097] tempMap.put("ruleName",busiRule.ruleName());
[0098] tempMap.put("className",myClasss.getName());
[0099] resultList.add(tempMap);
[0100] Field[]fields=Class.forName(method.getParameterTypes()[0].getName()).newInstance().getClass().getDeclaredFields();
[0101] Map paramMap=new HashMap();
[0102] List <map>list=new ArrayList<>();
[0103] for(Field field:fields){
[0104] ApiModelProperty apiModelProperty=field.getAnnotation(ApiModelProperty.class);
[0105] if(apiModelProperty!=null){
[0106] Map map=new HashMap();
[0107] map.put("value",apiModelProperty.value());
[0108] map.put("name",field.getName());
[0109] map.put("filedType",field.getType().getSimpleName());
[0110] list.add(map);
[0111] }
[0112] }
[0113] paramMap.put("type",method.getParameterTypes()[0].getName());
[0114] paramMap.put("field",list);
[0115] System.out.println(JSONObject.toJSONString(paramMap));
[0116] }catch(Exception e){
[0117] e.printStackTrace();
[0118] }
[0119] }
[0120] }
[0121] }
[0122] return resultList;
[0123] }
[0124] Embodiment 2:
[0125] Combined with Figure 2 , this embodiment proposes an annotation-based business process extensible configuration system, which includes:
[0126] Predefined modules are used to reserve and define at least one interface or module with metadata as a business extension point in the original application where business changes are expected to occur, so as to add new functions or change existing business processes as needed in the future;
[0127] The identification and registration module is used to identify and register valid business extension points when the application is started. The registered business extension points form a configurable service resource pool;
[0128] A summary presentation module is used to summarize the registered business extension point information and present it on a graphical interface, which allows non-technical personnel to view and understand the functional characteristics and configuration details of the registered business extension points;
[0129] The visual orchestration module is used to add components representing various business extension points on the canvas by dragging and dropping on the graphical interface according to the configurable service resource pool, and configure the corresponding parameters to complete the visual orchestration of the business process.
[0130] In this embodiment, at least one interface or module is reserved as a business extension point at a location in the original program where business changes are expected to occur. The specific operations are: defining an empty method in the project, and adding a custom annotation @BusiRule to the defined empty method. The custom annotation @BusiRule contains metadata that describes the characteristics of the business extension point, including function name, rule ID, rule name, input format, and output format, providing a detailed information basis for subsequent configuration and orchestration.
[0131] In this embodiment, the identification and registration module involved specifically includes:
[0132] Trigger scanning unit, which is used to activate the built-in scanner component when the application starts. The scanner component traverses the entire application class path and searches for all methods marked with @BusiRule annotations.
[0133] The extraction check unit is used to extract metadata from the @BusiRule annotation found by the scanner component and perform a validity check. In this process, the extracted metadata includes the function name, rule ID, rule name, input format, and output format. The performed validity checks include: checking that the rule ID is unique and checking whether the input and output formats meet the expected standards.
[0134] The tag registration module is used to register the methods marked with the @BusiRule annotation as business extension points in the Redis database through the scanner component after extracting and verifying that the information is correct.
[0135] In this embodiment, the visual arrangement module involved assists the user to complete the visual arrangement of the business process through dragging operations on the graphical interface, including: connecting to new third-party services, adjusting the order of existing processes, and implementing new business processes;
[0136] The visual orchestration module involved assists users in adding components on the canvas by dragging and dropping on the graphical interface, including business components and script components, among which: the business component encapsulates the interface of the business system and hides the technical details; the script component supports multiple programming languages such as Java, Groovy, JavaScripter and AviatorScript, and is used to process input and output parameters.
[0137] It should be added that after the user completes the visual orchestration of the business process by dragging and dropping on the graphical interface, when a function in the business process is triggered, the application identifies and runs the corresponding business extension point. The application framework uses the annotation processor to find and execute the business process that matches the business extension point ID at runtime, and the execution engine executes the preset logic according to the configured process.
[0138] In summary, the annotation-based extensible business process configuration method and system of the present invention can realize flexible customization and dynamic change of business processes through preset annotations and visual arrangement.
[0139] The above specific examples are used to explain the principles and implementation methods of the present invention in detail. These examples are only used to help understand the core technical content of the present invention. Based on the above specific embodiments of the present invention, any improvements and modifications made by technicians in this technical field without departing from the principles of the present invention should fall within the scope of patent protection of the present invention.< / map> < / map> < / map>
Claims
1. A business process extensible configuration method based on annotations, characterized in that: The steps include: S1. Reserve and define at least one interface or module with metadata as a business extension point in the original application where business changes are expected to occur, so as to add new functions or change existing business processes as needed in the future; S2. When the application is started, the valid business extension points are identified and registered. The registered business extension points form a configurable service resource pool. S3. The registered service extension point information is summarized and presented on a graphical interface, which allows non-technical personnel to view and understand the functional characteristics and configuration details of the registered service extension points; S4. Based on the configurable service resource pool, users can add components representing various business extension points on the canvas by dragging and dropping on the graphical interface, and configure corresponding parameters to complete the visual arrangement of business processes.
2. The annotation-based business process extensible configuration method according to claim 1, characterized in that: Execute step S1, reserve and define at least one interface or module with metadata as a business extension point at the location where business changes are expected to occur in the original application, and use the following method: define an empty method in the project, and add a custom annotation @BusiRule to the defined empty method. The custom annotation @BusiRule contains metadata that describes the characteristics of the business extension point, including function name, rule ID, rule name, input format, and output format, providing a detailed information basis for subsequent configuration and orchestration.
3. The annotation-based business process extensible configuration method according to claim 2, characterized in that: The step S2 specifically includes the following operations: S2.
1. Trigger scanning at startup: When the application starts, the built-in scanner component is activated. The scanner component traverses the entire application class path and searches for all methods marked with the @BusiRule annotation; S2.
2. For each @BusiRule annotation found, the scanner component extracts its metadata and performs a validity check. In this process, the extracted metadata includes the function name, rule ID, rule name, input format, and output format. The performed validity checks include: checking that the rule ID is unique and checking whether the input and output formats meet the expected standards. S2.
3. After extracting and verifying that the information is correct, the scanner component registers these methods marked with the annotation @BusiRule as business extension points in the Redis database.
4. The annotation-based business process extensible configuration method according to claim 3, characterized in that: Execute step S4, the user completes the visual arrangement of the business process by dragging and dropping on the graphical interface, including: connecting to new third-party services, adjusting the order of existing processes, and implementing new business processes; The components added by users on the canvas by dragging and dropping on the graphical interface include business components and script components. Among them: business components encapsulate the interface of the business system and hide the technical details; script components support multiple programming languages such as Java, Groovy, JavaScripter and AviatorScript, and are used to process input and output parameters.
5. The annotation-based business process extensible configuration method according to claim 4, characterized in that: After the user completes the visual orchestration of the business process by dragging and dropping on the graphical interface, when a function in the business process is triggered, the application identifies and runs the corresponding business extension point. The application framework uses the annotation processor to find and execute the business process that matches the business extension point ID at runtime, and the execution engine executes the preset logic according to the configured process.
6. An annotation-based business process extensible configuration system, characterized in that: It includes: Predefined modules are used to reserve and define at least one interface or module with metadata as a business extension point in the original application where business changes are expected to occur, so as to add new functions or change existing business processes as needed in the future; The identification and registration module is used to identify and register valid business extension points when the application is started. The registered business extension points form a configurable service resource pool; A summary presentation module is used to summarize the registered business extension point information and present it on a graphical interface, which allows non-technical personnel to view and understand the functional characteristics and configuration details of the registered business extension points; The visual orchestration module is used to add components representing various business extension points on the canvas by dragging and dropping on the graphical interface according to the configurable service resource pool, and configure the corresponding parameters to complete the visual orchestration of the business process.
7. The annotation-based business process extensible configuration system according to claim 6, characterized in that: At least one interface or module is reserved as a business extension point at the location where business changes are expected in the original program. The specific operation is: define an empty method in the project, add a custom annotation @BusiRule to the defined empty method, and the custom annotation @BusiRule contains metadata that describes the characteristics of the business extension point, including function name, rule ID, rule name, input format and output format, providing a detailed information basis for subsequent configuration and orchestration.
8. The annotation-based business process extensible configuration system according to claim 7, characterized in that: The identification and registration module specifically includes: Trigger scanning unit, which is used to activate the built-in scanner component when the application starts. The scanner component traverses the entire application class path and searches for all methods marked with @BusiRule annotations. The extraction check unit is used to extract metadata from the @BusiRule annotation found by the scanner component and perform a validity check. In this process, the extracted metadata includes the function name, rule ID, rule name, input format, and output format. The performed validity checks include: checking that the rule ID is unique and checking whether the input and output formats meet the expected standards. The tag registration module is used to register the methods marked with the @BusiRule annotation as business extension points in the Redis database through the scanner component after extracting and verifying that the information is correct.
9. The annotation-based business process extensible configuration system according to claim 8, characterized in that: The visual arrangement module assists users in completing the visual arrangement of business processes through dragging operations on the graphical interface, including: connecting to new third-party services, adjusting the order of existing processes, and implementing new business processes; The visual orchestration module assists the user in adding components on the canvas by dragging on the graphical interface, including business components and script components, wherein: the business component encapsulates the interface of the business system and hides the technical details; the script component supports multiple programming languages such as Java, Groovy, JavaScripter and AviatorScript, and is used to process input and output parameters.
10. The annotation-based business process extensible configuration system according to claim 9, characterized in that: After the user completes the visual orchestration of the business process by dragging and dropping on the graphical interface, when a function in the business process is triggered, the application identifies and runs the corresponding business extension point. The application framework uses the annotation processor to find and execute the business process that matches the business extension point ID at runtime, and the execution engine executes the preset logic according to the configured process.
