Method for automatically developing arrangement process

Abstract

The invention provides a method for automatically developing an arrangement process, belongs to the technical field of software development automation, and realizes the automatic development of the arrangement process by pre-defining a configuration file template. Comprising the following steps: formulating a standard configuration file template, and configuring information of a process Chinese name, a process English name, a service main table and an order sending message; reading and analyzing the content of the configuration file; and automatically executing a development and arrangement process according to preset steps, wherein the development and arrangement process comprises generation of a service main table, a data model, atomic power, order receiving task design, work order details, a service flow chart, product and service process binding and the like. The development efficiency can be remarkably improved, repeated work is reduced, manual operation errors are reduced, and standardization and automation of the development and arrangement process are achieved.

Description

Technical Field

[0001] This invention relates to the field of software development automation technology, and in particular to a method for automating the development of orchestration processes. Background Technology

[0002] The role of orchestration processes is to support the construction and operation of inbound customer services. With the continuous development of the social economy, the demand for dedicated lines from various departments is increasing, giving rise to many new types of services. In order to respond quickly to market demands, customers have an urgent need for the rapid deployment of dedicated line orchestration processes, which drives the R&D team to continuously improve the development efficiency of orchestration processes.

[0003] The current orchestration process involves eight mandatory manual operations: writing SQL table creation statements based on dispatch messages, generating data models, creating atomic capabilities, configuring dispatch task designs, drawing work order detail forms, creating products and flowcharts, and finally establishing binding relationships between products and flowcharts. These operations are essential for all orchestration business process development and are highly repetitive. Currently, there is no automated development solution; all steps must be performed manually by developers, which is tedious, time-consuming, error-prone, and lacks standardization. Summary of the Invention

[0004] To address the above technical problems, this invention provides a method for automating the development of orchestration processes, solving the problems of high repetition, tediousness, and time consumption in the development of business orchestration processes.

[0005] The technical solution of this invention is:

[0006] A method for automating orchestration process development includes the following steps:

[0007] S1. Construct a layered configuration template: Create a structured configuration file template containing a basic information layer, a process information layer, and a business information layer. The basic information layer defines the product code, operation code, and main table name. The process information layer defines the English name of the process, the Chinese name of the process, and the work order code. The business information layer defines the dispatch message structure and business rules.

[0008] S2. Parsing and Validating Configuration: The parsing engine performs structured parsing of the JSON format configuration file, extracts configuration parameters and builds an in-memory object model, and synchronously performs format validation, field integrity validation and business rule validation.

[0009] S3, Distributed Automatic Generation: Executes eight core processing services in parallel through a distributed processing engine, including:

[0010] Generates SQL statements for creating the business master table based on the master table name and dispatch message; generates data model definitions and attribute sets based on the master table name and dispatch message; generates dispatch atomic capability metadata and interface parameters based on basic information and business information; generates dispatch task nodes, execution sequences, and attribute mappings based on business information; generates work order detail orchestration configuration based on dispatch information; generates flowchart definitions based on process configuration; generates product information SQL scripts based on basic information; and binds products and processes to SQL scripts based on flowcharts and product outputs.

[0011] Furthermore,

[0012] In step S1, the basic information layer, process information layer and business information layer adopt a decoupled design. The dispatch message structure of the business information layer includes field name, data type, length and field description metadata.

[0013] Furthermore,

[0014] In step S2, the JSON configuration is converted into a tree-shaped memory object by a syntax parser.

[0015] When verifying field integrity, check whether the product code in the basic information layer, the English name of the process in the process information layer, and the dispatch message in the business information layer are non-empty values; business rule verification includes main table naming convention verification and process code uniqueness verification.

[0016] Furthermore,

[0017] The process of generating the business master table SQL statement based on the master table name and dispatch message involves the following operations: parsing the camelCase naming of the dispatch message fields and converting them to underscore format; mapping the field type to the database type; and generating a transaction-safe SQL file through the context manager.

[0018] The process generates data model definitions and attribute sets based on the main table name and dispatch message, generates model definition information and model attributes, and outputs a table file that can be directly imported into the model management system.

[0019] The process generates dispatch atomic capability metadata and interface parameters based on basic information and business information, generates basic atomic capability information and input / output parameters, and outputs a table file that can be directly imported into the atomic capability management system.

[0020] The system generates task nodes, execution sequences, and attribute mappings based on business information, generates model tasks, model task execution order, and model task attributes, and outputs a table file that can be directly imported into the task orchestration system.

[0021] The process involves generating work order details and arranging configurations based on dispatch information, generating custom services, custom service tasks, model saving tasks, and model saving parameters, and outputting a table file that can be directly imported into a low-code platform.

[0022] The process configuration generates a flowchart definition, which generates basic process information, order acceptance service information, basic information of each step, and connection information of each step, and outputs a table file that can be directly imported into the workflow engine.

[0023] The SQL script for generating product information based on basic information generates product type, product name, product code, and CRM product code, and outputs it as an executable SQL script.

[0024] The beneficial effects of this invention are

[0025] This invention provides a method for automating the development of orchestration processes based on configuration files. It enables the automatic generation of business master tables, data models, atomic capabilities, order task design, work order details, business process diagrams, and the binding relationship between flowcharts and products. This reduces repetitive work in business orchestration process development by 30%, greatly improves development efficiency and accuracy, and makes business orchestration process development more standardized and automated. Attached Figure Description

[0026] Figure 1 This is a schematic diagram of the overall architecture and workflow of the present invention;

[0027] Figure 2 This is a schematic diagram of the configuration file template structure. Detailed Implementation

[0028] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are some embodiments of the present invention, but not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0029] This invention discloses a method for implementing an automated development orchestration process based on configuration files. This method automates the development of the orchestration process by using predefined configuration file templates. For example... Figure 1As shown, the method includes: defining a standard configuration file template, configuring four pieces of information: Chinese name of the process, English name of the process, business master table, and dispatch message; reading and parsing the configuration file content; and automatically executing the development orchestration process according to eight preset steps, including generating the business master table, data model, atomic capabilities, order receiving task design, work order details, business process diagram, and binding of products and business processes.

[0030] The automated development process implementation method of the present invention includes the following core modules and their technical features:

[0031] 1. This automated development process implementation method includes a configuration file template module. For example... Figure 2 As shown, this module adopts a layered and scalable metadata architecture, realizing the design concept of structured, standardized, and highly cohesive configuration information. Its layered architecture includes a basic information layer (product code, operation code, master table name configuration), a process information layer (process English name, process Chinese name, work order code configuration), and a business information layer (dispatch message, business rule configuration). This effectively solves the problems of scattered configuration information, heterogeneous formats, and difficult maintenance in traditional development, establishing a unified and standardized configuration data input standard, laying a solid foundation for subsequent automated processing.

[0032] 2. This automated development process implementation method includes a configuration file parsing module. This module primarily performs structured parsing and validation of the input JSON format configuration file. Utilizing the built-in parsing engine, it extracts key configuration parameters at each level, constructs a complete configuration object model in memory, and rigorously performs multi-level validation, such as syntax format validation, required field integrity validation, and business rule compliance validation, to ensure the accuracy, completeness, and compliance of the input configuration data, providing a reliable and consistent data source for the automation engine.

[0033] 3. The automated development process implementation method includes an automated processing engine application module. This module adopts a distributed, loosely coupled microservice architecture, decomposing the entire development process into eight independent, atomic core processing services. Each service runs as an independent microservice, with its own task queue and execution engine. The engine's built-in intelligent task scheduler dynamically optimizes the task execution order based on factors such as inter-task dependencies and system resource utilization, maximizing overall processing efficiency. The functional descriptions of each core service are as follows:

[0034] (1) Generate main table service. This service parses all fields, field descriptions, field types, field lengths, etc. in the dispatch message based on the main table name and business information in the basic information of the configuration file, converts the fields from camelCase to underscore format, uses the context manager to safely process the file, and finally outputs an executable business main table creation statement SQL file.

[0035] (2) Data Model Generation Service: This service extracts key data from the main table name in the basic information of the configuration file and the dispatch message in the business information to generate model definition information and model attributes. The model definition includes a unique identifier, model name, model code, physical table name, etc. Model attributes include a unique identifier, attribute name, attribute code, physical column name, attribute type, database type, nullability, displayability, field collection, attribution enumeration, translation field, dictionary lookup, multi-selectability, data status, attribution model, translation function, field source, sequence number, attribute grouping, primary key, primary key generation strategy, etc. All generated content is processed by an Excel file processor, outputting a spreadsheet file that can be directly imported into the model management system. The data model is essentially a visual management of the main business table, allowing for quick addition, deletion, and modification of table fields, and also provides a storage mapping between dispatch message fields and main table fields.

[0036] (3) Generate atomic capability services. These services contain basic information and business information in the base configuration file. First, generate basic atomic capability information, including the service's Chinese name, English name, version, service type, applicable products, service address, and service method. Then, generate atomic capability input and output parameter information, including parameter category, service's English name, parameter name, whether the parameter is nullable, parameter type, parameter code, and parent parameter identifier. Finally, process the data using an Excel file processor to output a spreadsheet file that can be directly imported into the atomic capability management system. The function of atomic capabilities is to receive all data from dispatch messages and pass it to the task design.

[0037] (4) The order-taking task design service generates three parts based on the business information in the configuration file: the model task, the execution order of the model task, and the model task attributes. The model task includes information such as task identifier, task name, task type, model code, model name, mapping relationship, and mapping node. The model task execution order includes information such as sequence identifier, atomic capability code, task identifier, task name, and execution order. The model task attributes include information such as attribute identifier, task identifier, attribute code, attribute name, attribute type, mapping node, translation code, and dependency attributes. All generated information is processed through an Excel file processor, and the output is a spreadsheet file that can be directly imported into the task orchestration system. The main function of the order-taking task design is to establish the mapping relationship between dispatch fields and table fields, serving as the data storage basis when generating work orders.

[0038] (5) Generate Work Order Details Service. This service generates four parts based on the dispatch information in the configuration file: custom service, custom service task, model saving task, and model saving parameters. The custom service task includes information such as the service's Chinese name, service's English name, version, service type, and custom form message. It also includes information such as primary key identifier, service code, task identifier, task name, and sorting. The model saving parameters include information such as primary key identifier, task identifier, attribute code, attribute name, and reference parameters. The model saving task includes information such as primary key identifier, task name, task type, model code, model name, reference type, and reference parameters. All generated information is processed through an Excel file processor, and the output is a spreadsheet file that can be directly imported into the low-code platform. Work Order Details is a front-end information presentation component based on the low-code form designer, used to present the dispatch content of the workflow.

[0039] (6) Flowchart Generation Service: This service generates four types of information based on the flow configuration information in the configuration file: basic flow information, order acceptance service information, basic step information, and step connection information. Basic flow information includes the English name of the flow, the Chinese name of the flow, the version number, and the topology message. Order acceptance service information includes the Chinese name of the service, the English name of the service, the service version, and the service type. Basic step information includes the Chinese name of the step, the English name of the step, the horizontal offset, the vertical offset, and the step type. Step connection information includes the Chinese name of the connection, the English name of the connection, the English name of the starting point, the English name of the ending point, the horizontal offset of the starting point, the vertical offset of the starting point, the horizontal offset of the ending point, and the vertical offset of the ending point. All generated information is processed by an Excel file processor, outputting a spreadsheet file that can be directly imported into the workflow engine. A flowchart is a type of workflow used to carry business processing logic.

[0040] (7) Generate product service. This service generates product information based on the basic information in the configuration file, including product type, product name, product code, CRM product code, and finally outputs an executable SQL file.

[0041] (8) Product-to-Flowchart Binding Service: This service establishes a binding relationship between the generated product and the flowchart, and finally outputs an executable SQL file.

[0042] The above description is merely a preferred embodiment of the present invention and is used only to illustrate the technical solution of the present invention, and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention are included within the scope of protection of the present invention.

Claims

1. A method for automating the development of orchestration processes, characterized in that, Includes the following steps: S1. Construct a layered configuration template: Create a structured configuration file template containing a basic information layer, a process information layer, and a business information layer. The basic information layer defines the product code, operation code, and main table name. The process information layer defines the English name of the process, the Chinese name of the process, and the work order code. The business information layer defines the dispatch message structure and business rules. S2. Parsing and Validating Configuration: The parsing engine performs structured parsing of the JSON format configuration file, extracts configuration parameters and builds an in-memory object model, and synchronously performs format validation, field integrity validation and business rule validation. S3, Distributed Automatic Generation: Executes eight core processing services in parallel through a distributed processing engine, including: Generates SQL statements for creating the main business table based on the main table name and dispatch message; generates data model definitions and attribute sets based on the main table name and dispatch message; generates dispatch atomic capability metadata and interface parameters based on basic information and business information; generates dispatch task nodes, execution sequences, and attribute mappings based on business information; generates work order detail orchestration configuration based on dispatch information; generates flowchart definitions based on process configuration; generates product information SQL scripts based on basic information; and generates SQL scripts to bind products and processes based on flowcharts and product outputs.

2. The method as described in claim 1, characterized in that, In step S1, the basic information layer, process information layer and business information layer adopt a decoupled design. The dispatch message structure of the business information layer includes field name, data type, length and field description metadata.

3. The method as described in claim 1, characterized in that, In step S2, the JSON configuration is converted into a tree-shaped memory object by a syntax parser. When verifying field integrity, check whether the product code in the basic information layer, the English name of the process in the process information layer, and the dispatch message in the business information layer are non-empty values; business rule verification includes main table naming convention verification and process code uniqueness verification.

4. The method as described in claim 1, characterized in that, The process of generating the business master table SQL statement based on the master table name and dispatch message involves the following operations: parsing the camelCase naming of the dispatch message fields and converting them to underscore format; mapping the field type to the database type; and generating a transaction-safe SQL file through the context manager.

5. The method as described in claim 1, characterized in that, The process generates data model definitions and attribute sets based on the main table name and dispatch message, generates model definition information and model attributes, and outputs a table file that can be directly imported into the model management system.

6. The method as described in claim 1, characterized in that, The process generates dispatch atomic capability metadata and interface parameters based on basic information and business information, generates basic atomic capability information and input / output parameters, and outputs a table file that can be directly imported into the atomic capability management system.

7. The method as described in claim 1, characterized in that, The system generates task nodes, execution sequences, and attribute mappings based on business information, generates model tasks, model task execution order, and model task attributes, and outputs a table file that can be directly imported into the task orchestration system.

8. The method as described in claim 1, characterized in that, The process involves generating work order details and arranging configurations based on dispatch information, generating custom services, custom service tasks, model saving tasks, and model saving parameters, and outputting a table file that can be directly imported into a low-code platform.

9. The method as described in claim 1, characterized in that, The process configuration generates a flowchart definition, which generates basic process information, order acceptance service information, basic information of each step, and connection information of each step, and outputs a table file that can be directly imported into the workflow engine.

10. The method as claimed in claim 1, characterized in that, The SQL script for generating product information based on basic information generates product type, product name, product code, and CRM product code, and outputs it as an executable SQL script.

Images