Automation of workflow

The popularity of personal computers, the wide use of the Internet and E-mail make it possible to automate workflows. Computer software provides an efficient way for smart spreadsheets to replace paper forms; Databases provide storage space for vast amounts of data that used to be stored in file cabinets; The Internet gives birth to E-mail, which provides a fast and efficient way to transmit information. The inherent computing power of computers provides virtually endless control, management, and measurement of workflow processes.

Key components of workflow automation

Workflow automation is now a management buzzword. There are also many automation products on the market that claim to activate workflows. As long as their application supports basic E-mail functionality, vendors feel free to label “active workflow” on their products. However, the difference between these products and true workflow automation software is the same as the difference between a written version and Word. We believe that an application can only be considered a workflow automation solution if it has the following key characteristics:

Be able to draw flow charts, of course, graphical interface design is preferred;

Design a spreadsheet for each step;

Integrate external applications as part of workflow automation;

Links to spreadsheets and corporate databases;

Design the flow chart of conditional routing based on complex business rules, preferably without programming;

Pass information by rule based on function, user name, or superior/subordinate relationship;

Able to monitor workflow execution status;

Able to adjust workflow;

Ability to simulate and test workflow behavior;

Workflow applications must support multiple users and have high reliability.

Workflow applications must support intranets or the Internet and cross multiple platforms.

The workflow automation industry has a reputation for being good at handling complex business processes for several reasons

1. Regular workflow automation packages and their deployment are expensive. Often, a product is accompanied by a long consultation relationship. So buying and deploying software for very simple business processes is frowned upon. These software are typically used only for complex, critical, and high-control workflow applications where the benefits of workflow automation are significant. So both dealers and users are automatically focused on automating complex business problems.

2. For similar reasons, workflow researchers first focus on what complex business process problems are solved. In most cases, it is simply not economical to deploy automation software to solve simple workflow problems. Here’s a simple rule: you must crawl before you walk, you must walk before you run.

The last reason is “THE embarrassment of the IT industry”. General managers measure the job of IT department managers by their ability to solve complex problems. Naturally, IT managers will go to great lengths to solve complex problems, and their solutions are often complex and expensive.

All of this is changing, with the rapid growth of desktop applications and workflow solutions making it possible to solve everyday workflow problems. Less expensive and easier to deploy. In fact, organizations are increasingly aware of the importance of workflow and are willing to start with simple processes before deploying complex and critical process automation.

I also briefly introduce the workflow system of JNPF online office platform in my own words:

Support one-stop development, multi-end use, changes in demand only need to adjust the business service process or modify operations;

1. Workflow is the abstraction of the process in the work: it abstracts the process into two parts: link and route. The internal subdivision includes starting link, ending link and intermediate link. Routing contains the description of dynamic operation rules of business processes, such as dynamic route selection and static route selection, distribution, merge and so on. It abstracts the business operation process in the work into a process definition model, which contains a set of data structures, which is the definition data. It is generally drawn by a custom tool and stored as the required configuration data. The running time decides the current processing action according to the service data and configuration data, and selects the route to the corresponding next link according to the processing result, until the end link. Not much about subprocesses and process merges.

2. What is workflow for? It improves productivity, process flexibility, development speed, and BUG reduction; Because workflow is a further abstraction of the process, many kinds of business processes inside the factory are strange. If each of them has to be hard-coded if else to go through the process, it will consume a lot of human and material resources. Workflow only needs to run the first process smoothly, and the following process is almost drawing. Improved flexibility is reflected in the process can be updated at any time in a certain principle, and through the graphical interface, so that before going online, customers can confirm the process problems for many times before going online, without the need to modify the program; Development speed is mainly if a relatively perfect workflow, after the first program debugging through, almost no need to write code, or very little to write some very personalized code; Bugs are reduced because most of the code is shared, so you only have to change one place, and the whole system is locked in one or two places for bugs of the same type instead of having the same bugs everywhere, from beginning to end.

3, JNPF. WF workflow only need a computer or a mobile phone, anytime, anywhere viewing and approval progress, so even if you have more than one company only need a workflow system can monitor all the company’s business flow, schedule cost, financial income, job content, and so on a series of work, not only think not do;

4. Workflow is simply a concept, and the workflow engine is the one that realizes its value. Workflow does not fully adapt to every enterprise, but has some requirements for scalability, which determines the general way of data structure construction. The workflow definition tool is used to configure the definition of data.