A software automation production method in cloud environment

Abstract

The present invention relates to the field of automated software production, and discloses a method for automated software production in a cloud environment, including: creating a blank application based on user information, determining whether there is a scene template that matches the target scene of the blank application, configuring the scene layout based on a layout board, dragging and registering the component to the layout board according to the component information, translating the virtual coordinate information of the registered component into actual physical screen pixels, rendering the component, packaging based on an encapsulation tool, parsing the structure from the layout, formulating a standard data structure based on a data center server, monitoring the data center server using a third-party system based on user operation permissions, and publishing the application to a cloud platform after the configured application is reviewed and approved. The present invention improves software production efficiency, and produces software products that meet user needs in a high-quality and efficient manner.

Description

Technical Field

[0001] The present invention relates to the field of automated software production, and in particular to an automated software production method in a cloud environment. Background Art

[0002] The traditional software development method ("waterfall model" or "sequential development model"), as a classic software development method, is characterized by being executed in phases, and each phase is relatively independent. The phase division mainly includes requirements analysis, system design, detailed design, coding, testing (including unit testing, integration testing, system testing, acceptance testing, etc.), deployment and maintenance; each phase has clear inputs and outputs, and the output is usually a document or code. It emphasizes "sequentiality, document-driven, and phased review", and is carried out strictly in the established order, and the order is irreversible; it emphasizes the importance of written documents, and each step is carefully documented; at the end of each phase, a formal review is required to ensure that the conditions for entering the next phase are met.

[0003] With the rapid development of information technology, the field of software development is developing rapidly in a more flexible and efficient direction, while also paying more attention to ease of use to adapt to the rapidly changing market needs and technical environment. Traditional software development methods are no longer suitable for a rapidly changing environment, and there are some potential disadvantages: long development cycle. After getting the project, it is necessary to go through a series of processes such as demand analysis-design-coding-testing-acceptance-production deployment, which is relatively cumbersome, resulting in a long cycle from design to market launch; slow update iteration. After the product is released, the update and iteration of functions may not be fast enough to keep up with market changes; poor reusability and maintainability. Traditional methods tend to produce tightly coupled code, which is not conducive to module reuse and later maintenance; lack of flexibility. Traditional software development may not be flexible enough to adapt to the changing needs of customers; low user participation. Traditional development models may rarely involve user feedback, resulting in products that may not fully meet the actual needs of users; high maintenance costs. As the complexity of the software increases, the cost of maintenance and upgrades may be high; technical debt. Long-term accumulated technical debt may affect the long-term maintainability and scalability of the software.

[0004] In order to solve the shortcomings of traditional software development methods, it is urgent to propose a software automation production method based on a cloud environment to improve software production efficiency, so as to produce high-quality and efficient software products that meet user needs. Summary of the invention

[0005] The purpose of the present invention is to overcome one or more of the above-mentioned existing technical problems and provide a method for automated software production in a cloud environment.

[0006] To achieve the above object, the present invention provides a method for automated software production in a cloud environment, comprising:

[0007] Get user information, create a blank application based on the user information, determine whether there is a scene template that matches the target scene of the blank application, if not, initialize the blank scene, build relevant dependency information, and configure the scene layout for it. If there is, reuse the existing scene configuration based on the scene template import method and privatize the imported scene configuration;

[0008] Configure the layout of the scene based on the layout board, initialize the layout information, call the layout board to register the node type, drag and register the component to the layout board according to the component information, use the layout board to package the component, package the component into a layout node with relevant information, obtain the messages that each component supports sending and receiving, select the message sending and receiving ends, configure the trigger conditions by connecting, and realize component communication;

[0009] Translate the virtual coordinate information of the registered component into actual physical screen pixels, render the component, automatically calculate the display position and size on the screen, combine the hierarchical parameters, node configuration and build an independent environment, so as to initialize the blank area of ​​the component, build the context information of the component, build an independent scope based on the HTML and JavaScript information corresponding to the component type, and mount the upper and lower information;

[0010] Based on the encapsulation tool, the components are packaged and each component is packaged into independent component JavaScript information. The components are self-managed in terms of dependencies, and the components are regularly cleaned up. The components are forced to assemble and pass environment-level data, and different components are isolated.

[0011] Parse the structure from the layout, identify the nested modules, obtain the configuration and personalized configuration page information from the module pool based on the unique identifier of the module, initialize the configuration container in the sandbox environment, inject the key context parameters into the container as the basis for configuration level identification, so that the module can perceive the environment, embed the personalized configuration page into the above container, use the container framework to load and present the configuration, and complete the configuration interaction;

[0012] A standard data structure is formulated based on the data hub server for data interaction between modules and the data hub server. Based on data fields, the information representation structure is standardized and the field behavior is regulated, so as to initialize and assign values ​​to the modules. The data hub server uniformly manages the relationship between data. The source module and the target module are bridged through the data hub server, and the module data changes are realized based on the data triggers in the data hub server.

[0013] Based on user operation permissions, the third-party system is used to monitor, query and synchronize data on the data center server. When the data on the data center server changes, the data is pushed to the third-party system.

[0014] Review the configured applications, publish them to the cloud platform after they pass the review, monitor application information in real time, and privatize the applications.

[0015] According to one aspect of the present invention, the scene configuration import and export are sliced, and the special processing handles for each type of configuration are refined. Each type of configuration is placed in a file independently to generate import resources. The scene configuration is analyzed and organized into a file stream to simulate the export file effect. The file stream includes the scene layout resource flow, the module pool data flow, the module specific configuration flow and other dependent resource flows. Based on the operation handle corresponding to the file stream, the import logic distribution execution is completed, the import status is updated and the operation reminder is sent.

[0016] According to one aspect of the present invention, a layout board is virtually laid out, and the size and position of components on the virtual layout board are virtualized. The number of components occupying the layout board is used to represent the actual size and position of the components. The width of the layout board is equally divided into 24 parts, and the height of each part is fixed at 30px. When dragging to adjust the position of the component, it is abstracted into the number of height and width. When rendering, the virtual size and coordinates are converted to actual values;

[0017] Get the position information of existing components on the layout board and generate a two-dimensional grid. The grid without layout components is represented by a blank space. According to the starting point of the dragged and dropped component and the default size of the component, collision detection is performed in the two-dimensional grid. If there is overlap with the position of the newly registered component, it is moved down and the position change information is saved.

[0018] According to one aspect of the present invention, a hook method is used to distribute component node types, filter out components that can be added, analyze selectable components based on hierarchical configuration parameters, select components, assemble hierarchical parameters to generate new modules, mark the modules, and analyze whether the module exists in the module pool. If so, reuse the ID value of the corresponding level. If not, reallocate the ID value to store the module in the business module pool, execute module configuration privatization, add module nodes and basic information to the layout table, notify other dependencies for asynchronous processing, attach module data to the layout node, and render the layout board.

[0019] According to one aspect of the present invention, when module data in the data center server changes, the data service is notified to receive the change, and based on the data service inbox message, it is determined whether data triggering needs to be executed. If necessary, it is analyzed whether the module to which the current data belongs is configured with a data trigger, and the trigger and the corresponding number of modules need to be analyzed based on the change, and data operations that meet the update field filtering conditions are filtered. Based on the source module data, the dynamic fields and source data field values ​​in the target module are sorted and analyzed, and the mapping is sorted into the fixed values ​​required by the target module. The data of the target module is configured accordingly, the standard API of the target module is called, and an association relationship with the source module is established, and the index value of the target module data in the source module is sorted.

[0020] According to one aspect of the present invention, when the data of the data hub server module changes, the data service is notified to receive the data, and a push task is constructed based on the message received by the data service inbox;

[0021] Obtain module information based on the data level, analyze whether the module enables data push and whether it meets the push conditions, and merge the push tasks for this data in the queue;

[0022] Based on the push configuration data results, map it into the structure required by the third-party system, assemble the push data, and determine whether the push data needs to be encrypted;

[0023] Analyze the push data results. If the data push fails, determine whether the data needs to be added to the push queue again.

[0024] According to one aspect of the present invention, the data center server organizes the received module data and integrates the related information between different module data, wherein the method is to analyze the module key information, data title and operation data primary key Id, and in response to the new data change operation, verify whether the data primary key Id is unique. If not, directly return an error message. If it is unique, assemble the data for insertion. In response to the update data change operation, verify whether the data primary key Id data exists. If not, directly return an error message. If it exists, update the data title. In response to the delete data change operation, verify whether the data primary key Id data exists. If not, directly return an error message. If it exists, perform a data deletion operation. Analyze whether the module data change needs to synchronize related data. If it does not exist, ignore it directly. If it exists, analyze the related operation and write it synchronously into the association relationship table.

[0025] In response to the new data change operation, exclusive index information unique to this field is constructed and saved in the data center server index library. In response to the update data change operation, the old data row and the new data row data are extracted, and the specific changed field information is analyzed based on the field column of the standard data, and exclusive index information of the changed field information is constructed, and incrementally updated to the data center server index library. In response to the update data change operation, this index analysis module relationship change operation is deleted from the data center server index library. In response to the new data change operation, exclusive index data information unique to this field is constructed and then saved to the data center server index library.

[0026] According to one aspect of the present invention, when creating or deleting data, a field assertion method based on a standard data field is used to determine whether a trigger condition is met;

[0027] When updating data, the old and new data rows are extracted, and the specific changed field information is analyzed based on the standard data field to determine whether it meets the configured field value change conditions. If not, it is ignored; otherwise, the field assertion method of the standard data field is used to determine whether the trigger condition is met;

[0028] Sort out the data range and specific response operation information of the target module when responding to the operation. Based on the source data field + data row, construct the data field value configured in the response operation into a specific fixed value field, analyze the context information of the source data and construct mandatory context information.

[0029] Based on the target module tag, read the data integration API registered by the target module. If it does not exist, it will force an error. According to the response operation type, execute different data integration APIs, analyze the API execution results, and record the data trigger log.

[0030] If the target module responds to newly created data, it analyzes the newly created data ID and then builds an associated record with the current source data.

[0031] According to one aspect of the present invention, exclusive log information is constructed based on data field configuration, old data rows and new data rows to analyze data changes, and in response to a new data change operation, exclusive log change information for each field is constructed based on the field column configuration;

[0032] In response to the update data change operation, based on the standard data fields, the specific change fields are analyzed and the log change information exclusive to these fields is constructed;

[0033] In response to the deletion data change operation, directly record the deletion log information;

[0034] Analyze and check whether there is a log for the current data. If so, add it to the data log record table and delete it from the log table as a basis for verifying the entire life cycle of the data. Write the current log information to the log table as the latest log record of the current data.

[0035] According to one aspect of the present invention, the method for publishing the application to the cloud platform after the review is passed is:

[0036] Get application information, layout information and module information, generate json files, calculate md5 value for each json file, generate unique fingerprint identity, and verify the file information;

[0037] Merge product information, layout information, and module information with their corresponding md5 values, add the current date as the version tag and AppCode tag, encrypt them, generate a manifest.txt file, merge it into a zip file, upload the zip file to the cloud platform file server and return the zip file ID value, import the zip file to the cloud platform, decompress the zip file to import the application to the cloud platform, and privatize the scene configuration and module pool.

[0038] Based on this, the beneficial effects of the present invention are: by reusing shared components and architectures, the development process of new products can be significantly accelerated, duplication of work can be reduced, and it is possible to quickly derive multiple related but different products from a core foundation; and the manpower and time costs of software development can be significantly reduced;

[0039] Ability to quickly launch high-quality, customized software products, enhance product market competitiveness, meet diverse customer needs, and consolidate market share;

[0040] Based on modular and component-based development, the software production line ensures that software components follow consistent design specifications and standards, facilitating team collaboration and subsequent maintenance; making the software more adaptable to changes in demand while simplifying the maintenance and upgrade process. The standardized and component-based development model reduces the risk of project failure. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 is a flow chart of a method for automated software production in a cloud environment according to an exemplary embodiment;

[0042] Figure 2 It is a data interaction diagram of a software automation production method in a cloud environment according to an exemplary embodiment. DETAILED DESCRIPTION

[0043] The present invention will now be discussed with reference to exemplary embodiments. It should be understood that the embodiments discussed are only for enabling those skilled in the art to better understand and thereby implement the present invention, rather than implying any limitation on the scope of the present invention.

[0044] As used herein, the term “including” and variations thereof are to be interpreted as open-ended terms meaning “including but not limited to.” The term “based on” is to be interpreted as “based, at least in part, on,” and the terms “one embodiment” and “an embodiment” are to be interpreted as “at least one embodiment.”

[0045] According to one embodiment of the present invention, Figure 1 is a flow chart of a method for automated software production in a cloud environment according to an exemplary embodiment. Figure 1To achieve the above purpose, the present invention provides a method for automatic software production in a cloud environment, comprising:

[0046] Get user information, create a blank application based on the user information, determine whether there is a scene template that matches the target scene of the blank application, if not, initialize the blank scene, build relevant dependency information, and configure the scene layout for it. If there is, reuse the existing scene configuration based on the scene template import method and privatize the imported scene configuration;

[0047] Configure the layout of the scene based on the layout board, initialize the layout information, call the layout board to register the node type, drag and register the component to the layout board according to the component information, use the layout board to package the component, package the component into a layout node with relevant information, obtain the messages that each component supports sending and receiving, select the message sending and receiving ends, configure the trigger conditions by connecting, and realize component communication;

[0048] Translate the virtual coordinate information of the registered component into actual physical screen pixels, render the component, automatically calculate the display position and size on the screen, combine the hierarchical parameters, node configuration and build an independent environment, so as to initialize the blank area of ​​the component, build the context information of the component, build an independent scope based on the HTML and JavaScript information corresponding to the component type, and mount the upper and lower information;

[0049] Based on the encapsulation tool, the components are packaged and each component is packaged into independent component JavaScript information. The components are self-managed in terms of dependencies, and the components are regularly cleaned up. The components are forced to assemble and pass environment-level data, and different components are isolated.

[0050] Parse the structure from the layout, identify the nested modules, obtain the configuration and personalized configuration page information from the module pool based on the unique identifier of the module, initialize the configuration container in the sandbox environment, inject the key context parameters into the container as the basis for configuration level identification, so that the module can perceive the environment, embed the personalized configuration page into the above container, use the container framework to load and present the configuration, and complete the configuration interaction;

[0051] A standard data structure is formulated based on the data hub server for data interaction between modules and the data hub server. Based on data fields, the information representation structure is standardized and the field behavior is regulated, so as to initialize and assign values ​​to the modules. The data hub server uniformly manages the relationship between data. The source module and the target module are bridged through the data hub server, and the module data changes are realized based on the data triggers in the data hub server.

[0052] Based on user operation permissions, the third-party system is used to monitor, query and synchronize data on the data center server. When the data on the data center server changes, the data is pushed to the third-party system.

[0053] Review the configured applications, publish them to the cloud platform after they pass the review, monitor application information in real time, and privatize the applications.

[0054] According to one embodiment of the present invention, the scene configuration import and export are sliced, and the special processing handles for each type of configuration are refined. Each type of configuration is placed in a file independently to generate import resources. The scene configuration is analyzed and organized into a file stream to simulate the export file effect. The file stream includes the scene layout resource flow, module pool data flow, module specific configuration flow and other dependent resource flows. Based on the operation handle corresponding to the file stream, the import logic distribution execution is completed, the import status is updated and the operation reminder is sent.

[0055] According to an embodiment of the present invention, a layout board is virtually laid out, and the size and position of the components of the virtual layout board are virtualized. The number of components occupying the layout board is used to represent the actual size and position of the components. The width of the layout board is equally divided into 24 parts, and the height of each part is fixed at 30px. When dragging to adjust the position of the component, it is abstracted into the number of height and width. When rendering, the virtual size and coordinates are converted to actual values;

[0056] Get the position information of existing components on the layout board and generate a two-dimensional grid. The grid without layout components is represented by a blank space. According to the starting point of the dragged and dropped component and the default size of the component, collision detection is performed in the two-dimensional grid. If there is overlap with the position of the newly registered component, it is moved down and the position change information is saved.

[0057] According to one embodiment of the present invention, a hook method is used to distribute component node types, filter out components that can be added, analyze the selectable components based on hierarchical configuration parameters, assemble hierarchical parameters after selecting the components to generate new modules, mark the modules, and analyze whether the module pool exists. If so, reuse the ID value of the corresponding level. If not, reallocate the ID value and store the module in the business module pool. privatize the module configuration, add the module node and basic information to the layout table, notify other dependencies for asynchronous processing, attach module data to the layout node, and render the layout board.

[0058] According to one embodiment of the present invention, when the module data in the data center server changes, the data service is notified to receive the change, and based on the data service inbox message, it is determined whether the data trigger needs to be executed. If necessary, it is analyzed whether the module to which the current data belongs is configured with a data trigger, and the trigger and the corresponding number of modules need to be analyzed based on the change, and the data operations that meet the update field filtering conditions are filtered. Based on the source module data, the dynamic fields and source data field values ​​in the target module are sorted and analyzed, and the mapping is sorted into the fixed values ​​required by the target module. The data of the target module is configured accordingly, the standard API of the target module is called, and the association relationship with the source module is established, and the index value of the target module data in the source module is sorted.

[0059] According to one embodiment of the present invention, when the data of the data center server module changes, the data service is notified to receive the data, and a push task is constructed based on the message received by the data service inbox;

[0060] Obtain module information based on the data level, analyze whether the module enables data push and whether it meets the push conditions, and merge the push tasks for this data in the queue;

[0061] Based on the push configuration data results, map it into the structure required by the third-party system, assemble the push data, and determine whether the push data needs to be encrypted;

[0062] Analyze the push data results. If the data push fails, determine whether the data needs to be added to the push queue again.

[0063] According to one embodiment of the present invention, the data center server organizes the received module data and integrates the association information between different module data. The data center server needs to perform two operations. One is to organize the data into a data link, wherein the method is to analyze the module key information, data title and operation data primary key Id, and in response to the new data change operation, verify whether the data primary key Id is unique. If not, directly return an error message. If it is unique, assemble the data for insertion. In response to the update data change operation, verify whether the data primary key Id data exists. If not, directly return an error message. If it exists, update the data title. In response to the delete data change operation, verify whether the data primary key Id data exists. If not, directly return an error message. If it exists, perform a data deletion operation. Analyze whether the module data change needs to synchronize the associated data. If not, ignore it directly. If it exists, analyze the associated operation and write it synchronously into the association relationship table.

[0064] The other is to organize the data into the data link, respond to the new data change operation, build exclusive index information unique to this field, save it to the data center server index library, respond to the update data change operation, extract the old data row and the new data row data, analyze the specific changed field information based on the field column of the standard data, build exclusive index information of the changed field information, and update it incrementally to the data center server index library, respond to the update data change operation, delete this index analysis module relationship change operation from the data center server index library, respond to the new data change operation, build exclusive index data information unique to this field, and then save it to the data center server index library.

[0065] According to one embodiment of the present invention, when creating or deleting data, a field assertion method based on a standard data field is used to determine whether a trigger condition is met;

[0066] When updating data, the old and new data rows are extracted, and the specific changed field information is analyzed based on the standard data field to determine whether it meets the configured field value change conditions. If not, it is ignored; otherwise, the field assertion method of the standard data field is used to determine whether the trigger condition is met;

[0067] Sort out the data range and specific response operation information of the target module when responding to the operation. Based on the source data field + data row, construct the data field value configured in the response operation into a specific fixed value field, analyze the context information of the source data and construct mandatory context information.

[0068] Based on the target module tag, read the data integration API registered by the target module. If it does not exist, it will force an error. According to the response operation type, execute different data integration APIs, analyze the API execution results, and record the data trigger log.

[0069] If the target module responds to newly created data, it analyzes the newly created data ID and then builds an associated record with the current source data.

[0070] According to one embodiment of the present invention, exclusive log information is constructed based on data field configuration, old data rows and new data rows to analyze data changes, and in response to a new data change operation, exclusive log change information for each field is constructed based on the field column configuration;

[0071] In response to the update data change operation, based on the standard data fields, the specific change fields are analyzed and the log change information exclusive to these fields is constructed;

[0072] In response to the deletion data change operation, directly record the deletion log information;

[0073] Analyze and check whether there is a log for the current data. If so, add it to the data log record table and delete it from the log table as a basis for verifying the entire life cycle of the data. Write the current log information to the log table as the latest log record of the current data.

[0074] According to one embodiment of the present invention, application information, layout information and module information are obtained, a json file is generated, an md5 value is calculated for each json file, a unique fingerprint identity is generated, and information verification of the file is performed;

[0075] Merge product information, layout information, and module information with their corresponding md5 values, add the current date as the version tag and AppCode tag, encrypt them, generate a manifest.txt file, merge it into a zip file, upload the zip file to the cloud platform file server and return the zip file ID value, import the zip file to the cloud platform, decompress the zip file to import the application to the cloud platform, and privatize the scene configuration and module pool.

[0076] According to one embodiment of the present invention, in the architecture of the cloud platform, modules play a vital role and serve as the cornerstone for the realization of various business functions of software products. The cloud platform builds a centralized module pool for developers to register their own functional modules, so that they can easily select and combine these modules in the subsequent software product production process. The metadata information that needs to be provided when registering the module includes basic display information, including the module name, icon (including background color + picture), and accurate classification tags, so as to facilitate rapid identification and classification, run page information, and submit HTML and JS file paths of Web or H5 interfaces. Once the module is included in the software product, the cloud platform will automatically load these resources immediately, seamlessly integrate and present the module functions, personalize the setting information, and equip the module with independent setting page information—HTML and JS file paths. This design allows modules to be customized directly in the module pool or when the product is applied, which enhances the flexibility and adaptability of use, permission control information, clarifies operation codes and names, and connects with the integrated role permission management system built into the cloud platform. If the module design supports differentiated permission management, this step will ensure that it can be integrated into the platform's unified authorization framework, data integration configuration, module data structure, query and other APIs. The platform's built-in data hub server will complete data exchange and logical interaction between modules based on this, which paves the way for building a complex, interconnected software ecosystem and promotes seamless collaboration between modules.

[0077] According to one embodiment of the present invention, creating a blank application based on user information further includes obtaining user information, assigning a user identification code based on the user information, and determining in a distributed and concurrent manner whether the user identification code is a unique identification code, and if so, saving the user identification code in an App table;

[0078] Build a matching blank application based on the user identification code, assign a unique project identification code to the blank application, and save it in the Layout table;

[0079] Create a collaboration group for this application based on the blank application, mark the application creator as having the highest permissions, and save the collaboration group as a subgroup of the blank application in the collaboration table.

[0080] According to one embodiment of the present invention, configuring the scene layout further includes:

[0081] Initialize the scene layout information, write the blank layout information into the Layout data table, and create the scene information;

[0082] If it is a project scene, add a project template node, pass in parameters, write the scene data into the Project data table, generate privatization authorization information, and the default project manager role has all permissions;

[0083] If it is an application scene, the scene data is written into the Scene data table.

[0084] According to one embodiment of the present invention, if the scene template is imported online, the existing scene configuration is imported and reused from the semi-finished scene pool of the product production line; if the scene template is imported offline, the existing scene configuration is imported offline.

[0085] According to one embodiment of the present invention, new parameter data is generated for the scene layout resource flow and a new scene layout ID is generated based on the original scene layout ID; for the module specific configuration flow, it is analyzed whether the module exists in the current scene module pool. If so, the existing BusinessModuleId value is used to organize the module configuration, and the module is informed of the module-level configuration information that needs to be corrected. Based on EXTId, the specific module server is called to complete the specific module configuration import.

[0086] According to one embodiment of the present invention, a verification information method is executed to determine whether the module name, icon, and category label are filled in. If not, an error message is directly returned. If filled in, the module name is verified to be unique. If not, an error message is directly returned. It is determined whether the running page is filled in. If no error message is returned, if filled in, the filled HTML and JS files are verified to be normally accessible. If not accessible, an error message is returned. It is determined whether the permission operation code and name are filled in. If filled in, the code and name are verified to be unique. If not unique, an error message is returned. It is determined whether the data integration API is filled in. If filled in, it is verified whether it can be accessed normally. If not accessible, an error message is returned.

[0087] Execute the save module method to generate a unique module tag (TechModuleId) as the module's identity in the cloud platform product and save the module information to the database.

[0088] According to one embodiment of the present invention, the production of software products based on the cloud platform needs to go through the process of product creation, interface layout, module customization and product release. The whole process does not require additional programming tasks. The core lies in the interface layout construction stage. Users can directly select pre-registered modules from a rich module pool. These modules cover a wide range of functional units. With just a click of the mouse, they can be freely combined to build a unique business logic framework. The entire cloud platform system is divided into two core sections: product production end and application consumption end;

[0089] The product production end is responsible for product construction, assembly design and related configuration work, integrating the full-link functions of product design, covering from basic construction, configuration customization to advanced assembly design, and fully supporting the personalized and differentiated development of products;

[0090] The application consumption end is closely connected with the production end and is open to the end-user group, presenting the products carefully crafted by the production end to users in the most intuitive and easy-to-use form.

[0091] According to one embodiment of the present invention, a product is positioned as a business carrier, that is, a type of business module is assembled into a product, business data flows freely and interacts efficiently within the product, and data is isolated between different products. The metadata information that needs to be provided when creating a product includes: product name, which is used for query, display and use in the cloud platform prompt; product code, a unique code, which acts as a bridge for data interaction. Through the combination of this code + module unique mark, the accurate isolation and call of business data when the module is under different products is ensured, and efficient organization and safe isolation at the data level are achieved; product icon, background color + picture, which gives the product a unique visual image, enhances brand recognition and user's intuitive experience; product theme, selected from the interface style template provided by the cloud platform, unifies and beautifies the front-end display of the product, maintains consistency with the overall aesthetics of the platform, and enhances the user interface experience; product description, a text that explains the characteristics and uses of the product in detail, helps users and managers better understand the core value and application scenarios of the product. Although it is an optional option, it can effectively enhance internal and external communication and improve product awareness.

[0092] According to one embodiment of the present invention, when a product has been created, the execution logic of the cloud platform is to execute the verification information method to determine whether the product name, code and other information have been filled in. If not, an error message is directly returned. If filled in, the uniqueness of the product code is verified. If not, an error message is directly returned.

[0093] Execute the save product method to initialize the PC+H5 layout information of the product to ensure that the subsequent interface layout can work normally and save the product information into the database.

[0094] According to one embodiment of the present invention, in order to liberate module development from complex and highly customized application scenarios, the cloud platform has carefully designed a series of advanced components to seamlessly integrate business modules into the product matrix, and provides a series of standard specification constraints for module development, which enables developers to quickly embed their own modules into the cloud platform, and product builders only need to perform simple mouse operations to achieve zero-coding rapid assembly to meet diverse product needs. The interface is componentized and adopts a modular design concept to subdivide the user interface of cloud products into many independent and flexible components, creating unlimited possibilities like building blocks. The provided general component library includes menu components, which support flexible configuration of modules in a multi-level menu structure, especially in a Web environment, which can easily achieve multi-level navigation and optimize information classification display. The information display component integrates multiple elements such as text, pictures, and videos to add rich visual effects to the interface and enhance the user experience. The module component is responsible for loading and displaying the modules added by the cloud product. It not only displays the module content, but also bridges the interaction between different modules to ensure the smooth connection of information and enhance the synergy of the overall application. The virtual layout system ensures the high flexibility of the component layout by dividing the interface layout into a uniform 24-column horizontal grid and a 30-unit-high vertical grid. The system can intelligently adapt to different device screens and convert the design size into the optimal physical pixel display in real time to achieve perfect responsive design. The environmental isolation mechanism is To ensure high cohesion and low coupling of components, an environmental isolation strategy is implemented. Each component has an independent scope when loading, and context information is accurately transmitted to ensure that components do not interfere with each other, significantly improving their versatility and reuse rate. The efficient communication architecture promotes dynamic interaction and collaboration between components. The cloud platform has a built-in communication mechanism that allows components to send and respond to messages freely without in-depth understanding of the logic of other components. This mechanism effectively simplifies the message transmission process, ensuring that components only focus on their own interaction capabilities, while complex collaborative work is uniformly scheduled by the platform, thereby promoting a vivid presentation of the product interface and successfully building complex business scenarios.

[0095] According to one embodiment of the present invention, the entire interface layout process is as follows: initialize the layout panel, execute the component registration method, register the component information (HTML, JavaScript) supported by the cloud platform on the layout panel, so as to facilitate the subsequent display of the interface layout based on the component type. When registering, it is necessary to provide the default virtual layout size of the component, whether to allow resizing and other auxiliary configuration information, execute the component display method, traverse the existing layout components, display them to the correct position of the layout board, translate the virtual coordinate information of the component into actual physical screen pixels, thereby initializing the blank area of ​​the component, allowing the component to render its own content in this area, and constructing the context information of the component, such as the fixed text information of the text component, the icon link set displayed by the image component, and the specific module information of the module component. Based on the HTML and JavaScript information corresponding to the registered component type, an independent scope is constructed, and the context information is mounted to render the component.

[0096] According to one embodiment of the present invention, a layout component is added, a component selection method is executed, supported component types are listed for user selection, and after selection, it is determined whether it is a module component. If it is a module component, an interface pops up to allow the user to select available module data under the current product. After the selection is completed, a component rendering method is executed, the default size of the component registration is obtained, the appropriate position on the layout board is analyzed and calculated, the existing component position and size information on the layout board is obtained, and a two-dimensional grid is constructed. The grid without layout components is represented by a blank space. According to the starting point of the dragged and dropped position of the component and the default size of the component, a collision detection is performed in the existing grid. If there is an overlap with the position of the newly added component, it is automatically moved downward until all components have no overlap, and a layout saving method is executed to incrementally update the information related to the newly added component and the existing components whose positions have changed, and adjust the position and size of the component. The size of the component can be adjusted by dragging and dropping. The size and position of the component are processed in a similar logic to component rendering. When the size and position of the component are sensed to change, automatic layout calculations are performed to ensure collision and overlap between components. After the adjustment is completed, the position and size information is updated. Custom component configuration can be used to make some personalized configurations of the component under the current layout, such as the display method of the module (large icon, list, statistical icon). The component configuration method of component registration is executed, and it is handed over to the specific component to complete its own personalized configuration capabilities. After the component configuration is completed, the component configuration method is executed, and a refresh event is sent to notify the layout board to reload and render this component, and the component configuration is incrementally updated. Component linkage configuration obtains which messages each component supports sending and receiving, selects the message sending and receiving ends, and links them by dragging and dropping lines to achieve communication between the sending and receiving ends. The trigger conditions can be configured for the connection, so as to achieve more accurate linkage operations.

[0097] According to one embodiment of the present invention, the module component rendering process executes the module information acquisition method, queries the module page information registered in the module pool according to the TechModuleId, and if it does not exist, the interface directly prompts an error message, executes the module rendering method, constructs the module's own context information, module TechModuleId, product AppCode, layout display method (large icon, list, icon), loads HTML, JavaScript to do the actual rendering work; the actual rendering is completed by the module itself, executes the message monitoring method, monitors the messages sent by the business module, performs data processing, assembles them into the communication format between components, notifies the layout board to send messages, monitors the response messages sent by the layout board, parses the standardized data format, and notifies the module to respond.

[0098] According to one embodiment of the present invention, the cloud platform enables product development and supports product-level personalized configuration adjustment of the adopted modules. To achieve this function, the platform sets a standardized configuration hierarchical logic and integrates a unified access point, focusing on providing configuration access without intervening in the specific configuration details of the module. The execution logic of the entire process is as follows: execute the module information acquisition method, parse the product structure from the product layout, identify the nested modules, use the module's unique identifier TechModuleId to grab the configuration from the module pool, and integrate the module personalized configuration page information and return it together; execute the module list display method to display the basic properties of the module, such as name and label, and check whether the module is configured with personalized options. If so, the configuration module operation entrance is displayed to guide the user to enter the module personalized configuration process; execute the module personalized configuration method, initialize the configuration container (moduleSettingContainer), run as a sandbox environment, ensure that the module configuration operation does not affect the global Web context, assemble key context parameters (AppCode+TechModuleId), and inject them into the container, which is used as the basis for configuration level identification so that the module can perceive the current environment. This ensures accurate loading and seamless connection of module configuration, effectively drives a highly personalized configuration management mechanism, improves the accuracy and efficiency of system configuration, embeds the module's personalized configuration page into the above container, uses the container framework to load and present the configuration page, and completes the configuration interaction independently and securely.

[0099] According to one embodiment of the present invention, when a product is released, the built product will be released to the consumer end for user use. When released, the product-related configuration information will be packaged and compressed into a zip offline package. When released, the zip package will be uploaded to the application end. The application platform parses the zip package to restore the product production end configuration. The product production end generates a product offline zip package, executes the method of exporting application information, reads the basic information of the module from the database, generates the appinfo.json file, executes the method of exporting module information, traverses the added modules under the product, merges and generates the modules.json file, and queries the basic information of this module from the module pool based on the module TechModuleId to determine whether the module is configured with " Data Integration - Configuration Export" API, if it does not exist, it will be ignored. If it exists, the API will be called to complete the personalized configuration export of the module product level, execute the export layout information method, read the layout configuration of PC and H5, generate layouts.json file, execute the summary information method, calculate the md5 value for each json file, and generate a unique fingerprint identity; for subsequent information verification, merge the file information and the corresponding md5 value, add the current date as the version mark, add the AppCode mark, and encrypt it to generate the manifest.txt file, execute the generate zip method, merge the files into the zip, output them as a file stream to download the product consumer end, and decompress and restore the product configuration.

[0100] According to one embodiment of the present invention, a method for decompressing a zip package is executed to compress the zip package to obtain specific file information, a method for verifying information is executed to decrypt the manifest.txt file. If the decryption fails, it means that the zip package is invalid and an error message is directly returned. If the decryption is successful, the md5 file related to the product information can be obtained. Based on the AppCode, it is queried whether the product exists. If not, it is ignored. If it exists, the version mark of the product in the zip package and on the consumer side is compared. If it is greater than or equal to, it is ignored. Otherwise, it means that the zip is an old version and an error message is directly returned. Each json file is traversed to analyze the file md5 value. If it does not match the manifest.txt record value, it means that the product information has been tampered with and an error message is directly returned.

[0101] According to one embodiment of the present invention, Figure 2 is a data interaction diagram of a software automation production method in a cloud environment according to an exemplary embodiment. Figure 2As shown in the figure, in order to enhance the autonomy of modules and simplify development complexity, and ensure that each module focuses on its core business logic, the cloud platform provides data hub server services and provides a series of functional services and data interaction specifications, aiming to enhance the independence and development efficiency of modules, promote efficient collaboration and standardized operations of modules, and strengthen the consistency and security of data operations, providing a solid foundation for building complex business applications.

[0102] Data standards, through the implementation of a unified data information description framework, realize transparent processing of diverse data formats during the interaction between the data center server and the module. The overall structure is similar to that of a relational database (field + record). With the help of flexible field type support (such as JSON, array, XML), it can easily cope with the expansion needs of special business data, and provide external operation interfaces such as field condition judgment, initialization, and assignment based on data standards to enrich its application scenarios;

[0103] Data link management abstracts the data of each module into data nodes, records key data attributes (such as title, primary key, source TechModuleId, AppCode, etc.), and independently maintains the business associations between modules to generate a product-specific data relationship map, which greatly reduces the module's dependence on cross-module association management;

[0104] The data indexing service provides a one-stop index creation, query, and aggregation analysis tool based on data standards. It is equipped with preset list and chart Web components to accelerate the module's integrated standardized data query and analysis capabilities, helping developers focus on the innovation of core business logic.

[0105] Data change triggers, intelligently monitor any changes in module data (addition, modification, deletion), automatically process and call the target module API according to preset conditions. The module only needs to notify the data center server and the target module to provide a standardized interface when the data changes, so that complex business linkage can be seamlessly achieved, such as automatically adjusting contract terms according to changes in the collection module, without the need for additional coding;

[0106] Data log auditing, which comprehensively records detailed logs of module data changes in a unified format, provides product users with a transparent way to monitor the entire life cycle of data;

[0107] Open data interconnection, build standardized third-party system interaction logic, break down barriers between systems, and build in a sophisticated permission control system to promote cross-system data circulation;

[0108] Data push automatically identifies external systems to which data changes need to be pushed, and converts data into a format compatible with the corresponding system based on data standards to achieve seamless connection;

[0109] Data query: In response to data query requests from third-party systems, we parse query conditions based on data standards, efficiently coordinate data interaction between modules, and meet external retrieval needs.

[0110] Data reception supports the management and operation of cloud platform data by third-party systems, guides data mapping through data standards, and collaborates with data push mechanisms to achieve two-way data synchronization, making the process smooth and efficient.

[0111] According to one embodiment of the present invention, the source module: when the data changes (addition, deletion, modification), after processing its own business logic, assembles the required format data (data field + new and old data rows), and then calls the data center server interface to push the data and wait for the return result. The data center server: after receiving the data, synchronizes the data to the data link and data index, and then writes the data to the data inbox through the MQ message, executes the subsequent asynchronous processing logic, and the data inbox registers the data trigger, data opening, and data log specific data processor. After receiving the message, the inbox starts multi-threaded parallel calls to the specific data processor to complete the subsequent processing of specific business data. The target module: cooperates with the data trigger to complete the creation, modification, and deletion of its own qualified data, and then sorts out the changed data, becomes the source module itself, and delivers data change information to the data center server.

[0112] According to one embodiment of the present invention, the data interaction between the module and the data hub server is shown in the following process: the recommended execution logic when the module data changes, this logic is completed by the module itself, the preparation work, assembling the relevant configuration of the field column of the data standard, which is used to describe which fields the data consists of, the specific configuration of the field, whether it is updated or deleted, if so, query the old data field information, assemble it into the data standard data row, exist as the old data row, push the data to the data hub server, whether it is added / updated, if so, query the latest data information, assemble it into the data standard data row, exist as the new data row, merge the field column configuration and the old data row in the "preparation work", add the new data row, execute the SDK / api provided by the data hub server, and push the data to the data hub server.

[0113] According to an embodiment of the present invention, the data link is analyzed to determine which data the current data is associated with, and then compared with the old associations. If there is no change, it is ignored. If there is a change in the relationship, the associated data is made redundant.

[0114] Analyze the data link to determine which data the current data is associated with. If there is no association, ignore it. Otherwise, make the data redundant.

[0115] Execute the method of sorting related data, reverse-parse and sort out the related data information from the data index, and write it into the data row for subsequent conditional analysis. Execute the method of delivering data to the inbox, put the data into the inbox queue to facilitate subsequent asynchronous logic processing, generate a unique message primary key ID for the current data, and write the data into the inbox table. Use the message primary key ID as data, send an MQ message, and notify the recipient that there is new data to be processed, so as to realize asynchronous processing of subsequent logic.

[0116] According to one embodiment of the present invention, the data inbox receives the distribution execution process of the MQ message, obtains the message primary key Id, verifies whether the corresponding module data exists, if not, it means it has been processed and can be ignored, obtains which processors are in the inbox, if no processor exists, ignores this message, obtains the processing record of this message, traverses the message processors, determines which processors have not processed this message, if not, it means they have all been processed and can be ignored, if exists, concurrently executes the processor call, and receives the result returned by the processor; and analyzes whether the message is processed successfully, if not, records the error information, and determines the number of errors, if exceeds the number of retries, directly forces to ignore, if successful, introduces the message into the history table.

[0117] According to one embodiment of the present invention, a method for triggering a target module response is executed. Based on the target module tag, the data integration API registered by the target module is read. If it does not exist, an error is forced to be reported. According to the response operation type, different data integration APIs are executed, the API execution results are analyzed, and then subsequent processing is performed, and the data trigger log is recorded to determine whether it is successful. If not, the cause of the error is analyzed, the log is recorded, and then the result is returned to facilitate the next retry. If successful, a success log is recorded. If the target module is responding to new data, the new data Id is analyzed, and then an associated record is constructed with the current source data.

[0118] According to one embodiment of the present invention, the data open processor executes a process, executes a method for obtaining an open platform, analyzes and organizes the open configuration of the module configuration to which the data belongs, and if no configuration exists, ignores the return, executes a method for determining whether the data needs to be pushed, and determines whether the data meets the push conditions based on the field condition assertion method provided by the data standard; if not, ignores it, and analyzes whether there is an unfinished previous push for the data. If so, the data is forced to enter a waiting queue, and the push is automatically restarted after the previous push is completed. If it is an update data operation, if the new push has not been completed, enter the waiting queue. If it is a new data operation, there is no previous push, and the data is pushed directly. If it is a deletion operation, if the new creation and update push have not been completed, enter the waiting queue, analyze whether the data needs to be merged and pushed, and if it is an update operation, cancel the previous update push that has not been completed, and directly push the latest update operation.

[0119] According to one embodiment of the present invention, a method for constructing push data is executed to determine whether data field mapping configuration has been made. If not, the data format is maintained; otherwise, the standard data format is mapped into a configured data format that complies with the third-party system; it is determined whether data encryption operation is configured; if not, the data is maintained as it is; otherwise, the data is encrypted based on the configured encryption key; a method for sending push data is executed, an HttpClient object is constructed, a post request is executed to send push data, and based on the API result, whether the push is successful is analyzed; if successful, the push log is directly written; if failed, the reason for the failure is recorded in the log; the number of failures is calculated and compared with the configured number of failures to determine whether the push needs to be retried; if necessary, the push is put into the push queue and waits for the next polling.

[0120] According to one embodiment of the present invention, the module, as the carrier of the actual business function, is added to the application through the module component of the scenario layout; the production line provides a large number of service mechanisms for decoupling the module from the external business association, so that the module only needs to focus on the implementation of its own core business logic functions without paying attention to the external environment; in this way, the module itself has high cohesion and low coupling, is naturally highly adaptable, and can be reused under different scenario requirements.

[0121] According to one embodiment of the present invention, the data synchronization demand between applications and third-party systems is solved. Based on data services, data push, query, and receiving configuration are provided, and account authorization can be performed based on accounts to achieve fine-grained control of data flow. Through the unified mechanism of the production line, the decoupling of the production line module and the third-party system is achieved.

[0122] Based on this, the beneficial effect of the present invention is that by reusing shared components and architectures, the development process of new products can be significantly accelerated, duplication of work can be reduced, and it is possible to quickly derive multiple related but different products from a core foundation; and the manpower and time costs of software development can be significantly reduced, and high-quality, customized software products can be quickly launched, thereby enhancing the market competitiveness of products, meeting diverse customer needs, and consolidating market share. Based on modular and componentized development, the software production line ensures that software components follow consistent design specifications and standards, facilitates team collaboration and subsequent maintenance, and makes the software easier to adapt to changes in demand. At the same time, it simplifies the maintenance and upgrade process. The standardized and componentized development model reduces the risk of project failure.

[0123] Those of ordinary skill in the art will appreciate that the modules and algorithm steps described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0124] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and equipment can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0125] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0126] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present invention.

[0127] In addition, each functional module in the embodiment of the present invention may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0128] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the energy-saving signal sending / receiving method of each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.

[0129] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the present application.

[0130] It should be understood that the size of the serial numbers of each step in the content of the invention and the embodiments of the present invention does not absolutely mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

Claims

1. A software automation production method in a cloud environment, characterized in that: include: Get user information, create a blank application based on the user information, determine whether there is a scene template that matches the target scene of the blank application, if not, initialize the blank scene, build relevant dependency information, and configure the scene layout for it. If there is, reuse the existing scene configuration based on the scene template import method and privatize the imported scene configuration; Configure the layout of the scene based on the layout board, initialize the layout information, call the layout board to register the node type, drag and register the component to the layout board according to the component information, use the layout board to package the component, package the component into a layout node with relevant information, obtain the messages that each component supports sending and receiving, select the message sending and receiving ends, configure the trigger conditions by connecting, and realize component communication; Translate the virtual coordinate information of the registered component into actual physical screen pixels, render the component, automatically calculate the display position and size on the screen, combine the hierarchical parameters, node configuration and build an independent environment, so as to initialize the blank area of ​​the component, build the context information of the component, build an independent scope based on the HTML and JavaScript information corresponding to the component type, and mount the upper and lower information; Based on the encapsulation tool, the components are packaged and each component is packaged into independent component JavaScript information. The components are self-managed in terms of dependencies, and the components are regularly cleaned up. The components are forced to assemble and pass environment-level data, and different components are isolated. Parse the structure from the layout, identify the nested modules, obtain the configuration and personalized configuration page information from the module pool based on the unique identifier of the module, initialize the configuration container in the sandbox environment, inject the key context parameters into the container as the basis for configuration level identification, so that the module can perceive the environment, embed the personalized configuration page into the above container, use the container framework to load and present the configuration, and complete the configuration interaction; A standard data structure is formulated based on the data hub server for data interaction between modules and the data hub server. Based on data fields, the information representation structure is standardized and the field behavior is regulated, so as to initialize and assign values ​​to the modules. The data hub server uniformly manages the relationship between data. The source module and the target module are bridged through the data hub server, and the module data changes are realized based on the data triggers in the data hub server. Based on user operation permissions, the third-party system is used to monitor, query and synchronize data on the data center server. When the data on the data center server changes, the data is pushed to the third-party system. Review the configured applications, publish them to the cloud platform after they pass the review, monitor application information in real time, and privatize the applications.

2. The method for automated software production in a cloud environment according to claim 1, characterized in that: Slice the scene configuration import and export, refine the special processing handles for each type of configuration, place each type of configuration independently in a file, generate import resources, analyze and organize the scene configuration into file streams, and simulate the export file effect. The file stream includes the scene layout resource flow, module pool data flow, module specific configuration flow and other dependent resource flows. Based on the corresponding operation handle of the file stream, complete the import logic distribution execution, update the import status and send operation reminders.

3. The method for automated software production in a cloud environment as claimed in claim 2, characterized in that: Perform virtual layout on the layout board, virtual layout board component size and position, use the number of components occupying the layout board to represent the actual size and position of the component, divide the layout board width into 24 equal parts, and fix the height of each part at 30px. When dragging and adjusting the position of the component, it is abstracted into the height and width. When rendering, convert the virtual size and coordinates to actual values; Get the position information of existing components on the layout board and generate a two-dimensional grid. The grid without layout components is represented by a blank space. According to the starting point of the dragged and dropped component and the default size of the component, collision detection is performed in the two-dimensional grid. If there is overlap with the position of the newly registered component, it is moved down and the position change information is saved.

4. The method for automated software production in a cloud environment according to claim 3, characterized in that: Use the hook method to distribute the component node type, filter out the components that can be added, analyze the selectable components based on the hierarchical configuration parameters, assemble the hierarchical parameters after selecting the components to generate new modules, mark the modules, and analyze whether the module pool exists. If so, reuse the ID value of the corresponding level. If not, reallocate the ID value to store the module in the business module pool, perform module configuration privatization, add the module node and basic information to the layout table, notify other dependencies for asynchronous processing, attach module data to the layout node, and render the layout board.

5. The method for automated software production in a cloud environment according to claim 4, characterized in that: When the module data in the data center server changes, the data service is notified to receive it. Based on the data service inbox message, it is determined whether data triggering needs to be executed. If necessary, it analyzes whether the module to which the current data belongs is configured with a data trigger. The corresponding number of triggers and modules needs to be analyzed based on the change, and the data operations that meet the update field filtering conditions are filtered. Based on the source module data, the dynamic fields and source data field values ​​in the target module are sorted and analyzed, and mapped into fixed values ​​required by the target module. The data of the target module is configured accordingly, the standard API of the target module is called, and the association relationship with the source module is established. The index value of the target module data in the source module is sorted.

6. The method for automated software production in a cloud environment according to claim 5, characterized in that: When the data in the data center server module changes, the data service is notified to receive the data, and a push task is constructed based on the message received in the data service inbox; Obtain module information based on the data level, analyze whether the module enables data push and whether it meets the push conditions, and merge the push tasks for this data in the queue; Based on the push configuration data results, map it into the structure required by the third-party system, assemble the push data, and determine whether the push data needs to be encrypted; Analyze the push data results. If the data push fails, determine whether the data needs to be added to the push queue again.

7. The method for automated software production in a cloud environment according to claim 6, characterized in that: The data center server organizes the received module data and integrates the related information between different module data, wherein the method is to analyze the module key information, data title and operation data primary key Id, and in response to the new data change operation, verify whether the data primary key Id is unique. If not, directly return an error message. If it is unique, assemble the data for insertion. In response to the update data change operation, verify whether the data primary key Id data exists. If not, directly return an error message. If it exists, update the data title. In response to the delete data change operation, verify whether the data primary key Id data exists. If not, directly return an error message. If it exists, perform a data deletion operation. Analyze whether the related data that needs to be synchronized for the module data change exists. If not, ignore it directly. If it exists, analyze the related operation and write it synchronously into the association relationship table. In response to the new data change operation, exclusive index information unique to this field is constructed and saved in the data center server index library. In response to the update data change operation, the old data row and the new data row data are extracted, and the specific changed field information is analyzed based on the field column of the standard data, and exclusive index information of the changed field information is constructed, and incrementally updated to the data center server index library. In response to the update data change operation, this index analysis module relationship change operation is deleted from the data center server index library. In response to the new data change operation, exclusive index data information unique to this field is constructed and then saved to the data center server index library.

8. The method for automated software production in a cloud environment according to claim 7, characterized in that: When creating or deleting data, the field assertion method based on the standard data field is used to determine whether the trigger condition is met; When updating data, the old and new data rows are extracted, and the specific changed field information is analyzed based on the standard data field to determine whether it meets the configured field value change conditions. If not, it is ignored; otherwise, the field assertion method of the standard data field is used to determine whether the trigger condition is met; Sort out the data range and specific response operation information of the target module when responding to the operation. Based on the source data field + data row, construct the data field value configured in the response operation into a specific fixed value field, analyze the context information of the source data and construct mandatory context information. Based on the target module tag, read the data integration API registered by the target module. If it does not exist, it will force an error. According to the response operation type, execute different data integration APIs, analyze the API execution results, and record the data trigger log. If the target module responds to newly created data, it analyzes the newly created data ID and then builds an associated record with the current source data.

9. The method for automated software production in a cloud environment according to claim 8, characterized in that: Analyze data changes based on data field configuration, old data rows, and new data rows to build exclusive log information. In response to new data change operations, build exclusive log change information for each field based on field column configuration. In response to the update data change operation, based on the standard data fields, the specific change fields are analyzed and the log change information exclusive to these fields is constructed; In response to the deletion data change operation, directly record the deletion log information; Analyze and check whether there is a log for the current data. If so, add it to the data log record table and delete it from the log table as a basis for verifying the entire life cycle of the data. Write the current log information to the log table as the latest log record of the current data.

10. The method for automated software production in a cloud environment according to claim 9, characterized in that: The method for publishing the application to the cloud platform after the review is passed is: Get application information, layout information and module information, generate json files, calculate md5 value for each json file, generate unique fingerprint identity, and verify the file information; Merge product information, layout information, and module information with their corresponding md5 values, add the current date as the version tag and AppCode tag, encrypt them, generate a manifest.txt file, merge it into a zip file, upload the zip file to the cloud platform file server and return the zip file ID value, import the zip file to the cloud platform, decompress the zip file to import the application to the cloud platform, and privatize the scene configuration and module pool.

Images