13 process integration with electronic forms in Web Workflow Management System Development

ArticleDirectory

• Generally, workflow management systems are divided into process engines, electronic forms systems (Custom forms), process designers, process management and monitoring platforms, and other main modules. The process engine and the electronic form system should be weakly coupled, and each of them can complete functions independently.

Generally, workflow management systems are divided into process engines, electronic forms systems (Custom forms), process designers, process management and monitoring platforms, and other main modules. The process engine and the electronic form system should be weakly coupled, and each of them can complete functions independently.

 

At the same time, both the process engine and the electronic form have designed interface events to facilitate mutual integration or integration with other systems.

 

 

I. Process Engine event interfaces:

 

When defining the process,Step node, Action node, action resultAll nodes are configured with pre-and post-event functions;

When the process flows to these nodes, the node's pre-event function is triggered;

When a node is left, a post-event is triggered;

 

Note: However, the process engine-driven electronic forms are not implemented using event interfaces: The Action node of the process engine has a view attribute and the URL of the form is mounted, when the process runs to this action node, read the view attribute URL, open and run this form. This form can be a form defined by the eform custom tool or a JSP page developed by the user.

 

 

Node pre-post event functions:

 

All the pre-and post-functions implement a unified interface functionprovider.

Functionprovider. Java interface, only one method is execute. All classes that implement this interface need to implement this method.

 

Public void execute (MAP transientvars, map ARGs, propertyset PS) throws workflowexception;

 

Map transientvars: process context information can be obtained from this map;

Map ARGs: parameters for node definition can be obtained from this map;

Propertyset PS: the persistent variables in the process instance are obtained from this.

 

 

Condition node judgment function interface:

Conditions can be defined in the action results of the flow engine. The flow engine defines some built-in condition judgments. You can also extend some custom condition judgment functions by implementing the condition. Java interface.

 

Condition. There is only one method in the Java interface. All the conditional functions that implement this interface must implement this method:

 

Public Boolean passescondition (MAP transientvars, map ARGs, propertyset PS) throws workflowexception;

 

Map transientvars: process context information can be obtained from this map;

Map ARGs: parameters for node definition can be obtained from this map;

Propertyset PS: the persistent variables in the process instance are obtained from this.

 

When defining a condition node, this condition judgment function is introduced. when the process is running, the engine executes the passescondition () function in the custom function to return true and false results.

 

 

 

Ii. Electronic Form event interface:

Event interfaces for all electronic forms:

 

Classes registered for all events:

 
This class registers the pre-post event class and uses reflection to instantiate the pre-post event class.

 

For example, before and after saving an electronic form, register it in this class, cn.com. fcsoft. eworkflow. workflowdoaction. java is an event that is executed after the electronic form is saved. This class is responsible for continuing the process after the electronic form is saved.

 

All the pre-and post-event functions in the electronic form implement the eventprovider interface, and the defined classes are registered in the eventresolver class. The reflection mechanism is used to obtain the class instance where it needs to be triggered, execute the execute () method to execute the Custom Event function.

 

 

 

 

 

Related links;

Workflow concept in Web Workflow Management System Development

Web workflow management system development 2 workflow engine

Web workflow management system development 3 visualization process designer

Custom forms for Web Workflow Management System Development

Development of Web workflow management system 5 open source osworkflow-user system transformation

Six-form permission and process permission Control for Web Workflow Management System Development

8. Open-source osworkflow Task Management in Web Workflow Management System Development

 

Ten database connections and transaction settings for Web Workflow Management System Development

Interaction between process data and business data during Web Workflow Management System Development

Twelve permission controls for transferring a single form to multiple nodes in a process developed by the Web workflow management system

13 process integration with electronic forms in Web Workflow Management System Development

14 Implementation of the Process designer attribute page in Web Workflow Management System Development