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

When designing a workflow system, we often encounter the following situation:

The same form needs to be processed in multiple steps of the process, and the processing status of each link is inconsistent. Some nodes can be written and some nodes can be read.

For example, the same reimbursement form: when an employee fills out a reimbursement form, only the subject information and details of the reimbursement form can be filled in. Other information is invisible;
The manager can only enter the review results and comments for approval. Only the owner and details of the reimbursement form can be viewed;
During financial approval, the details of the report subject and the manager's audit information can only be viewed, and only information about whether to set the collection fee can be set.

In this way, the same form is transferred in three steps of the process, and each step has different permissions to control the form information.

Processing Process:

1. When designing an electronic form, set a form that contains all the information of the report. Set permissions for related roles.

Employee: You have the permission to enter the subject and detailed information of the reimbursement form;
Manager-you have the write permission for audit results and comments, the read-only permission for the report owner and detailed information, and the financial expense information is invisible;
Financial Personnel-have the write permission to receive the fee information, and all other information is read-only;

2. Define the flow of the design process
set the steps of the process and the actions of the process, and connect the electronic form;
set the process action permissions at the same time.
Fill in the action for an employee-only the employee role can be executed.
the manager approves the action-only the manager role can be executed;
financial approval action-only available to financial personnel;
3. Start the process and run the form.
when the process instance is running and the report is filled in, only employee roles can perform the filling action, open the form, and read the form's permission control. Only the subject and details of the reimbursement form can be filled in. Other invisible;
process instances are transferred to the manager's approval stage: the manager role can perform approval actions, open the form, read the form's permission control, and only the approval results and review comments can be written, other information is read-only.
the information is transferred to the financial audit stage. financial personnel can perform the audit action, open the form, and read the form's permission control. Only whether the fee information is collected can be edited, and other information is read-only;
This method combines the form permission control with the process permission control to achieve the transfer of the same form in multiple stages of the process.

Problem:

If an employee needs to view the review result at any time, the employee can only view the review result. The employee can no longer modify any information about the review form and still access the same form.

The above method cannot achieve this result.

Tip solution 1:

Employees can view the review results at any time. This should not be designed as a process, not a process. This design is wrong. A query module should be designed to enter query conditions to query the reimbursement form. Both the process instance and the historical process instance can be queried, so that you can access the service at any time.

 Tip solution 2:

If the business requires a form that can be written by the same user in the first step, and the document is transferred to the next step, that is, the same user can only read the document. The following method is used to handle this problem:
1. When designing an electronic form, set the read and write permissions of the Form Control, and select the link action of the process, set the read, write, and invisible features of the control at each stage of the process. After the settings are complete, save the settings in the form;
2. When designing a process, set the process action permission and mount the form;
3. When the process instance is running, execute the action, load the electronic form, and load the control permission configuration information during form initialization. Verify the control permissions and initialize the control attributes. Achieve read-only, writable, invisible, and other features;

 

 

The production process will be attached later;

 

 

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
Four integrated workflows and 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
Seven latest DTD format verification and modification in Web Workflow Management System Development
8. Open-source osworkflow Task Management in Web Workflow Management System Development