Almost no one company, anything one person, we need everyone together in consultation, coordination will finally take effect, we need to take a process, and this is the reason management software approval process required components.
Probably around the year 2002 in the company's portal EIP, which require an administrative approval process components, was used MySQL, PHP program functions with a database is required to achieve the leadership, leadership that functions to achieve what we put what function realize, was nothing profound feeling, anyway, did not spend long to do it, and feeling nothing, and is still relatively easy to use with it.
By 2008, the company has a hundreds of thousands of customized ERP project needs to be done, which requires a free approval process components, then we realized the worth of software components required approval process, and this component was responsible for me to write , probably before and also wrote a month or so, they tested a month or so, it really can, and even then not been able to achieve a parallel approval process function, on the one hand is the lack of experience, on the other hand is limited capacity.
This year is 2010, and have a B / S project requires a review process, and spent two weeks time to the approval process of the underlying database redesign bit, then spent one week whole test, and finally put this freedom approval process finishing once again, on a higher level, the technical problems failed to achieve last time, review time constraints, technical issues parallel review solved, with the progress of a deepening of the requirements for the daily management of the work links meaning approval on another deep awareness, and management software approval process is too necessary, the approval process is a core management software of the highlights.
In 2002, the approval process does not know how many important management component, do not know the economic value of the degree of attention which the customers.
In 2008, fully aware of the approval process management component how much effect, but also to spend quite a long time to make up their own stable and easy to use will encounter technical problems, bottlenecks in the design.
By 2010, the underlying data structures and redesign the look, the underlying code and a complete interface functions also carried out a thorough optimization of components with them smoother and more comfortable.
In fact, recycling is really PDM database design file, this is the business model, whether it is with this design JAVA development projects, or development of .NET projects, can be reused, there is some reference value, from design It can also be seen on a person's idea whether strict? Consider whether the design was adequate? Is there a certain amount of experience in the industry and so on, a lot of modeling business areas are valuable, this is one of the important aspects of the accumulation of software development can settle down labor.
Specific data table following effects [reviewed current workflow status table]
Specific data sheets effects are as follows [step workflow audit history record table]
Whether it is B / S system Ye Hao, C / S system or, some underlying components, so-called business logic components is a great reuse value, the code in the package a lot of business logic, business logic, no matter what these systems are captive, these details are required to implement it again, if the code written in more rigorous, there is a certain value reuse, the more these business logic code that accumulate, the more rigorous accumulation, the more perfect the future can make big money the more opportunity, and so on because the opportunity came, and soon you can get, because the preparation of these business logic often takes several months, one month's wages calculated at 10,000, in order to accumulate these proven components, at least all good burned thousands of dollars of costs, the use of the idea brought this spending thousands of dollars on saving.
Again from scratch to achieve the time it takes, to take over more often than read, and then change to change a lot more time, may be familiar with the code took one week, modify the code also spent one week, although the total cost of time is 2 weeks, but their own all written from scratch, it may take two months to write, and do not believe, they can see the writing, will always find a lot of details did not deal with, write to write to, the debugger to debug a month to go I do not know not sleep in the past.
Next, we enter the combat to program C / S as an example, may be required when the approval process example B / S, and the interface is substantially the same effect, because all of the same underlying function call processing data, data design will be the same, not because B / S, the design data is not the same, we assume that there is such a: free workflow approval process (assuming that leave the process): development director (Jiri Gala) - personnel director (Tu Zhigang) - General Manager (Hu condition Ming)
User accounts follows the results page
首先我们需要启动这个审批流程，让一个单据进入审批流程环节，这里只是做了一个示意图，就是可以显示的是请假单，也可以是请假单的核心参数（当然可以是其他单据，不只限于请假单，还可以是入库单、出库单、付款单、借货单等等一大堆单据）。
网友问？
这里的表名 订单代码 为什么要手动输入呢？ 有什么特别的好处吗？
Ψ吉日嘎拉:
这个是一个单据的 核心数据的意思，当然从数据库里读也可以的，这个是唯一识别一个单据用的
例如， 请假单，入库单等,都可以走审批流程的嘛,是我们的流程组件，需要知道 有这4个信息,才能进入审核流程里
网友问？
但是这几个让用户输入 有时候会让用户不知所措吧? 就是不知道输入什么?
Ψ吉日嘎拉:
你误会了，不是让用户输入,这个页面，应该是一个请假单页面（例如）程序只关心其中的4个参数,其他信息，就没显示了,可能这4个参数还是隐藏的
我们看看第一步审核流程的情况，先用吉日嘎拉账户登录系统，看看会是什么效果？
点待审批流程菜单，查看需要待审批的数据项
的确显示出了待审批数据了，我们把请假单递交给下一个审批环节
用下一个审批环节的用户进行登录
正好是我们需要审批的数据显示出来了，同时我们审批通过，可以选择最后又一步的审核环节。
这里是递交审批的效果图
我们再以最后一个审批环节的账户来登录系统
我们可以看到前面2步的审批详细情况，我们这步审核通过后，我们事先假设的3步自由审核流程也走完了。
自由审批流组件，有3个比较关键的功能。
1：当前需要审批的数据列表获取方法（可以按角色、按账户兼容的）
2：查看审批流程历史记录（都谁什么时候审批的？有啥批示？）
3：当起流程监控功能（都有哪些数据在待审核状态？）
核心功能由2个组件组成
1：进入审批流程组件。
2：审批流程组件。
Freedom of assembly approval process Although strictly speaking, can not be equated workflow components, or even a formal review process components, but still quite realistic job requirements, because there is no well defined strict pre-defined process steps, etc., but also What role do not have a strict definition of the various approval processes and so on, as long as there is the most basic user data, configuration roles can run up, relatively speaking is the minimum configuration requirements, the most flexible approval process, and more suitable the review process of the domestic small and medium enterprises, in particular small companies review process, absolutely.
In fact, daily life, most of our approval process, are their own boss audit, nor Dayong tube is what the audit, most of them forwarded to your boss about the audit, 90% will not be wrong. At most, leading forwarded to someone else review it, or scolded about the next, ha ha.
Writing articles tired, but still more than from 20:00 until about 12:30 until the end, you have to get to sleep or else tomorrow's work will be affected, and we welcome the exchange of many criticisms, hope u guys more exchanges, improve together.
Reproduced in: https: //my.oschina.net/iwenr/blog/227916