Refer to the enterprise WeChat approval service to implement business approval in the workflow module in the Winform development framework.

According to the enterprise approval business, in the Winform development framework, the workflow module implements business approval and the winform Workflow

The current enterprise number has been switched to the enterprise. This is an APP that provides a wide range of enterprise applications, including business approval, the approval business involves multiple approval scenarios, such as leave, reimbursement, expense, and travel. In the Winform development framework, the workflow module can also be well implemented. This article describes how to refer to the enterprise approval business, combined with the workflow module in the framework, various forms can be approved.

1. Enterprise Approval

Before introducing the workflow module in the framework, let's take a look at the approval business in the enterprise, as shown in the following interface. These approval forms include: leave, reimbursement, expense, business trip, purchase, overtime, out-of-office, vehicle use, seal, contract approval, item collection, payment, item repair, meeting room reservation, and other common process services.

Let's open a business and look at the business form information.

This includes some information about the leave service, including content input and attachment management, so that you can submit and copy the information to the corresponding personnel.

After submission, you can view and process the data in the business form. The following is the business form Viewing Interface.

 

2. Business Approval of the workflow module in the development framework

First, we need to fill in the relevant information based on the data of the business form, so that we can display the new form in the dynamic display list of the business, as shown in the following interface.

As for the development of each business form, I will introduce the business form development of the workflow module in the Winform development framework in detail. Each process business form mainly involves processing several forms, one is to add and edit a business application form, the other is to view the business application and display the Application Form user control, as well as a interface required for regular business query. Some forms have been encapsulated as base classes, the code of the subclass form is simplified, as shown in the following figure.

For example, for the leave application form, our interface effect is as follows.

It mainly inherits FrmAddApply and implements data verification of the business application form, sending the form flow, and displaying the data (displayed when re-editing. The interface code is relatively simple.

For the display interface for viewing specific business forms, inherit the FrmViewApply class base class for viewing the application form, then this subclass only needs to be responsible for displaying data.

The data display part consists of fixed and common application form information and business form information. The attachment processing part uses the buttons of the general attachment management module, as shown below.

These are displayed on user controls. The effects of user controls in the design status are as follows.

The preceding Application Form for leave is a single table. Sometimes, our application form is a master-slave table. For example, we need to summarize the total reimbursement information, including the total amount, then, submit the detailed records. The following figure shows the effect of the form interface.

This type of detail form can be added and edited directly on the table control Griview.

View the detailed form interface as follows.

This type of business application form is only a single table, which is relatively complicated. It needs to process the data input, storage, and display of the data in the GridView, but it is also a standard process, we also inherit the same base class and implement different business processing codes in the subclass.

In order to reduce the development workflow, we can use the code generation tool to generate the interfaces of these business forms in one click and directly use them. This saves a lot of trouble.

 

3. code generation on the workflow business interface

We can see from the above that the form interface of the workflow business form can be implemented with standard processing, inherited from a base class, and then integrated with relevant data processing rules.

After business information is extracted, you can use the code generation tool to quickly generate the data, which greatly improves the development efficiency.

For the above ideas, we spent several days creating automatic generation rules and repeated verification on the workflow interface, and finally integrating them into the code generation tool for convenient development.

For the master-slave table interface, you can still use the code generation tool to quickly generate the workflow interface.

 

For how to use this function, I will introduce the process in detail later.

Workflow series of WInform development framework:

Simple WorkFlow Design Based on Winform development framework

Table Design and Analysis of the workflow module in the Winform development framework

Business form development of the workflow module in the Winform development framework

Approval and signing of the workflow module in the Winform development framework

Workflow module approval and signing in Winform development framework (2)

Implement business approval for the workflow module in the Winform development framework with reference to the enterprise approval business