In fact, as early as close to 10 years ago in the company's ERP system and approval process components, then vb code is written only by personnel turnover, and later always wanted to achieve a set of .NET components of the administrative approval process, has been no energy to write, usually there are a lot of things to do at work, it has become the center section. 51 holiday just very sensitive to small hands to do. Well two days ago on the half-done work to continue to improve the details.
Some software components are sometimes face the problem, you can achieve some of the difficult components, others will think you are a strong ability to not look down on you. This is also a proof of the strength of their own ideas rigorous performance, a few years after the familiar No. features many software can ahead of time, you can get when there is a need in the shortest possible time, so that customers with admiration of your colleagues.
Good use approval process is also a component of the strength of the company's information reflects, reflect management capabilities, not just the software components so simple. Choose a suitable, and simple and easy to use, real component selection also reflects the positioning capability.
Approval process components can in front of customers, in front of colleagues, peers when in front of a thing to say, but also enhance the competitiveness of their own software development projects, will increase a lot when bidding to win chips and so on, others more difficult to imitate you.
1: in fact, try to find someone to outsource this component approval process, the end result is a failure, a failure for several reasons: Firstly, he did a good design, there is no clear requirements document. Second: the development of people positioning approval process is not clear, functional realization is not clear. Third: all his spare time to complete the work, with not many funds. Fourth: No actual work urgently required, not project-driven. Fifth: approval process requires a very demanding, very regulated companies can use to get up, ordinary difficult for companies to implement the approval process components. Fifth: we are not understanding the depth of the approval process components. Sixth: This approval process components being perfect than a few people for a short time to develop a good, it requires very specialized knowledge, professional team, and constantly refined and improved to a mature product.
2: Although the work is not an urgent need for the approval process components, but for the next 5 - 10 years to make a foundation, the future will definitely have big projects in the components used in the approval process, although previously the implementation of several major components of the company's approval process , but supporting function is not so complete as this one, to each feature sophisticated test again. Here we introduce the core functionality of our approval process components:
Pending Documents: The current operator needs the documents reviewed.
Approval Process Monitor: to the administrator with a view of the status of various processes.
Approval process definition management: defining various processes to the backend administrator approval procedures used.
Holiday List: You can set the company's statutory holidays and rest days, control the number of days with the approval flow, improve efficiency, facilitate personnel urged to use.
Here is the database structure:
1: Separation user rights database design and approval process library, unrelated, independent upgrade, positioning clear division of labor; better integration with other systems. Strong independence, relevance, if relatively few.
2: a small table process components, simple structure, targeting approval process components is suggested, easy to use, although they can not meet the limited function 100% approval Liu Chen, 80% of the approval process to meet the requirements on it, not perfectionist but requires easy to use functionality and stability.
3: Call simple, simple debugging, integration is simple, easy to understand, easy to use, this is the positioning of our common rights management system approval process components.
Effects reference holiday setting function
Some approval process can be classified management, can be classified according to their needs.
Here is the definition part of the approval process for a variety of administrative examination and approval process, the program calls mainly by "number" unique to call flow, the approval process can also be written back to the state of the main table, you can also personalize the definition of flow processing class, carried out according to their own specific requirements of some flow processing logic, but by default, no need to modify the settings, according to the default value of the system can be, just stay out of this room is personalized for professional developers.
Here the number of processes to use the name of the form, which can be reflected by double-clicking on it, calling out the influence of form in pending interface.
审批流程的步骤定义部分，主要是确定每个审核的节点的审核人员，这里可以支持多种审核方式，可以按人员进行审核、部门审核、角色（岗位）来审核，每个不住可以设置流转承诺期限，方便监督管理智能部门进行查询。
自己的程序里需要调用审批流程组件，基本上一行代码，设计几个参数就可以按预先设定的流程进行流转了，这就是审批流程组件最牛的部分，调用就这么简单，然后自动进入流转状态了，其中有点儿技术含量的部分是：
01：系统有自动的提示信息，会提醒需要审核的人。
02：可以有邮件提醒、手机短信提醒接口。
03：退回的单据也会有相应的提醒，会提醒前面所有参与审批的人，审批完成的人。
04：流转完成的、进入下一个缓解的也会有相应的提醒功能，当然流转完毕的也会有提醒。
05：当然可以实现，流程节点多个人的会签功能，任何一个人审核功能、按部门审核、按角色审核、按岗位审核功能。
06：也可以支持流程结束条件表达式，例如 小于2天的，部门主管审核就可以了。
07：不只是支持C\S，程序同时能支持B\S的接口，B\S的相应效果。
08：系统比较严谨，整个审批流程过程支持数据库事务，不会有异常流程出现，不会有死流程等等。
09：调用简单、接口完善、定位明确、程序代码简洁思路清晰，易于维护完善。
10：专门针对大数据进行了优化工作，可以支撑千万级别的数据、也有很强的并发新能细节优化。
11：流程审核步骤有变更时已经在流转中的流程不受影响，不会有宕机流程等等。
12：支持多数据库，主流数据库都支持。
13：程序都面向对象，面向接口，面向服务soa的理念编写，经得起长期维护完善。
待审批单据页面的C\S效果图。
C\S自己带的消息提醒功能参考如下图，双击列表就可以进入相应的web页面，或者单出流程绑定的相应的单据窗体了，非常万能，简单好用。
审批组件都做了用户控件化优化，调用简单，在自己的业务窗体里拖一个，就实现了一个业务模块的审批流程化，绝对又快又好提升软件的档次，特别是流程化规范化的档次。
当然以上知识一些标准例子，可以将系统集成到自己的OA里，自己的业务系统里，当然可以美化界面、美化消息提醒功能，美化B\S的展示效果等等，我们提供的是后台组件源码及相关的集成服务，当然客户有相应的项目、有相应的预算，我们也可以制作出满足客户要求的漂亮界面。
组件都开发好了，相应的改进优化就简单很多了。定位明确了才能把握好方向，不求最强、只求最简单好用，做个让大家可以放心用的组件、提高软件开发效率，走专业化的道路，组组件提供商的道路。
我们销售的是组件 + 售后服务。很多时候想想简单、但是靠自己开发好、测试好、性能改进、功能稳定、不断重构、不断完善细节，可能会耗费4-5个月时间，或者更长时间，而且需求一有变动就经不起折腾，很可能需要推倒从来，其实购买软件组件是最省心省事、提高工作效率的方法。耗费几个月时间、又有心里压力、又加班加点、也没多大好处，能买的直接买过来是最省事的。没必要把自己的身体都累跨了，然后年纪大了一身病，其实也没什么好处。该买的买，该卖的卖，人活着就是我为你服务，你为我服务的事情。
可能大家30-40岁后，大多人都理解我了，能买到的事情，都是容易的事情，很多时候很多技术并不是花钱就能买来的。多年想完善的审批流程组件终于开发完善好了，心理的一个石头落下来了，权限实现好了，流程审批组件也实现好了，可以放心睡觉了，接着有空时按客户反馈的意见要求改进改进就可以了。
用瑞士军刀的思想制作出来的通用权限管理系统组件、终于完成了最初的功能范围部分，持续10年的梦想实现了，接着就是如何销售推广应用的问题了。我们追求的目标就是当我们需要什么功能就可以马上实现好，而不是还要等待漫长的开发过程、成熟过程。
转载于:https://my.oschina.net/iwenr/blog/227828