CN103744647B - A kind of Java workflow development system and method based on workflow visualization toolkit - Google Patents

Abstract

The invention discloses a Java workflow development system and method based on a workflow visualization development tool (GPD), including: an operation visualization graphic navigation tool module, which is used to provide developers with visualized and convenient engineering navigation, and guide development in the navigation Personnel configuration system database and business database information; enterprise user organization model visualization view module, used to model the enterprise organization model that needs to be used in workflow engineering; reusable component library view module, used to manage reusable components Classification, increase system modularity, reduce coupling; form visualization and binding module, used in the realization of this system, integrated form visualization developer, integrates the development of forms into the entire system; engineering one-key deployment module, used for Compress and package the entire project for release. By adopting the invention, the focus of workflow process developers can be placed on the realization of business logic, greatly reducing the workload of developers.

Description

A Java workflow development system based on a workflow visualization development tool and its method

technical field

The present invention relates to the development technology of workflow visualization development tools, in particular to a Java workflow development system and method based on workflow visualization development tools, which belongs to the expansion of the development environment of workflow visualization development tools and is an enterprise-level A technology that provides an efficient and convenient development environment for workflow developers.

Background technique

With the deepening of enterprise informatization, more and more enterprise process requirements cannot be met by ordinary office automation systems, and workflow systems have gradually become popular. In enterprise resource planning (ERP), customer relationship management (CRM), enterprise In classic enterprise application fields such as application integration (EAI), the application of workflow technology has been deeply rooted and indispensable. The definition of a workflow management system is that the system supports a set of specially set business processes by executing calculated process definitions. It is used to support defining, managing and executing workflows. The goal of universal enterprise-level workflow design is to manage the flow of work to ensure that the work is performed by the expected personnel at the correct time, and to insert manual execution and intervention in the automated business process, which is precisely workflow management. The value of the system is also the main task of the workflow system developers. Workflow technology is a rapidly developing information technology, and enterprises in various industries are gradually adopting workflow management systems.

Domestic workflow development has the characteristics of intensive manual tasks. During the workflow development process, it is necessary to provide a good user-interactive process design interface, which is different from the general process development that only needs to automatically execute nodes. The existing workflow The system cannot fully meet these needs.

JBPM (JAVA Business Process Management) is a lightweight workflow management software package based on JAVAEE. It is an extensible and flexible enterprise-level development framework capable of implementing workflow/business process management. It provides process definition and process deployment. , process execution, process management and other functions. JBPM is an open source code project, which has been supported and concerned by the majority of developers. JBPM has become a first-class open source workflow product.

Through the analysis of workflow visualization development tools, its shortcomings mainly include the following points:

a) For project configuration, it is necessary to manually open the source file for configuration.

b) For the configuration of component parameters, it is necessary to manually open the source file for configuration.

c) The execution of the process engine needs to manually copy the package.

d) The establishment of the enterprise organization model needs to be created using codes, without visibility.

e) Insufficient support for component granularity, and a lot of repetitive work.

The traditional workflow development environment only provides a simple process graphical editor. In the development of workflow engineering, developers need to perform tedious configuration work, unfriendly code forms to implement enterprise organization models, and manual copying and use of existing components. It prevents developers from focusing on the development of business logic and requires a series of development and configuration work. Therefore, it is of great significance to optimize the existing workflow visualization development tools to provide an efficient and convenient development environment for enterprise-level workflow developers.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a Java workflow development system and method based on a workflow visualization development tool. Navigation, increase organizational model modeling and realize component granulation and reusability, increase form design integration function and engineering deployment function, provide a good development environment for process developers, and enable developers to focus on the development of business logic, so that they do not need to Carry out a series of development and configuration work to reduce the cost of engineering development and maintenance.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A Java workflow development system based on workflow visualization development tools, including: operation visualization graphic navigation tool module, enterprise user organization model visualization view module, reusable component library view module, form visualization and binding module, and project one-click deployment module; among them,

Operation visualization graphic navigation tool module, which is used to provide developers with visualized and convenient project navigation, guide developers to configure system database and business database information in the navigation, and add system database and business database windows for development on the basis of new dynamic web projects personnel to enter;

The enterprise user organization model visualization view module is used to model the enterprise organization model that needs to be used in workflow engineering; it is used to establish the corresponding user organization model in the workflow engineering development process, and to save and import the model;

The reusable component library view module is used for developers to manage and classify reusable components during the development process, increase system modularity, reduce coupling, and reduce development overhead; it is also used to provide visual management functions and provide EJB components. Support, and be able to load components into the view of the process editor for direct use of components, and provide a visual setting function for component parameters;

The form visualization and binding module is used in the implementation of this system, integrating the form visualization developer, and integrating the development of the form into the entire system, so that developers do not need to change the development environment, which provides convenience for developers;

The project one-click deployment module, when the entire project is developed, select the network address of the server to be deployed, package it and upload it to the server for release.

Wherein, the operation visualization graphic navigation tool module is also used to encapsulate the new process of the background project, automatically run the package copy in the background, configure the work of the file, and simplify the development process; it is also used to summarize a series of simplified projects in the process development process Create a method and implement it.

The enterprise user organization model visualization view module, as a visual enterprise organization model modeling view tool for developers, usually expresses in the form of a tree structure in the enterprise organization model, and provides a tree-like visualization structure in the organization model view for The developer edits, the import of the model provides two formats of XML and database; the view provides the function of adding, deleting and modifying the enterprise organization model, and after the modification is completed, it can be imported from the view into the system database for the process engine to execute the workflow used when.

The reusable component library view module provides the organization of reusable components, so that developers can reuse existing components in different projects, reducing research and development costs; it also provides the functions of adding and loading components, mainly for components in the available state , to add the component to the user component library view, so as to manage the component, which can be added, deleted and modified.

The reusable component library view module is loaded from the user component library view to the workflow file editor when the project needs to use the component, and the component can be directly used as a component by using the drag and drop function of the editor. After completion , which can provide basic parameter configuration functions for component calls.

The reusable component library view module uses the existing EJB components in the component library view in different projects. Since the EJB components are published in the jboss server, as long as the EJB components are available, they can be used in different projects. Binding usage reduces the cost of development and makes full use of reusable components.

The form visualization and binding module provides an integration function for the form designer, integrates the form designer into the workflow development system, and facilitates the development and design work of developers; provides a visual binding function for artificial nodes and forms .

The project one-click deployment module is used for the developer to finally deploy the project, simplifies the deployment steps, and provides a visualized interface navigation for deployment.

A Java workflow development method based on a workflow visualization development tool, comprising the steps of:

A. Use the operation visualization graphic navigation tool module to guide developers to configure system database and business database information during navigation, and add a system database business database window for developers to input on the basis of new dynamic web projects;

B. Through the enterprise user organization model visualization view module, model the enterprise organization model that needs to be used in the workflow engineering; then establish the corresponding user organization model in the workflow engineering development process, and save and import the model;

C. Use the reusable component library view module to manage and classify reusable components during the development process; provide visual management functions, support for EJB components, and load components into the view of the process editor for direct use of components, providing The function of visually setting the parameters of components;

D. In the system implementation, through the form visualization and binding module, integrate the form visualization developer, and integrate the development of the form into the entire system;

E. When the entire project is developed, use the project one-click deployment module, select the network address of the server to be deployed, package it and upload it to the server for release.

Wherein, step B further includes:

B1. Steps for importing and exporting organization models:

B2. Steps of editing the organization model;

B3. Steps of visualization of manual node assignment.

The Java workflow development system and method thereof based on the workflow visualization development tool provided by the present invention have the following advantages:

The Java workflow development system of the present invention integrates the development platform and deployment platform of the process to realize the visual design of the process, the visual design of the personnel organization, the visual design of the form, the one-click release of the process, and the management staff. Humanized management setting function of process definition, process instance and role. It mainly includes five modules, among which, the operation visual graphic navigation provides developers with visual engineering navigation, visual configuration database parameters and visual configuration component parameters and other functions. The enterprise personnel organization model view provides a visual view of the tree organization model, and interacts with the background database to update data. The reusable component library view provides functions such as management and classification of available components, matches the server that publishes components, and allows developers to call components, which can improve the decoupling and reusability of the system, and significantly reduce the development and maintenance costs of components , and also provides support for developers to develop workflow projects efficiently. With the form visualization and binding module, the form editing function can be integrated into the entire development system, and one-click deployment of human task nodes and forms can be provided. The one-click deployment function module of the project provides visual assistance for the one-click deployment of the project. After the developer provides the required server address, the entire project can be compressed and packaged for release. By adopting the development system and method of the present invention, the Java workflow development system can be optimized and expanded on the basis of the visual process development tool, so that the focus of the workflow process developers can be placed on the business logic implementation, greatly reducing the Developer workload.

Description of drawings

Fig. 1 is the scene diagram of Java workflow development system of the present invention;

Fig. 2 is a system architecture diagram of the Java workflow development system of the present invention;

Fig. 3 is the flow chart of operating visualization graphic navigation tool module;

FIG. 4 is a schematic diagram of a scene of a visual view module of an enterprise user organization model;

Fig. 5 is a user development example process diagram of the enterprise user organization model visualization view module;

Fig. 6 is a process diagram of an example user development of the view module of the reusable component library.

detailed description

The Java workflow development system and method based on the workflow visualization development tool of the present invention will be further described in detail below in conjunction with the accompanying drawings and the embodiments of the present invention.

The basic idea of the present invention is: the present invention focuses on the characteristics of dense artificial nodes in the domestic workflow system, optimizes and realizes it on the basis of the plug-in of the workflow visualization development tool of the original development process file, and reduces the cost of workflow development. Improve system granularity and provide support for developers to develop workflow systems efficiently.

Aiming at the demand characteristics of domestic workflow systems, this invention proposes a workflow development system based on workflow visualization development tools, from manual task nodes, graphical navigation requirements, component library resources, form visualization and binding, and one-key deployment of projects Five aspects optimize and realize the workflow development system. The user object of this system is the developer of enterprise-level workflow system. The purpose of this system is to realize the visual customization and design of enterprise-level workflow, publish workflow, manage workflow users, administrators, and bind and manage corresponding component libraries. Greatly shorten the development cycle and facilitate management, and realize random deployment.

FIG. 1 is a schematic diagram of a scene of the Java workflow development system of the present invention, and FIG. 2 is a system architecture diagram of the Java workflow development system of the present invention. As shown in Figure 1 and Figure 2, the Java workflow development system is divided into five basic parts, namely the operation visualization graphic navigation tool module, the enterprise user organization model visualization view module, the reusable component library view module, the form visualization and Binding modules, project one-click deployment function modules. in,

First, the operation visualization graphical navigation tool module. In the process of developing process engineering in the research stage, many characteristics and defects of using workflow visualization development tools have been accumulated. For example, after creating a dynamic web project, a lot of jar package copies and configuration file modifications are required, and the source code needs to be modified for binding Java nodes. For these aspects, the system corresponds to the development, deployment, and test development of dynamic web projects. corresponding navigation functions. The system navigates the parameters of Java nodes visually. All of these have realized the developer's visual graphic navigation, which greatly facilitates the developer's deployment test. The key technologies in this part include: Eclipse plug-in development technology, realizing navigation needs to inherit and cover the navigation of dynamic web projects and add new functions. The parameter setting of the Java node needs to be implemented using SWT graphic technology.

Second, the visual view module of the enterprise user organization model. The original system uses code implementation when processing the organization model, that is, developers need to call the relevant interface in the background code to carry out the modeling work of the organization model, and the effect is that the organization model information is inserted into the system database . The goal of this system is an enterprise-level workflow process design tool. In an enterprise, the modeling of the organizational model is essential, and the roles and positions of personnel need a unified development environment to deploy. In view of this, research on organizational model modeling tools is quite necessary. The organization model modeling view is added in this system, the purpose is to make the developer conveniently and visually carry out the modeling work of the organization model, and at the same time, it can visually assign manual tasks to the corresponding personnel. Corresponding to the workflow visualization development tool, the implementation of the organizational model modeling tool is a view added to the original Eclipse plug-in tool. The view needs to ensure that the model still exists when the development environment is opened for the second time, but the plug-in mode of Eclipse does not support this situation. Secondly, the organizational model needs to be written into the database in order to be used by the process engine, that is, the organizational model needs It can directly transfer information with the database. Moreover, in order to facilitate the portability of the model developed by the developer, the organization model is stored, and the previously edited organization model can be used in another development environment. The XML file is adopted. storage method. To realize the organizational model modeling view mainly needs to add the organizational model view in the Eclipse environment, and then design and implement the organizational model on the basis of this view.

Third, the reusable component library view module. The workflow visual development tool itself does not implement the part of the component library, but JBPM supports the direct call of EJB components in the process definition file, and the structure of the component library can be expanded on this basis. In some mature workflow design tools, the component library is an essential part. A component is a replaceable part that actually exists in the system. It implements a specific function, conforms to a set of interface standards, and implements a set of interfaces. A component can be understood as an independent part that executes specific business logic without external interference. It only needs to call the interface to return the corresponding result, which greatly reduces the coupling degree for process design. Based on the above research, the component library has become an indispensable part in the optimization of workflow visualization development tools. The system designs commonly used components for use by process developers, which enables developers to reuse existing components and reduces the workload. Just load the required components, drag and drop, and fill in the parameters before you can use it. In addition, considering that the provided component library cannot meet the actual application, developers can also develop their own components and add them to the user-defined component library for use. The low coupling and high reusability of the system are fully considered.

Fourth, form visualization and binding function modules. In the workflow visualization development tool development environment, manual modification of the source code is required when the manual node is bound to the form. In this system, this function is packaged in a visual interface. The original environment of the form designer is in the form of a browser. It is integrated into the Eclipse development environment in this system. When a manual node is bound to a form, double-click it, and the system provides a visual form list, which is selected by the developer, and the source code is modified in the background. It is convenient for developers to design the form.

Fifth, the project can deploy functional modules with one click. This functional module is relatively inconvenient during the development process. After the project development is completed, you only need to right-click on the project and select Deploy. After that, the developer provides the network address of the server, and then packages and deploys the project.

As shown in the system architecture diagram shown in Figure 2, it can be clearly seen that the system includes five main parts and the original process editor part. Since the five main parts of the system are relatively independent, they will be described separately to further describe the present invention in detail.

1) Operate the visual graphic navigation tool module.

Fig. 3 is a flow chart of operating the visual graphic navigation tool module. Describes the steps that need to be performed in the process of creating a new project. In the original workflow visualization development tool environment, the new project needs to copy the configuration file, open it for manual configuration writing, and copy the corresponding package to the project directory. for use when the process is published. Operation visualization graphic navigation provides convenient new project navigation, fills in the system database and business database information during the navigation process, and provides a simple connection test to ensure the correctness of the entered database information. When the project is newly created, the database information will be written into the configuration file without manual filling. In addition, for the automatic running nodes in the workflow, that is, the Java nodes provide a visual navigation tool, provide parameters to fill in, and configure the visual services of the Java nodes. In the original workflow visualization development tool environment, these tasks require developers to learn Java node-related properties, and modify the source file to support. In the editor, for a Java node, just double-click to pop up the corresponding dialog box for configuring the Java node file and parameters. Developers only need to configure the parameters in the dialog box to automatically write the information to the In the workflow definition file, there is no need to manually modify the workflow definition file.

2) Visual view module of enterprise user organization model.

(1) The first is the import and export of organizational models. The view needs to ensure that the model still exists when the development environment (that is, Eclipse) is opened for the second time, but the plug-in mode of Eclipse does not support this situation. Secondly, the organization model needs to be written into the database in the end before it can be used by the process engine. That is, the organization model needs to be able to directly transmit information with the database. Furthermore, in order to facilitate the portability of the model developed by developers, the organization model is stored so that it can be used in another development environment. The previously edited organization model is adopted. How XML files are stored. To sum up, the import of the organization model is divided into two parts, one is the edited XML file, and the format needs to conform to the defined format; the other is from the engine database, both of which should be recognized by the organization model view support. Corresponding to the import of the organization model, the export of the organization model also requires two methods, that is, the XML file and the engine database. The XML file is convenient for information to be stored in the form of a file to increase portability; the engine database is to enable the edited organization model to be recognized by the engine, so as to perform correct manual task assignment and make the workflow process run correctly.

(2) Second is the editing problem of the organizational model. In the organizational model modeling view, if you simply import the information model from an XML file or database, and then assign the corresponding manual tasks, this lacks a lot of flexibility. If you need to modify the organizational model, you can only Modifications are made in two data sources, files or databases. This situation will greatly increase the workload of developers, and the XML file form and the list form of database tables determine the complexity of this work. The user organization model is usually a tree model. There are several sub-organizations under an organization. There are situations such as a certain user under the organization. Based on the above reasons, the organization model editing function is added to the organization model view. Some basic copy, paste, new, edit, etc. functions are required.

(3) Again, it is the visualization problem of manual node assignment. In the process designer, the allocation of human task nodes is just a simple text box, and developers need to manually enter the user or group id, and there is no visual graph to help developers choose. The significance of establishing an organization model is to display the organization model graphically, so that developers can easily allocate manual tasks. This allocation can assign specific tasks to groups or individuals. Therefore, it is necessary to add corresponding information in the attribute view of the human task node. In order to improve the inconvenience of manual input, a button is added to the position of the corresponding text box in the attribute view of the human task node. The function of clicking this button is to display the entire organization model. Perform single or multiple selections to assign tasks. This implementation frees users from the cumbersome search and identification of organizational models, and the graphical interface is more conducive for users to find out the inclusion relationship between organizational models.

FIG. 4 is a schematic diagram of a scenario of a visual view module of an enterprise user organization model. As shown in Figure 4, the scene schematic diagram of the modeling module of the organizational model. In the organization model, developers can display the tree structure of the organization model in the organization model view in the form of XML files or databases, providing developers with a visual reference. Developers can make corresponding adjustments to the organization model in the view. After modification and editing, the latest organizational model in the view can be saved in the form of XML file or in the form of database. Saving to the system database is for the use of the organizational model by the process engine.

Figure 5 provides a specific example process of user development of the organization model modeling module. In this process, there are corresponding functional support services for each operation of the user.

3) Reusable component library view module.

The first is the research and requirements of the system component library. The system component library is a list of components contained in the workflow tool itself, and process developers can select existing components in the system to load according to specific needs. After loading, it can be regarded as an ordinary JAVA node and dragged into the editor to select a method and add corresponding parameters to call it in the workflow.

The second is the research and demand of user-defined component library. Process developers will continuously accumulate required components during the actual development process. In order to save developers from doing some repetitive work, this workflow tool provides a user-defined component library for these components. Components developed by developers can be added to the development environment through added functions, and can be loaded, dragged, and filled in parameters in the same way as the system component library. It should be noted that the developer must provide a valid interface of the EJB component, such as the JNDI name of the EJB component and the list of methods. If there is an error here, the development tool cannot detect the error here, which will cause the process to call this EJB component. mistake.

The third is the study of the search function. The component library will increase with the development time of developers, and a search function is required to quickly locate a certain component. This function is implemented on the component library view. Developers input keywords, and the system component library and user-defined component library will filter out the corresponding content in real time according to the change of keyword content, so as to facilitate developers to search and use.

Figure 6 provides an example process of user development of the view module of the reusable component library. Developers can use components in the existing system component library, or add components created by themselves in the development process to the component library for reuse. Thereby reducing development costs. The component library view also provides a simple keyword search function for developers to quickly find the required components for loading and binding.

The loading and binding of components is similar to that of ordinary automatic execution nodes (Java nodes). After loading them into the editor, dragging them to the process definition file, and double-clicking, a dialog box for configuring parameters will pop up. Developers only need to click on the By configuring the corresponding parameters, the parameter information can be written into the source file of the process definition file without manually opening the source file for writing configuration.

4) Form visualization and binding function modules.

In the workflow visualization development tool development environment, manual modification of the source code is required when the manual node is bound to the form. In this system, this function is packaged in a visual interface. The original environment of the form designer is in the form of a browser. It is integrated into the Eclipse development environment in this system. When a manual node is bound to a form, double-click it, and the system provides a visual form list, which is selected by the developer, and the source code is modified in the background. It is convenient for developers to design the form.

5) Project one-click deployment of functional modules.

This functional module is relatively inconvenient during the development process. After the project development is completed, you only need to right-click on the project and select Deploy. After that, the developer provides the network address of the server, and then packages and deploys the project.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (9)

1. A Java workflow development system based on a workflow visualization development tool, comprising: the system comprises an operation visual graphic navigation tool module, an enterprise user organization model visual view module, a reusable component library view module, a form visual and binding module and an engineering one-key deployment module; wherein,

the visual graphical navigation tool module is operated and used for providing visual and convenient engineering navigation for developers, guiding the developers to configure the system database and the business database information in the navigation, and increasing windows of the system database business database for the developers to input on the basis of newly building a dynamic web project; the operation visual graphic navigation tool module is also used for encapsulating a background engineering new building process, automatically copying a background operation package and configuring the work of files, and simplifying a development process; the method is also used for summarizing a series of methods capable of simplifying engineering establishment in the process development process and realizing the methods;

the visual view module of the enterprise user organization model is used for modeling the enterprise organization model required to be used in the workflow engineering; the system is used for establishing a corresponding user organization model in the workflow engineering development process, and storing and importing the model;

the reusable component library view module is used for managing and classifying the reusable components by developers in the development process, so that the modularity of the system is increased, the coupling degree is reduced, and the development expense is reduced; the system is also used for providing a visual management function, providing support for EJB components, loading the components into a view of a flow editor for directly using the components and providing a parameter visual setting function for the components;

the form visualization and binding module is used for realizing the system, integrating a form visualization developer and integrating the form development into the whole system, so that developers do not need to change the development environment, and convenience is provided for the developers;

and the project one-key deployment module selects the network address of the server to be deployed after the whole project is developed, packages the network address and uploads the packaged network address to the server for publication.

2. The Java workflow development system based on workflow visualization development tool according to claim 1, wherein the enterprise user organization model visualization view module, as an enterprise organization model modeling view tool for providing visualization for developers, is usually represented in a tree structure in an enterprise organization model, provides a tree visualization structure in an organization model view for developers to edit, and provides XML and database formats for importing the model; the view provides the functions of adding, deleting and modifying the enterprise organization model, and after modification is completed, the view can be imported into a system database for a process engine to use when executing a workflow.

3. The Java workflow development system based on workflow visualization development tool according to claim 1, wherein the reusable component library view module provides organization of reusable components, so that developers can reuse existing components in different projects, and research and development cost is reduced; and the adding and loading functions of the components are also provided, and the components are added into the user component library view mainly in a component available state, so that the components are managed, and can be added, deleted and modified.

4. The Java workflow development system based on workflow visualization development tool according to claim 1 or 3, wherein the reusable component library view module is loaded from the user component library view to the workflow file editor when the components are needed by the project, the components can be directly used as one component by using the dragging function of the editor, and after the completion, the calling of the components provides the basic parameter configuration function.

5. The Java workflow development system based on workflow visualization development tool of claim 4 wherein the reusable component library view module uses EJB components already existing in the component library view in different projects, and since EJB components are published in the jboss server, the EJB components can be bound for use in different projects as long as they are available, thereby reducing development cost and fully utilizing the reusable components.

6. The Java workflow development system based on workflow visualization development tool according to claim 1, wherein the form visualization and binding module provides an integration function for a form designer, and integrates the form designer into the workflow development system, thereby facilitating development and design work of developers; and providing a visual binding function for the manual node and the form.

7. The Java workflow development system based on workflow visualization development tool according to claim 1, wherein the project one-key deployment module is used for developers to finally deploy projects, simplify deployment steps and provide interface navigation for visualization deployment.

8. A Java workflow development method based on a workflow visualization development tool is characterized by comprising the following steps:

A. guiding developers to configure information of a system database and a business database in navigation by using an operation visual graphic navigation tool module, and increasing a window of the business database of the system database for the input of the developers on the basis of newly building a dynamic web project; the operation visualization graphical navigation tool module is used for encapsulating a background engineering new building process, automatically operating package copying and configuring the work of files in a background, and simplifying a development process; summarizing a series of methods capable of simplifying engineering establishment in the process development process by using the operation visualization graphical navigation tool module, and realizing the methods;

B. modeling an enterprise organization model required to be used in workflow engineering through an enterprise user organization model visual view module; then establishing a corresponding user organization model in the workflow engineering development process, and performing model storage and import operation;

C. using a reusable component library view module to manage and classify the reusable components in the development process; providing a visual management function, supporting an EJB component, loading the component into a view of a process editor for directly using the component, and providing a function of visually setting parameters of the component;

D. in the system implementation, a form visualization developer is integrated through a form visualization and binding module, and the form development is also integrated into the whole system;

E. and after the whole project is developed, selecting the network address of the server to be deployed by using a project one-key deployment module, packaging and uploading the network address to the server for publishing.

9. The method for developing Java workflow based on workflow visualization development tool according to claim 8 wherein step B further comprises:

b1, step of importing and exporting tissue model:

b2, editing the tissue model;

b3, visualization of the manual node distribution.