Flowman Design Example 1: Leave application process

Generally, enterprises have daily business processes, such as leave and reimbursement. Most enterprises have used or plan to use electronic processes, instead of using paper processes. This will accelerate interaction between different departments, reduce the time required for the signing process, and save manpower.

So how can we quickly deploy it? Here we use sharepoint2010 and flowman2010 to implement a simple leave process.

 

1.Form definition

First, we need a form.

Name	Type	Description
Document No.	Single Line Text	Unique identification of a document
Application date	Time
Applicant	Personnel or group
Leave Start Time	Time
Leave End Time	Time
Leave days	Number
Leave reason	Multi-Line Text
Document Status	Single Line Text	Draft, submitted, approved, rejected, completed

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Leave application configuration table

 

Name	Type	Description
Title	Single Line Text	The value is "configuration"
Days	Number	Minimum days for leave that require approval by the department manager

2. Process Definition

A form also requires a process. Let's look at what the requirement is.

This is a relatively simple leave process with Level 2 Approval.

First, the applicant's line manager must approve the request. If the line manager rejects the request, the process ends.

If the line manager approves the application, check the number of days for leave. If the number of days for leave is greater than or equal to a certain number of days, the department manager is required to approve the request.

If the department manager rejects the approval, the process ends.

If the department manager approves the application, it must be reviewed by HR.

Review by HR and complete the process.

Note: The number of days is configured in the configuration table.

 

 

Now that the requirements are clear, let's design the form and process.

 

3. Form Design

Open the SharePoint site and create a new list [application for leave]

 

 

Click "list Settings" in the newly generated list to add new columns.

 

 

According to the form design, we need to add the [document number], [leave start time], [leave end time] and other columns.

 

 

Now that the form has been generated successfully, we will do some code-level beautification enhancement to see the new results.

 

 

4. Process Design

With the form, of course, the next step is the process design. Here we use the flowman workflow designer to implement the process.

 

Go to the leave application list and click [LIST]-[settings]-[workflow design] on the menu bar To Go To The flowman Design Screen.

 

 

Start Design

To make the process easier to identify, we need to change the process name and click [settings]-[workflow settings] on the menu bar.

 

 

 

You can select multiple startup modes in [workflow startup option settings ].

 

 

Generally, you want to start the workflow after adding an application. Therefore, select [automatically start the workflow after creating a project].

 

 

To keep the applicant informed of the application's document status, you must control the document status value during the process, the first node we add is [set field value] in [SharePoint operation], and set [Document Status] to [submitted].

 

 

 

Click the icon on the node to open the configuration screen. Select a field on the left and enter or select a value on the right.

 

 

 

As needed, the first approver is a line manager, so we select the role-line manager in the approver.

 

 

 

The approval node has two branches: consent and rejection. When you perform different approval operations, the corresponding branch is executed. We put [set field values] On the rejected branch, and assigned [Approval denied] to [Document Status], plus the [send notification] node in [Human-Computer Interaction, to inform the applicant that his application has been rejected.

 

 

Open the notification sending configuration screen and select the recipient. You can also select the desired person using the staff selector. This time, we select the [initiator] in the role as the initiator. Enter in topic: Your application is rejected. In this way, when the line manager rejects the application, it will send an email to the initiator.

 

 

On the branch approved for approval, you can put [set field values] and assign [approval and approval] to [Document Status].

 

 

After the approval by the line manager is completed, if you need to wait for a certain number of days for the leave to be approved by the department manager, we have a list: apply for leave configuration table, used to configure the number of days for approval by the department manager.

 

 

Next we drag and drop a node in the process logic class [condition settings]. To achieve this, the department manager must approve the node only when the number of days for leave exceeds the configured number of days, therefore, the [department manager approval] node should be placed on the [condition setting] Yes branch.

 

 

In [condition settings], select [if the current project domain], select the field [days], then, use the value selector to select the number of days of the field in the list [leave application configuration table] marked with the configuration item. The comparison character is greater than or equal.

In this way, compare the number of days for asking for leave with the number of days set in the configuration table.

 

 

On the [department manager approval] node, select the approver as the role department manager in the organizational structure.

Finally, put the [set field value] node on the two branches for approval to assign a value to the document status.

After all the approvals are completed, you need to add a HR review. Next we drag and drop a node of the Human Computer Interaction Class to [require review], select the role HR as the reviewer, and change the node name: HR review.

 

 

 

In this way, you can complete the design of a leave application process, the content or title of the notification, and the name of the node by dragging the configuration. If you need to control the permissions of the current project in the process, you can also add [set record permissions] on the appropriate flowchart to assign access permissions to different users. Finally, let's release this process. This process is only available after it is released.

 

 

 

 

 

5. Run

Now let's simulate the operation of this process.

Create application:

 

 

After clicking submit, there is an ongoing leave application in the list

 

After you log on to the site, you can approve the application.

 

 

The above is a quick leave application process with SharePoint 2010 and flowman 2010.