摘要：【中文】本发明公开了数据管理类的软件系统代码自动生成方法，包括：完成软件开发前置工作，以建立软件系统所需要的数据库及相关字段；编写代码生成工具，通过所述代码生成工具读取数据库内的数据结构元数据；建立数据结构元数据的实体映射类变量及代码文件生成逻辑；根据实体映射类产量，采用模版引擎语法结合代码规范，编写模版文件；配置各个代码文件生成的目录；运行代码生成工具，将表结构信息加载到实体映射类变量；将加载后的实体映射类变量遍历输入到模版文件中，生成代码文件至指定的目录；对目录内的代码文件进行微调，补充个性的业务逻辑，完成增删改查功能及单元测试编码工作。对指定目录的具体代码进行人工调整，以补充个性业务逻辑。 【EN】The invention discloses a method for automatically generating software system codes of data management classes, which comprises the following steps: completing the prepositive work of software development to establish a database and related fields required by a software system; writing a code generation tool, and reading data structure metadata in a database through the code generation tool; establishing entity mapping type variables and code file generation logic of data structure metadata; according to the entity mapping type yield, compiling a template file by combining template engine grammar and code specifications; configuring a directory generated by each code file; running a code generation tool, and loading the table structure information to an entity mapping type variable; traversing and inputting the loaded entity mapping type variable into a template file, and generating a code file to a specified directory; and finely adjusting the code files in the directory, supplementing individual service logic, and completing the work of adding, deleting, modifying, checking functions and unit testing and coding. The specific code of the designated directory is manually adjusted to supplement the individual service logic.

摘要：【中文】本发明公开了协作流程异常处理方法包括：执行主业务逻辑的A段直至A段执行结束；当主业务逻辑有调用需要时，调用外部接口获取次要逻辑C段；当调用失败时，启用异步任务创建和伪状态更新逻辑后，生成次要逻辑执行情况的返回值；当调用成功时，直接生成次要逻辑执行情况的返回值；接收次要逻辑执行情况的返回值并更新主业务逻辑内的数据；继续运行主业务逻辑后续的逻辑B段，并接收由消息服务系统推送的主业务逻辑执行情况的任务结果消息；根据任务结果消息中的返回码将实际业务中的相关代码和状态更新；记录业务逻辑执行日志。在非因果关系系统间调用出现异常时保障主流程操作的正常进行，也可保障非因果关系的调用操作最终会被执行。 【EN】The invention discloses a method for processing an exception of a cooperative flow, which comprises the following steps: executing the A section of the main service logic until the A section is executed; when the main service logic needs to be called, calling an external interface to obtain a secondary logic section C; when the calling is failed, after the asynchronous task creation and the pseudo state updating logic are started, a return value of the secondary logic execution condition is generated; when the calling is successful, directly generating a return value of the secondary logic execution condition; receiving a return value of the execution condition of the secondary logic and updating data in the main business logic; continuing to operate the subsequent logic B section of the main service logic, and receiving a task result message of the main service logic execution condition pushed by the message service system; updating relevant codes and states in the actual service according to the return codes in the task result message; and recording the service logic execution log. When the call between the non-causal relationship systems is abnormal, the normal operation of the main flow operation is guaranteed, and the call operation of the non-causal relationship can be guaranteed to be executed finally.