Some Opinions on OA workflow design specifications, oa Workflow

Some Opinions on OA workflow design specifications, oa Workflow

It has been several years since the group applied OA workflows. It has been applied since the earliest simple and commonly used workflows for leave and now Engineering Project Contract workflows involving more than 10 departments, we step by step infiltrate the workflow application into many departments and work, which indeed improves a lot of efficiency, reduces the time cost of intermediate communication, and reduces the occurrence of problems such as competition.

When there are more workflow applications, there are also many management problems. How can we manage them more efficiently? Here I have summarized some experiences based on our daily work for your reference only.

 

1. Process Classification

All processes are classified by process nature or department. Now the system supports multi-level directory classification. Just like we manage files on a computer, it is much easier to find them by dividing them into folders. However, in the current version, the display of the level-2 directory is canceled when a workflow is created. This is a result of a regression. The level-2 workflow is directly displayed together, and it is very difficult to find it when there are many times, this is not as good as before the upgrade, and the displayed space is also occupied.

2. Form Classification

Same as above, you can classify forms and create multi-level directories.

3. Process and form naming

The process and form names must directly reflect the purpose of the process. Generally, they are directly associated with the form and use the original work name. If multiple subsidiaries are involved in independent design, you need to add the abbreviation of a subsidiary to the beginning of the process name. It is recommended that the form name correspond to the process name. For example, if the process is called "ABCD process", the form is called "ABCD form" and the process directory is saved to the form directory.

4. Form Design

Try not to use word to store the form in another way, because word will generate a lot of junk code. The name of the control is consistent with the description text, and you do not need to write a specific person. You will know this when you access the control on your mobile phone. This article will be written separately, these problems have been addressed in the last two days. Form design requires a lot of HTML knowledge. It is very helpful to learn more about this workflow design.

5. Document No. Specification

The document number is the name of the specific process generated. It is best to standardize it. Generally, you can add a suffix if it cannot be modified. The document number can be automatically generated using the process name and date format and expressions, for example, "{F}-[{SD}-{U}] ({Y}-{M}-{D} {H }:{ I })", for specific expression rules, see the workflow prompts.

The benefit of naming is that it will be easy to find later, and you can directly use the name for query.

6. Step name

Now we have specific steps to design the process. Each step should clarify who is handling the process and what action is taken. If a person has multiple steps in the process, it is also necessary to distinguish between direct differences. You can add serial numbers to distinguish them. Step name: here we will show who is going through the process, but we should not make the people here specific, that is, we should not write it as "Zhang San approval, because this step may not be approved by James tomorrow, but by Li Si, it will take a lot of effort to modify it every time. Here we can use the title name to write it, for example, if you write "Approval by the finance department manager", then there is no problem for Li Si to take over from him.

7. Permission range

Permissions are frequently adjusted. We recommend that you set a department if you can set a department. If you can set a role, you can set a role. Try not to specify a specific person, similar to the one mentioned at, in order to avoid personnel changes. After setting a department, you can set a default organizer. If the default owner changes, the transferee can manually select the department.

8. Default person

Setting the default person for the steps is a trivial matter, but such a trivial matter can reflect the meticulous work. For example, when the general manager approves his work and transfers it down, the organizer does not set it by default or the settings are unreasonable. He will feel that the process is wrong, that is, the work is not done well, all the small details must be well done and checked.

9. Conditions

When you need to set sub-conditions, try not to be too complex, because it is easy to confuse when there are many and or conditions. It is easier to create a workflow independently than to set this condition. In addition, if the condition is deleted, ITS sequence number is arranged from top to bottom, and the Set Condition expression is also changed.

When necessary, the receiving process shared by multiple conditions should be copied separately. Do not use them together. It is easier to add a step separately.

10. Graphic Process

It is recommended that workflows be visually displayed, which is very good and intuitive and convenient. It is better to organize the relevant steps in a logical order, rather than simply stacking them together. It is easier for few people to view the steps, but it is easier to manage them.

 

In addition, it is best to form a flow chart before each workflow. This can be done by the required department, and the process needs to be confirmed by the relevant department. If a major modification is involved in the process designed in OA, it is best to use the export function in Tongda OA to export the process and form for backup. We generally store these documents in the public file cabinet, if necessary, it is convenient.

WorkFlow Design for Tongda 2011 2011

For example, if there are three approvers, you can use the three controls to name them respectively: approver 1 (I am the department supervisor for approval ), approver 2 (I name it department manager for approval), approver 3 (general manager for approval ). All three controls are set to display the current user name.
Next, in the process design, fields can be divided in different operators. For example, when the process is submitted to the department supervisor for approval, you can enter "approver 1" in the field that can be written in this step. Other 2 and 3 are not included. When entering this step, you can only automatically enter approver 1, that is, the current user name is automatically displayed.
Similarly, when you enter the manager's approval, you can set the field to approver 2. In this way, the approver column in step 1 cannot be changed in step 2. in step 2, you can only enter the name of the second approver.
The third step is the same

How can I use a Tongda OA workflow?

1. You can select "Free Commission" for "set delegation" and "Commission by step". In "System Management", "workflow Settings", and "set process", there is a delegate type.
2. If you log on to the admin console and click workflow to create a new job, you can directly initiate the job.
3. After the process design is clicked, set the managers of the first step, for example, set the whole department, so that everyone can initiate the new process.